Xorg crashed with SIGSEGV in WriteToClient()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg-server (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Using up-to-date precise as of 2012-03-23. I was using my system as normal when my X session crashed.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: xserver-xorg-core 2:1.11.4-0ubuntu7
ProcVersionSign
Uname: Linux 3.2.0-20-generic x86_64
.tmp.unity.
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for `/apps/
CompositorRunning: compiz
CrashCounter: 1
Date: Fri Mar 23 10:11:40 2012
DistUpgraded: 2012-01-16 21:49:12,983 DEBUG enabling apt cron job
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/bin/Xorg
ExtraDebuggingI
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: System76, Inc. Lemur UltraThin
ProcCmdline: /usr/bin/X :0 -auth /var/run/
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: xorg-server
StacktraceTop:
?? () from /lib/x86_
WriteToClient ()
?? ()
?? ()
?? ()
Title: Xorg crashed with SIGSEGV in WriteToClient()
UpgradeStatus: Upgraded to precise on 2012-01-17 (66 days ago)
UserGroups:
dmi.bios.date: 11/11/2010
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: CALPELLACRB.
dmi.board.
dmi.board.name: Lemur UltraThin
dmi.board.vendor: System76, Inc.
dmi.board.version: lemu2
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: System76, Inc.
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: Lemur UltraThin
dmi.product.
dmi.sys.vendor: System76, Inc.
version.compiz: compiz 1:0.9.7.
version.ia32-libs: ia32-libs 20090808ubuntu35
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 #941953, 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.