I just realized a new element that all of these scenarios have in common: the screensaver.
The screensaver is activated when coming back from resume. The crash during installation happened at just about the point where the screensaver activated due to an activity timeout (I noticed during my second attempt that it activated at just about the point where it had crashed). This would potentially explain why we've been unable to trigger the bug with suspend/resume stress testing, because there's no screensaver timeout. This is just a guess at this point, but I think the coincidence justifies a closer look. -- X server crash: *** glibc detected *** free(): in valid next size (fast) https://bugs.launchpad.net/bugs/328035 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs -- universe-bugs mailing list universe-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/universe-bugs
