CloudBook Hibernation Mode: Slow and Error-Prone

I posted a few hours ago about the long boot time on the CloudBook. and some users suggested that I try the hibernation mode and see how that works. The hope, of course, was that hibernating and then waking would be a lot faster than cold booting. In fact, it is faster; it’s just not that fast and it returns some strange errors.

This morning, when I tried to enter hibernation mode, the CloudBook would not turn off at all. The screen turned black for a few seconds and then spit back a password request at me. When I entered the password, I was back to my desktop again and free to try (and fail) at hibernating again. I later figured out that this password request screen is the same one you get when you wake the computer after a successful hibernation. I can only guess that the machine was hibernating and then waking itself instead of powering down like it should have.

But, as I said in my previous post, the CloudBook (at least the one we received) is temperamental and problems that occur at one time may not be reproducible, even when you try the same exact thing later. Tonight, I tried to hibernate again and it worked. After a few seconds of The storage device that holds your OS, programs, and data.
Learn Morehard drive whirring, the CloudBook did indeed power down.

So what happened when it woke up?

In case you didn’t watch the entire video with a pen in hand to write down the timestamps of major events, here’s what happened:

• 1:15 from power on to a login prompt
• After the login prompt, two different error messages appeared on-screen.
  • Volume Control Has Quit Unexpectedly: If you reload a panel object, it will automatically be added back to the panel. Two buttons appeared Don’t Reload and Reload. I hit reload. I have no idea what this error meant and whether it was a reference to the audio volume or to mounting different volumes on the hard drive. However, it didn’t seem to affect anything.
  • Enter password for Default Keyring to Unlock: The application nm-applet (/usr/bin/nm-applet) wants access to the default keyring, but it is locked. I entered my password and this prompt disappeared. Again, I have no idea what it meant or why it appeared when I woke the CloudBook from hibernation.

With the odd error messages, it took a total of 1:55 to wake the computer from hibernation, about a minute less than it took to cold boot.