Suspend on this machine has always been flaky*, but with Lucid the
problems are perfectly reproducible.
The major problem with Lucid is that suspend-and-resume restarts my GDM
session. I've tested with two users logged in (regular and test) and
after resume, I cannot delete the test user because the system thinks
the test user is still logged in. Yet here I am back at the login
console.
How to reproduce:
Boot machine
Login, get a gnome session going
Suspend by closing lid, choosing suspend from gnome's 'power button' menu,
pm-suspend, etc.
Resume by pressing the Fn key or opening the lid
Presented with login prompt
Therefore, this is a resume failure. I've had no flashing caps-lock,
been looking for that for a while. This cycle worked with Intrepid and
Karmic, though it had its flakiness (Occasionally, display would be
dimmed, if resuming on power after suspending on battery; required
reboot to fix. Occasionally, would not resume and power button was
disabled, had to remove battery and unplug to "free" the machine, then
power-up.)
The reboot with no_console_suspend and
setfont /usr/share/consolefonts/Uni1-VGA8.psf.gz
sudo pm-suspend
trick produced nothing. No output, same results.
I've not tried hibernate yet, I never use it.
I am about to run checkbox's suspend-test.
--
[Hewlett-Packard HP Pavilion dv7 Notebook PC] late resume failure [non-free:
nvidia]
https://bugs.launchpad.net/bugs/432230
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
