Dear Maintainer,

When locking the screen (manually or automatically), it's not possible to
unlock it. It's not accepting password.

According to this bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756552
from a previous version, there is a problem with running kcheckpass.

I confirm that changing permissions with
"chmod 4755 /usr/lib/x86_64-linux-gnu/libexec/kcheckpass"
solved the issue.

Dear Maintainer,

I discovered, that in the bookworm repo in the package libscreenlocker5, the mentioned file "kcheckpass" is not existent. Thus the above workaround does not work.

I also tried to manually copy the file from bullseye with no success and suppose, kcheckpass from bullseye is incompatible with bookworm. Please repack the lib with the missing file.

Thank you very much.

Best regards

Hans

Hi Hans,

On Fri, 11 Aug 2023 23:35:23 +0200 "Hans-J. Ullrich"   <hans.ullrich@loop.de> wrote:
[...]

The "kcheckpass"-binary was removed from kscreenlocker over a year ago,
because it was obsolete.
Hence, distributions cannot ship the binary as it is not built anymore.

If you cannot unlock your screen, a simple "It doesn't work" is
unfortunately not sufficient to debug it. The first thing you can do is to
create a new user on your system and try to unlock the screen with that
user.
That will tell you whether something is wrong with the system or just
with your default user.

Dear Maintainer,

tried with a fresh user, but no success. Verified and confirm, that "loginctl unlock-session XX" as normal user is unlockung the session. So it looks like this command might not be sent correctly from KDE.

Tested on two computers, both running debian bookworm, actual packages, same package status.

Both computers got this issue. NOT tested on my 32-bit system yet.

I will tell more, if I got news.

Thanks for any help.

Best regards

Hans

Hello Patrick,

in the meantime I checked with my 32-Bit System (it is an EEEPC), and on this system unlocking of the
screenlocker is working perfectly. As all my systems (2 x 64-bit and 1 x 32-bit) are running the same
versions of package and are all completely updated, I could compare all settings of the related files
on all machines. However, i could discover no difference among the installations, except the working one
is compiled for 32-bit.

Sadly I could tell no other news, but I can fully confirm, that 64-bit is not working. On both 64-bit I
tried with a fresh user and on both I got no success.

I hope, this might help though, although it is not much usefull information in this report.

Best regards

Hans

Hi Hans,

On Tue, 15 Aug 2023 16:53:52 +0200 "Hans-J. Ullrich"  <hans.ullrich@loop.de> wrote:
[...]

Unless you can find some error message in e.g. your syslog, there isn't
really much a maintainer can do.

The best thing would probably be to report the bug upstream at
https://bugs.kde.org/ if that hasn't been done yet. They know much
better how to debug this error. I'm sorry that I cannot do more than
that.