https://bugs.kde.org/show_bug.cgi?id=366421
Martin Gräßlin <mgraess...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |UPSTREAM
Status|UNCONFIRMED |RESOLVED
--- Comment #3 from Martin Gräßlin <mgraess...@kde.org> ---
> Now, whether it's worth treating the symptom (hide the warning), or the
> disease (the cause for the warning)?
We can only treat the symptom. We don't know where the GetGeometry call fails
(multiple locations in KWin) and the event does not tell us either. KWin always
uses the calls which report errors on the event loop as all calls are allowed
to fail. From KWin side it can always happen that a call fails: that's just in
the nature of a window manager. If KWin processes events when the window got
destroyed, calls like GetGeometry will fail (as the window is gone). We had
looked into this once and concluded that trying to not get the errors (e.g.
grab server) will result in much worse situations than just having the calls
fail.
The correct thing to do would be introduce categorized logging in Qt's xcb
plugin, so that the warnings can be filtered out.
--
You are receiving this mail because:
You are watching all bug changes.
