Bug 463231

Summary: kwin_x11 terminates: The X11 connection broke: I/O error (code 1)
Product: [Plasma] kwin Reporter: valdikss
Component: coreAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: major CC: ads-kde-bugs
Priority: NOR    
Version: 5.26.4   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Kwin X11 termination
Kwin X11 termination 2

Description valdikss 2022-12-19 13:37:47 UTC
Created attachment 154693 [details]
Kwin X11 termination

SUMMARY
Kwin in X11 session terminates with "The X11 connection broke: I/O error (code 1)" message in syslog. This usually happens once in 2-3 days of active work on the PC. X11 does not crash, nor any other software using X11, only kwin terminates (and not crashes either).

STEPS TO REPRODUCE
1. Run Plasma session in X11
2. Work for 2-3 days
3. See kwin termination

OBSERVED RESULT
Kwin terminates, window titles and utility buttons disappear, everything other continue to work.

EXPECTED RESULT
Kwin does not terminate.


SOFTWARE/OS VERSIONS

ADDITIONAL INFORMATION
No crash dumps, no crash records in dmesg, no suspicious records in journalctl.
Latest log records:

    $ journalctl -b -1 --user -u plasma-kwin_x11.service
    дек 19 16:23:18 val kwin_x11[1927]: The X11 connection broke: I/O error (code 1)
    дек 19 16:23:18 val kwin_x11[1927]: X connection to :0 broken (explicit kill or server shutdown).
    дек 19 16:23:18 val systemd[1747]: plasma-kwin_x11.service: Consumed 26min 12.525s CPU time.

Full log is in attachment.
Comment 1 valdikss 2022-12-22 10:55:23 UTC
Created attachment 154753 [details]
Kwin X11 termination 2

Just happened again, right after I clicked on the link in Gajim (XMPP client) and Firefox opened.
Last seconds of journalctl is in attachment.

kwin_x11[1931]: The X11 connection broke: I/O error (code 1)
kwin_x11[1931]: X connection to :0 broken (explicit kill or server shutdown).
Comment 2 valdikss 2022-12-22 10:56:19 UTC
plasma-workspace-x11-5.26.4.1-1.fc37.x86_64
Comment 3 valdikss 2022-12-22 11:04:37 UTC

*** This bug has been marked as a duplicate of bug 461316 ***