compiz crashed with SIGSEGV in unity::launcher::Controller::Impl::EnsureLaunchers() from unity::launcher::Controller::Impl::OnScreenChanged()

Bug #966127 reported by rob
30
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Unity
Won't Fix
Medium
Unassigned
unity (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

crashed, relaunched automatically and then crashed again after update / upgrade of the system by Ubuntu Software Center.

Regards,
Rob.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity 5.8.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic i686
ApportVersion: 1.95-0ubuntu1
Architecture: i386
Date: Tue Mar 27 12:45:36 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111129.1)
ProcCmdline: compiz
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: unity
Title: compiz crashed with SIGSEGV in unity::launcher::Controller::Impl::EnsureLaunchers()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
rob (lattyr) wrote :
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in unity (Ubuntu):
status: New → Confirmed
Revision history for this message
Chris J Arges (arges) wrote :

This bug occured when booting my Precise desktop after upgrading today.

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

StacktraceTop:
 unity::launcher::Controller::Impl::EnsureLaunchers (this=0x95d6a70, primary=0, monitors=...) at /build/buildd/unity-5.8.0/plugins/unityshell/src/LauncherController.cpp:286
 unity::launcher::Controller::Impl::OnScreenChanged (this=0x95d6a70, primary_monitor=0, monitors=...) at /build/buildd/unity-5.8.0/plugins/unityshell/src/LauncherController.cpp:334
 operator() (_A_a2=..., this=0x9641d94, _A_a1=<optimized out>) at /usr/include/sigc++-2.0/sigc++/functors/mem_fun.h:1917
 operator()<const int&, std::vector<nux::Rect>&> (_A_arg2=..., this=0x9641d90, _A_arg1=<optimized out>) at /usr/include/sigc++-2.0/sigc++/adaptors/adaptor_trait.h:103
 sigc::internal::slot_call2<sigc::bound_mem_functor2<void, unity::launcher::Controller::Impl, int, std::vector<nux::Rect, std::allocator<nux::Rect> >&>, void, int, std::vector<nux::Rect, std::allocator<nux::Rect> >&>::call_it (rep=0x9641d78, a_1=@0x9579fa4, a_2=...) at /usr/include/sigc++-2.0/sigc++/functors/slot.h:173

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-i386-retrace
summary: compiz crashed with SIGSEGV in
- unity::launcher::Controller::Impl::EnsureLaunchers()
+ unity::launcher::Controller::Impl::EnsureLaunchers() from
+ unity::launcher::Controller::Impl::OnScreenChanged()
Changed in unity:
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 unity:
status: Confirmed → Won't Fix
Changed in unity (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.

Other bug subscribers

Remote bug watches

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