SUMMARY "Screen locker is broken and unlocking is not possible" KDE neon User 5.25 fully up to date as of right now. Reported to https://invent.kde.org/plasma/kscreenlocker/-/issues/4 Reproduced by Nate Graham STEPS TO REPRODUCE 1. Run /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet --testing OBSERVED RESULT /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet --testing file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml:222: ReferenceError: wallpaper is not defined file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml:0: ReferenceError: wallpaper is not defined Locked at 1655853372 file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:43:9: Unable to assign [undefined] to bool file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:43:9: Unable to assign [undefined] to bool qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Segmentation fault SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.25
Can you please paste the output of `coredumpctl list kscreenlocker_greet`?
(In reply to Nate Graham from comment #1) > Can you please paste the output of `coredumpctl list kscreenlocker_greet`? coredumpctl list kscreenlocker_greet No coredumps found.
> No coredumps found. Is coredump service enabled at all? It might be turned off by default. https://wiki.archlinux.org/title/Core_dump
Looks like you'll need to get the backtrace manually. Here's how you can do it. 1. run `gdb --args /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet --testing` in a terminal window 2. enter "run" at the prompt 3. when it crashes, enter "bt" at the prompt 4. copy-and-paste the output here
(In reply to Nate Graham from comment #4) > Looks like you'll need to get the backtrace manually. Here's how you can do > it. > > 1. run `gdb --args /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet > --testing` in a terminal window > 2. enter "run" at the prompt > 3. when it crashes, enter "bt" at the prompt > 4. copy-and-paste the output here gdb --args /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet --testing GNU gdb (Ubuntu 9.2-0ubuntu1~20.04.1) 9.2 Copyright (C) 2020 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet... (No debugging symbols found in /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet) (gdb) run Starting program: /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet --testing [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Cannot find user-level thread for LWP 317551: generic error (gdb) bt Selected thread is running. (gdb) quit
(In reply to ratijas from comment #3) > > No coredumps found. > > Is coredump service enabled at all? It might be turned off by default. > > https://wiki.archlinux.org/title/Core_dump Thanks for the link. That page described how do disable coredups, but it seems it does not state how to enable it? This is what I have ATM in cat /etc/systemd/coredump.conf [Coredump] #Storage=external #Compress=yes #ProcessSizeMax=2G #ExternalSizeMax=2G #JournalSizeMax=767M #MaxUse= #KeepFree= Thanks for your help.
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". > Cannot find user-level thread for LWP 317551: generic error Well that's weird. Apparently it's an issue in glibc??? https://bugs.archlinux.org/task/69657
(In reply to Nate Graham from comment #7) > > Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". > > Cannot find user-level thread for LWP 317551: generic error > > Well that's weird. Apparently it's an issue in glibc??? > https://bugs.archlinux.org/task/69657 Looking at the post in various places, this error message seems to be displayed in quite varied contexts and I suspect it may occur in wide range of causes. Use of word "generic error" may be a hint. In any case - can someone please look at the problem at hand - eg "Screen locker is broken and unlocking is not possible"? @Nate - you are able to reproduce this bug, correct? Thanks, Andrej
I would guess the original bug here is caused by Qt being upgraded during the session. Did you have the /release archive enabled?
I do confirm that gdb doesn't like talking to kscreenlocker_greet with the unhelpful message of "Cannot find user-level thread for LWP 186659: generic error". But gdb and glib are stuff handled by Ubuntu, we don't get involved with them.
I was able to reproduce in the past, but now I can't anymore with current git master. I think we're going to need a backtrace to proceed here.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!