Bug 1655961 - qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), ....
Summary: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), ....
Alias: None
Product: Fedora
Classification: Fedora
Component: qt5-qtbase
Version: 28
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2018-12-04 10:34 UTC by Peter Tselios
Modified: 2019-05-28 23:24 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-05-28 23:24:59 UTC
Type: Bug

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1497564 0 unspecified CLOSED QXcbConnection: XCB error: 2 (BadValue), sequence: 34905, resource id: 16777232, major code: 141 (Unknown), minor code: ... 2021-02-22 00:41:40 UTC

Description Peter Tselios 2018-12-04 10:34:37 UTC
Description of problem:
It's crystal clear that this is not a Fedora related bug since it's an issue with the upstream QT. However, the related bug (Bug 1497564) is supposedly fixed for Fedora 27. 
Thus, I kindly request to implement it for Fedora 28 as well. 

So, in brief: QT libraries fill the log files with completely useless for the end user error messages. 

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

How reproducible:

Steps to Reproduce:
1. Start a KDE session
2. Monitor the /var/log/messages. 
3. Move the mouse over the notification area (for example). Log will be filled with those messages. 

Actual results:

Expected results:
No logs. 

Additional info:

Comment 1 Ben Cotton 2019-05-02 20:10:57 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Ben Cotton 2019-05-28 23:24:59 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.