Xorg crashed with SIGABRT in raise()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg-server (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Happens regularly when booting, after error messages everything seems to be ok. This error always goes together with an apt crash/error message.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: xserver-xorg-core 2:1.11.4-0ubuntu10
ProcVersionSign
Uname: Linux 3.2.0-22-generic x86_64
.tmp.unity.
ApportVersion: 2.0-0ubuntu4
Architecture: amd64
CompizPlugins: [core,composite
CompositorRunning: compiz
CrashCounter: 1
Date: Thu Apr 5 12:34:07 2012
DistUpgraded: 2012-02-04 18:00:31,641 DEBUG enabling apt cron job
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/bin/Xorg
ExtraDebuggingI
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: System manufacturer System Product Name
ProcCmdline: /usr/bin/X :0 -auth /var/run/
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: xorg-server
Title: Xorg crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to precise on 2012-02-04 (61 days ago)
UserGroups:
dmi.bios.date: 09/16/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0301
dmi.board.
dmi.board.name: P8Z68-V GEN3
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.7.4-0ubuntu1
version.ia32-libs: ia32-libs 20090808ubuntu35
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 #962892, 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.