compiz crashed with SIGSEGV in std::list<unity::debug::Introspectable*, std::allocator<unity::debug::Introspectable*> >::remove()

Bug #916792 reported by Anders Ekberg on 2012-01-15
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nux (Ubuntu)

Bug Description

Time doesn't showe in the notificaztion pane, so I was trying to use dconf to whitelist all entries just in case this was the cause (which it was not). At doing unity --replace compiz crashed on startup.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: libnux-2.0-0 2.0.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-8.15-generic 3.2.0
Uname: Linux 3.2.0-8-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.90-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Sun Jan 15 15:21:20 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120105)
ProcCmdline: compiz
 Segfault happened at: 0x7f8b3893698c <_ZNSt4listIPN5unity5debug14IntrospectableESaIS3_EE6removeERKS3_+44>: cmp %rax,0x10(%rbp)
 PC (0x7f8b3893698c) ok
 source "%rax" ok
 destination "0x10(%rbp)" (0x00000040) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: nux
 std::list<unity::debug::Introspectable*, std::allocator<unity::debug::Introspectable*> >::remove(unity::debug::Introspectable* const&) () from /usr/lib/compiz/
 unity::debug::Introspectable::~Introspectable() () from /usr/lib/compiz/
 unity::dash::SearchBar::~SearchBar() () from /usr/lib/compiz/
 unity::dash::SearchBar::~SearchBar() () from /usr/lib/compiz/
 nux::Object::Destroy() () from /usr/lib/
Title: compiz crashed with SIGSEGV in std::list<unity::debug::Introspectable*, std::allocator<unity::debug::Introspectable*> >::remove()
UpgradeStatus: Upgraded to precise on 2012-01-13 (1 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Anders Ekberg (henry-ekberg) wrote :

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #916258, 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
visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers