Super-W shows vanishing windows the first time you hit it. Windows fly off the screen instead of spreading.

In addition, the window that had focus when I hit super-w this first time now appears to be inaccessible. It shows up in Alt-` listings, and I can give it focus. When it has focus, I can click on my nautilus desktop and still get menus for this window. I suspect that it has fallen behind nautilus's root window analogue.

Status changed to 'Confirmed' because the bug affects multiple users.

I can't reproduce the issue here, with unity-5.6.0 up to date.
Maybe this is specific to a driver (Intel). I'm running on radeon here.

Can you please make a video of the problem you are facing?

Here's a video showing the "vanishing windows" effect.

And here's a video showing the "invisible window" effect we think is related to this bug. (No otters were harmed in the making of this video.)

Uh, that hurts :/

In the end, the otters didn't particularly look like Benedict Cumberbatch: http://emmark.info/otter/

Upon reflection, however, David Mitchell is absolutely a Koala: http://davidmitchellisakoala.tumblr.com/

I can confirm that here, quite "scary" in some way, it's easy to reproduce this way
- start a session
- click on nautilus on the launcher
- ctrl-alt-right to go to ws2
- click on nautilus
- ctrl-alt-left to go to ws1
- super-W

it does it most of the time here with those steps

Daniel, Alan, do you think that's something you could look at? It seems a bug that should be fixed in a SRU, the effect can be quite disturbing the first time you seem it

Can we consider this related to bug 933776?

This issue happens to me not only the first time I hit Super+W but it bites me later as well. I am actively using 4 workspaces if that matters.
I regularly lose windows as described in comment #2 and I have to run 'compiz --replace &' to get them back without having to close the applications but then my windows get mixed up between workspaces so not a very convenient workaround.

Fix committed into lp:compiz at revision 3271

Fix committed into lp:compiz-core/0.9.7 at revision 3110

12.04 LTS packages for testing at https://launchpad.net/~timo-jyrinki/+archive/compiz-precise-sru - please give feedback.

Tested Timo's PPA and all looks good. I don't get the flying windows problem anymore.

Using Timo's ppa Super+W for spreading all windows works fine here.

Alan Pope:
> Tested Timo's PPA and all looks good. I don't get the flying windows
> problem anymore.

This is all well and good, but did the otters look like Benedict
Cumberbatch?

--
Nick Moffitt

This bug was fixed in the package compiz - 1:0.9.8+bzr3319-0ubuntu1

---------------
compiz (1:0.9.8+bzr3319-0ubuntu1) quantal-proposed; urgency=low

  [ Didier Roche ]
  * debian/patches/ubuntu-config.patch:
    - refresh with latest trunk
  * debian/*docs:
    - remove the TODO copy now removed upstream
  * debian/compiz-plugins.install:
    - install stackswitch, trip plugins
  * debian/rules, debian/control:
    - remove the compiz gnome-control-center key sedding through metacity.
      Compiz now directly ships them.
    - we do not need metacity-common anymore as a build-dep then
  * debian/compiz-gnome.migrations, debian/control:
    - build-dep on dh-migrations and ship gconf -> gsettings migration file

  [ Matthieu Baerts (matttbe) ]
  * Update apport hook for python3 ; thanks to Edward Donovan (LP: #1013171)

  [ Timo Jyrinki ]
  * New upstream snapshot.
    - Fix Compiz crash in movementWindowOnScreen (LP: #1015151)
    - Start window decorator when decor plugin starts (LP: #1014461)
    - Fixed: Crash in compiz::wall::movementWindowOnScreen (LP: #1015151)
    - Don't waste memory leaving /bin/sh running (LP: #1015422)
    - Add reliable detection of the compiz bin directory (LP: #1015898)
    - Check if the window would actually paint before painting the shadow,
      since it is possible that another plugin could be inhibiting paint of
      the dock window. (LP: #1012956)
    - Don't insert the window into the server list above the window it was
      created above. (LP: #1008020) (LP: #886605)
    - makes compiz enhanced zoom and show mouse plugins considerably
      smoother to use (LP: #930783)
    - Don't set decoration contexts on undecorated windows, since that
      might be read later and code will assume the window is decorated when
      it isn't. (LP: #1015593)
    - Fix potentially unterminated string leading to an uninitialized memory
      read (LP: #1018302)
    - Lift the 31/32 character restriction on key names that was causing so
      many warnings. It's now 1024 characters according to glib. (LP: #1018730)
    - Don't print the result of BUILD_DEB. It prevents ccsm et al from
      installing. (LP: #1018916)
    - Use the XDamage extension more efficiently (the way it was designed to be
      used). This dramatically reduces CPU usage, reduces wakeups, and
      increases frame rates. It also solves at least one observed performance
      bug (LP: #1007299) and probably several more.
    - Do the initial work to get libcompizconfig under test. (LP: #990690)
    - Add support for initiating window picker in other than nomal mode. For
      now added only the additional 'All windows' picker (LP: #933776)
      (LP: #955035)
    - Fixes (LP: #1018602) : An invalid read when using g_variant_iter_loop.
    - Don't allow unbinds of textures kept around for animations in any case,
      not just resizing. (LP: #1016366)
    - Wait for the server to finish processing requests before doing a bind
      (LP: #1016367)
    - Using the next/previous bindings the wall plugin didn't calculate
      correctly the next workspace when it reaches the begin or the end of a
      row of workspaces, so it didn't jump to the n...

I think Nick Moffitt has either lost his marbles or his account has been hijacked...

Hi, the package has been uploaded to quantal-proposed, but the fix was manually excluded from the precise-proposed upload because:

  * debian/patches/revert_fix_933776_955035.patch:
    - Cherry-pick the revert from upstream since the bug fix is not
      suitable for SRU as is

Is there any extra information about this not being "suitable as is", and how to make it suitable?

Margarita: you can read on the problematics of the fix in the lenghty discussion of bug #933776. If this bug could be fixed separately from that bug, it'd be acceptable for a SRU even if the #933776 would remain unfixed for a longer time than this.

Marked the upstream bug as unfixed, since the patch was also reverted there.

Timo, I think the issue in this bug is definitely different from bug #933776 since irrespective of the keyboard shortcut used, the vanishing window appears. I seriously hope this bug is dealt separately and becomes available as a SRU. This vanishing window has been present on precise for almost 9 months now. Please let it land as an SRU considering the fix is already available in code.

@Timo, that said can I just install compiz from your ppa despite it being an older version than what is currently offered as an update?

Timo, thanks for the reply, I've been reading the discussion in the other bug, and I had a look at the code and the reverted patch.

I'm not sure how the other patch actually fixed this issue. The code for "layoutThumbsAll" looks much simpler than the current "layoutThumbs", and nothing seems to be explicitly done to prevent this problem. I'm guessing that the problem that causes this bug is in this piece of complex code, which is not present at all in the other one:

    for (std::map<ScaleWindow *, ScaleSlot>::iterator it = slotWindows.begin ();
         it != slotWindows.end (); it++)
    {
        slots.push_back (it->second);
        windows.push_back (it->first);
        it->first->priv->slot = &slots.back ();
        it->first->priv->slot->setX (it->first->priv->slot->x () + (it->first->priv->window->defaultViewport ().x () - screen->vp ().x ()) * screen->width ());
        it->first->priv->slot->setY (it->first->priv->slot->y () + (it->first->priv->window->defaultViewport ().y () - screen->vp ().y ()) * screen->height ());
    }

But I don't see where exactly the problem lies.

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release