Xorg crashed with SIGABRT in raise()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg-server (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
No idea what it is. Nothing visible
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: xserver-xorg-core 2:1.13.0-0ubuntu5
ProcVersionSign
Uname: Linux 3.5.0-16-generic i686
.tmp.unity.
ApportVersion: 2.6.1-0ubuntu1
Architecture: i386
CompizPlugins: [core,composite
CompositorRunning: compiz
CrashCounter: 1
Date: Fri Oct 5 08:22:42 2012
DistUpgraded: 2012-10-05 07:34:58,384 DEBUG enabling apt cron job
DistroCodename: quantal
DistroVariant: ubuntu
ExecutablePath: /usr/bin/Xorg
ExecutableTimes
GraphicsCard:
Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] Device [1025:0205]
Subsystem: Acer Incorporated [ALI] Device [1025:0205]
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MachineType: Acer Aspire 5738
ProcCmdline: /usr/bin/X :2 -core -auth /var/run/
ProcCwd: /etc/X11
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
raise () from /lib/i386-
abort () from /lib/i386-
OsAbort ()
?? ()
FatalError ()
Title: Xorg crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to quantal on 2012-10-05 (2 days ago)
UserGroups:
dmi.bios.date: 04/14/2009
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.06
dmi.board.name: JV50
dmi.board.vendor: Acer
dmi.board.version: Rev
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: Aspire 5738
dmi.product.
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.8.4-0ubuntu1
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 #1037518, 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.