Oh, and there is one other possibility here. On resume from S4, the BIOS has done an initial fixup of all the hardware after which the OS gets handed control and then had to restore all state. On resume from S3, all hardware was powered off (except for RAM) and the OS has a "blank slate" from which it does the resume. It is possible that if there is a common S3/S4 hook involved here, that the hook works okay if the hardware is in the initial power on state but not if the hardware was previously initialized. Completely reinitializing the hardware would then do the right thing.
-- Sound problems on hibernate, IBM T41 https://bugs.launchpad.net/bugs/98605 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
