Compiz should not move windows to workspace 0,0 when restarted

Bug #980026 reported by Alan Griffiths
40
This bug affects 8 people
Affects Status Importance Assigned to Milestone
Compiz
Fix Released
Low
Alan Griffiths
Compiz Core
Status tracked in 0.9.7
0.9.7
Fix Released
Low
Alan Griffiths
compiz (Ubuntu)
Fix Released
Undecided
Alan Griffiths
Precise
Fix Released
Undecided
Alan Griffiths

Bug Description

[Impact]
No impact to regular users except possibly in how gracefully the system recovers from compiz crashes. Mainly impacts usability for developers who are starting and stopping compiz regularly. When compiz is closed down (typically as a result of replacing the window manager) it incorrectly dumps windows into the first workspace.

[Development Fix]
Revision 3092 of lp:compiz-core (in both 0.9.7 and 0.9.8 series). Defer call to window->windowNotify (CompWindowNotifyUnreparent) on shutdown.

[Stable Fix]
As above.

[Test Case]
1. Compile and run compiz-core from source.
2. Place windows on different workspaces (usually requiring compiz-plugins-main too).
3. Kill compiz gracefully (SIGTERM).
4. Restart compiz
5. Verify all your windows have not moved to workspace 0.

[Regression Potential]
Low. This fix has been well tested for almost 2 weeks so far. Initially it did trigger a regression, bug 981703. However we found that this fix was not the root cause of that bug, only a trigger. That regression is also fixed in this same release - 0.9.7.8 & 0.9.8.0. So there are now no known regressions.

ORIGINAL DESCRIPTION:
When compiz is closed down (typically as a result of replacing the window manager) it incorrectly dumps windows into the first workspace.

Changed in compiz (Ubuntu):
assignee: nobody → Alan Griffiths (alan-griffiths)
Changed in compiz-core:
status: New → In Progress
assignee: nobody → Alan Griffiths (alan-griffiths)
importance: Undecided → Low
milestone: none → 0.9.7.8
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Is this possibly related to bug 804036?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Fix committed into lp:compiz-core at revision 3092

Changed in compiz-core:
status: In Progress → Fix Committed
Revision history for this message
Alan Griffiths (alan-griffiths) wrote :

> Is this possibly related to bug 804036?

Doesn't seem like it (at least the fix for this isn't a fix for that).

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Fix reverted in lp:compiz-core at revision 3093. It was causing regression bug 981703.

Changed in compiz-core:
status: Fix Committed → Triaged
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Fix re-committed into lp:compiz-core at revision 3097. The regression bug 981703 has now been resolved properly.

Changed in compiz-core:
status: Triaged → Fix Committed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Fix released in Compiz Core 0.9.7.8.

description: updated
Revision history for this message
Martin Pitt (pitti) wrote : Please test proposed package

Hello Alan, or anyone else affected,

Accepted compiz into precise-proposed. The package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Changed in compiz (Ubuntu Precise):
status: New → Fix Committed
tags: added: verification-needed
Revision history for this message
jhfhlkjlj (fdsuufijjejejejej-deactivatedaccount) wrote :

It's not fully functional. I've put maximized firefox in 0,0 - a terminal in 0,1 - nautilus in 1,0 - and system settings in 1,1. All stayed there except the terminal (which moved to 0,0 on compiz --replace). The terminal moves back to 0,0 no matter what workspace I put it on.

Further, if I use compiz --replace while on a non-0,0 screen, it will move the windows randomly to different workspaces.

needless to say, it's half-baked.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I've found the same. Most of the windows-moving-workspaces-when-compiz-restarts bugs are still present for me.

But this particular bug is not important enough to care about if it fails SRU verification.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package compiz - 1:0.9.7.8-0ubuntu1

---------------
compiz (1:0.9.7.8-0ubuntu1) precise-proposed; urgency=low

  [ Didier Roche ]
  * New upstream bug fix release:
    - [fglrx] Title bar does not update on non-maximized windows (LP: #770283)
    - Some apps (like Remmina) can't full-screen under Compiz (or Unity)
      (LP: #946388)
    - Compiz-core fails to compile with gcc-4.7 - 'cc1plus: all warnings
      being treated as errors' (LP: #972519)
    - Menu shadow clipping flickers while switching menubar items/indicators
      (LP: #978900)
    - Compiz should not move windows to workspace 0,0 when restarted
      (LP: #980026)
    - regression / unable to interact with window-titlebar (window decoration)
      after minimizing/unminimizing gnome-terminal (LP: #981703)
  * debian/patches/workaround_770283.patch,
    debian/patches/fix_976467.patch:
    - removed, upstreamed

  [ Oliver Grawert ]
  * update the GLES2 patch for the new upstream release.

compiz (1:0.9.7.6-0ubuntu2) precise-proposed; urgency=low

  [ Łukasz 'sil2100' Zemczak ]
  * debian/patches/workaround_770283.patch:
    - Workaround a problem with fglrx not refreshing window decoration textures
      on pixmap modification (LP: #770283)

  [ Oliver Grawert ]
  * update GLES patch for new quilt patch, fix issue with GLES patch that
    forcefully unapplied other quilt patches and resulted in
    gtk-window-decorator to not be started.
 -- Didier Roche <email address hidden> Thu, 26 Apr 2012 09:19:51 +0200

Changed in compiz (Ubuntu):
status: New → Fix Released
Changed in compiz (Ubuntu Precise):
status: Fix Committed → Fix Released
Changed in compiz:
status: New → Fix Committed
importance: Undecided → Low
assignee: nobody → Alan Griffiths (alan-griffiths)
milestone: none → 0.9.8.0
no longer affects: compiz-core/0.9.8
Changed in compiz-core:
milestone: 0.9.8.0 → none
status: Fix Committed → Fix Released
Changed in compiz:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.