Xorg crashed with SIGABRT
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg-server (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: xserver-xorg-core 2:1.13.0-0ubuntu4
ProcVersionSign
Uname: Linux 3.5.0-15-generic i686
.tmp.unity.
ApportVersion: 2.5.2-0ubuntu4
Architecture: i386
CompizPlugins: No value set for `/apps/
CompositorRunning: compiz
Date: Sat Sep 22 00:51:24 2012
DistUpgraded: Fresh install
DistroCodename: quantal
DistroVariant: ubuntu
DkmsStatus:
vboxhost, 4.1.22, 3.5.0-14-generic, i686: installed
vboxhost, 4.1.22, 3.5.0-15-generic, i686: installed
ExecutablePath: /usr/bin/Xorg
ExtraDebuggingI
GraphicsCard:
NVIDIA Corporation GT218 [NVS 3100M] [10de:0a6c] (rev a2) (prog-if 00 [VGA controller])
Subsystem: Dell Latitude E6510 [1028:040b]
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328)
MachineType: Dell Inc. Latitude E6510
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdline: /usr/bin/X :0 -core -auth /var/run/
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
?? () from /lib/i386-
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: Xorg crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 11/30/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0N5KHN
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Latitude E6510
dmi.product.
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.8.
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 #1033533, 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.