Bug 484842

Summary: Window List cannot restore window to current workspace
Product: [Fedora] Fedora Reporter: Cao, Chen <kcao>
Component: gnome-panelAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 11CC: beland, jslavin, mclasen, ndai, rstrode, yzhou
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-01-05 21:02:19 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Cao, Chen 2009-02-10 04:05:13 EST
Description of problem:
Window List cannot restore the windows in another workspace 
to current workspace.

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

How reproducible:
100% reproducible.

Steps to Reproduce:
1. make sure there is a window list on the panel.
2. set the properties of the Window List by right click on the 
left part of the window list and choose 'Preferences'.
3. set 'Window list content' to 'show windows from all workspaces'.
4. set 'restoring minimized windows' to 'restore to current workspace'
5. open gedit in workspace 2, minimize gedit. and go to worspace 1.
6. left click the icon of gedit in the window list on the panel.

Actual results:
the program (gedit) cannot be restored. the lable (or icon) of program, 
which is in the window list, just blinks.

Expected results:
the program (gedit) can be restored in the current workspace.

Additional info:
uname -r 
Comment 1 Matthias Clasen 2009-02-13 01:24:11 EST
Comment 2 Matthias Clasen 2009-02-13 01:59:50 EST
*** Bug 484172 has been marked as a duplicate of this bug. ***
Comment 3 Bug Zapper 2009-06-09 07:12:15 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
Comment 4 Christopher Beland 2010-01-05 21:02:19 EST

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