Xorg crashed with SIGABRT
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg-server (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Just logged in and got a crashreport !!
Running Unity on gdm 3.5.91-0ubuntu2 with compiz on Ubuntu quantal (development branch).
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: xserver-xorg-core 2:1.13.0-0ubuntu4
ProcVersionSign
Uname: Linux 3.5.0-14-generic x86_64
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
Date: Sat Sep 22 15:44:05 2012
DistUpgraded: Fresh install
DistroCodename: quantal
DistroVariant: ubuntu
DkmsStatus: virtualbox, 4.1.18, 3.5.0-14-generic, x86_64: installed
ExecutablePath: /usr/bin/Xorg
GraphicsCard:
Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Intel Corporation Device [8086:2031]
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120809.1)
ProcCmdline: /usr/bin/X :0 -br -once -config /etc/X11/
ProcEnviron:
TERM=linux
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
?? ()
Title: Xorg crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 02/24/2012
dmi.bios.vendor: Intel Corp.
dmi.bios.version: KCH7710H.
dmi.board.name: DH77KC
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG39641-400
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCor
version.compiz: compiz 1:0.9.8.0-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.39-0ubuntu1
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 #1054051, 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.