Ubuntu
unity package

compiz crashed with SIGSEGV in std::__detail::_List_node_base::_M_hook() from sigc::internal::signal_impl::insert() from sigc::internal::signal_impl::connect()

Bug #1011496 reported by Iain Lane
50
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Unity
Fix Released
High
Unassigned
unity (Ubuntu)
Fix Released
High
Unassigned

Bug Description

At session start

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: unity 5.12-0ubuntu3
ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0
Uname: Linux 3.4.0-5-generic x86_64
ApportVersion: 2.1.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Mon Jun 11 09:59:20 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0x7f321b87e950 <_ZNSt8__detail15_List_node_base7_M_hookEPS0_>: mov 0x8(%rsi),%rax
 PC (0x7f321b87e950) ok
 source "0x8(%rsi)" (0x0001807d) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown 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
 sigc::internal::signal_impl::insert(std::_List_iterator<sigc::slot_base>, sigc::slot_base const&) () from /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0
 sigc::internal::signal_impl::connect(sigc::slot_base const&) () from /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0
 sigc::signal_base::connect(sigc::slot_base const&) () from /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0
 unity::UnityScreen::UnityScreen(CompScreen*) () from /usr/lib/compiz/libunityshell.so
Title: compiz crashed with SIGSEGV in std::__detail::_List_node_base::_M_hook()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo

Revision history for this message
Iain Lane (laney) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 std::__detail::_List_node_base::_M_hook (this=0x2688860, __position=0x18075) at ../../../../../src/libstdc++-v3/src/c++98/list.cc:131
 insert (__x=..., __position=..., this=<optimized out>) at /usr/include/c++/4.6/bits/list.tcc:103
 sigc::internal::signal_impl::insert (this=0x1806d, i=..., slot_=...) at ../../sigc++/signal_base.cc:64
 sigc::internal::signal_impl::connect (this=<optimized out>, slot_=...) at ../../sigc++/signal_base.cc:54
 sigc::signal_base::connect (this=<optimized out>, slot_=...) at ../../sigc++/signal_base.cc:122

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
Daniel van Vugt (vanvugt)
summary: compiz crashed with SIGSEGV in std::__detail::_List_node_base::_M_hook()
+ from sigc::internal::signal_impl::insert from
+ sigc::internal::signal_impl::connect
Changed in unity (Ubuntu):
importance: Medium → High
Changed in unity:
importance: Undecided → High
Revision history for this message
Iain Lane (laney) wrote : Re: compiz crashed with SIGSEGV in std::__detail::_List_node_base::_M_hook() from sigc::internal::signal_impl::insert from sigc::internal::signal_impl::connect

I'm an idiot.

Changed in unity (Ubuntu):
status: New → Invalid
Changed in unity:
status: New → Invalid
Daniel van Vugt (vanvugt)
summary: compiz crashed with SIGSEGV in std::__detail::_List_node_base::_M_hook()
- from sigc::internal::signal_impl::insert from
- sigc::internal::signal_impl::connect
+ from sigc::internal::signal_impl::insert() from
+ sigc::internal::signal_impl::connect()
Changed in unity:
status: Invalid → Confirmed
Changed in unity (Ubuntu):
status: Invalid → Confirmed
Changed in unity:
milestone: none → 6.2
Didier Roche-Tolomelli (didrocks)
Changed in unity:
milestone: 6.2 → 6.4
Daniel van Vugt (vanvugt)
Changed in unity:
milestone: 6.4 → 6.6
Daniel van Vugt (vanvugt)
Changed in unity:
milestone: 6.6 → 7.0
Stephen M. Webb (bregma)
Changed in unity:
milestone: 7.0.0 → 7.0.1
Marco Trevisan (Treviño) (3v1n0)
Changed in unity:
milestone: 7.0.1 → 7.3.1
Stephen M. Webb (bregma)
Changed in unity:
milestone: 7.3.1 → 7.3.2
Stephen M. Webb (bregma)
Changed in unity:
milestone: 7.3.2 → 7.3.3
Revision history for this message
Christopher Townsend (townsend) wrote :

This is a rather old bug report now and there have been no new reports of this issue. It seems it's been fixed some releases ago, so I'm marking as such.

If this does still occur, we can either reopen this bug report or open a new one.

Changed in unity:
status: Confirmed → Fix Released
Changed in unity (Ubuntu):
status: Confirmed → Fix Released
Changed in unity:
milestone: 7.3.3 → none
Apport retracing service (apport)
tags: added: wily
Revision history for this message
Hans Joachim Desserud (hjd) wrote :

>If this does still occur, we can either reopen this bug report or open a new one.

Hello.

I recently encountered bug 1497426 on Ubuntu Wily, which was automatically marked as a duplicate of this one. It's not clear to me how it was triggered as it was apport reporting a crash. However, if it is indeed a duplicate it looks like this issue has resurfaced. How do you prefer we proceed with this, should I reopen bug 1497426 so that someone may take a look at it?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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