RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 643450 - Gnome session saves application positions, but not workspace assignment
Summary: Gnome session saves application positions, but not workspace assignment
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: metacity
Version: 6.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Owen Taylor
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 662543 782183 835616
TreeView+ depends on / blocked
 
Reported: 2010-10-15 16:15 UTC by Scott Spurrier
Modified: 2018-11-14 16:50 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-12 22:13:51 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Possible patch to address the issue in metacity (6.11 KB, patch)
2010-12-13 14:30 UTC, Olivier Fourdan 		no flags Details | Diff
View All

Description Scott Spurrier 2010-10-15 16:15:19 UTC 
Description of problem:

In RHEL 6.1 RC, when you log out of gnome is saves which applications are running and their position, but it isn't saving which workspace it is assigned to so all applications end up on the first workspace when you log back in.
Comment 5 Olivier Fourdan 2010-12-13 14:30:12 UTC 
Created attachment 468386 [details]
Possible patch to address the issue in metacity

What happens is that metacity uses the same state file each time, named after the SM client-id which remains.

gnome-session removes 'old' the state file after the app has saved its state but metacity uses the same so its state file is removed by the session manager and the state is not restored (thus the position and workspace of running windows is not restored).

TBH this is really a gnome-session issue, it should have been addressed by that commit upstream:

  http://git.gnome.org/browse/gnome-session/commit/?id=3e346957cebcbf9e747757d2d649329266743afc

That patch is already in gnome-session 2.28.0 in el6, but unfortunately it does not seem to work as expected and the state file is really removed by gnome-session (the discard_exec hash should prevent this, but it does not, I am investing this as to why it does not work as expected).

This patch here is for metacity (although again, this is a gnome-session issue, not metacity), and is mainly a proof of concept, it allows for --sm-save-file and --sm-client-id to be used simultaneously in metacity.
 
Initially metacity allows for only --sm-client-id or --sm-save-file to be used and name its save state file after the client-id.
 
Other GNOME applications using eggsmclient use a  different state file each time, so that the new one does not get removed along  with the old state file.

It works well and the session is properly restored, but YYMV and a proper fix in gnome-session might be preferable.
Comment 6 Suzanne Logcher 2011-01-05 19:44:46 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated 
in the current release, Red Hat is unfortunately unable to 
address this request at this time.  This request has been 
proposed for the next release of Red Hat Enterprise Linux.
If you would like it considered as an exception in the 
current release, please ask your support representative.
Comment 8 RHEL Program Management 2011-07-06 01:00:45 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 9 Ray Strode [halfline] 2011-07-27 21:09:59 UTC 
suggest we either WONTFIX this or dupe it with bug 664516 which, when fixed, will render the patch in attachment 468386 [details] unnecessary
Comment 11 Tom Lavigne 2012-09-18 15:22:46 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
    
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Comment 12 RHEL Program Management 2013-10-14 01:14:31 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Comment 13 Andrius Benokraitis 2013-11-12 22:13:51 UTC 
After thorough deliberation, this bugzilla is not planned on being addressed in the Red Hat Enterprise Linux 6 time frame.
Note You need to log in before you can comment on or make changes to this bug.