[Bug 1115358] Re: Xorg crashed with SIGABRT in raise() [drm] failed to set drm interface version.

2013-02-05 Thread Daniel Winzen
Yes, deleting the xorg.conf file and adding sleep 10 to the /etc/init/lightdm.conf can also be used as a workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1115358 Title: Xorg crashed with

[Bug 1115358] Re: Xorg crashed with SIGABRT in raise() [drm] failed to set drm interface version.

2013-02-05 Thread Bryce Harrington
*** This bug is a duplicate of bug 982889 *** https://bugs.launchpad.net/bugs/982889 Thanks, so that confirms it is the same issue. ** Changed in: xorg-server (Ubuntu) Status: Incomplete = New ** This bug has been marked a duplicate of bug 982889 X trying to start before plymouth

[Bug 1115358] Re: Xorg crashed with SIGABRT in raise()

2013-02-04 Thread Bryce Harrington
** Description changed: After starting Ubuntu, a Message showed up, that I'm running in low graphics mode. In the console I realized that the /etc/X11/xorg.conf file was deleted, so I copied a backup and after restarting Ubuntu this Apport-bug came up. + + [39.722] (EE) RADEON(0):

[Bug 1115358] Re: Xorg crashed with SIGABRT in raise()

2013-02-04 Thread Bryce Harrington
From the core, the X server is terminating due to lack of the drm driver: #3 0x7fe9b9fcaf93 in AbortServer () at ../../os/log.c:655 No locals. #4 0x7fe9b9fcb80d in FatalError (f=f@entry=0x7fe9b9fcf1a2 no screens found) at ../../os/log.c:793 args = {{gp_offset = 8, fp_offset

[Bug 1115358] Re: Xorg crashed with SIGABRT in raise()

2013-02-04 Thread Bryce Harrington
From Xorg.0.log, X is started at [38.095] sec. But from dmesg, it indicates drm is not initialized until 38.165: [ 38.165478] [drm] Initialized radeon 2.29.0 20080528 for :02:00.0 on minor 0 Then X fails due to not being able to see the drm it expects: [39.722] (EE) RADEON(0):

[Bug 1115358] Re: Xorg crashed with SIGABRT in raise()

2013-02-04 Thread Bryce Harrington
@Daniel, can you see if the workarounds I posted to bug #982889 work here too? If they do, that probably verifies this is indeed the same issue. ** Changed in: xorg-server (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1115358] Re: Xorg crashed with SIGABRT in raise()

2013-02-04 Thread Daniel Winzen
I realized that the /etc/X11/xorg.conf file was deleted, so I just copied a backup and after restarting Ubuntu everything was working, but I tried restarting it before coping the config file, but this didn't work. I don't know why the xorg.conf was deleted, but after restoring it, it worked like a

[Bug 1115358] Re: Xorg crashed with SIGABRT in raise()

2013-02-04 Thread Bryce Harrington
Perhaps xserver reading xorg.conf adds just enough delay to resolve the race condition. So my bet is that what's in your xorg.conf doesn't actually matter. Try putting a 1 sec sleep into your lightdm config as described in the above bug and remove your xorg.conf, and I bet it'll work then too.

[Bug 1115358] Re: Xorg crashed with SIGABRT in raise() [drm] failed to set drm interface version.

2013-02-04 Thread Bryce Harrington
** Summary changed: - Xorg crashed with SIGABRT in raise() + Xorg crashed with SIGABRT in raise() [drm] failed to set drm interface version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1115358