Today’s update of qt6-qtwayland to 6.9.1-2 appears to break the KDE Plasma lockscreen functionality. (When you attempt to unlock, you have to drop to a terminal to do so - at least the lockscreen displays instructions of what to do.)
Downgrading to 6.9.1-1 seems to fix this, but better not to upgrade to 6.9.1-2 for now if you haven’t already.
UPDATE: a “new” version of the package, 6.9.1-3, has now been released. This is in effect identical to 6.9.1-1: it reverts the change from the problematic 6.9.1-2.
So a normal sudo dnf upgrade --refresh should now resolve the issue.
Historical information: the below was the temporary workaround from before 6.9.1-3 was released
I have had even more severe problems after updating to qt6-qtwayland-0:6.9.1-2.
Almost every application crashes on startup (including the crash reporter, and frequently the plasma shell itself).
This user’s issues were fixed by downgrading qt6-qtqwayland to 6.9.1-1.
Downgrading via these steps also fixed my issue of “everything crashes over and over in an endless nightmare whenever I try to use a Wayland session”. Thank you very much!
This also affects Fedora Kinoite, but luckily I have the unlock command added to KDE Connect so I don’t have to drop into terminal.
I don’t know how to start downgrading with rpm-ostree, but since the impact is so wide I hope it will be fixed quickly even if I did nothing and I imagine this also affects less techncaal users who don’t know what a downgrade even is let alone how to do it.
Neat! Some users have seen impacts beyond the lockscreen, but that sounds like a smart solution of only the lockscreen is broken.
Indeed. I don’t use Kinoite but I’m guessing that rolling the whole deployment back to a previous day’s image (via the GRUB menu?) would be easier than trying to downgrade an individual package.
I am on Kiniote and am getting this error too, but for some reason I cannot get into the TTY.. Not only that though.. If I put my IdeaPad to sleep and then wake it up again, most of the time it somehow turned itself all the way off. Then when I log on, it completely crashes and freezes, I have to fully restart the system with the physical power button. Luckily I can rollback to the previous image, but in this case that’s from the 3rd of June because I neglected to update my system for several weeks
I’m on Kinoite and mine’s doing pretty much the same thing. I’ll put it to sleep, but when I go to use it again I’ll get a fresh login screen and a fresh session. I thought I must have just forgot I did a restart before going to bed, but then I read your post here and tried it again and it did the same thing. No crashes on mine though. I’ve got kinoite pinned to the June 13th build due to this and a bluetooth related issue that also only seems to appear on KDE.
These are the first major problems I’ve had from system upgrades on silverblue/kinoite (that I didn’t cause myself) and it’s quite nice being able to just “nope” my way out of an upgrade rather than having to figure out a fix before I can use my system normally again.
Is this happening to everyone with the update? I might not have installed it yet, because I haven’t been having the problem myself, which is odd because I am on KDE. This isn’t a “works on my machine” response to be clear; I’m just interested in what the commonality is here on systems where it works vs systems where it has broken.
Yeah that’s what I was trying to refer to, I just couldn’t remember the word “session”. It starts a new session for me too. I have not experienced the Bluetooth issue, but I also have not used Bluetooth since updating. This is like one of 2-3 major issues I have had on Fedora KDE and the first on Kinoite specifically. It is quite nice to just boot to the previous one, albeit a month old heh.
It’s a good question! From what I’ve seen on here and other forums, there seems to be a spectrum of impact from:
Lock screen problems only, fixed by changing the wallpaper
Lock screen problems, not reliably fixed by changing the wallpaper, but reliably fixed by downgrading the package
More extensive app crashing, reliably fixed by downgrading the package
So it does seem conceivable that there’s also “0. No impact” and we’re just not hearing about it because people don’t proactively post that their system is fine!
Aha! To clarify, after you downgraded qt6-qtwayland only, did your issues resolve - or did you also have to downgrade fcitx5? (Wondering if there is some interaction here or whether they’re two separate issues that coincided in time.)
Since the poster in that thread had an issue with libfcitx5platforminputcontextplugin.so, I did a hash check on my pre- and post-update versions of that file and they were totally unchanged. Then I saw this thread and thought it might be my issue, and this resolved it.
It wasn’t clear whether that poster’s old version was older than the one I had, so I can’t rule out his being the same issue as mine, but the behavior did sound similar. Basically when I log in there’s immediately a crash error from wine-preloader, then plasma shell starts crashing and restarting in a loop about 3 times until there’s a black screen. I tried to open the terminal but it also crashed. I ended up doing ctrl-alt-F3 and rebooting the system to get back into an x11 session.
Edit: To be clear, I only downgraded qt6-qtwayland and nothing else.
Cool, interesting to know! So maybe the reason that fcitx5 segfaulted is the same reason that the screenlocker did, i.e. the ABI change introduced by qt6-qtwayland 6.9.1-2.
Yeah, my guess was that the two might be interacting somehow. I figured I would wait for a while and see whether something got updated to fix the issue (since the qt6-qtwayland issue seems to be well-known at this point), and if it persisted even after updates then I’d try messing with fcitx5 as well to report further.
It’s interesting that the other poster resolved the issue by backing out the fcitx5 binary.
Maybe the common pattern is that errors which normally would be non-critical (like an issue with wallpaper config, or whatever was happening in fcitx5) end up causing segfaults in the presence of the 6.9.1-2 ABI change.
I tested locking and unlocking my screen, so it seems there is a “no problems” category. Interesting. I’d be interested in the hardware of those who are experiencing issues.
I have an AMD processor and AMD GPU, for instance. Do those experiencing issues have NVIDIA?
