| Summary: | gnome-session-save doesn't save session state. | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Herbert Poetzl <herbert> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | dmorganec, fundawang, herbert, marianne, marja11 |
| Version: | 1 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | gnome-session-2.32.1-3.mga1.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Herbert Poetzl
2011-06-04 22:50:19 CEST
@ leumanu, can you reproduce this bug CC:
(none) =>
manuel, marja11 I confirm but the option: gnome-session-properties "remember currently running application" button work here. CC:
manuel =>
(none) 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 ... (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! 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 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 cc'ing the two main committers of gnome-session CC:
(none) =>
dmorganec, fundawang still no maintainer for gnome-session
Marianne Lombard
2012-01-13 16:47:46 CET
CC:
(none) =>
marianne 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? 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 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 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 |