Created attachment 182760 [details] Lock screen SUMMARY If screen locks, it cannot be unlocked. STEPS TO REPRODUCE 1. Lock the screen or let it lock by itself 2. 3. OBSERVED RESULT It cannot be unlocked. See screenshot. EXPECTED RESULT Unlocked SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Operating System: Fedora Linux 42 KDE Plasma Version: 6.4.1 KDE Frameworks Version: 6.15.0 Qt Version: 6.9.1 ADDITIONAL INFORMATION /usr/libexec/kscreenlocker_greet --testing Locked at 1751120775 qml: The backend got an unknown wallpaper provider type. The wallpaper will now fall back to the default. Please check your wallpaper configuration! qml: The backend got an unknown wallpaper provider type. The wallpaper will now fall back to the default. Please check your wallpaper configuration! org.kde.plasma.libtaskmanager: The PlasmaWindowManagement protocol hasn't activated in time. The client possibly got denied by kwin? Check kwin output. file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockOsd.qml:10:1: "../osd": no such directory file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockOsd.qml:10:1: "../osd": no such directory Segmentation fault (core dumped) #0 0x00007fcbf177919d in QWaylandXdgActivationV1::requestXdgActivationToken(QtWaylandClient::QWaylandDisplay*, wl_surface*, std::optional<unsigned int>, QString const&) [clone .constprop.0] () at /lib64/libLayerShellQtInterface.so.6 #1 0x00007fcbf1779990 in LayerShellQt::QWaylandLayerSurface::requestActivate() () at /lib64/libLayerShellQtInterface.so.6 #2 0x00007fcbeef5662c in QObject::event(QEvent*) () at /lib64/libQt6Core.so.6 #3 0x00007fcbeeef9f38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt6Core.so.6 #4 0x00007fcbeeefdd26 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt6Core.so.6 #5 0x00007fcbef21016f in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt6Core.so.6 #6 0x00007fcbed0eb880 in g_main_context_dispatch_unlocked.lto_priv () at /lib64/libglib-2.0.so.0 #7 0x00007fcbed0f47a8 in g_main_context_iterate_unlocked.isra () at /lib64/libglib-2.0.so.0 #8 0x00007fcbed0f4953 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #9 0x00007fcbef20f9ad in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt6Core.so.6 #10 0x00007fcbeef07b03 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt6Core.so.6 #11 0x00007fcbeef03419 in QCoreApplication::exec() () at /lib64/libQt6Core.so.6 #12 0x000055792850d8be in main ()
I can reproduce this under Fedora's qt6-qwayland package, version 6.9.1-2. Reverting to 6.9.1-1 appears to fix the issue. Fedora bugtracking link: https://bugzilla.redhat.com/show_bug.cgi?id=2375356
(In reply to pg_tips from comment #1) > I can reproduce this under Fedora's qt6-qwayland package, version 6.9.1-2. Sorry for typo - package name is qt6-qtwayland.
*** Bug 506331 has been marked as a duplicate of this bug. ***
*** Bug 506341 has been marked as a duplicate of this bug. ***
*** Bug 506351 has been marked as a duplicate of this bug. ***
*** Bug 506360 has been marked as a duplicate of this bug. ***
*** Bug 506364 has been marked as a duplicate of this bug. ***
One more observation. On a system with Plasma 6.4.1, and qt6-qtwayland 6.9.1-1 (i.e. the good, reverted version), I still get this log line: > file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockOsd.qml:10:1: "../osd": no such directory but I don't get the lockscreen breakage or any other negative effects. So while this missing directory might be something that should be tidied up in Plasma, it doesn't appear to be the cause of the issues seen here.
Try running "/usr/libexec/kscreenlocker_greet" on a Konsole session. I get the missing directory message and and immediate segfault.
(In reply to Brian Kaye from comment #9) > Try running "/usr/libexec/kscreenlocker_greet" on a Konsole session. I get > the missing directory message and and immediate segfault. On my system with Plasma 6.4.1 and qt6-qtwayland 6.9.1-1 (i.e. the good, reverted one), I get the missing directory message, but no segfault and a normal lock/unlock process. Console output: $ /usr/libexec/kscreenlocker_greet --testing Locked at 1751263124 file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockOsd.qml:10:1: "../osd": no such directory file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockOsd.qml:10:1: "../osd": no such directory file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockOsd.qml:10:1: "../osd": no such directory Unlocked Unlocked Unlocked Unlocked Unlocked Unlocked Unlocked Unlocked Unlocked
❯ ./kscreenlocker_greet --testing kf.svg: The theme "BreezeOutline" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format. kf.svg: The theme "BreezeOutline" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format. kf.plasma.core: The theme "BreezeOutline" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format. kf.plasma.core: The theme "BreezeOutline" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format. QQmlComponent: Component is not ready kscreenlocker_greet: Root item not a WallpaperItem kf.plasma.quick: "file:///home/akseli/Repositories/kde/usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml" "Error loading QML file.\n12: Cannot load library /home/akseli/Repositories/kde/usr/lib64/qml/org/kde/plasma/plasmoid/libplasmoidplugin.so: /home/akseli/Repositories/kde/usr/lib64/qml/org/kde/plasma/plasmoid/libplasmoidplugin.so: undefined symbol: _ZNK13WallpaperItem10metaObjectEv\n" file:///home/akseli/Repositories/kde/usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:194: ReferenceError: wallpaper is not defined kscreenlocker_greet: Wallpaper needs to be a QtQuick Item Locked at 1751276435 kf.svg: The theme "BreezeOutline" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format. fish: Job 1, './kscreenlocker_greet --testing' terminated by signal SIGSEGV (Address boundary error)
(In reply to Akseli Lahtinen from comment #11) > ❯ ./kscreenlocker_greet --testing > kf.svg: The theme "BreezeOutline" uses the legacy metadata.desktop. Consider > contacting the author and asking them update it to use the newer JSON format. > kf.svg: The theme "BreezeOutline" uses the legacy metadata.desktop. Consider > contacting the author and asking them update it to use the newer JSON format. > kf.plasma.core: The theme "BreezeOutline" uses the legacy metadata.desktop. > Consider contacting the author and asking them update it to use the newer > JSON format. > kf.plasma.core: The theme "BreezeOutline" uses the legacy metadata.desktop. > Consider contacting the author and asking them update it to use the newer > JSON format. > QQmlComponent: Component is not ready > kscreenlocker_greet: Root item not a WallpaperItem > kf.plasma.quick: > "file:///home/akseli/Repositories/kde/usr/share/plasma/wallpapers/org.kde. > image/contents/ui/main.qml" > "Error loading QML file.\n12: Cannot load library > /home/akseli/Repositories/kde/usr/lib64/qml/org/kde/plasma/plasmoid/ > libplasmoidplugin.so: > /home/akseli/Repositories/kde/usr/lib64/qml/org/kde/plasma/plasmoid/ > libplasmoidplugin.so: undefined symbol: _ZNK13WallpaperItem10metaObjectEv\n" > file:///home/akseli/Repositories/kde/usr/share/plasma/shells/org.kde.plasma. > desktop/contents/lockscreen/LockScreenUi.qml:194: ReferenceError: wallpaper > is not defined > kscreenlocker_greet: Wallpaper needs to be a QtQuick Item > Locked at 1751276435 > kf.svg: The theme "BreezeOutline" uses the legacy metadata.desktop. Consider > contacting the author and asking them update it to use the newer JSON format. > fish: Job 1, './kscreenlocker_greet --testing' terminated by signal SIGSEGV > (Address boundary error) I tried several different themes and I tried deleting the image from the theme. Did not fix it. I don't know whether that should be enough.
*** Bug 506410 has been marked as a duplicate of this bug. ***
*** Bug 506415 has been marked as a duplicate of this bug. ***
user@fedora:~$ /usr/libexec/kscreenlocker_greet --testing Locked at 1751362071 file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockOsd.qml:10:1: "../osd": no such directory file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockOsd.qml:10:1: "../osd": no such directory file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockOsd.qml:10:1: "../osd": no such directory Segmentation fault (core dumped) Operating System: Fedora Linux 42 KDE Plasma Version: 6.4.1 KDE Frameworks Version: 6.15.0 Qt Version: 6.9.1 Kernel Version: 6.15.4-200.fc42.x86_64 (64-bit) Graphics Platform: Wayland
*** Bug 506428 has been marked as a duplicate of this bug. ***
*** Bug 506478 has been marked as a duplicate of this bug. ***
*** Bug 506491 has been marked as a duplicate of this bug. ***
qt6-qtwayland 6.9.1-3.fc42 (which reverts the problematic change in 6.9.1-2 and restores the ABI of 6.9.1-1) has now been released into stable Fedora 42. So a normal "sudo dnf upgrade --refresh" should apply the fix. https://bugzilla.redhat.com/show_bug.cgi?id=2375356#c33
The crash problem is fixed. However the missing directory error is still there. Should we open a new bug for that problem.
Created attachment 182983 [details] kde junk After using KDE as my choice desktop environment for over 15 years, I am done with this. My original bug submission mentioned the screen lock issue but that was only a symptom, but someone marked it as a duplicate. The real problem is the hugely pixelated screen I get when I login and I cannot get anything done. See the attachment. So long.
(In reply to geekiehiway from comment #21) As you say, I doubt that that's the same problem as this. I think that should have been commented at the linked bug you mention, but it doesn't seem like you're much in the mood to be helpful... There's certainly no point in disparaging the DE as a whole, here. Do remember that you get a free desktop environment because your payment is being a tester. You can't much have your cake and eat it. If you're going to reply with "I donate", then maybe file that bug, and take the money you would have donated, and instead put it into a bug bounty for your bug.
(In reply to geekiehiway from comment #21) > Created attachment 182983 [details] this is not a solution to the bug, but it seems to me the screen unlocks zoomed in to the max, can you zoom out using super+minus?