After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 325929 - workspace change from keyboard gets screens confused
workspace change from keyboard gets screens confused
Status: RESOLVED DUPLICATE of bug 319423
Product: metacity
Classification: Other
Component: general
2.12.x
Other Linux
: Normal normal
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2006-01-05 23:49 UTC by Sebastien Bacher
Modified: 2006-01-06 00:38 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sebastien Bacher 2006-01-05 23:49:45 UTC 
That bug has been been open on http://bugzilla.ubuntu.com/show_bug.cgi?id=21628

"So I have a dualhead setup, with 2 video cards.  This is all set up fine in X11,
and the screens are :0.0 and :0.1

metacity 2.12.1-0ubuntu1 initializes itself on these screens ok.  However,
imagine I have workspaces laid out like:

Screen 0
[0 - window] [1 - window] [2 - window] [3 - window]

Screen 1
[0 - window] [1 - window] [2 - empty ] [4 - empty ]

If I'm on screen 1 workspace 1, and hit the keyboard shortcut for workspace 2,
then screen 1 will switch to workspace 2.

Now if I keyboard shortcut for workspace 1 again, screen 0 will switch to
workspace 1.  Screen 1 loses focus.

It's craziness!"
Comment 1 Elijah Newren 2006-01-05 23:59:38 UTC 
Oh, oops, I forgot to apply that patch to the stable branch.  Thanks for the reminder; I applied it just now.  Anyway, it's a duplicate.

*** This bug has been marked as a duplicate of 319423 ***
Comment 2 Sebastien Bacher 2006-01-06 00:11:33 UTC 
sorry for the duplicate, I read the other bug before filling that one but since the descriptions was not the same it was not clear duplicate or not :)
Comment 3 Elijah Newren 2006-01-06 00:38:35 UTC 
no problem; it reminded me that I forgot to to apply to patch to stable when I really had meant to.  And I fully understand how it's difficult to recognize these as duplicates considering the different wording (I had problems determine whether some of the other dupes of that bug really were dupes before someone mailed me a 2nd monitor and videocard so I could try it out and investigate the problem).