It seems multiple users have reported this issue, but I was wondering since we're in 2018 this bug maybe is fixable: [..] feb 13 21:49:56 desktop kwin_x11[30985]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 41429, resource id: 52432018, major code: 19 (DeleteProperty), minor code: 0 feb 13 21:49:56 desktop kwin_x11[30985]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 41439, resource id: 52432018, major code: 19 (DeleteProperty), minor code: 0 feb 13 21:49:56 desktop kwin_x11[30985]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 41440, resource id: 52432018, major code: 18 (ChangeProperty), minor code: 0 feb 13 21:49:56 desktop kwin_x11[30985]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 41441, resource id: 52432018, major code: 19 (DeleteProperty), minor code: 0 feb 13 21:49:56 desktop kwin_x11[30985]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 41442, resource id: 52432018, major code: 19 (DeleteProperty), minor code: 0 feb 13 21:49:56 desktop kwin_x11[30985]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 41443, resource id: 52432018, major code: 19 (DeleteProperty), minor code: 0 feb 13 21:49:56 desktop kwin_x11[30985]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 41444, resource id: 52432018, major code: 7 (ReparentWindow), minor code: 0 feb 13 21:49:56 desktop kwin_x11[30985]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 41445, resource id: 52432018, major code: 6 (ChangeSaveSet), minor code: 0 feb 13 21:49:56 desktop kwin_x11[30985]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 41446, resource id: 52432018, major code: 2 (ChangeWindowAttributes), minor code: 0 feb 13 21:49:56 desktop kwin_x11[30985]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 41447, resource id: 52432018, major code: 10 (UnmapWindow), minor code: 0 It really floods the journal log, and without setting a limit, this may cause issues for some. It seems upstream support for this has been landed: https://bugreports.qt.io/browse/QTBUG-55167 I have tried the workaround, but this didn't to anything for me. Maybe my distro (Arch) requires a different fix. If this is isn't a KDE bug, sorry for the report.
The warnings need to be disabled through Qt. We could filter them out, but that would also filter out legit warnings from Qt. So there is nothing we could do.
*** This bug has been marked as a duplicate of bug 337690 ***