I recently installed Fedora 37, and
plasmashell on Fedora 37 seems to be crashing a good deal more than on Fedora 36. In the journal, I see the following entries just before
Nov 16 07:01:22 thelio kwin_wayland_wrapper: unknown object (55), message get_surface_feedback(4no)
Nov 16 07:01:22 thelio kwin_wayland_wrapper: error in client communication (pid 51782)
Nov 16 07:01:22 thelio plasmashell: wl_display@1: error 1: invalid arguments for email@example.com_surface_feedback
Nov 16 07:01:22 thelio plasmashell: The Wayland connection experienced a fatal error: Invalid argument
I’m not sure exactly what steps are needed to reproduce this yet, but anecdotally, I have experienced it most when clicking on a launcher in the task bar. Any suggestions on where to start troubleshooting this?
I’ve been experiencing a different kwin crash with F37 that wasn’t occurring in F36. I filed a bug report with the KDE team, and I would encourage you to open one for your bug as well. There’s not much the Fedora team can do; this is likely a problem with the upstream code.
install updated qt, plasma and KDE frameworks (instruction at the top of this page): https://bodhi.fedoraproject.org/updates/FEDORA-2022-a57b72eeb5
You may need to remove
qt5-qtwebengine-freeworld for now, if you have it.
gnome-abrt help with reporting crashes to appropriate bug-trackers.
Yikes, that update broke more stuff (Screen Lock for example). I’m having the same issue where launching apps from the Task bar will cause Plasmashell to crash.
I’m a Linux novice, but was able to figure out how to rollback dnf updates. On the bright side, I learned something new today!
This update has been edited and fixed my Screen Lock issue. Maybe you got older version from outdated mirror.
I’m confused…I was able to remove the updates yesterday and the system went back to it’s previous state. This morning “Discovery” showed a lot of updates, I applied them and had the same issues…Lock screen message (broken), restart button not working, etc. I was able to back them out using the same dnf history command…
Just ran the Discovery update on another workstation and am getting the same errors… Damn it. Worse part is that I cannot roll this one back.