Bug 166490

Summary:	Windows do not restore to native workspace
Product:	[Fedora] Fedora	Reporter:	Sumit Khanna <sumdog>
Component:	gnome-applets	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED DUPLICATE	QA Contact:	Mike McLean <mikem>
Severity:	low	Docs Contact:
Priority:	medium
Version:	4	CC:	d.bz-redhat, rosen.nedialkov
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-09-08 15:05:18 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sumit Khanna 2005-08-22 14:17:34 UTC

Description of problem:

Even when the option "Restore window to native workspace" is selected on the
Window List applet, the window is restored to the current workspace.

Version-Release number of selected component (if applicable):
Fedore Core 4

How reproducible:
Every time

Steps to Reproduce:
1. Right click window list applet 
2. Select "Restore to native workspace"
3. Attempt to restore a window on another workspace
  
Actual results:
Window is placed on current workspace

Expected results:
Window should be placed on native workspace

Additional info:

Comment 1 Didier 2005-09-06 12:07:49 UTC

Confirmed ; please note that this worked in the past (on FC4). It was not only
until recently (approx. 8-14 days ago), that this bug showed up.

Unfortunately, gnoeme-panel-2.10.1-10.2 dates from july 26th, and I am (almost)
certain the erroneous behaviour started occuring more recently, indicating a
change in a dependency being the culprit ?

Comment 2 Didier 2005-09-07 09:29:43 UTC

Reverted back to gnome-panel-2.10.1-10 and tested with a new user account (as to
avoid contaminated GConf settings) : the erroneous behaviour still occurs.

Any hint about which recently updated packages (FC4 Updates/Extras) may have
ignited this bug ?

Comment 3 Rosen Nedialkov 2005-09-08 13:51:41 UTC

Isn't this a bug in metacity?
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=165658

Comment 4 Sumit Khanna 2005-09-08 15:05:18 UTC


*** This bug has been marked as a duplicate of 165658 ***