Xorg crashed with SIGABRT in raise()

Bug #1163381 reported by Christopher Townsend
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

When this occurs, I see a blank screen with a cursor when the lightdm screen should be displayed.

#4 0x00007fca0045fa9d in FatalError (f=f@entry=0x7fca00463442 "no screens found") at ../../os/log.c:793
        args = {{gp_offset = 8, fp_offset = 48, overflow_arg_area = 0x7fffbc2d7810,
            reg_save_area = 0x7fffbc2d7750}}
        args2 = {{gp_offset = 8, fp_offset = 48, overflow_arg_area = 0x7fffbc2d7810,
            reg_save_area = 0x7fffbc2d7750}}
        beenhere = 1
#5 0x00007fca002eb7d2 in main (argc=9, argv=0x7fffbc2d7958, envp=<optimized out>)
    at ../../dix/main.c:207
        i = <optimized out>
        alwaysCheckForInput = {0, 1}

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: xserver-xorg-core 2:1.13.3-0ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
Uname: Linux 3.8.0-16-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Apr 2 11:08:51 2013
DistUpgraded: 2013-03-18 12:26:08,332 DEBUG enabling apt cron job
DistroCodename: raring
DistroVariant: ubuntu
ExecutablePath: /usr/bin/Xorg
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:058b]
MachineType: Dell Inc. Dell System XPS L322X
MarkForUpload: True
ProcCmdline: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-16-generic root=UUID=e50fc373-bec4-4757-8dd6-152c23b0dc3e ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 OsAbort ()
 ?? ()
 FatalError ()
Title: Xorg crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to raring on 2013-03-18 (14 days ago)
UserGroups:

dmi.bios.date: 08/17/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: X29
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnDellInc.:bvrX29:bd08/17/2012:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: Dell System XPS L322X
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.9~daily13.03.29-0ubuntu1
version.ia32-libs: ia32-libs 20090808ubuntu36
version.libdrm2: libdrm2 2.4.43-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.5-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1

Revision history for this message
Christopher Townsend (townsend) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

sigh, this is actually a dupe of bug 982889, you could try what's suggested on https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/comments/115

and check if it helps

information type: Private → Public
Changed in xorg-server (Ubuntu):
status: New → Incomplete
Revision history for this message
Bryce Harrington (bryce) wrote :

Has this happened more than once? Any thoughts on what triggers it?

The stack trace is the same as bug #1163270.

description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.