Well, thanks for making an effort in any case. With crashes, there's so many ways that X can crash that it's hard to debug without knowing where in the code it crashed, or a reliable sequence of steps to reproduce the crash. Ideally the automated bug reporter tool thingee would take care of that, but in this case it didn't. You can see the stack trace here is just "??" which obviously doesn't give us much to go on.
For what it's worth, I've just started with Canonical a couple weeks ago to handle X bugs; I can understand why it's seemed like bugs have been languishing, but hopefully going forward the process will be more productive. So anyway, if you can reproduce this crash situation, and want to help us narrow it down, you can follow the steps on the DebuggingProgramCrash page to get a backtrace, and maybe we can figure it out. -- [apport] Xorg crashed with SIGSEGV https://bugs.launchpad.net/bugs/104757 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
