Comment 8 for bug 305339

I did some more playing around with this today. I'm now running the 2.6.27-11-generic kernel, and I have also tried 2.6.28 and 2.6.29-rc5 (the latter two compiled from kernel.org source). They all behave similarly, but the testing reported here was with the 2.6.27-11-generic kernel from Ubuntu.

Some things I've noticed:

a) The sleep.sh script is not working consistently for me lately, when run from a terminal window inside Gnome. I can suspend (the computer shuts down to its suspended state, and the blue LED blinks, so the hardware must think it's asleep). But it often doesn't resume past the blinking cursor (see description above). Sometimes it does boot up again, but I get a Gnome login prompt and I've lost my previous Gnome session, so that's not very good.

b) Using the "Suspend" menu items in the Gnome GUI consistently fails to resume to a booted state at all, or sometimes I might get the blinking cursur.

c) If I use control-alt-f1 to get to the tty1 console from Gnome, log in at the console prompt, and run sleep.sh from there, I can consistently sleep and resume.

c) After sleep/resume from tty1 console, I can use alt-f7 and get back to my previous Gnome session (yeah!! It actually resumes! I have a work-around!). Usually the network is not properly connected, but after taking care of that, I can work as normal. (This is what I normally do when I first boot up the computer after a shutdown, so it is not a surprise -- I use a custom network config.)

So it seems as though the problem has to do with suspending from Gnome, and resuming straight to Gnome. Does that tell anyone anything? Any troubleshooting ideas?