I have ran into what I believe is the same problem. I get a similar stack trace: Backtrace: 0: /usr/bin/X(xf86SigHandler+0x94) [0x10092df4] 1: [0x100344] 2: /usr/bin/X(VidModeGetCurrentModeline+0x3c) [0x1009769c] 3: /usr/lib/xorg/modules/extensions//libextmod.so [0xf971c84] 4: /usr/bin/X [0x10135380] 5: /usr/bin/X(Dispatch+0x38c) [0x1004ad4c] 6: /usr/bin/X(main+0x4a4) [0x1002bcc4] 7: /lib/libc.so.6 [0xfb6db10] 8: /lib/libc.so.6 [0xfb6dcd0]
which happens when I run displayconfig-restore. Removing displayconfig- restore enables me to login. Otherwise the X server just crashed during KDE startup (I'm running kubuntu). I'm running on a PPC Mac Mini. I don't really believe that's relevant, though. The videocard is (from lspci): 0000:00:10.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200] (rev 01) I'm using the "radeon" X driver. I didn't have these problems when I installed hardy. But when I did a apt-get dist-upgrade today (for the very first time since installing Hardy, I think) this problem started to appear. -- [hardy] displayconfig-restore causes X to crash https://bugs.launchpad.net/bugs/202164 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
