Workspaces on Gutsy switch incorrectly using Compiz with left over Feisty settings
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
Binary package hint: compiz
I am running dual monitors using Nvidia Twinview with 2 workspaces. With compiz disabled workspaces work as expected. Enabling Compiz causes some odd behavior switching workspaces.
To reproduce:
1. Enable Compiz with Appearances applet.
2. I didn't make any changes to Gconf for Compiz, but my hsize is set to 2, number of desktops 1, vsize 1.
3. On workspace 1 open 2 terminals.
4. Move one terminal to workspace 2(to the workspace on the right)
5. Using the mouse and Workspace Switcher in the panel, switch between the 2 workspaces. It should switch correctly.
6. Go back to workspace 1(on the left)
7. Try using the keyboard to switch to the right workspace. Instead of switching the "cube" animation will run, but the workspace will stay on 1(left).
8. With workspace 1(left) still in view, use the keyboard toswitch to workspace left(since we have 2 workspaces this will be workspace 2"right"). The "cube" animation should run and workspace 2 will be correctly displayed.
9. Now on workspace 2, from the keyboard try to switch again to workspace left(should take us back to workspace 1). The cube animation should run, but we end up still on the same workspace(2).
10. Still on workspace 2 try going to workspace right. The "cube" animation runs and we are switched to workspace 1 correctly.
11. Now for even more weirdness. On workspace 1 using the keyboard very quickly issue 2 commands to switch to workspace right. The "cube" animation will run and we correctly get switched to workspace right. The same thing happens if you quickly issue 2 workspace left commands from the keyboard(it works correctly).
I hope my explanation make sense. It's kind of hard to describe what I'm seeing,
Changed in compiz: | |
importance: | Undecided → High |
status: | New → Confirmed |
I just verified that I have the same issue on a single monitor system(still nvidia no twinview).