Hi Bryce, I don't think that I can reproduce this, unfortunately. I've had several more hard-locks of the system thanks to ATI's rubbish fglrx driver, and those other crashes required a hard reboot, but X came back as I'd expect it to. [Now I'm using the VESA driver, everything has been stable.]
The important question is: what does the X startup script do if it fails to start X. Does Feisty now have 'magic' code to do "oops, couldn't start X; let's re-generate a clean xorg.conf" , or does it still correctly do "oops, couldn't start X; lets drop the user to a console to let him fix it". [I can't find anything obvious, by doing grep -r xorg.conf /etc ]. Your suggestion is certainly plausible - but would be near impossible to reproduce. So I think we should probably let this bug sleep - I'll re- activate it if I come across any more information. Richard -- xorg.conf gets (wrongly) overwritten after hardware crash https://bugs.launchpad.net/bugs/114941 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
