Ubuntu
unity-scope-gdrive package

scope-runner-dbus.py crashed with SIGSEGV in PyObject_Call()

Bug #1237301 reported by Robbie Williamson
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
unity-scope-gdrive (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I was using the Canonical Employee Directory scope and this occurred, but fwiw the scope worked.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: unity-scopes-runner 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: Wed Oct 9 10:29:40 2013
Dependencies:

ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py
InstallationDate: Installed on 2013-01-26 (256 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python2 /usr/share/unity-scopes/scope-runner-dbus.py /usr/share/unity-scopes/canonicaldirectory/unity_canonicaldirectory_daemon.py
SegvAnalysis:
 Segfault happened at: 0x53bef0 <PyEval_CallObjectWithKeywords+80>: mov 0x18(%rcx),%esi
 PC (0x0053bef0) ok
 source "0x18(%rcx)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: libunity
StacktraceTop:
 PyEval_CallObjectWithKeywords ()
 _pyglib_handler_marshal () from /usr/lib/libpyglib-2.0-python2.7.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.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
Title: scope-runner-dbus.py crashed with SIGSEGV in PyEval_CallObjectWithKeywords()
UpgradeStatus: Upgraded to saucy on 2013-06-07 (123 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

StacktraceTop:
 PyObject_Call (kw=0x0, arg=0x7fcd2bac3050, func=0x7fcd2ba48460) at ../Objects/abstract.c:2527
 PyEval_CallObjectWithKeywords (func=0x7fcd2ba48460, arg=0x7fcd2bac3050, kw=0x0) at ../Python/ceval.c:3890
 _pyglib_handler_marshal (user_data=0x151fc30, user_data@entry=<error reading variable: value has been optimized out>) at /build/buildd/pygobject-2-2.28.6/glib/pyglib.c:532
 g_timeout_dispatch (source=source@entry=0x7fcd18001720, callback=<optimized out>, user_data=<optimized out>) at /build/buildd/glib2.0-2.38.0/./glib/gmain.c:4450
 g_main_dispatch (context=0x13eb570) at /build/buildd/glib2.0-2.38.0/./glib/gmain.c:3065

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 libunity (Ubuntu):
importance: Undecided → Medium
summary: - scope-runner-dbus.py crashed with SIGSEGV in
- PyEval_CallObjectWithKeywords()
+ scope-runner-dbus.py crashed with SIGSEGV in PyObject_Call()
tags: removed: need-amd64-retrace
Michal Hruby (mhr3)
affects: libunity (Ubuntu) → unity-scope-gdrive (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in unity-scope-gdrive (Ubuntu):
status: New → Confirmed
Michal Hruby (mhr3)
tags: added: scopes-s
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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