Bug 217307

Summary: Silently fails to hibernate when (Linux) kernel forbids it, no explanation given
Product: [Unmaintained] solid Reporter: JR <zorael>
Component: powermanagement-daemonAssignee: Dario Freddi <drf>
Status: RESOLVED DUPLICATE    
Severity: normal CC: psychonaut
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description JR 2009-12-04 09:53:19 UTC 
Version:            (using KDE 4.3.4)
OS:                Linux
Installed from:    Ubuntu Packages

(Unsure of whether this is the correct product or whether it should be marked as a bug or as a wishlist item, so please correct it as needed.)

When the Linux kernel forbids hibernating, such as when a kernel update has been applied, KDE still allows for hibernating but will fail silently without giving any indication why.

At such times, the kernel creates the file /var/run/do-not-hibernate. An example from pm-utils' log (/var/log/pm-suspend.log) at such an occasion;
  "kernel update inhibits hibernate (/var/run/do-not-hibernate present)"

If Powerdevil (or Solid?) were to check for the existence of this and if so tell the user of the kernel update forbidding hibernation, that way the user would know what was causing it and how to deal with it (eg. plan a reboot, instead of just trying to click the button several times.)
Comment 1 Tristan Miller 2010-09-16 16:55:12 UTC 
It doesn't "fail silently" for me.  If I suspend after a kernel update, it seems to work, but when I turn the computer on again, it won't boot completely.  It's been a while since this has happened, but to the best of my recollection the root partition refuses to mount "due to errors".  I need to boot a kernel using the "e" parameter, log in, and manually fsck the root partition.  Then I can restart the machine and it will boot.
Comment 2 Dario Freddi 2010-11-10 17:11:28 UTC 
This bug is mostly a duplicate, because we're missing these kind of infos from HAL or upower. However, such a situation shouldn't happen anymore with upower.

*** This bug has been marked as a duplicate of bug 256512 ***