[REGRESSION] cannot switch to a given window after showing desktop

[v]

Using Unity Launcher to bring-up Terminal in order to switch between 6 terminal windows, clicking (or alt-tabbing) on the item will bring up the wrong window. When that happens, the next time you go through the selection process and click on the one you want, it will bring the window to the foreground, but it will be missing window decoration? or window titles, and borders.. etc

Screenshot provided.

[v (v-)]

Ubuntu 15.04 with Unity package version: 7.3.2+15.04.20150420-0ubuntu1

[v (v-)]

Here is how I was able to replicate it every time:

Launch Multiple Terminals through side launcher.
Click on "Show Desktop" on side launcher.
Click on Terminal icon on the side launcher.
Last active Terminal will appear (even though there are multiple Terminals).
Click on Terminal again, and terminal selection will appear.
Select Terminal other than the currently active Terminal.
The newly selected Terminal will blink, and disappear (another bug in itself or related?)
Click on Terminal again, and select the same terminal that just disappeared.
Terminal will re-appear, and will loose all borders, and menus.

[Gerry Boland (gerboland)]

Can you give more detail about your system setup?I'm aware you have multiple GPUs. Also what driver you're using?
This command also attaches useful info to this report:
    apport-collect 1483014

Thanks
-G

[v (v-)]

2x EVGA GTX970

$ lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 970] (rev a1)
03:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 970] (rev a1)

$ nvidia-settings -v
nvidia-settings: version 346.59 (buildd@toyol) Thu Apr 9 09:44:23 UTC 2015

[Gerry Boland (gerboland)]

I can repro using vivid, intel graphics

[v (v-)]

Not fixed. Similar problem. Two terminals.

Click on Show Desktop.
Click on Terminal.
Last Active Terminal shows up.
Click on Terminal Again.
Select a different terminal.
Last Active Terminal shows up.

[Andrea Azzarone (azzar1)]

The bug you are describing look similar to #1582056. Not sure why are you mixing the bugs. Which version are you running?

[v (v-)]

Sorry - you are right. I mixed them up again. :(