After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 318306 - metacity crashes when removing workspaces with windows
metacity crashes when removing workspaces with windows
Status: RESOLVED FIXED
Product: metacity
Classification: Other
Component: general
trunk
Other Linux
: High normal
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
: 330801 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-10-08 23:13 UTC by Elijah Newren
Modified: 2006-02-11 15:54 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Remove the window, then add it (can't have windows on more than one workspace) (602 bytes, patch)
2005-10-08 23:15 UTC, Elijah Newren 		committed Details | Review

Description Elijah Newren 2005-10-08 23:13:57 UTC 
Looks like this was a side-effect of the patch in bug 156182; interesting that
no one appears to have run across it until now (I only did because I was trying
to test the patch in bug 151183).  Anyway, the patch is trivial and I'll attach
it momentarily.
Comment 1 Elijah Newren 2005-10-08 23:15:51 UTC 
Created attachment 53243 [details] [review]
Remove the window, then add it (can't have windows on more than one workspace)
Comment 2 Elijah Newren 2005-10-08 23:22:25 UTC 
Since I believe this qualifies as an obvious fix, I commited this patch to both
HEAD and gnome-2-12.

2005-10-08  Elijah Newren  <newren@gmail.com>

	Fix a crash that occurs when removing some virtual desktops and
	windows happen to be on those desktops.  #318306.

	* src/workspace.c (meta_workspace_relocate_windows): Since windows
	cannot be on more than one workspace at a time, remove the window
	from the old workspace before adding it to the new one.
Comment 3 Elijah Newren 2006-02-11 15:54:44 UTC 
*** Bug 330801 has been marked as a duplicate of this bug. ***