Comment 5 for bug 838729

Revision history for this message
Jonathan Lange (jml) wrote :

Bug appears in:

 * Linux truth 2.6.38-10-generic #46-Ubuntu SMP Tue Jun 28 15:07:17 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
 * Linux truth 3.0.0-10-generic #16-Ubuntu SMP Fri Sep 2 18:32:04 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
 * Linux truth 3.0.0-9-generic #12-Ubuntu SMP Sat Aug 20 18:55:02 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
 * Linux truth 3.0.0-8-generic #11-Ubuntu SMP Fri Aug 12 20:23:58 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
 * Linux truth 3.0.0-7-generic #9-Ubuntu SMP Fri Jul 29 21:27:24 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

Testing protocol:
 1. Boot into kernel
 2. Record `uname -a`
 3. Unplug laptop
 4. Close lid
 5. Suspend once
 6. Open lid
 7. Unlock and wait until network connection re-established
 8. Close lid
 9. Wait for one minute while laptop fails to suspend
 10. Force shutdown by holding power off button
 11. Power on

Some times, closing the lid didn't trigger a suspend. This seemed to be only when gnome-settings-daemon had crashed / misbehaved. (themes were wrong, keymappings were wrong etc). In those cases I killed gnome-settings-daemon and then relaunched it in the background.

I've tried to double check and be careful that I've been reporting the test results correctly, and testing what I think I'm testing, but I couldn't be 100% sure.

Hope this helps. I really want to have a working laptop again.