Xorg crashed with SIGABRT in WriteToClient()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg-server (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Ubuntu 12.04 LTS Beta 2 nightly build
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: xserver-xorg-core 2:1.11.4-0ubuntu10
ProcVersionSign
Uname: Linux 3.2.0-23-
.tmp.unity.
ApportVersion: 2.0.1-0ubuntu2
Architecture: i386
CompizPlugins: [core,composite
CompositorRunning: compiz
Date: Fri Apr 13 20:12:04 2012
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/bin/Xorg
ExtraDebuggingI
GraphicsCard:
Advanced Micro Devices [AMD] nee ATI RS880M [Mobility Radeon HD 4200 Series] [1002:9712] (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Device [103c:1604]
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120327.1)
MachineType: Hewlett-Packard Presario CQ56 Notebook PC
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: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 09/14/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.05
dmi.board.
dmi.board.name: 1604
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 88.05
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: Presario CQ56 Notebook PC
dmi.product.
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.7.
version.libdrm2: libdrm2 2.4.32-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.