It's probably important to note that the r128 card was not the system's primary vid card. The text console was on the internal g965, and that's the hardware the BIOS POSTed; my BIOS is explicitly set to use the internal vga as the primary VGA device.
X servers that start after the nasty hang that required SIGKILLing the X server all crash. They seem to be using the g965 video BIOS with the r128, even though the r128 is the only device configured. There's a line in the log like (II) R128(0): VESA VBE Total Mem: 262080 kB (II) R128(0): VESA VBE OEM: Intel(r)Broadwater-G Graphics Chip Accelerated VGA BIOS *snicker* that's some confused hardware. A reboot took care of it... Also, all X backtraces seem to include FontFileCompleteXLFD. I was confused before about which direction the backtrace was going and thought it was significant; F.F.C.XLFD is somehow showing up as the parent of _libc_start_main. So X must do something to the stack that the backtracer doesn't like. It's obviously not significant that all the backtraces have the same parent, since it's the same program. Sorry for any confusion. -- libGLcore crash (probably screensaver-induced) https://launchpad.net/bugs/75592 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
