compiz crashed with SIGSEGV in unity::launcher::LauncherModel::end from unity::launcher::Controller::Impl::OnLauncherAddRequestSpecial from unity::launcher::Controller::Impl::OnDBusMethodCall

Bug #1065364 reported by Adolfo Jayme Barrientos
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Unity
New
Undecided
Unassigned
unity (Ubuntu)
New
Medium
Unassigned

Bug Description

Sorry, but this time I don't remember what happened. Apport popped up after a reboot.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: unity 6.8.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.6.1-0ubuntu2
Architecture: i386
Date: Wed Oct 10 11:50:53 2012
ExecutablePath: /usr/bin/compiz
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=es_MX:es
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=es_MX.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb337d958 <_ZN5unity8launcher13LauncherModel3endEv+8>: mov 0x4c(%edx),%edx
 PC (0xb337d958) ok
 source "0x4c(%edx)" (0x000000e4) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 unity::launcher::LauncherModel::end() () from /usr/lib/compiz/libunityshell.so
 unity::launcher::Controller::Impl::OnLauncherAddRequestSpecial(std::string const&, std::string const&, std::string const&, int, int, int) () from /usr/lib/compiz/libunityshell.so
 unity::launcher::Controller::Impl::OnDBusMethodCall(_GDBusConnection*, char const*, char const*, char const*, char const*, _GVariant*, _GDBusMethodInvocation*, void*) () from /usr/lib/compiz/libunityshell.so
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: compiz crashed with SIGSEGV in unity::launcher::LauncherModel::end()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Adolfo Jayme Barrientos (fitojb) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __normal_iterator (this=0xbfadfbdc, __i=<optimized out>) at /usr/include/c++/4.6/bits/stl_iterator.h:720
 end (this=0xe0) at /usr/include/c++/4.6/bits/stl_vector.h:482
 unity::launcher::LauncherModel::end (this=0x98) at /build/buildd/unity-6.8.0/launcher/LauncherModel.cpp:439
 unity::launcher::Controller::Impl::OnLauncherAddRequestSpecial (this=0x9f958c8, path=..., aptdaemon_trans_id=..., icon_path=..., icon_x=-1079116836, icon_y=-1079116836, icon_size=96) at /build/buildd/unity-6.8.0/launcher/LauncherController.cpp:375
 unity::launcher::Controller::Impl::OnDBusMethodCall (connection=0xb5805040, sender=sender@entry=0xb4e10380 ":1.96", object_path=0xb4e29cb0 "/com/canonical/Unity/Launcher", interface_name=interface_name@entry=0xb4e3bb68 "com.canonical.Unity.Launcher", method_name=0xbfadfbdc "\032\266O\263\250cg\n\250cg\n\f\374\255\277\360\\g\n\220\066o\n", parameters=0xbfadfbdc, invocation=0xbfadfbdc, user_data=0xbfadfbdc) at /build/buildd/unity-6.8.0/launcher/LauncherController.cpp:1440

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in unity (Ubuntu):
importance: Undecided → Medium
summary: - compiz crashed with SIGSEGV in unity::launcher::LauncherModel::end()
+ compiz crashed with SIGSEGV in __normal_iterator()
tags: removed: need-i386-retrace
summary: - compiz crashed with SIGSEGV in __normal_iterator()
+ compiz crashed with SIGSEGV in unity::launcher::LauncherModel::end from
+ unity::launcher::Controller::Impl::OnLauncherAddRequestSpecial from
+ unity::launcher::Controller::Impl::OnDBusMethodCall
visibility: private → public
Revision history for this message
Bilal Akhtar (bilalakhtar) wrote :

This seems weird. OnLauncherAddRequestSpecial was called it seems during login, though it should only be called on an application install. Had you installed a new application in the last session?

Revision history for this message
Adolfo Jayme Barrientos (fitojb) wrote :

Hi Bilal. I guess you're right, I had used the Software Center (in Guest session) before turning off the computer.

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.