Comment 97 for bug 577916

Thank you for the clarifications, I'll follow your directions. And yes, the hardware I am using is always the same.

Regarding this:
"Also, the fact that hibernate and suspend do not always work in VirtualBox will not make the bug critical, since VirtualBox must be run on real hardware. Does the hardware installation work?"

I guess I din't explain myself clearly enough.
The only issues I am experiencing _are_ on the hardware installation. Ubuntu is my _host_ operating system, installed on real hardware, and it is the one that (more often than not) doesn't hibernate or suspend correctly. I have never tried running Ubuntu on a virtual machine.
I use VirtualBox as an application on Ubuntu (usually running Windows 7 as a guest OS on top of it), and I had been under the impression that the bug on the host system showed up when and only when I ran virtual box (as an application inside the host system) - so I thought that virtual box (perhaps its kernel module) may be triggering the issue. But as I have mentioned (I think) I found out that that wasn't true: I am experiencing the issue even without using VirtualBox.

The criticity (or criticalness?? or whatever) of the bug has nothing to do with using Virtual Box. The bug is critical by itself, in that an operating system that fails to hibernate and/or suspend cannot be used safely.