compiz crashed with SIGSEGV in std::_List_node_base::_M_hook()

[Mihai-Tudor Popescu]

Binary package hint: compiz

compiz crashed with SIGSEGV in std::_List_node_base::_M_hook()

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: compiz-core 1:0.9.2.1+glibmainloop4-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.37-12.26-generic 2.6.37
Uname: Linux 2.6.37-12-generic i686
Architecture: i386
DRM.card0.LVDS.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1024x600
 edid-base64: AP///////wAGryAQAAAAAAESAQOAEwt4CvpWklZUmCQaT1QAAAABAQEBAQEBAQEBAQEBAQEBsBMAQEFYGSAYiAMBw3EAAAAYAAAADwAAAAAAAAAAAAAAAAAgAAAA/gBBVU8KICAgICAgICAgAAAA/gBBMDg5U1cwMSBWMCAKABk=
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
Date: Wed Jan 26 11:50:39 2011
DistUpgraded: Yes, recently upgraded Log time: 2011-01-23 12:49:51.463108
DistroCodename: natty
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
GraphicsCard:
 Subsystem: ASUSTeK Computer Inc. Device [1043:830f]
   Subsystem: ASUSTeK Computer Inc. Device [1043:830f]
InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: ASUSTeK Computer INC. 901
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=ro_RO:ro:en_GB:en
 LANG=ro_RO.UTF-8
 LC_MESSAGES=ro_RO.utf8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.37-12-generic root=UUID=df297b47-8cb7-433b-8128-a23dda9042c4 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x682077 <_ZNSt15_List_node_base7_M_hookEPS_+23>: mov %edx,(%ecx)
 PC (0x00682077) ok
 source "%edx" ok
 destination "(%ecx)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 std::_List_node_base::_M_hook(std::_List_node_base*) () from /usr/lib/libstdc++.so.6
 sigc::internal::signal_emit0<void, sigc::nil>::emit(sigc::internal::signal_impl*) () from /usr/lib/compiz/libunityshell.so
 Launcher::EventLogic() () from /usr/lib/compiz/libunityshell.so
 Launcher::DrawContent(nux::GraphicsEngine&, bool) () from /usr/lib/compiz/libunityshell.so
 nux::View::ProcessDraw(nux::GraphicsEngine&, bool) () from /usr/lib/libnux-0.9.so.0
Title: compiz crashed with SIGSEGV in std::_List_node_base::_M_hook()
UnitySupportTest:

UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare
dmi.bios.date: 07/11/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1101
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 901
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd07/11/2008:svnASUSTeKComputerINC.:pn901:pvrx.x:rvnASUSTeKComputerINC.:rn901:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 901
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.
version.libdrm2: libdrm2 2.4.23-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10-1ubuntu1
version.xserver-xorg: xserver-xorg 1:7.5+6ubuntu8
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.13.2-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.13.901-2ubuntu3
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20100805+b96170a-0ubuntu1

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #706511, 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.

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 711916, so it 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.