Xorg crashed with SIGABRT in raise()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg-server (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I've no idea what went wrong. This was on login from gdm loading Classic Mode.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: xserver-xorg-core 2:1.11.4-0ubuntu10
Uname: Linux 3.4.0-rc1-nimi x86_64
.tmp.unity.
ApportVersion: 2.0-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for `/apps/
CompositorRunning: compiz
Date: Sun Apr 8 22:29:34 2012
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/bin/Xorg
ExtraDebuggingI
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120314.1)
MachineType: Hewlett-Packard HP Mini 110-3500
ProcCmdline: /usr/bin/Xorg :0 -background none -verbose -auth /var/run/
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
TERM=linux
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: xorg-server
Title: Xorg crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 11/30/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.14
dmi.board.
dmi.board.name: 1584
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 85.2B
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP Mini 110-3500
dmi.product.
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.7.4-0ubuntu3
version.ia32-libs: ia32-libs N/A
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 #971182, 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.