[frameworks-kwindowsystem] [Bug 366421] kwin_x11: QXcbConnection: XCB error: 9

2019-02-15 Thread Yaroslav Sidlovsky
https://bugs.kde.org/show_bug.cgi?id=366421

Yaroslav Sidlovsky  changed:

   What|Removed |Added

 CC||zawer...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwindowsystem] [Bug 366421] kwin_x11: QXcbConnection: XCB error: 9

2019-02-09 Thread Robin Laing
https://bugs.kde.org/show_bug.cgi?id=366421

Robin Laing  changed:

   What|Removed |Added

 CC||me...@telusplanet.net

--- Comment #5 from Robin Laing  ---
Don't know if this will help or not but I found that I can generate as many
error messages as I like by just moving my mouse between two different
indicators on the task manager on my KDE desktop.

qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 37284, resource
id: 69206033, major code: 141 (Unknown), minor code: 3
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 37303, resource
id: 79691782, major code: 141 (Unknown), minor code: 3
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 37321, resource
id: 69206033, major code: 141 (Unknown), minor code: 3
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 37332, resource
id: 79691782, major code: 141 (Unknown), minor code: 3

The sequence number changes but the resource id remains the same between each
application displayed.  Still happening in the current plasma on Fedora 29.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwindowsystem] [Bug 366421] kwin_x11: QXcbConnection: XCB error: 9

2016-08-05 Thread Rex Dieter via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366421

--- Comment #4 from Rex Dieter  ---
Per comment #3, filed
https://bugreports.qt.io/browse/QTBUG-55167
requesting support for categorized logging be added here.

-- 
You are receiving this mail because:
You are watching all bug changes.


[frameworks-kwindowsystem] [Bug 366421] kwin_x11: QXcbConnection: XCB error: 9

2016-08-04 Thread Martin Gräßlin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366421

Martin Gräßlin  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Martin Gräßlin  ---
> Now, whether it's worth treating the symptom (hide the warning), or the 
> disease (the cause for the warning)?

We can only treat the symptom. We don't know where the GetGeometry call fails
(multiple locations in KWin) and the event does not tell us either. KWin always
uses the calls which report errors on the event loop as all calls are allowed
to fail. From KWin side it can always happen that a call fails: that's just in
the nature of a window manager. If KWin processes events when the window got
destroyed, calls like GetGeometry will fail (as the window is gone). We had
looked into this once and concluded that trying to not get the errors (e.g.
grab server) will result in much worse situations than just having the calls
fail.

The correct thing to do would be introduce categorized logging in Qt's xcb
plugin, so that the warnings can be filtered out.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwindowsystem] [Bug 366421] kwin_x11: QXcbConnection: XCB error: 9

2016-08-04 Thread Rex Dieter via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366421

--- Comment #2 from Rex Dieter  ---
Confirmed,

qtbase-opensource-src-5.6.1/src/plugins/platforms/xcbqxcbconnection.cpp:
qWarning("QXcbConnection: XCB error: %d (%s), sequence: %d, resource id: %d,
major code: %d (%s), minor code: %d",

Now, whether it's worth treating the symptom (hide the warning), or the disease
(the cause for the warning)?

-- 
You are receiving this mail because:
You are watching all bug changes.


[frameworks-kwindowsystem] [Bug 366421] kwin_x11: QXcbConnection: XCB error: 9

2016-08-04 Thread Rex Dieter via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366421

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@math.unl.edu

--- Comment #1 from Rex Dieter  ---
I suspect this is coming from Qt

-- 
You are receiving this mail because:
You are watching all bug changes.