Comment #1 on issue 381 by allbery.b: lack of NETWM compliance triggers Qt bug http://code.google.com/p/xmonad/issues/detail?id=381 That sounds like a bad idea except possibly as a contrib module marked specifically as "hack for broken Qt", because advertising but ignoring those messages could well break other programs. On the other hand, the fix in Qt would be ugly but compatible: retrieve the _NET_VIRTUAL_ROOTS (if not in _NET_SUPPORTED, use the root window(s) for all managed screens directly) and then walk the tree of children of these windows to see if they have frame windows. If it happens that no such windows exist, track what happens when creating the first window and remember it. The *real* fix for this is for the EWMH spec to include a _NET_REPARENT atom in _NET_SUPPORTED (value boolean), thus allowing random programs to discover if the window manager reparents without any hackery. One would think that, with the number of programs that behave oddly if they don't know the current wm is reparenting (note the hardcoded wm list in the JRE and some other environments), someone would have considered this already. -- 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