Bug 340318

Summary: lot of QXcbConnection: XCB error: 3 (BadWindow)
Product: [Plasma] kwin Reporter: luigide
Component: compositingAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal CC: abone27, jsamyth, steffen.klee
Priority: NOR    
Version: 5.1.0   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description luigide 2014-10-24 20:05:08 UTC 
i just post here for keep informed.i see lots of above(title) error into my log.
Also lots of entries eg: 
kwin_x11[416]: PERMITTED 'ID: 27263041 ;WMCLASS: "plasmashell" : "plasmashell" ;Caption: "Plasma" ' true

also see this:

Oct 24 19:48:27 pc kwin_x11[416]: Trying to load decoration plugin "Oxygen"
Oct 24 19:48:27 pc kwin_x11[416]: Decoration plugin not found
Oct 24 19:48:27 pc kwin_x11[416]: KWin: The default decoration plugin is corrupt and could not be loaded.
Oct 24 19:48:27 pc kwin_x11[416]: QObject::connect: invalid null parameter

full log entry here: http://pastebin.com/GdxnWY0H

i dont know what happening.just post.

hw:ivybridge

soft: xorg-server-1.16.1 xcb-1.11 breeze-5.1.0 breeze-kde4-5.1.0 oxygen-icons-4.14.2          
 (arch names)

Reproducible: Always
Comment 1 Martin Flöser 2014-10-25 05:40:05 UTC 
The warning about the decoration says that you don't have the Oxygen decoration installed.

Otherwise none of them are errors and just debug output.
Comment 2 Thomas Lübking 2014-10-25 13:54:28 UTC 
fyi, the xcb errors happen because "someone" (kwin in this case) attempts to alter a property on a window that has already been destroyed.
X11 is an async protocol, so this can happen.

The only way around would be to
- grab the server
- check whether the window is still there
- alter the property and then
- release the server

You would not like that behavior, though ;-)
Comment 3 Martin Flöser 2014-10-27 08:03:30 UTC 
there is another way, though I haven't tested it yet. At XDC I had been told by the designer of XCB that if we used the checked variants and discard the reply we wouldn't get the errors any more.
Comment 4 Thomas Lübking 2014-10-27 11:59:21 UTC 
because xcb sucks the error instead of putting it into the event queue =)
probably required for kwindowsystem because of the "gdk: i kill myself on X11 errors" attitude.
Comment 5 John Andersen 2016-09-03 02:44:53 UTC 
Wow.  Two years later and this stuff is still flooding everybody's logs.
People have no pride in workmanship these days.  I've fired guys for less.
Comment 6 Martin Flöser 2016-09-03 08:24:38 UTC 
@John: this is a volunteer project. This is totally not acceptable behavior. Please have a look at https://www.kde.org/code-of-conduct/ and reflect what you wrote.