[xmonad] Issue 200 in xmonad: xmonad spins in a tight loop changing focus back and forth

[codesite-noreply at google.com]

Issue 200: xmonad spins in a tight loop changing focus back and forth
http://code.google.com/p/xmonad/issues/detail?id=200

Comment #5 by k.kosciuszkiewicz:
I have some further findings, obtained by logging Events using EventHook.

After switching focus from floating "Open File" dialog window to main OO  
window, I
recorded a repeating sequence of events (fields abbreviated/omitted):

PropertyEvent {send_event = False, window = ...75, atom = 141, time = ...31,
propstate = 0}
PropertyEvent {send_event = False, window = ...07, atom = 141, time = ...31,
propstate = 0}
PropertyEvent {send_event = False, window = ...75, atom = 141, time = ...42,
propstate = 0}
PropertyEvent {send_event = False, window = ...07, atom = 141, time = ...42,
propstate = 0}

xlsatoms shows that atom 141 == WM_STATE, and Xlib programming manual says:
"According to ICCCM adopted as of Release 4, the window manager sets this  
property on
top level windows".

I guess that OO spins idle trying to identify the top-level window, without  
being
prepared for failure... Arguably this is a bug in OO rather than in xmonad,  
but
probably proper handling of WM_STATE on xmonad's side wouldn't hurt.



-- 
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings