Xorg crashed with SIGABRT
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg-server (Ubuntu) |
Expired
|
Low
|
Unassigned |
Bug Description
Don't know if it is a dupe.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: xserver-xorg-core 2:1.14.3-3ubuntu2
ProcVersionSign
Uname: Linux 3.11.0-14-generic x86_64
.tmp.unity.
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
CompizPlugins: No value set for `/apps/
CompositorRunning: compiz
CompositorUnred
CompositorUnred
Date: Fri Dec 20 23:04:23 2013
DistUpgraded: 2013-12-20 22:58:55,429 DEBUG enabling apt cron job
DistroCodename: saucy
DistroVariant: ubuntu
ExecutablePath: /usr/bin/Xorg
ExtraDebuggingI
GraphicsCard:
NVIDIA Corporation G86M [Quadro NVS 135M] [10de:042b] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Dell Device [1028:01f9]
InstallationDate: Installed on 2011-09-20 (822 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
MachineType: Dell Inc. Latitude D630
MarkForUpload: True
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdline: /usr/bin/X -core :0 -auth /var/run/
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: Xorg crashed with SIGABRT
UpgradeStatus: Upgraded to saucy on 2013-12-20 (0 days ago)
UserGroups:
dmi.bios.date: 07/28/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A13
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Latitude D630
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.10+
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.46-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 #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.