Xorg crashed with SIGABRT in WriteToClient()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg-server (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I'm not really sure what happened. My Dell Studio 1558 crashed while awaking from sleep this morning.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: xserver-xorg-core 2:1.11.4-0ubuntu6
ProcVersionSign
Uname: Linux 3.2.0-19-
.tmp.unity.
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
CompizPlugins: No value set for `/apps/
CompositorRunning: compiz
Date: Wed Mar 21 09:12:35 2012
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/bin/Xorg
ExtraDebuggingI
GraphicsCard:
Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller])
Subsystem: Dell Device [1028:0413]
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
MachineType: Dell Inc. Studio 1558
ProcCmdline: /usr/bin/X :0 -auth /var/run/
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
?? () from /lib/i386-
WriteToClient ()
?? ()
?? ()
?? ()
Title: Xorg crashed with SIGABRT in WriteToClient()
UpgradeStatus: Upgraded to precise on 2012-03-11 (10 days ago)
UserGroups:
dmi.bios.date: 03/30/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 0G939P
dmi.board.vendor: Dell Inc.
dmi.board.version: A12
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Studio 1558
dmi.product.
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.7.
version.libdrm2: libdrm2 2.4.30-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 #943880, 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.