kwin(1258)/(default) KWin::Workspace::updateClientArea: screens: 1 desktops: 1 kwin(1258)/(default) KWin::Workspace::updateClientArea: Done. kwin(1258)/(default) KWin::Workspace::updateClientArea: screens: 1 desktops: 1 kwin(1258)/(default) KWin::Workspace::updateClientArea: Done. kwin(1258)/(default) QXcbConnection::handleXcbError: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 6049, resource id: 48236056, major code: 14 (GetGeometry), minor code: 0 kwin(1258)/(default) QXcbConnection::handleXcbError: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 6052, resource id: 48236056, major code: 14 (GetGeometry), minor code: 0 kwin(1258)/(default) QXcbConnection::handleXcbError: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 6055, resource id: 48236056, major code: 14 (GetGeometry), minor code: 0 kwin(1258)/(default) QXcbConnection::handleXcbError: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 6058, resource id: 48236056, major code: 14 (GetGeometry), minor code: 0 kwin(1258)/(default) QXcbConnection::handleXcbError: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 6061, resource id: 48236056, major code: 14 (GetGeometry), minor code: 0 kded5(1197)/(default) NetworkManager::Device::propertyChanged: virtual void NetworkManager::Device::propertyChanged(const QString&, const QVariant&) Unhandled property "AccessPoints" QPainter::end: Painter ended with 2 saved states QPainter::end: Painter ended with 2 saved states QPainter::end: Painter ended with 2 saved states QPainter::end: Painter ended with 2 saved states QPainter::end: Painter ended with 2 saved states QPainter::end: Painter ended with 2 saved states
This is just a non-fatal runtime warning that an XCB request failed. Unfortunately it's not possible to suppress those warnings properly without adding performance cost.
Unfortunately it is filling up my journal to the point that I have to use a script to delete those lines before the size explodes to several gigabytes every day...
Sorry, there's nothing we can do. The warning is thrown by Qt. Qt should use categorized logging so that it can be suppressed.
What about this here: http://blog.qt.io/blog/2014/03/11/qt-weekly-1-categorized-logging/ `LoggingCategory::setFilterRules("*.debug=false\n" "fc.io.debug=true");` Isn't that exactly what is needed? You can introduce your own logging categories and supress the default ones if I am not mistaken.
no, the problem is that Qt itself doesn't use categorized logging for these warnings.
I actually got rid of it by running: echo "QT_LOGGING_RULES='*.debug=false'" >> /etc/environment This disables all the QT debug logging though.
*** Bug 390403 has been marked as a duplicate of this bug. ***
*** Bug 441071 has been marked as a duplicate of this bug. ***
@Martin Flöser , @Nate : This might be a little hard before but now we are serving Qt with our community patches so couldnt we just add a filtre just for in QXcbConnection ? Or will it be fixed already in Qt6 ?
The rules of the community patch collection is that it can only contain accepted and merged patches for Qt6; we aren't making any other changes or bugfixes to Qt with it. So if someone fixes this in Qt6 (or finds that it is already fixed in Qt6), then we can add the patch for the fix into the patch collection, But otherwise, we cannot. Did anyone ever file a Qt bug report about this?
Ah, found it: https://bugreports.qt.io/browse/QTBUG-55167 Looks like it's marked as fixed in Qt 5.11.1. I wonder if it works.
Does not seem to be working for me. :( I left a comment in the upstream bug report.