Some further testing shows that every alternate wake from suspend to RAM while running off the amd64 live image results in a blank screen at wake. Switching to the first or second virtual console works, and then going to virtual console 7 (in which the x session is running) brings back the display. The order of events is: 1. Suspend by closing lid. 2. Open lid, note problem with mouse pointer disappearing as reported above. 3. Suspend by closing lid. 4. Open lid and get a black screen. 5. Attempt to switch to different virtual console, successful. 6. Switch back to virtual console 7. Get restored X session. 7. Suspend by closing lid. 8. Open lid and have system restore to X session very fast. 9. Suspend by closing lid. 10. Open lid and get a black screen. 11. Switch to virtual console 1 or 2. Then back to 7 and return to X session.
So it appears that waking from suspend to RAM in even-numbered sessions has problems with restoring the X session and requires that you switch to a different virtual console and switch back to console 7. I have also noticed that the problem with the mouse (reported above) only happened after the first wake from suspend to RAM. -- mouse does not resume after waking from suspend to ram triggered by closing lid https://bugs.launchpad.net/bugs/550046 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
