I've tried all of the things listed in here and in various sites to sort out this problem, but none of the solutions seems to help me. What I am experiencing is resuming from suspend to ram works properly only about 30% of the time. During the successful resume, everything is working fine, including wireless/wired network connectivity. However, most of the time, then resuming my X session restarts with a clean gdm login and I have to relogin and reopen all the programs again, which obviously makes the suspend to ram useless.
I've spent a few months trying to figure out if there is a consistency of some sort that reproduces the successful or unsuccessful resume, however, I couldn't find any correlation. I even tried to open a clean gnome session with no open programs apart from what comes default. Even with that i have occasionally successfull resumes, but most of the time I end up with restarted X server. I am a disappointed with what seems to work perfectly fine on Ubuntu 7.10 when I have never had a failed resume from suspend when I even tried suspending while playing 3D games, watching movies, copying files across wireless/wired network and with Ubuntu 8.04 it is a complete mess. The worst thing is despite so many people are having issues with suspend/resuming to RAM, ubuntu development team is doing nothing to fix the problem. Even this bug is in Undecided state! -- Hardy recent update broke suspend to ram on Thinkpad T61p https://bugs.launchpad.net/bugs/217841 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
