When Unity is loaded, expo exits to the workspace being pointed at (not the one highlighted)

[Vincent Ladeuil]

Since I upgraded to quantal I encounter the following issue:
- press Super+S to quickly find the relevant workspace I want to go,
- realize I'm in the right one
- press Super+S again to come back to the normal display

Oops, the workspace is switched to where the mouse pointer is.

This happens only when pressing Super+S twice. If instead I press escape or navigate with direction keys and press return or click to the target workspace (obviously ;), I'm switched to the correct workspace.

[Vincent Ladeuil (vila)]

The attached branch reproduces the issue with an autopilot test.

[Marco Biscaro (marcobiscaro2112)]

Confirmed. It's easily reproducible.

[Vincent Ladeuil (vila)]

Ping, can we have some feedback here ? (And happy Christmas ;)

[John Swing (john-swing)]

Hello,

For me it isn't a bug, I use everyday Super+S and the mouse cursor to switch workspace :

- I press Super+S
- I keep the Super key down, move my mouse cursor to the desired workspace
- I press S and the desired workspace comes up.

I think it's the smoothest way to change workspace, with this way I don't have to click on the desired workspace I just move my cursor and S again.

I don't understand why you think of it as a bug.

John

[Daniel van Vugt (vanvugt)]

In a duplicate I mentioned:
This bug does not exist in upstream Compiz. It only seems to happen when the unityshell plugin is loaded. Hence assigned to Unity.

[Vincent Ladeuil (vila)]

@John: You do:
- press super-S
- *move* the cursor
- press super-S

I do:
- press super-S
- press super-S

I don't expect the workspace to change if I'm not moving my cursor.

It's also a regression in behaviour from the previous release which is why I reported it. *I* can adapt and stop pressing super-S twice but I think it's an unexpected (and confusing) behavior.

[John Swing (john-swing)]

@Vincent

I understand that if you don't move your cursor you don't expect the workspace to change, but one never only do :
- press Super-S
- press Super-S
because it's supposed to do nothing, I think one do :
-press Super-S
-move between workspace with directions key
-press enter
OR
- press super-S
- *move* the cursor
- press super-S

The workspace switcher is like its name says a workspace *switcher*. In my opinion it would be a bad idea to remove a useful behavior to correct a bug in a situation where you use the workspace to do nothing.

John

[Omer Akram (om26er)]

That must be related to the compiz patch that adds the glow and stuff to the switcher, wondering who should we poke, Sam ? :)

[Daniel van Vugt (vanvugt)]

Omer,

I have tested upstream expo with the Ubuntu patch. This bug does not happen there. It only happens when unityshell is also loaded.

[Vincent Ladeuil (vila)]

@John: I think you miss my point, *I* do super-S twice. I do it because sometimes I'm searching for the right workspace to switch to or because I'm searching for an empty one. And one can imagine that people will also do the double super-S when discovering the feature.

And sometimes, well, I just change my mind and decide to stay on the same workspace.

Before reporting this bug I checked that any action that lead to a workspace change is not affected (using the mouse, the arrow keys, leaving the expose mode with Escape, whatever, that's what I use to workaround the issue) and focused this bug report on the do-nothing case.

I'm not asking to change the behaviour when the cursor is moved.

[Stephen M. Webb (bregma)]

Here's an interesting thing.

I have a two-monitor setup. I can reproduce this bug on monitor1 (the leftmost monitor, the one built in to my laptop), but it does not obtain on monitor 2 (an external monitor).

Curious, no? Perhaps a clue.

[Bruno Nova (brunonova)]

I was affected by this bug until Saucy.
But I'm not affected by it in Trusty (I have not checked Utopic).
Maybe it's fixed now?

[Andrea Azzarone (azzar1)]

Seems to work fine here. Can you still reproduce it?

[Bruno Nova (brunonova)]

@Andrea, no, I can't reproduce it in Trusty anymore (also checked a Utopic VM).
It seems to have been fixed. Maybe you should mark it as "Fixed Released"?

Offtopic: Andrea, could you, or anyone else, check bug #1393523 (also about Expo) and possibly triage it?