GNOME Bugzilla – Bug 445835
KDE apps demand attention after workspace switching
Last modified: 2007-06-10 16:13:11 UTC
Please describe the problem: When switching workspaces, partially overlaid KDE application windows get the "_NET_WM_STATE_DEMANDS_ATTENTION" flag set. For example see the following debug output leading to the call of meta_window_set_demands_attention: _NET_ACTIVE_WINDOW message sent for 0x1000012 (0 - KCalc) at time 2032604 by client type 1. last_user_time (2075379) is more recent; ignoring _NET_ACTIVE_WINDOW message. Marking 0x1000012 (0 - KCalc) as needing attention The timestamp for the _NET_ACTIVE_WINDOW message is always the same, on each workspace switch. Steps to reproduce: 1. You need at least two workspaces (1 and 2) 2. Open a KDE application and another application on the first workspace. Make sure the other application overlays the KDE one at least partially. 3. Make sure the mouse pointer is not over the KDE application when using "focus follows mouse", then switch to workspace 2 4. Switch back to workspace one. Actual results: The KDE application should be flashing in the window list because their "_NET_WM_STATE_DEMANDS_ATTENTION" is set. Expected results: The KDE application should not be flashing in the window list as there is no reason to demand attention. Does this happen every time? Yes, but only with KDE applications. Other information: I am actually not sure yet if thats a metacity or KDE specific problem, although I only see it with metacity, so any hints or requests for more debug are appreciated.
Confirming. What I want to know is why KDE apps are sending a _NET_ACTIVE_WINDOW on workspace switching. I'll investigate.
The people on #kde-devel tell me to contact the kwin people, who will apparently be able to explain things better than anyone else. Here goes.
http://lists.kde.org/?l=kwin&m=118141987904513&w=2
Additional note as the question might come up: does not happen with QT apps (without KDE libs), only with actual KDE applications.
Before running into problems (X crashing when I add too much debug output) I found that the according meta_window_activate_with_workspace is called from reload_net_startup_id in window.c for the offending KDE app window.
(In reply to comment #4) > Additional note as the question might come up: does not happen with QT apps > (without KDE libs), only with actual KDE applications. That's very much worth knowing: thanks.
Oh, there's an older bug I didn't know about, and this is a duplicate. *** This bug has been marked as a duplicate of 400167 ***