Bug 469837

Summary:	Lockscreen failure on Manjaro KDE
Product:	[Unmaintained] kscreenlocker	Reporter:	lapak1
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED DOWNSTREAM
Severity:	critical	CC:	nate
Priority:	VHI
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Manjaro
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description lapak1 2023-05-16 07:23:34 UTC

Unfortunately, since the last update (Manjaro), I have this unpleasant message every time the PC goes into standby. But you can log in via it.
Does anyone know what the problem is?
I would like to log in normally again.
I already tried to change the Kernel Version, but it didn't function.

Text (translation from german):
The screen lock has malfunctioned and the session cannot be unlocked. To unlock, switch to a console (e.g. Ctrl+Alt+F2), log in with your credentials and run the command: loginctl unlock-session 2. Then log out of the virtual session with Ctrl+D and switch back to the current session with Ctrl+Alt+F1.

Thank you very much!

I originally posted this on the Manjaro Forum, but they recommend asking KDE.
Link to Manjaro Forum:
https://forum.manjaro.org/t/die-bildschirmsperre-ist-gestort-loginctl-unlock-session-2/140579

German
Leider habe ich seit dem letzten Update diese unangenehme Meldung, jedes mal wenn der PC in Standby geht. Man kann sich darüber aber anmelden.
Kennt jemand das Problem und weiß woran es liegt?
Ich würde mich gern wieder normal einloggen.

Text:
Die Bildschirmsperre ist gestört und die Sitzung kann nicht wieder freigegeben werden. Zum Freigeben, wechseln Sie auf eine Konsole (z.B. Strg+Alt+F2), melden Sie sich mich Ihren Zugangsdaten an und führen Sie den Befehl: loginctl unlock-session 2 aus. Melden Sie sich danach mit Strg+D aus der virtuellen Sitzung ab und wechseln Sie mit Strg+Alt+F1 wieder zur laufenden Sitzung.

Vielen Dank!

Link to Manjaro Forum:
https://forum.manjaro.org/t/die-bildschirmsperre-ist-gestort-loginctl-unlock-session-2/140579

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

STEPS TO REPRODUCE
1. Change to Standby

OBSERVED RESULT
Just follow the instructions.

EXPECTED RESULT
Login but with more effort. :/

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9
Kernel Version: 6.3.0-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 16 × 12th Gen Intel® Core™ i5-1240P
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: Acer
Product Name: Swift SFX14-51G
System Version: V1.09

Comment 1 Nate Graham 2023-05-16 19:03:57 UTC

Is it broken of you run the screen locker in testing mode in a terminal window with `QT_LOGGING_RULES='kscreenlocker_greet=true' /usr/libexec/kscreenlocker_greet --testing --theme ~/kde/src/plasma-workspace/lookandfeel`?

Comment 2 lapak1 2023-05-21 18:02:47 UTC

(In reply to Nate Graham from comment #1)
> Is it broken of you run the screen locker in testing mode in a terminal
> window with `QT_LOGGING_RULES='kscreenlocker_greet=true'
> /usr/libexec/kscreenlocker_greet --testing --theme
> ~/kde/src/plasma-workspace/lookandfeel`?

When i write 

QT_LOGGING_RULES='kscreenlocker_greet=true' /usr/lib/kscreenlocker_greet --testing --theme ~/kde/src/plasma-workspace/lookandfeel

in the console
i get this answer

kscreenlocker_greet: Greeter is starting up.
kscreenlocker_greet: [PAM] Starting...
kf.kirigami: Failed to find a Kirigami platform plugin
Cannot mix incompatible Qt library (5.15.8) with this library (5.15.9)
zsh: IOT instruction (core dumped)  QT_LOGGING_RULES='kscreenlocker_greet=true' /usr/lib/kscreenlocker_greet   

So it looks like my qt library is to new?

Comment 3 Nate Graham 2023-05-21 22:28:10 UTC

Yep. If you didn't compile anything yourself, this is a distro build issue. They probably forgot to recompile everything after upgrading Qt. I would strongly recommend that you report this to them.