Ubuntu
gnome-panel package

window list restore to current workspace does not work

Bug #216049 reported by Miek Gieben
34
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Metacity
New
Medium
OpenBox
Incomplete
Undecided
Unassigned
gnome-panel (Fedora)
Invalid
Medium
gnome-panel (Ubuntu)
Incomplete
Low
Unassigned
Nominated for Hardy by Jesse Gilles
Nominated for Jaunty by Jamin W. Collins
Nominated for Karmic by komputes
metacity (Fedora)
Won't Fix
Medium
metacity (Ubuntu)
Incomplete
Low
Ubuntu Desktop Bugs
Nominated for Hardy by Jesse Gilles
Nominated for Jaunty by Jamin W. Collins
Nominated for Karmic by komputes
openbox (Ubuntu)
Incomplete
Undecided
Unassigned
Nominated for Hardy by Jesse Gilles
Nominated for Jaunty by Jamin W. Collins
Nominated for Karmic by komputes

Bug Description

Binary package hint: gnome-panel

In the window list applet I can observe the following behavior:
(this is on hardy with AMD64)
- set the preference to: 'restore to current workspace'
- minimize a window
- try to restore the window in a different workspace

It will not work, instead the window in the window list will just flash and do nothing. Only when you
click on the minimized window in the correct workspace will it restore.

Revision history for this message
In , Edmond (edmond-redhat-bugs) wrote :

Description of problem:

hidden window is unable to restore to current workspace

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

Window List 2.20.1

How reproducible:

Every time

Steps to Reproduce:
1. Goto Window list preferences and set "Restore to current workspace", and
"Show windows from all workspace"
2. Minimize a window
3. Move to another workspace
4. click at the minimized windows from window list

Actual results:

The window is not restore to current workspace

Expected results:

The window is restored, and move to the current workspace

Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue could be due to the recent window-manager change

Changed in metacity:
importance: Undecided → Low
Revision history for this message
Kelvin Gardiner (kelvingardiner) wrote :

I can confirm this on Hardy AMD64. Status changed to confirmed.

Changed in metacity:
status: New → Confirmed
Revision history for this message
Jamin W. Collins (jcollins) wrote :

I've been annoyed by this same behavior since upgrading to Hardy. Note: this is happening with the x86 (32-bit) version as well.

Revision history for this message
Tchalvak (tchalvak) wrote :

Yep, same for me, Hardy AMD64.

Since clicking to restore doesn't work from another desktop, you end up actually having to cycle through your workspaces clicking to restore to find which workspace the minimized window is living in.

Revision history for this message
In , Bug (bug-redhat-bugs) wrote :

This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 8 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Revision history for this message
Filip Dąbek (filedil) wrote :

It seems this bug is still unfixed in Intrepid. I can only unminimize a window on it's workspace, which makes this option quite broken.

Revision history for this message
In , Bug (bug-redhat-bugs) wrote :

Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.

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

Revision history for this message
In , Edmond (edmond-redhat-bugs) wrote :

still seeing this problem on F10

Revision history for this message
Pedro Villavicencio (pedro) wrote :

this seems to be fixed on jaunty, may someone else confirm it? thanks.

Changed in metacity:
assignee: nobody → desktop-bugs
status: Confirmed → Incomplete
Revision history for this message
In , Cao (cao-redhat-bugs) wrote :

Description of problem:
Window List cannot restore the windows in another workspace
to current workspace.

Version-Release number of selected component (if applicable):
gnome-panel-2.25.90-1.fc11

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
----------------
2.6.29-0.96.rc3.git12.fc11.i586
----------------

Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in metacity:
status: Incomplete → Invalid
Revision history for this message
In , Matthias (matthias-redhat-bugs) wrote :

----------------
http://bugzilla.gnome.org/show_bug.cgi?id=571588

Revision history for this message
In , Matthias (matthias-redhat-bugs) wrote :

*** Bug 484172 has been marked as a duplicate of this bug. ***

Revision history for this message
Jamin W. Collins (jcollins) wrote :

Confirmed this is still a problem with metacity on up to date Jaunty

Changed in metacity:
status: Invalid → Confirmed
Bug Watch Updater (bug-watch-updater)
Changed in metacity:
status: Unknown → New
Revision history for this message
Christopher N. Deckard (chris-globalfoo) wrote :

I can confirm that this bug exists in Jaunty beta with compiz 0.8.2-0ubuntu6. In Workspace Switcher, I have 1 column, 12 rows, in Window List Preferences set "Restore to current workspace". After minimizing and switching to another workspace, restore of minimized window goes back to native workspace.

Revision history for this message
In , Bug (bug-redhat-bugs) wrote :

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:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)
Changed in metacity (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
komputes (komputes) wrote :

I can also confirm this issue on Ubuntu 9.04. The issue is specifically with the "Window List Applet", so I'm not sure if the metacity compositing window manager has any part in this bug.

The has been reproduced on multiple releases and distributions.

I will add video capture of the issue and link to existing bug on redhat bugzilla.

Revision history for this message
komputes (komputes) wrote :
Revision history for this message
komputes (komputes) wrote :
Bug Watch Updater (bug-watch-updater)
Changed in gnome-panel (Fedora):
status: Unknown → Confirmed
Changed in metacity (Fedora):
status: Unknown → In Progress
Pedro Villavicencio (pedro)
Changed in gnome-panel (Ubuntu):
status: New → Triaged
importance: Undecided → Low
Revision history for this message
In , Owen (owen-redhat-bugs) wrote :

Upstream bug is https://bugzilla.gnome.org/show_bug.cgi?id=571588

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.

Revision history for this message
In , Bug (bug-redhat-bugs) wrote :

This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Revision history for this message
In , Bug (bug-redhat-bugs) wrote :

Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.

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

Bug Watch Updater (bug-watch-updater)
Changed in metacity (Fedora):
status: In Progress → Won't Fix
Revision history for this message
In , Christopher (christopher-redhat-bugs) wrote :

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

Bug Watch Updater (bug-watch-updater)
Changed in gnome-panel (Fedora):
status: Confirmed → Invalid
Revision history for this message
Jamin W. Collins (jcollins) wrote :

Not only is this bug still present, it appears to have gotten worse. Before it was only present with gnome and metacity. Now, I'm seeing the same problem with openbox also, which used to work fine prior to upgrading to 10.04 (lucid)

Revision history for this message
jettero (j-launchpad-voltar-confed-org) wrote :

I have reported a related bug (which was incorrectly marked a duplicate of this): 591529

Bug Watch Updater (bug-watch-updater)
Changed in metacity:
importance: Unknown → Medium
Launchpad Janitor (janitor)
Changed in openbox (Ubuntu):
status: New → Confirmed
Bug Watch Updater (bug-watch-updater)
Changed in gnome-panel (Fedora):
importance: Unknown → Medium
Bug Watch Updater (bug-watch-updater)
Changed in metacity (Fedora):
importance: Unknown → Medium
Revision history for this message
Chris Guiver (guiverc) wrote :

Thank you for reporting this bug to Ubuntu.

Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.
Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012.
Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.
Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011.
Ubuntu 9.04 (jaunty) reached end-of-life on October 23, 2010.
Ubuntu 8.10 (intrepid) reached end-of-life on April 30, 2010.
Ubuntu 8.04 (hardy) reached end-of-life on May 12, 2011.
Ubuntu 7.10 (gutsy) reached end-of-life on April 18th, 2009.
Ubuntu 7.04 (feisty) reached end-of-life on October 19, 2008.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in.

Changed in openbox:
status: New → Incomplete
Changed in gnome-panel (Ubuntu):
status: Triaged → Incomplete
Changed in metacity (Ubuntu):
status: Triaged → Incomplete
Changed in openbox (Ubuntu):
status: Confirmed → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.