Locked at 1751125159
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
Segmentation fault (core dumped)
I tried to search for this problem but nothing came up.
Thank you in advance
Changing the theme Breeze apparently fixed the issue
When I changed back to Fedora, I got the same issue again
However, if I change the lock screen wallpaper, then at first it seemed like the Fedora theme worked without problems, but later the same thing appeared again.
The package I’m most suspicious of is qt6-qtwayland (6.9.1-2) because:
In the last update transaction I did on the affected system, that was the only package that seems at all related to the desktop environment. No Plasma packages were upgraded.
I have another system where I haven’t yet upgraded that package, and I’m not seeing the lock screen issue there.
Update: Downgrading qt6-qtwayland to 6.9.1-1 appears to fix the issue.
Yeah, the bug reports exactly what I got as well.
And for the fix, I didnt get any issue from changing the lock screen wallpaper, but maybe it’ll cause issue after a few reboot.
For the fedora theme, I haven’t tried it, I’ll prob just delete that theme and stick to breeze for now, thanks for sharing
Hi, it’s my blog post. Glad it helped. Before I applied Breeze, I was getting the screen locker error every time I locked the session. The fact that I managed to lock the session without fault led me to believe I’d solved the problem. Sadly, it still happens, now sometimes.
I then tried changing the lockscreen wallpaper, but that also seems a red-herring.
Prompted by @pg-tips post above, I’ve just downgraded qt6-qtwayland. Because the problem is now intermittent, I need to give it some time to see if this has solved the problem. I’m keeping the blog post updated.