Skip to main content
 —  James Oakley
Screen Locker error

Just a quick post in case this helps someone.

My PC (Fedora 42) has just updated to KDE Plasma 6.4.

Immediately, every time I locked the session (Super key + L), an error appeared on the screen

Screenshot of error message

The screen locker is broken and unlocking it is not possible anymore. In order to unlock it, switch to a virtual terminal (e.g. Ctrl+Alt+F1), log in to your account and execute the command:

loginctl unlock-session 2

Then log out of the virtual session by pressing Ctrl+D, and switch back to the running session (Ctrl+Alt+F2).

Should you have forgotten the instructions, you can get back to this screen by pressing Ctrl+Alt+F2.

Firstly, for some reason, tty1 wouldn't work, so I needed to use Ctrl+Alt+F3 to get to tty3.

But I didn't want to be doing that every time my session locked.

Searching the web I found various bug reports (none recent) that sounded similar. There was nothing in the KDE bug tracker to match the error (that was opened since the Plasma 6.4 release). I went down various blind alleys that didn't help: changing my wallpaper from picture of the day to a fixed image, looking into the error file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockOsd.qml:10:1: "../osd": no such directory, and the error "ml: The backend got an unknown wallpaper provider type. Both those errors were popping up in journalctl at exactly the moment I locked my session and got the error message.

In the end, something someone posted somewhere prompted me to change the desktop theme. I simply opened the Settings app, and clicked to choose Breeze Dark.

The KDE Plasma System Settings window

Now my sessions lock and unlock without a hitch.

Update 24 hours later: Take 2

Not so fast!

Before applying a theme freshly, this error would happen every time I locked my session.

Now, I can mostly lock and unlock fine, but sometimes (maybe 1 in 10?) I still get the error screen.

The one message I'm seeing in my journalctl that seems relevant is this one:

The backend got an unknown wallpaper provider type. The wallpaper will now fall back to the default. Please check your wallpaper configuration!

That led me to this page on /Fedora reddit.

That pointed me to two things

  1. Someone claimed this is a known bug that should be patched within a week. Wait and see
  2. If the problem is caused by lock screen wallpaper, set that to a new wallpaper manually. That's System Settings > Screen Locking > Change Appearance. I've done that. Wait and see

Take 3

Another 24 hours, and the problem is still happening. It seems the lockscreen wallpaper may have been causing errors, but was not the problem.

I found two threads on the Fedora forum and the KDE forum. They suggest that the upgrade of KDE Plasma may not be teh cause, but that qtwayland6 updated at the same time and that is at fault. So, following the tips there, I have downgraded that.

sudo dnf downgrade qt6-qtwayland-0:6.9.1-1.fc42.x86_64

(You need to have the fedora-updates-archive.repo enabled for dnf to find the older version.)

Because the fault is intermittent, I now need to wait another 24 hours before I can be sure it has been solved. I'll report back.

Another 24 hours later

I’ve now had 24 hours without a hitch. That said, no sooner did I come here to update this, but a comment has popped up from someone who found the downgrade did not solve it for them. So maybe the mystery rumbles on.

I see that a tagged release of qt6-qtwayland is being reviewed by Fedora prior to release. That will be 6.9.1-3, and will be identical to 6.9.1-1 but with a higher minor release number so that people can upgrade to undo the damage of going to 6.9.1-2.

Blog Category:
Submitted by WILLIAM HOPE on Tue, 01/07/2025 - 11:28 Permalink

But I also didn't do the theme change and after reading some other things, it may be a combination of items.

Thanks for the pointers...

Submitted by CMORE on Thu, 03/07/2025 - 00:25 Permalink

I tried changing the desktop theme as well as the appearance of the lock screen and it persist. I see this in the message file when the lock screen error comes up.

file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockOsd.qml:10:1: "../osd": no such directory

And this 

kscreenlocker_greet[12102]: qml: The backend got an unknown wallpaper provider type. The wallpaper will now fall back to the default. Please check your wallpaper configuration!

I don't want to bother with the "downgrades" at this time so I suppose I'll turn off screen lock for now and see if an KDE update comes through to fix this since multiple people are reporting this issue. Sub'd for tracking. Thx

Submitted by James Oakley on Thu, 03/07/2025 - 07:09 Permalink

You've followed exactly the path I was on, and you're left with the errors I was left with. The downgrade of qt6-qtwayland did fix things for me, so if you don't want to bother with that just turn off screen locking (as you say) and wait for 6.9.1-3 which will revert the change that caused the problem.

Submitted by bozwayed on Thu, 03/07/2025 - 11:52 Permalink

I can confirm rolling back the version of qt works for me now for 3 days not issues.  laptop sleeps and wakesup with no issues during unlocking.  thank you for this fix.

Submitted by James Oakley on Thu, 03/07/2025 - 11:54 Permalink

Happy to help, and thanks for posting a comment to say so, as this gives others more confidence to use this solution.

Submitted by bozwayed on Sun, 06/07/2025 - 00:26 Permalink

Fedora pushed .3 for the qwin thing and everything works fine now.  it has been rock solid for the past 2 days.

thank you again for all of your help!

Submitted by James Oakley on Sun, 06/07/2025 - 06:43 Permalink

Yep, so you didn't want to do the downgrades. Essentially the "upgrade" you've just been given bumps the version number but under the hood it simply reverts the broken change. So you now have the downgrade via a regular upgrade. As it were.

Submitted by mnstr0 on Sun, 06/07/2025 - 22:34 Permalink

I'm on the latest Fedora Discover update and my Qt Version is 6.9.1 and I'm STILL receiving an error every time I lock the computer. Anyone else still having this issue after the latest round of updates?

Submitted by James Oakley on Sun, 06/07/2025 - 22:37 Permalink

What's your exact version number for qt6-qtwayland?

dnf-3 list installed | grep qtwayland

Mine is 6.9.1-3.fc42, and the -3 is the difference between a working version and a broken version.

Submitted by mnstr0 on Sun, 06/07/2025 - 22:42 Permalink

Thanks for the helpful console commands, my version number is 6.9.1-2.fc42 looks like I'll either need to revert or wait for the update to -3. I'm currently attempting to add the archive repo so I can pull the older qt6 version. I'm new to Linux so apologies for my ignorance.
 

Submitted by mnstr0 on Sun, 06/07/2025 - 22:54 Permalink

Thanks to your comment and double checking my work I'm now on the -3 version of Qt and the lock function at least for now appears to be working. Thanks for the help this forum was able to offer me, it's nice that places like this still exist on the internet.

Add new comment
The content of this field is kept private and will not be shown publicly.