https://bugzilla.novell.com/show_bug.cgi?id=641164 https://bugzilla.novell.com/show_bug.cgi?id=641164#c0 Summary: Failure to resume from hibernate (thaw) on system without s2{ram,disk} installed Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: abrouwers@gmail.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.99 Safari/533.4 I'm using an 11.3-based distribution (built in Studio with a few custom apps), with a KDE4 desktop environment. In my setup, pm-utils is installed for KDE to use for suspending the machine, however the s2ram or s2disk components are non-existent on my machine. On my machine, I can suspend to disk nicely using "pm-hibernate" ; however, when attempting to thaw the laptop, it boots normally. My grub config does have the appropriate resume= line for the image, but seems to be completely ignored! After researching a little bit more, I've found the pm-utils package to be extremely hacked up with patching (including some additional "should I resume?" checks that were failing, and specific calls to prefer s2disk, which weren't installed on my machine); I've tried rebuilding a more "vanilla" version of pm-utils ( https://build.opensuse.org/package/files?package=pm-utils&project=home:abrouwers ) , without much luck. For some reason, grub completely ignores my resume= line , which I have confirmed is correctly specified. Furthermore, the /var/log/pm-suspend.log entry shows every hook completely perfectly. Reproducible: Always Steps to Reproduce: 1. Hibernate machine using un-patched pm-hibernate 2. Attempt to resume from grub 3. Actual Results: System boots fresh Expected Results: System boots from dumped hibernate image -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.