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

Bug #982681 reported by Jon Smirl
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity (Ubuntu)
New
Medium
Unassigned

Bug Description

Turned on the 3D cube desktop via Settings Manager. Got this crash right when I enabled it.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity 5.10.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
ApportVersion: 2.0.1-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Sun Apr 15 19:49:33 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0x7f6265772433 <_ZNSt8__detail15_List_node_base7_M_hookEPS0_+19>: mov %rdi,(%rax)
 PC (0x7f6265772433) ok
 source "%rdi" ok
 destination "(%rax)" (0x00000740) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 std::__detail::_List_node_base::_M_hook(std::__detail::_List_node_base*) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 unity::launcher::LauncherIcon::EmitNeedsRedraw() () from /usr/lib/compiz/libunityshell.so
 unity::launcher::LauncherIcon::OnDelayedUpdateTimeout(void*) () from /usr/lib/compiz/libunityshell.so
 g_timeout_dispatch (source=<optimized out>, callback=<optimized out>, user_data=<optimized out>) at /build/buildd/glib2.0-2.32.0/./glib/gmain.c:3859
 g_main_dispatch (context=0x1c8bb30) at /build/buildd/glib2.0-2.32.0/./glib/gmain.c:2515
Title: compiz crashed with SIGSEGV in std::__detail::_List_node_base::_M_hook()
UpgradeStatus: Upgraded to precise on 2012-04-02 (13 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Revision history for this message
Jon Smirl (jonsmirl) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Possible regression detected

This crash has the same stack trace characteristics as bug #944217. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

tags: added: regression-retracer
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 std::__detail::_List_node_base::_M_hook (this=0x435ae00, __position=0x2c269e8) at ../../../../src/libstdc++-v3/src/list.cc:129
 emplace<sigc::slot_base> (__position=<optimized out>, this=<optimized out>) at /usr/include/c++/4.6/bits/list.tcc:92
 insert (__x=..., __position=<optimized out>, this=<optimized out>) at /usr/include/c++/4.6/bits/stl_list.h:1062
 temp_slot_list (slots=<optimized out>, this=0x7fff300e4e20) at /usr/include/sigc++-2.0/sigc++/signal_base.h:183
 emit (_A_a1=..., impl=<optimized out>) at /usr/include/sigc++-2.0/sigc++/signal.h:1004

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in unity (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.