|
Bugzilla – Full Text Bug Listing |
| Summary: | System -> Log Out -> Suspend doesn't restore X session | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Aidan Skinner <aidan> |
| Component: | GNOME | Assignee: | Rodrigo Moya <rodrigo> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Blocker | ||
| Priority: | P5 - None | CC: | hpj |
| Version: | Beta 3 | ||
| Target Milestone: | Beta 5 | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Package with fix | ||
|
Description
Aidan Skinner
2005-09-16 16:37:01 UTC
a work around could be using kpowersave to initiate suspend (it should work on GNOME, too) Unfortunately, this is also present in RC4. See also bug 71003 comment 2. The expected behavior is to trigger the suspend without closing the current GNOME session. *** Bug 134542 has been marked as a duplicate of this bug. *** gdm is running --suspend-to-disk, while we do --suspend-to-ram in the power manager applet. Does running 'powersave --suspend-to-ram' trigger the expected behavior? It seems to me --suspend-to-disk does not work on all systems. What do you get apart from not coming back to the GNOME session? I get a kernel panic :( sorry, it is suspend-to-ram what doesn't work in all systems. Rodrigo, are you trying to fix this for some 10.0 update? I'll have a look how things are working with 10.1 Beta1. Moving to 10.1. The problem remains, it has _nothing_ changed. Reproducable: - Log into GNOME - Choose "Log Out" from the "Desktop" entry in gnome-panel - Choose radio button for "Suspend the computer" - Click OK (* at this point you already see X shutting down rather than staying as-is *) - System suspends & power off - Power on & system resumes - You'll find yourself back in GDM, your previous session is destroyed. We really need to get this fixed. Moving to 10.1. I'm fixing it for NLD10/10.1. Aidan, could you please tell me if running 'powersave --suspend-to-ram' on the command line does trigger the expected result? Rodrigo, what we're doing is a suspend to disk (see 'gdm-conf.patch'): +RebootCommand=/sbin/shutdown -r now +HaltCommand=/sbin/shutdown -h now +SuspendCommand=/usr/bin/powersave --suspend-to-disk We're currently _not_ providing any option to trigger suspend to ram with GDM. When I first hit this bug (10.0) I could narrow down the problem to GDM: - using kpowersave left X running. After resume the X session was still running. - using 'powersave --suspend-to-disk' left X running. After resume the X session was still running. - using the log out button of GDM to trigger suspend to disk killed the X session. After resume you were thrown back to the GDM login screen. Session destroyed. (I expect the very same results for 10.1) by no means you should default to suspend-to-ram. It just does not work on too many machines and though is disabled per default. Also, it looks like GDM first logs out, then suspends. This is fundamentally wrong. For suspend, it should not log out, but instead lock the screen; then trigger suspend. If you log the user out, suspend is basically useless since then it will be almost like a reboot for him. Same with Beta2. Any updates? Anyone working on it at all? Moving to Beta2. yes, I'm working on it Still present in Beta 3. Progress? Created attachment 67121 [details]
Package with fix
Attached package submitted to autobuild. Timo, can you confirm it works for you? Gave it a try on Beta3 with the updated package. The problem is not fixed. The logout dialog simply disappears once I choose "Suspend the computer" and hit OK. It leaves the X session running and does not suspend the system at all. Fixed package submitted to autobuild |