[Bug 871631] New: yast2: QXcbConnection: XCB error: 2 (BadValue), sequence: 418, resource id: 683
https://bugzilla.novell.com/show_bug.cgi?id=871631 https://bugzilla.novell.com/show_bug.cgi?id=871631#c0 Summary: yast2: QXcbConnection: XCB error: 2 (BadValue), sequence: 418, resource id: 683 Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: x86-64 OS/Version: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers@suse.de ReportedBy: mpluskal@suse.com QAContact: jsrain@suse.com CC: mvidner@suse.com Found By: --- Blocker: --- Created an attachment (id=584735) --> (http://bugzilla.novell.com/attachment.cgi?id=584735) y2logs When executing yast2 (X forwarded via ssh) I can see following errors: QXcbConnection: XCB error: 2 (BadValue), sequence: 418, resource id: 683, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 2 (BadValue), sequence: 422, resource id: 683, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 2 (BadValue), sequence: 423, resource id: 683, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 2 (BadValue), sequence: 424, resource id: 683, major code: 130 (Unknown), minor code: 3 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=871631
https://bugzilla.novell.com/show_bug.cgi?id=871631#c1
Josef Reidinger
https://bugzilla.novell.com/show_bug.cgi?id=871631
https://bugzilla.novell.com/show_bug.cgi?id=871631#c2
Martin Vidner
Egbert, Stefan, what about the XCB errors? How severe are they? (BTW can a layperson decode the major/minor numbers to some identifiers?)
I don't know! These are extension errors. As long as Qt doesn't resolve the extension number there is no go on the nature of the error. But these errors are not the direct cause of the crash. Qt handles the errors somehow - and I've often seen Qt applications getting loads of X error events. Please note that those errors are not the result of a faulty behavior in Xlib/XCB/Xserver but are caused by some invalid X request.
There is some code to log the request that caused the error, but it is not compiled by default: https://qt.gitorious.org/qt/qtbase/source/1a31561178d9cb9e5a6f3f986075df24ea... I don't know whether enabling Q_XCB_DEBUG would help tracing these errors and what the performance impact would be. I also don't know where to find the matching extension. Maybe we should ignore this? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=871631
https://bugzilla.novell.com/show_bug.cgi?id=871631#c3
Max Lin
participants (1)
-
bugzilla_noreply＠novell.com