Bug#973677: marked as done (libkscreenlocker5: No login dialog is shown, user cannot unlock session)
Your message dated Mon, 4 Jan 2021 21:24:59 +0900
with message-id <X/MJG2wIKK2GFpJR@burischnitzel.preining.info>
and subject line Re: Bug#973677: libkscreenlocker5: No login dialog is shown, user cannot unlock session
has caused the Debian Bug report #973677,
regarding libkscreenlocker5: No login dialog is shown, user cannot unlock session
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
973677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973677
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: libkscreenlocker5: No login dialog is shown, user cannot unlock session
- From: Mikko Korhonen <mjkorhon@gmail.com>
- Date: Tue, 03 Nov 2020 09:32:56 +0200
- Message-id: <160438877620.41166.4988950914922123690.reportbug@taavi>
Package: libkscreenlocker5
Version: 5.17.5-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: mjkorhon@gmail.com
This is same as
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852162
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904074
but happens every time and at any unlock, not just on dehibernation and with a
single monitor: only the cursor is shown on a black screen and there is no way to login.
As a workaround killing the process helps as the new instance shows the login screen.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.8.0-3-amd64 (SMP w/24 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libkscreenlocker5 depends on:
ii kpackagetool5 5.74.0-2
ii libc6 2.31-4
ii libkf5configcore5 5.74.0-2
ii libkf5configgui5 5.74.0-2
ii libkf5coreaddons5 5.74.0-2
ii libkf5crash5 5.74.0-2
ii libkf5declarative5 5.74.0-2
ii libkf5globalaccel-bin 5.74.0-2
ii libkf5globalaccel5 5.74.0-2
ii libkf5i18n5 5.74.0-3
ii libkf5idletime5 5.74.0-2
ii libkf5notifications5 5.74.0-2
ii libkf5package5 5.74.0-2
ii libkf5quickaddons5 5.74.0-2
ii libkf5waylandclient5 4:5.74.0-2
ii libkf5waylandserver5 4:5.74.0-2
ii libkf5windowsystem5 5.74.0-2
ii libpam0g 1.3.1-5
ii libqt5core5a 5.14.2+dfsg-6
ii libqt5dbus5 5.14.2+dfsg-6
ii libqt5gui5 5.14.2+dfsg-6
ii libqt5network5 5.14.2+dfsg-6
ii libqt5qml5 5.14.2+dfsg-3
ii libqt5quick5 5.14.2+dfsg-3
ii libqt5widgets5 5.14.2+dfsg-6
ii libqt5x11extras5 5.14.2-2
ii libseccomp2 2.4.4-1+b1
ii libstdc++6 10.2.0-15
ii libwayland-client0 1.18.0-2~exp1.1
ii libwayland-server0 1.18.0-2~exp1.1
ii libx11-6 2:1.6.12-1
ii libxcb-keysyms1 0.4.0-1+b2
ii libxcb1 1.14-2
ii libxi6 2:1.7.10-1
ii psmisc 23.3-1
Versions of packages libkscreenlocker5 recommends:
ii kde-config-screenlocker 5.17.5-2
libkscreenlocker5 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Mikko,
> Thank you, with 5.20.4 the issue seems to be gone.
Thanks for the confirmation, much appreciated. So I am closing this bug.
In case you see something similar, either reopen or submit a new one.
Thanks
Norbert
--
PREINING Norbert https://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
--- End Message ---
Reply to: