compiz crashed with SIGSEGV in nux::ROProperty<std::string>::operator std::string()

Bug #945694 reported by Jorge Castro
62
This bug affects 9 people
Affects Status Importance Assigned to Milestone
Nux
Won't Fix
Medium
Unassigned
nux (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Crash browsing around on the web

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: libnux-2.0-0 2.4.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.94-0ubuntu1
Architecture: amd64
Date: Fri Mar 2 12:42:33 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0xdc2e610: and %al,(%rax)
 PC (0x0dc2e610) in non-executable VMA region: 0x0165b000-0x134c5000 rw-p [heap]
 source "%al" ok
 destination "(%rax)" (0x7ffff3a9f7c0) ok
SegvReason: executing writable VMA [heap]
Signal: 11
SourcePackage: nux
StacktraceTop:
 ?? ()
 nux::ROProperty<std::string>::operator std::string() const () from /usr/lib/compiz/libunityshell.so
 unity::dash::ResultViewGrid::OnKeyNavFocusChange(nux::Area*, bool, nux::KeyNavDirection) () from /usr/lib/compiz/libunityshell.so
 sigc::internal::signal_emit3<void, nux::Area*, bool, nux::KeyNavDirection, sigc::nil>::emit(sigc::internal::signal_impl*, nux::Area* const&, bool const&, nux::KeyNavDirection const&) () from /usr/lib/libnux-2.0.so.0
 nux::WindowCompositor::SetKeyFocusArea(nux::InputArea*, nux::KeyNavDirection) () from /usr/lib/libnux-2.0.so.0
Title: compiz crashed with SIGSEGV in nux::ROProperty<std::string>::operator std::string()
UpgradeStatus: Upgraded to precise on 2011-12-02 (92 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

Revision history for this message
Jorge Castro (jorge) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 operator() (this=<optimized out>) at /usr/include/sigc++-2.0/sigc++/functors/slot.h:440
 nux::ROProperty<std::string>::operator std::string (this=<optimized out>) at /usr/include/Nux-2.0/NuxCore/Property-inl.h:142
 unity::dash::ResultViewGrid::OnKeyNavFocusChange (this=0xcb19240, area=<optimized out>, has_focus=<optimized out>, direction=nux::KEY_NAV_DOWN) at /build/buildd/unity-5.4.0/plugins/unityshell/src/ResultViewGrid.cpp:497
 sigc::internal::signal_emit3<void, nux::Area*, bool, nux::KeyNavDirection, sigc::nil>::emit (impl=<optimized out>, _A_a1=@0x7ffff3a9f8b8, _A_a2=@0x7ffff3a9f8cf, _A_a3=@0x7ffff3a9f88c) at /usr/include/sigc++-2.0/sigc++/signal.h:1501

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 nux (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nux (Ubuntu):
status: New → Confirmed
Changed in nux:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Will Cooke (willcooke) wrote :

As part of the big bug clear up for 16.04 LTS I am marking this bug as Wont Fix.
These types of crasher are better handled by errors.ubutnu.com which can collate similar crash reports to help us identify persitent bugs rather than one-off crashes.
Sorry we are not able to help with this specific issue. If you are still experiencing this crash, please re-open the bug and add the tag "desktop-bugscrub-reopened". See https://wiki.ubuntu.com/BigDesktopBugScrub for more information.

Changed in nux:
status: Confirmed → Won't Fix
Changed in nux (Ubuntu):
status: Confirmed → Won't Fix
tags: added: desktop-bugscrub-autoclosed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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