compiz crashed with SIGSEGV in sigc::signal_base::impl()

Bug #846658 reported by Chad Miller
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity (Ubuntu)
New
Undecided
Unassigned

Bug Description

SIGSEGV

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity 4.14.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic-pae 3.0.4
Uname: Linux 3.0.0-10-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.22.1-0ubuntu2
Architecture: i386
Date: Sat Sep 10 17:16:03 2011
ExecutablePath: /usr/bin/compiz
ProcCmdline: compiz --replace
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb7145e2e <_ZNK4sigc11signal_base4implEv+30>: mov 0x4(%edi),%esi
 PC (0xb7145e2e) ok
 source "0x4(%edi)" (0x00000084) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 sigc::signal_base::impl() const () from /usr/lib/libsigc-2.0.so.0
 sigc::signal_base::connect(sigc::slot_base const&) () from /usr/lib/libsigc-2.0.so.0
 UnityScreen::UnityScreen(CompScreen*) () from /usr/lib/compiz/libunityshell.so
 PluginClassHandler<UnityScreen, CompScreen, 0>::get(CompScreen*) () from /usr/lib/compiz/libunityshell.so
 CompPlugin::VTableForScreenAndWindow<UnityScreen, UnityWindow>::initScreen(CompScreen*) () from /usr/lib/compiz/libunityshell.so
Title: compiz crashed with SIGSEGV in sigc::signal_base::impl()
UpgradeStatus: Upgraded to oneiric on 2010-09-09 (366 days ago)
UserGroups: adm admin audio camera cdrom dialout floppy fuse lpadmin mythtv plugdev pulse pulse-access sambashare scanner staff video

Revision history for this message
Chad Miller (cmiller) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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

visibility: private → public
tags: removed: need-i386-retrace
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.