Bug 24865 - plasmashell spewing lots of qt.qpa.xcb errors
Summary: plasmashell spewing lots of qt.qpa.xcb errors
Status: RESOLVED DUPLICATE of bug 26900
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-24 17:02 CEST by w unruh
Modified: 2020-12-30 16:45 CET (History)
3 users (show)

See Also:
Source RPM: plasma-workspace-5.15.4-1.mga7.x86_64
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description w unruh 2019-05-24 17:02:30 CEST 
Description of problem: About every 10 seconds or less (sometimes up to 10 a second) an error is created 
May 24 15:46:25 localhost plasmashell[30120]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 43244, resource id: 56623518, major code: 141 (Unknown), minor code: 3

I have no idea what this means, but it is filling the log files. 






Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
Comment 1 w unruh 2019-05-24 17:06:22 CEST 
10000 instances in 5 days.
Marja Van Waes 2019-05-24 18:14:38 CEST

Assignee: bugsquad => kde
CC: (none) => marja11

Comment 2 Jüri Ivask 2019-05-31 08:23:04 CEST 
I'm also seeing such messages filling the log, but here they are somehow related to plasma desktop freezes. See bug 24841.

CC: (none) => jyri2000

Comment 3 w unruh 2020-06-27 00:55:30 CEST 
Still doing it with new install and update of 7.1 on Asus ux333
2700 messages in 16 hrs.

Version: Cauldron => 7

Comment 4 Aurelien Oudelet 2020-07-07 00:08:41 CEST 
26900 related?

CC: (none) => ouaurelien

Comment 5 Aurelien Oudelet 2020-12-30 16:45:12 CET 
This is a duplicate.
Sorry if this is more ancient than those in 26900, but fix proposed here is for other annoying qt logging bug.

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

Resolution: (none) => DUPLICATE
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.