Summary: | plasmashell produces a lot of warnings in the journal | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Thiago Macieira <thiago> |
Component: | general | Assignee: | David Edmundson <kde> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | a.samirh78, aoudelet, auxsvr, plasma-bugs |
Priority: | NOR | ||
Version: | 5.19.2 | ||
Target Milestone: | 1.0 | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/plasma/plasma-workspace/commit/5aebd1a8c122a30f950582832ab3d6cf1bc978f7 | Version Fixed In: |
Description
Thiago Macieira
2020-07-15 20:31:21 UTC
Yeah...but we're stuck on how to nicely fix this, maybe you'll have some ideas. [320853.312257] plasmashell[2176]: file:///usr/lib64/qt5/qml/QtQuick/Controls/Styles/Plasma/BusyIndicatorStyle.qml:39:9: This is in frameworks, KDE frameworks has to support Qt 5.12 Qt 5.12 doesn't support the new connection syntax. We can't port the code, it'd break We can't just add an #ifdef as it's QML (well, not without some external pre-processing) I did add a faux Qt logging category so one can turn them off. My initial intention was I would just make Plasma ship an environment variable with that set, but it turns out that breaks other people's custom Qt logging rule files so I wasn't able to ship it. You have this as an option for yourself. Maybe I could maybe add QLoggingCategory::installFilter() into every applicable app? A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/156 (In reply to David Edmundson from comment #1) > This is in frameworks, KDE frameworks has to support Qt 5.12 > Qt 5.12 doesn't support the new connection syntax. > > We can't port the code, it'd break > We can't just add an #ifdef as it's QML (well, not without some external > pre-processing) Then please report this on the Qt bug tracker against QML. QML knows which version of things you imported, so it shouldn't warn about things you can't use in that version. Or any other solution the QML developers feel you should use. As a user, I don't care how this is solved. So long as it's solved. (cc me in the bug report or paste the link here so I can say so). > I did add a faux Qt logging category so one can turn them off. > > My initial intention was I would just make Plasma ship an environment > variable with that set, but it turns out that breaks other people's custom > Qt logging rule files so I wasn't able to ship it. You have this as an > option for yourself. > > Maybe I could maybe add QLoggingCategory::installFilter() into every > applicable app? Unclean solutions. But since we need to put up with existing releases of Qt, that might be needed. Git commit 5aebd1a8c122a30f950582832ab3d6cf1bc978f7 by Aleix Pol Gonzalez, on behalf of David Edmundson. Committed on 06/08/2020 at 10:56. Pushed by davidedmundson into branch 'master'. Fitler out annoying QML warnings Qt 5.15 introduces a new syntax for connections. Framework code can't port away due to having to support Qt5.12 which does not include the new syntax. This filters out the category. We should remove this once we depend on Qt5.15 in frameworks. M +18 -0 shell/main.cpp https://invent.kde.org/plasma/plasma-workspace/commit/5aebd1a8c122a30f950582832ab3d6cf1bc978f7 *** Bug 425051 has been marked as a duplicate of this bug. *** Nice, It will be for Plasma 5.19.5? Or 5.20 version of Plasmashell? What about: plasmashell [4788]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 43244, resource id: 56623518, major code: 141 (Unknown), minor code: 3 Does these warning be catched by your commit? No OK, so I will open a bug. FTR, reading the MR, for the fix to take effect one needs to be running Qt 5.15.1. |