Xorg assert failure: *** glibc detected *** /usr/bin/X: double free or corruption (out): 0x00007f3fda5f9d50 ***

[Paul]

After waking from sleep, X.org is unresponsive and does not redraw the screen.

I ran /usr/share/apport/apport-gpu-error-intel.py to generate this report.

Intel graphics.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: xserver-xorg-core 2:1.11.4-0ubuntu6
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
AssertionMessage: *** glibc detected *** /usr/bin/X: double free or corruption (out): 0x00007f3fda5f9d50 ***
CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell]
CompositorRunning: compiz
Date: Fri Mar 16 20:30:12 2012
DistUpgraded: Log time: 2012-01-24 15:43:34.672171
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/bin/Xorg
ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:029b]
   Subsystem: Acer Incorporated [ALI] Device [1025:029b]
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
MachineType: Acer Aspire 1810T
ProcCmdline: /usr/bin/X :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic root=UUID=46b09540-36ca-47ef-9c67-240a87a35845 ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: xorg-server
Stacktrace:
 #0 0x00007f3fd4e9e445 in __GI_raise (sig=<optimised out>, sig@entry=<error reading variable: Cannot access memory at address 0x7fff07de2fd8>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
         resultvar = 0
         pid = <optimised out>
         selftid = 5149
 Cannot access memory at address 0x7fff07de2fd8
StacktraceTop: __GI_raise (sig=<optimised out>, sig@entry=<error reading variable: Cannot access memory at address 0x7fff07de2fd8>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
Title: Xorg assert failure: *** glibc detected *** /usr/bin/X: double free or corruption (out): 0x00007f3fda5f9d50 ***
UpgradeStatus: Upgraded to precise on 2012-01-24 (52 days ago)
UserGroups:

dmi.bios.date: 08/31/2010
dmi.bios.vendor: INSYDE
dmi.bios.version: v1.3314
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JM11-MS
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810T:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.name: Aspire 1810T
dmi.product.version: v1.3314
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.7.0+bzr3035-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.30-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.1-0ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.1-0ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2

[Apport retracing service (apport)]

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 #933504, 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.