I use intensively Plasma - about 10 to 12 hours a day - on 2 laptops, but I am with Wayland instead of X11 and never got those issues after the last updates.
Did you try a Wayland session? ( Even if as a workaround)
I’m switching between x11 and wayland and have no problem at all. Not a single crash
AMD 5600X // RX6800XT
No problem here either. I have purposely tried Wayland on KDE also and no issues either. But again as i have said many times users change stuff like themes or other things and then they run into problems.
1 Like
On an other topic the problem was, that the screen goes black but the mouse keep moving… but with xfce. In the recent days I had similar “issues” but though that my system on the hardware base makes trouble with the sleep-mode.
But when it happens under xfce too, the problem is more likely x11, kernel…
That supposed, since the last Kernel 6.0.7 update (testing), I had no black screen anymore.
Hello,
I have analyzed the last crashes and in the logs appear coredumps of the binary: wpscloudsvr
This is related to the wps-office software.
I’m going to keep an eye on it and see if when I have a crash I have the application open.
I will keep you informed.
Thanks!
Do you have the language thing installed? Hunspell?
Hello,
I completely rule out that it is the wps-office software, today it was not running and my Plasma broke.
Last logs:
nov 07 15:47:06 HOSTNAME plasmashell[846]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationItem.qml:221:21: QML SelectableLabel: Binding loop detected for property "implicitHeight"
nov 07 15:47:06 HOSTNAME plasmashell[846]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 26570, resource id: 25169280, major code: 149 (Unknown), minor code: 4
nov 07 15:47:06 HOSTNAME plasmashell[846]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 26584, resource id: 25169284, major code: 149 (Unknown), minor code: 4
nov 07 15:47:06 HOSTNAME plasmashell[846]: qt.qpa.xcb: QXcbConnection: XCB error: 136 (Unknown), sequence: 26587, resource id: 25169285, major code: 148 (Unknown), minor code: 1
nov 07 15:47:06 HOSTNAME plasmashell[846]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 26590, resource id: 25169287, major code: 149 (Unknown), minor code: 4
nov 07 15:47:06 HOSTNAME plasmashell[846]: qt.qpa.xcb: QXcbConnection: XCB error: 136 (Unknown), sequence: 26591, resource id: 25169288, major code: 148 (Unknown), minor code: 1
nov 07 15:47:07 HOSTNAME kwin_x11[796]: The X11 connection broke: I/O error (code 1)
nov 07 15:47:07 HOSTNAME kwin_x11[796]: X connection to :0 broken (explicit kill or server shutdown).
nov 07 15:47:07 HOSTNAME xembedsniproxy[902]: Container window visible, stack below
nov 07 15:47:07 HOSTNAME systemd[727]: plasma-kwin_x11.service: Consumed 15min 19.422s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit UNIT completed and consumed the indicated resources.
nov 07 15:47:08 HOSTNAME plasmashell[2485]: ATTENTION: default value of option mesa_glthread overridden by environment.
nov 07 15:48:09 HOSTNAME wireplumber[1517]: dbus[1517]: Attempted to unregister path (path[0] = MediaEndpoint path[1] = A2DPSink) which isn't registered
nov 07 15:48:09 HOSTNAME wireplumber[1517]: dbus[1517]: Attempted to unregister path (path[0] = MediaEndpoint path[1] = A2DPSink) which isn't registered
nov 07 15:48:09 HOSTNAME wireplumber[1517]: dbus[1517]: Attempted to unregister path (path[0] = MediaEndpoint path[1] = A2DPSink) which isn't registered
nov 07 15:48:09 HOSTNAME wireplumber[1517]: dbus[1517]: Attempted to unregister path (path[0] = MediaEndpoint path[1] = A2DPSink) which isn't registered
nov 07 15:48:09 HOSTNAME wireplumber[1517]: dbus[1517]: Attempted to unregister path (path[0] = MediaEndpoint path[1] = A2DPSink) which isn't registered
nov 07 15:48:09 HOSTNAME wireplumber[1517]: dbus[1517]: Attempted to unregister path (path[0] = MediaEndpoint path[1] = A2DPSink) which isn't registered
nov 07 15:48:09 HOSTNAME wireplumber[1517]: dbus[1517]: Attempted to unregister path (path[0] = MediaEndpoint path[1] = A2DPSink) which isn't registered
nov 07 15:48:09 HOSTNAME wireplumber[1517]: dbus[1517]: Attempted to unregister path (path[0] = MediaEndpoint path[1] = A2DPSink) which isn't registered
nov 07 15:48:09 HOSTNAME wireplumber[1517]: dbus[1517]: Attempted to unregister path (path[0] = MediaEndpoint path[1] = A2DPSink) which isn't registered
nov 07 15:48:09 HOSTNAME wireplumber[1517]: dbus[1517]: Attempted to unregister path (path[0] = MediaEndpoint path[1] = A2DPSink) which isn't registered
Regards
First of all, sorry for posting here, this seems to be off topic, but I guess it could be useful to discard WPS as the culprit of DE crashes.
I have same errors with wpscloudsvr on EOS and Linux Mint 21, both on Cinnamon DE.
I’ve tried installing it, including spanish dictionary, but the error persists, generally, after opening a file:
- On Linux Mint: WPS is closed
- On EOS: WPS is closed and restarted
Hello,
I rule out that the problem is due to wps, as it keeps happening to me without having wps running.
nov 09 17:52:57 HOSTNAME kwin_x11[784]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 14504, resource id: 17477377, major code: 3 (GetWindowAttributes), minor code: 0
nov 09 17:52:57 HOSTNAME kwin_x11[784]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 14505, resource id: 17477377, major code: 14 (GetGeometry), minor code: 0
nov 09 17:52:57 HOSTNAME rtkit-daemon[1693]: Supervising 9 threads of 6 processes of 1 users.
nov 09 17:52:57 HOSTNAME rtkit-daemon[1693]: Supervising 9 threads of 6 processes of 1 users.
nov 09 17:53:08 HOSTNAME kwin_x11[784]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 21262, resource id: 17479591, major code: 149 (Unknown), minor code: 4
nov 09 17:53:08 HOSTNAME kwin_x11[784]: qt.qpa.xcb: QXcbConnection: XCB error: 136 (Unknown), sequence: 21263, resource id: 17479592, major code: 148 (Unknown), minor code: 1
nov 09 17:53:08 HOSTNAME kwin_x11[784]: The X11 connection broke: I/O error (code 1)
nov 09 17:53:08 HOSTNAME kwin_x11[784]: XIO: fatal IO error 62 (El temporizador llegó al final) on X server ":0"
nov 09 17:53:08 HOSTNAME kwin_x11[784]: after 6312806 requests (6312806 known processed) with 0 events remaining.
nov 09 17:53:08 HOSTNAME xembedsniproxy[890]: Container window visible, stack below
nov 09 17:53:09 HOSTNAME systemd[715]: plasma-kwin_x11.service: Consumed 30min 31.960s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit UNIT completed and consumed the indicated resources.
nov 09 17:53:09 HOSTNAME plasmashell[840]: qt.svg: <input>:303:256: Could not add child element to parent element because the types are incorrect.
nov 09 17:53:09 HOSTNAME plasmashell[840]: qt.svg: <input>:303:461: Could not add child element to parent element because the types are incorrect.
nov 09 17:53:09 HOSTNAME plasmashell[840]: qt.svg: <input>:303:657: Could not add child element to parent element because the types are incorrect.
nov 09 17:53:09 HOSTNAME plasmashell[840]: qt.svg: <input>:303:911: Could not add child element to parent element because the types are incorrect
Last crash
1 Like
I don’t get any of these errors so something you have installed or something you have changed from the initial install.
Hi, I have to read it more carefully, but in Kde bugs there is a problem similar to mine:
Hello,
At the moment it is confirmed that there is a bug still under study in kwin_x11.
@ricklinux , this is a clear example, just because it doesn’t happen to you doesn’t mean that there is no bug.
Regards
Just because it happens to you also doesn’t mean it’s a bug. All issues are not bugs. 
Hi, I agree, but I’m not the only one who had this problem .
Hello, after the update of the mesa package I have not had any more crashes.
Regards
My input to this discussion (may or may not be useful)
I read in a discussion somewhere (perhaps in this forum) someone was experiencing random crashes and was able to find a solution by installing the zen kernel.
I installed the zen kernel 6.16-zen1-2-zen, using akm
Rebooted. Observing the messages scrolling during the reboot I saw a bunch of errors related to my AMD GPU about attempting to use memory areas that were unavailable.
After rebooting, again I restarted my laptop to seen if the AMD GPU errors were still present. They had disappeared. The only difference is a stop job for SDDM delays rebooting for 1m30s.
This may or may not help.