unity-scope-loader crashed with SIGSEGV in cached_dir_invoke_monitors()

Bug #1235541 reported by Matthew Perrone on 2013-10-05
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
unity-lens-applications (Ubuntu)
Medium
Unassigned

Bug Description

crashed while attempting to install the game limbo by terminal

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: libunity9 7.1.2+13.10.20131003-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-11-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
Date: Fri Oct 4 19:52:19 2013
ExecutablePath: /usr/bin/unity-scope-loader
InstallationDate: Installed on 2013-10-04 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
MarkForUpload: True
ProcCmdline: /usr/bin/unity-scope-loader applications/applications.scope applications/scopes.scope commands.scope applications/runningapps.scope
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fe0567f57e0: mov (%rbx),%rax
 PC (0x7fe0567f57e0) ok
 source "(%rbx)" (0x2d706f746b736564) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: libunity
StacktraceTop:
 ?? () from /usr/lib/libgnome-menu-3.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 unity_scope_dbus_connector_run () from /usr/lib/x86_64-linux-gnu/libunity.so.9
Title: unity-scope-loader crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Matthew Perrone (matt-perrone) wrote :
information type: Private → Public

StacktraceTop:
 cached_dir_invoke_monitors (dir=0x1f080d0) at /build/buildd/gnome-menus-3.8.0/./libmenu/entry-directories.c:446
 emit_monitors_in_idle () at /build/buildd/gnome-menus-3.8.0/./libmenu/entry-directories.c:474
 g_main_dispatch (context=0x1cc92b0) at /build/buildd/glib2.0-2.38.0/./glib/gmain.c:3065
 g_main_context_dispatch (context=context@entry=0x1cc92b0) at /build/buildd/glib2.0-2.38.0/./glib/gmain.c:3641
 g_main_context_iterate (context=0x1cc92b0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at /build/buildd/glib2.0-2.38.0/./glib/gmain.c:3712

Changed in libunity (Ubuntu):
importance: Undecided → Medium
summary: - unity-scope-loader crashed with SIGSEGV in g_main_context_dispatch()
+ unity-scope-loader crashed with SIGSEGV in cached_dir_invoke_monitors()
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

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

Changed in libunity (Ubuntu):
status: New → Confirmed
Michal Hruby (mhr3) on 2013-10-16
affects: libunity (Ubuntu) → unity-lens-applications (Ubuntu)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers