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 571588 - restore to current workspace
restore to current workspace
Status: RESOLVED OBSOLETE
Product: gnome-panel
Classification: Other
Component: window list
2.26.x
Other Linux
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
: 586852 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-02-13 06:22 UTC by Matthias Clasen
Modified: 2020-11-06 20:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Description Matthias Clasen 2009-02-13 06:22:51 UTC 
Restore to current workspace does not work.

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.
Comment 1 Matthias Clasen 2009-02-23 19:58:51 UTC 
Not sure this deserves showstopper status, but it is pretty annoying...
Comment 2 Vincent Untz 2009-02-23 21:12:28 UTC 
Did it work in 2.24? Because there's absolutely no related change in the applet or in libwnck. It could well be a WM bug, in that case.
Comment 3 Vincent Untz 2009-02-23 21:17:14 UTC 
Also, does it work with wnckprop:

 + run wnckprop and click on a window to get its xid
 + move the window to another workspace and minimize it
 + do wnckprop --set-workspace=$NUM --unminimize --xid $XID (workspace number starts at 0)

Seems to work fine here, but I think the currently running metacity is 2.24.x.
Comment 4 Matthias Clasen 2009-02-23 21:59:57 UTC 
I think it is likely related to metacity changes in this area.

And no, wnckprop shows the same issue when running it on a window that is minimized on another workspace.
Comment 5 Owen Taylor 2009-11-17 23:10:21 UTC 
Presumably this broke when the changes in:

 https://bugzilla.gnome.org/show_bug.cgi?id=482354

Went in, since they changed "activating" a window not to hop workspaces unless
it was a transient window.

The right fix seems to involve two parts:

 A) The pager/libwnck needs to set the source indication properly in the 
    _NET_ACTIVE_WINDOW. Right now it is using the legacy/indeterminate 
    value of 0.

 B) Metacity should always hop workspaces when it gets a _NET_ACTIVE_WINDOW
    message with a value of 2 (from a pager)

The libwnck only fix would be to have the libwnck tasklist explicitly move of
the window it was activating to the current workspace.
Comment 6 André Klapper 2009-12-19 21:31:27 UTC 
*** Bug 586852 has been marked as a duplicate of this bug. ***
Comment 7 Rimas Kudelis 2010-02-07 20:37:22 UTC 
Is anyone working on this issue? It's really annoying...
Comment 8 André Klapper 2020-11-06 20:21:54 UTC 
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.

If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/gnome-panel/-/issues/

Thank you for reporting this issue and we are sorry it could not be fixed.