compiz crashed with SIGSEGV in sigc::slot_base::~slot_base()

Bug #881013 reported by Alexander Anisimov
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Compiz Core
Expired
Undecided
Unassigned
compiz (Ubuntu)
Expired
Medium
Unassigned

Bug Description

This bug report was automatically created by apport. I tried to configure compize through compize settings manager.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libnux-1.0-0 1.16.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6
Uname: Linux 3.0.0-13-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu3
Architecture: i386
CrashCounter: 1
Date: Mon Oct 24 23:59:42 2011
Disassembly: => 0x3e122bc5: Cannot access memory at address 0x3e122bc5
ExecutablePath: /usr/bin/compiz
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0x3e122bc5: Cannot access memory at address 0x3e122bc5
 PC (0x3e122bc5) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
 ?? ()
 sigc::slot_base::~slot_base() () from /usr/lib/libsigc-2.0.so.0
 std::_List_base<sigc::slot_base, std::allocator<sigc::slot_base> >::_M_clear() () from /usr/lib/libsigc-2.0.so.0
 sigc::signal_base::~signal_base() () from /usr/lib/libsigc-2.0.so.0
 LauncherIcon::~LauncherIcon() () from /usr/lib/compiz/libunityshell.so
Title: compiz crashed with SIGSEGV in sigc::slot_base::~slot_base()
UpgradeStatus: Upgraded to oneiric on 2011-10-18 (6 days ago)
UserGroups: adm admin audio cdrom dialout dip fuse lp lpadmin netdev plugdev sambashare tty vboxusers video

Revision history for this message
Alexander Anisimov (alenyashka) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 destroy (this=0x8b7bf70) at ../../sigc++/functors/slot_base.h:98
 ~slot_rep (this=0x8b7bf70, __in_chrg=<optimized out>) at ../../sigc++/functors/slot_base.h:87
 sigc::slot_base::~slot_base (this=0x8b7bf60, __in_chrg=<optimized out>) at ../../sigc++/functors/slot_base.cc:124
 destroy (__p=0x8b7bf60, this=<optimized out>) at /usr/include/c++/4.6/ext/new_allocator.h:118

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 compiz (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
jhfhlkjlj (fdsuufijjejejejej-deactivatedaccount) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. Compiz, in particular, is in heavy development and this bug may have been fixed in the development version of Ubuntu (12.04) if not on the current 11.10 release. If you are able, it would be of great help if you could confirm if the bug still exists by testing a livecd (available at http://cdimage.ubuntu.com/daily-live/current/). When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue. Please keep in mind that the development version (12.04) is not suitable for daily use - please only use it for testing purposes.

Thank you for your help and patience.

visibility: private → public
Changed in compiz (Ubuntu):
status: New → Incomplete
Changed in compiz-core:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for compiz (Ubuntu) because there has been no activity for 60 days.]

Changed in compiz (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Compiz Core because there has been no activity for 60 days.]

Changed in compiz-core:
status: Incomplete → Expired
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.