Xorg crashed with SIGABRT in raise()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg-server (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Xorg crashed with SIGABRT in raise()
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: xserver-xorg-core 2:1.11.4-0ubuntu10
ProcVersionSign
Uname: Linux 3.2.0-23-
.tmp.unity.
ApportVersion: 2.0.1-0ubuntu4
Architecture: i386
CompizPlugins: No value set for `/apps/
CompositorRunning: None
Date: Mon Apr 16 17:44:42 2012
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/bin/Xorg
ExtraDebuggingI
GraphicsCard:
Intel Corporation N10 Family Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:83ac]
Subsystem: ASUSTeK Computer Inc. Device [1043:83ac]
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328)
MachineType: ASUSTeK Computer INC. 1001PX
ProcCmdline: /usr/bin/X :0 -auth /var/run/
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
raise () from /lib/i386-
abort () from /lib/i386-
?? () from /lib/i386-
?? () from /lib/i386-
?? ()
Title: Xorg crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 04/30/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0601
dmi.board.
dmi.board.name: 1001PX
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: 1001PX
dmi.product.
dmi.sys.vendor: ASUSTeK Computer INC.
version.compiz: compiz 1:0.9.7.6-0ubuntu1
version.libdrm2: libdrm2 2.4.32-1ubuntu1
version.
version.
version.
version.
version.
version.
version.
version.
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #943880, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.