Hibernation is broken in ubuntu-desktop

I have the same problem on my laptop and Lucid AMD64.
However, I guess this is a duplicate of Bug #577916.

I would check the dmesg and see if there are messages about inode errors like we got on the other report, and then just mark it as a dupe if so. Otherwise, I wouldn't mark it confirmed unless you agree that it is with the custom user account issue.

I Confirmed it because I don't see how "custom" user accounts could matter here (this is Linux after all, enough said). However the bug reporter should indeed check for dmesg messages about FS problems, but I don't see how could possibly these simptoms have any other cause than not resuming from hibernation at boot. That makes me think this is the mentioned already reported problem.

I guess this would be more appropriate.

Something I should have noted earlier: Hibernation works correctly on this same system *if* the standard Ubuntu desktop is installed in the normal way (disabled root account, normal user with admin privileges) from the live-CD installer. It's only when I start with a minimal system with a traditional user/root account duo that the problem arises.

I looked over bug #577916. I've noticed the same filesystem-orphan errors intermittently (sometimes they're there, sometimes not); I think these have more to do with the fact that the filesystem remains dirty when the system goes into hibernation, than the failure to resume itself. When the system boots up and fails to resume, after all, it finds the system in much the same way it would be if you had pressed the reset button. Whether or not you get orphan errors thus depends on the state of the disk cache when you hibernated, which is extraneous.

I do see the "PM: Resume from disk failed" message on bootup after hibernation.

This is interesting. Symptoms are almost the same as the other bug, yet it is somewhat different. Besides the difference in installation type, I guess main difference would be that "resume failed" message. I don't get that msg, and I guess the other bug references no such thing. It is possible something else is wrong here, perhaps some part of the power subsystem. Can you confirm what is the difference in installed packages in both cases?

There are a few packages different, but none of them look relevant. The diff is attached. (The only packages I installed manually on the non-hibernating system are the ssh-related ones.)

One thing I should point out: the "PM: Resume from disk failed" message doesn't only appear when the system should resume but fails to do so; it also appears every time the system boots up normally (when there is no saved image). The meaning of the message is thus more "no image found, proceeding with normal boot" than "uh oh, I tried to resume but something went wrong."

Have you tried to reproduce this bug? I used the alternate installer, with the cli-expert option, to create the minimal system. It should be possible to reproduce this without even installing a full desktop environment---I only did so because of the half-dozen ways to do hibernation in Linux, I was only concerned with the one used by the desktop.

I am seeing this with Lucid netbook-edition (UNE), system up to date as of today, incl. the proposed repo. I'm at a different machine right now, but I believe UNE doesn't use the ubuntu-desktop package but a purpose-built alternative metapackage (altho I might be wrong).

Patient: an Asus eeepc 1001p; this model is said to have been had working hibernation under Karmic 9.10.

Daniel Richard G., this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]