Bug 451322 - screen locker does not work anymore after upgrading to 5.24.3
Summary: screen locker does not work anymore after upgrading to 5.24.3
Status: RESOLVED DUPLICATE of bug 451315
Alias: None
Product: kscreenlocker
Classification: Plasma
Component: general (show other bugs)
Version: 5.24.3
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-03-09 16:28 UTC by Franco Pellegrini
Modified: 2022-03-10 16:14 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
error reported by kde (542.32 KB, image/jpeg)
2022-03-10 10:22 UTC, Franco Pellegrini
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Franco Pellegrini 2022-03-09 16:28:56 UTC
SUMMARY
I get a message that state that I need to use loginctl unlock-session 5 to restore my locked session, in a black screen.

STEPS TO REPRODUCE
1. set screen lock to 5 minutes
2. wait until lock
3. try to login again

OBSERVED RESULT
a black screen with instructions to unlock the session using commands

EXPECTED RESULT
unlock my session using the gui login manager

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.24
KDE Plasma Version: 5.24.3
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.3
Kernel Version: 5.13.0-35-generic (64-bit)
Graphics Platform: X11
Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz
Memory: 22.9 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 630
Comment 1 David Edmundson 2022-03-09 17:34:58 UTC
Crashes need a backtrace to be actionable.

You may find it easier to run kscreenlocker_greet --testing manually
Comment 2 Gabriel 2022-03-09 21:50:48 UTC
This appears to be the same problem as mentioned in bug 451315. I'd mark this as a duplicate, but since it was reported first I'm not sure if that is the right way to go about it. Either way, there is more information to be found in the other reports on the same bug. :^)
Comment 3 Franco Pellegrini 2022-03-10 10:22:59 UTC
Created attachment 147418 [details]
error reported by kde

This is the error reported when I woke up my pc after session lock down
Comment 4 Franco Pellegrini 2022-03-10 10:24:26 UTC
(In reply to David Edmundson from comment #1)
> Crashes need a backtrace to be actionable.
> 
> You may find it easier to run kscreenlocker_greet --testing manually

Can you list the commands to log this error? I tried that command without success
Comment 5 David Edmundson 2022-03-10 10:50:21 UTC
/usr/lib/libexec/kscreenlocker_greet --testing
Comment 6 Franco Pellegrini 2022-03-10 11:11:27 UTC
(In reply to David Edmundson from comment #5)
> /usr/lib/libexec/kscreenlocker_greet --testing

it say: command not found
Comment 7 David Edmundson 2022-03-10 11:18:39 UTC
Some distros change it. It might be lib64 instead of lib.

You can try finding the file, failing that lets hope someone else hits the same bug
Comment 8 Franco Pellegrini 2022-03-10 11:32:23 UTC
(In reply to David Edmundson from comment #7)
> Some distros change it. It might be lib64 instead of lib.
> 
> You can try finding the file, failing that lets hope someone else hits the
> same bug

cannot find either
Comment 9 Gabriel 2022-03-10 13:04:38 UTC
For KDE Neon it should be: /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet --testing
Comment 10 Franco Pellegrini 2022-03-10 13:51:46 UTC
(In reply to Gabriel from comment #9)
> For KDE Neon it should be:
> /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet --testing

I get:

/usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet: symbol lookup error: /lib/x86_64-linux-gnu/libLayerShellQtInterface.so.5: undefined symbol: wl_proxy_marshal_flags
Comment 11 Gabriel 2022-03-10 15:15:25 UTC
(In reply to Franco Pellegrini from comment #10)
> I get:
> /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet: symbol lookup error:
> /lib/x86_64-linux-gnu/libLayerShellQtInterface.so.5: undefined symbol: wl_proxy_marshal_flags
Hm, okay. A guess would be that 'wl' means Wayland perhaps? I know that there were some related packages missing in the 5.24.3 update, so could you please make sure that you're completely up to date and try the screen locker again? I encountered this same issue and updating resolved it for me.
It's best to rule out that possibility first before before digging deeper. :^)
Comment 12 Antonio Rojas 2022-03-10 16:14:51 UTC

*** This bug has been marked as a duplicate of bug 451315 ***