Bug 1583 - gnome-session-save doesn't save session state.
Summary: gnome-session-save doesn't save session state.
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-04 22:50 CEST by Herbert Poetzl
Modified: 2012-12-02 14:32 CET (History)
5 users (show)

See Also:
Source RPM: gnome-session-2.32.1-3.mga1.src.rpm
CVE:
Status comment:


Attachments

Description Herbert Poetzl 2011-06-04 22:50:19 CEST
Description of problem:

I'm unable to save the gnome session during the session with gnome-session-save.
The only way to get gnome to remember its session is to set it to save settings on logout, and then actually log out.

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

gnome-session-2.32.1-3.mga1

How reproducible:

Always.

Steps to Reproduce:
1. start fresh gnome session.
2. open gnome-terminal
3. run gnome-session-save from terminal
4. log out.
5. log in again. gnome-terminal will not be running.
Comment 1 Marja Van Waes 2011-10-18 10:08:39 CEST
@ leumanu, can you reproduce this bug

CC: (none) => manuel, marja11

Comment 2 Manuel Hiebel 2011-10-18 22:37:15 CEST
I confirm but the option: gnome-session-properties "remember currently running application" button work here.

CC: manuel => (none)

Comment 3 Herbert Poetzl 2011-10-18 23:11:52 CEST
as stated in the actual bug report (people please start actually reading the bug reports)

also, that is not an acceptable workaround, as you do not want to actually log out everytime you want to set a session default ...
Comment 4 Marja Van Waes 2011-10-19 09:36:23 CEST
(In reply to comment #3)
> as stated in the actual bug report (people please start actually reading the
> bug reports)

One of the required steps before a bug can be assigned to a developer, is that a bug must be reproduced, must be confirmed. That is what Manuel did.

BTW, we are drowning in the bug reports here, there are very few triagers and those we have have been offering all free time they could miss and even sleep. If it irritates you that we can't help faster, please join the bug squad and help us!
Comment 5 Marja Van Waes 2011-10-19 10:32:04 CEST
I didn't find this bug on 2.32 in Gnome Bugzilla (although it was there in an older version of gnome, so it could very well be an upstream bug) 

I didn't yet check against other Linux distro's
Comment 6 Marja Van Waes 2011-10-21 23:45:37 CEST
Didn't think of that before, even if it is an upstream bug: would they patch an old version?

It can't be assigned now, because there is no maintainer for gnome-session atm
Comment 7 Marja Van Waes 2011-11-13 11:39:59 CET
cc'ing the two main committers of gnome-session

CC: (none) => dmorganec, fundawang

Comment 8 Marja Van Waes 2012-01-05 21:43:20 CET
still no maintainer for gnome-session
Marianne Lombard 2012-01-13 16:47:46 CET

CC: (none) => marianne

Comment 9 Marja Van Waes 2012-04-13 16:45:19 CEST
3 months later and still no maintainer

But mageia 2 is on its way :)

@ Herbert

Did you happen to check whether this problem exists in cauldron, too?
Comment 10 Herbert Poetzl 2012-04-14 15:33:50 CEST
well, the answer is yes and no

there is no chance in hell to save your session on gnome3 in Cauldron simply because there is no gnome-session-save anymore.

session saving on logout works, but has its own issues (i.e. only a fraction of the session is saved)

CC: (none) => herbert

Comment 11 Manuel Hiebel 2012-11-05 16:53:35 CET
This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

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 
Mageia version prior to Mageia 1'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 Mageia 1 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 Mageia, 
you are encouraged to click on "Version" and change it against that version 
of Mageia.

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 Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad
Comment 12 Manuel Hiebel 2012-12-02 14:32:49 CET
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 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 Mageia 
please feel free to click on "Version" change it against that version of Mageia and reopen this bug.

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

--
Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX


Note You need to log in before you can comment on or make changes to this bug.