← Back to team overview

compiz team mailing list archive

[Bug 980026] Re: Compiz should not move windows to workspace 0, 0 when restarted

 

** Description changed:

- When compiz is closed down (typically as a result of replacing the
- window manager) it incorrectly dumps windows into the first workspace.
+ [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.

-- 
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/980026

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz-core/+bug/980026/+subscriptions


References