Comment 2 for bug 278573

James Westby wrote:
> Firstly I will say that hibernate isn't the preferred way of hibernating
> your system. Some even suggest we should remove the package
> from Ubuntu to save confusion.

Thanks James: I'd assumed that hibernate did what the Gnome User
Switcher's hibernate option did (the GUI route doesn't work either -
hence me looking for a command line equivalent for easier debugging).

> Running hibernate with the option "-v4" should give you more output
> that may help you diagnose what is going on.

OK - I'm not so much worried about figuring out the problem for me
as for noting that currently Hardy to Intrepid upgrades will break the
hibernate configuration for at least some users, assuming that this
behaviour isn't due to something specific to my installation.

Going to -v2 was enough for some more information:

$ sudo hibernate -v2 2>&1 | more
hibernate:Warning: Tuxonice binary signature file not found.
hibernate: Trying method in suspend2.conf...
hibernate: Trying method in disk.conf...
hibernate: Trying method in ususpend-disk.conf...
hibernate: [01] Executing CheckLastResume ...
hibernate: [01] Executing CheckRunlevel ...
hibernate: [01] Executing LockFileGet ...
hibernate: [01] Executing NewKernelFileCheck ...
hibernate: [10] Executing EnsureUSuspendCapable ...
hibernate: [11] Executing XHacksSuspendHook1 ...
hibernate: [59] Executing RemountXFSBootRO ...
hibernate: [89] Executing SaveKernelModprobe ...
hibernate: [91] Executing ModulesUnloadBlacklist ...
Unloading blacklisted modules listed /etc/hibernate/blacklisted-modules
hibernate: [95] Executing XHacksSuspendHook2 ...
hibernate: [98] Executing CheckRunlevel ...
hibernate: [99] Executing DoUSuspend ...
hibernate: Running /sbin/s2disk ...
s2disk: Could not stat the resume device file. Reason: No such file or
directory
hibernate: [90] Executing ModulesLoad ...
hibernate: [89] Executing RestoreKernelModprobe ...
hibernate: [85] Executing XHacksResumeHook2 ...
hibernate: [70] Executing ClockRestore ...
...

So it seems that the upgrade to Intrepid may not have left s2disk in a
working state (assuming that that was being used in Hardy in my case),
although I'll look into getting Tuxonice working, since I'd prefer to move
to using it anyway...