Red Hat Bugzilla – Bug 137730
Window List does not list windows on second head when using Twinview
Last modified: 2007-11-30 17:10:53 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041016
Description of problem:
When configured to "display windows from all workspaces", the Window
List applet does not display the names of windows on the 2nd head of a
system set up with Twinview. If you drag the window from the 2nd head
to the 1st head, the window title appears when you drop the window.
For the purposes of this explanation, "1st" head refers to the head on
which the panel is placed. The two heads are combined into one
spanning desktop (i.e., windows can stradle the border between the two
heads. Interestingly enough, the window only shows up in the Window
list when the window is more than half on the 1st head.
Also interesting -- if you put a panel on the 2nd head, all windows --
regardless of head -- are listed!
After doing a "killall -HUP gnome-panel", the window lists are still
out of sync, but the 1st head has all windows listed, and the 2nd head
is missing windows on the 1st head.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set up a dualhead display using Twinview
2. Put a panel on both heads, put a Window List applet on both heads
3. Set both panels to display windows from all workspaces.
4. Open windows on both heads, move them around a bit
Actual Results: The panels get out of sync.
Expected Results: The panels should always agree.
I would like to claim that this should be raised to "high" severity,
meaning crash or data loss, based on the following scenario:
1. Open a document in 2nd monitor (e.g. word processor)
2. Enter lots and lots of important information
3. Accidentally click the "minimize" icon.
Hey, where did my window go? The window has been minimized but is not
visible anywhere. The only way I've been able to find, to restore it,
is to use alt-tab. But many users don't know about this feature. To
them, this scenario is data loss.
This looks like a dup of bug #138874
*** This bug has been marked as a duplicate of 138874 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.