Most recent kernel where this bug did not occur:
Hardware Environment: ASUS Z53T
Software Environment: Fedora Core 7 - Linux version 184.108.40.206-65.fc7 (firstname.lastname@example.org) (gcc version 4.1.2 20070502 (Red Hat 4.1.2-12)) #1 SMP Tue Aug 21 22:36:56 EDT 2007
Problem Description: if I'm using the function "Suspend to RAM" in any Energy-Program (for example "KPowersave") the Computer goes Suspending to RAM, is waking up (when I hit a button) and everything is okay than. But the Laptop isn't able to log off the user after a "Suspend to RAM". Also the Logoff-Screen looks different. It's only possible to choose "Logout User", not like otherwise, Shutdown, Restart and so on.
The same problem consists with other kernel-versions.
Steps to reproduce: Choose in KLaptop or KPowersave "Suspend to RAM", wake up the PC and try to logout
Hm, I'm not sure if that is a kernel problem.
What exactly do you mean by "the Laptop isn't able to log off the user"?
The Laptop is hanging on by logging of the user. Isn't restarting the x-server, as usually and doesn't react for any input (Strg + Alt + Backspace or something like this)
Then, probably, the X gets confused by the suspend. What video driver do you use?
Can you please try without it?
yes. i will and report
Kernel version 220.127.116.11-85 solved the Problem. Except of the Wireless card, everything works fine after suspend to ram =)
Problem not finished yet. A Process is hanging up while waking up from Sleep-Mode.
Everything works fine, except the Wireless-Adapter after an "Suspend-to-Ram" but the Restart doesn't work. It is closing all opened Services regularly. But at the End it shows "Rebooting System" and nothing happens --> Coldstart
Hardware: ASUS Z5305T
How to reproduce: Take your PC/Notebook in "Suspend-to-Ram"-Mode. Wake it up and restart the PC/Notebook.
I think it's the same issue as in Bug #6655.
If this is the only (except for the wireless adapter) problem that you have with suspend, I'll mark this bug as a duplicate of Bug #6655.
Please confirm or deny.
Yes, it can be the same problem now. for first it was another.
*** This bug has been marked as a duplicate of bug 6655 ***