Xorg crashed with SIGABRT in OsAbort()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg-server (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
After upgrade from precise to current development quantal, I received this error.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: xserver-xorg-core 2:1.12.
ProcVersionSign
Uname: Linux 3.5.0-13-generic x86_64
ApportVersion: 2.5.1-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Wed Aug 29 09:08:19 2012
DistUpgraded: 2012-03-12 13:59:22,955 DEBUG icon theme changed, re-reading
DistroCodename: quantal
DistroVariant: ubuntu
DkmsStatus: virtualbox, 4.1.18, 3.5.0-13-generic, x86_64: installed
ExecutablePath: /usr/bin/Xorg
GraphicsCard:
Advanced Micro Devices [AMD] nee ATI Cayman XT [Radeon HD 6970] [1002:6718] (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:03bc]
MachineType: System manufacturer System Product Name
ProcCmdline: /usr/bin/X :0 -core -auth /var/run/
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
OsAbort ()
?? ()
FatalError ()
?? ()
__libc_start_main (main=0x7ff061f
Title: Xorg crashed with SIGABRT in OsAbort()
UpgradeStatus: Upgraded to quantal on 2012-03-12 (170 days ago)
UserGroups:
dmi.bios.date: 10/03/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0604
dmi.board.
dmi.board.name: P9X79 DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.8+
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.38-0ubuntu2
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 #1037518, 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.