Summary: | DEMANDS_ATTENTION remains on even after URGENT hint removed by app | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Michael Tharp <gxti> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | annma, deryni |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
xprop -spy full log of error
xprop -spy annotated log of error xprop -spy where the bug happened much more quickly xprop -spy _NET_WM_STATE WM_HINTS where the bug happened much more quickly |
Description
Michael Tharp
2006-03-11 01:27:14 UTC
Created attachment 17858 [details]
xprop -spy full log of error
Created attachment 17859 [details]
xprop -spy annotated log of error
Some repetitive middle bits were taken out.
I have also experienced this bug with Gaim 1.5.1cvs and earlier versions, as well as the mentioned Beta2. Gaim developer Etan Reisner (irc deryni) went over the window manager hints log with me and confirmed that this has to do with gaim setting the urgency hint, but gaim seems to be removing the hint correctly. I'm attaching the "xprop -spy WM_HINTS _NET_WM_STATE" logs I took when this error occured: one is the full log, and the other is an annotated version with some of the intermediate repetitions taken out. Wrong component. I tested this bug and found that this is a problem of kwin. Even using Gnome, as soon as I replaced metacity with kwin, this bug occurred. Created attachment 18255 [details]
xprop -spy where the bug happened much more quickly
Shows xprop -spy on the window in question where the bug happened on the second
try.
Created attachment 18256 [details]
xprop -spy _NET_WM_STATE WM_HINTS where the bug happened much more quickly
Ran xprop -spy _NET_WM_STATE WM_HINTS on the window in question; bug happened
on the second try.
Just wanted to mention this problem still exists on KDE 3.5.5 on i386 installed from ubuntu (edgy) packages, to which I recently upgraded. The bug was reported for a somewhat unusual configuration; just wanted to say it exists on less esoteric setups as well. Met Arrenlex on IRC said it's a non-issue and I can close so closing! He also talked to Zarin. |