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

Bug #1206678 reported by Nicolas DERIVE
38
This bug affects 8 people
Affects Status Importance Assigned to Milestone
unity-scope-gdrive (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Searching something using unity dash, I got this crash from scope-runner.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: unity-scopes-runner 7.0.9+13.10.20130729-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
Uname: Linux 3.10.0-6-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.11-0ubuntu1
Architecture: i386
CheckboxSubmission: c4273c0f4f2b8d26cd6bf31cadfd2912
CheckboxSystem: a871981cb5bdf4d6ebd55be46becf77e
Date: Tue Jul 30 22:40:57 2013
Dependencies:

EcryptfsInUse: Yes
ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s files/gdrive.scope
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=fr_FR:en
 PATH=(custom, user)
 LANG=fr_FR.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb5149836: cmp %edi,(%eax)
 PC (0xb5149836) ok
 source "%edi" ok
 destination "(%eax)" (0xaaaaaaaa) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: libunity
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/libsignon-glib.so.1
 ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic (closure=0x8f800a0, return_gvalue=0x0, n_param_values=3, param_values=0x8fc6dc0, invocation_hint=0xbf9c1d6c, marshal_data=0x0) at /build/buildd/glib2.0-2.37.3/./gobject/gclosure.c:1454
 g_closure_invoke (closure=0x8f800a0, return_value=return_value@entry=0x0, n_param_values=3, param_values=param_values@entry=0x8fc6dc0, invocation_hint=invocation_hint@entry=0xbf9c1d6c) at /build/buildd/glib2.0-2.37.3/./gobject/gclosure.c:777
Title: scope-runner-dbus.py crashed with SIGSEGV in ffi_call_SYSV()
UpgradeStatus: Upgraded to saucy on 2013-05-25 (65 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev pulse pulse-access scanner tape users video

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

StacktraceTop:
 auth_session_state_changed_cb (proxy=0x8f80550, state=8, message=0x8fc6ed8 "The request is started successfully", user_data=0xb0b05850) at signon-auth-session.c:746
 ffi_call_SYSV () at ../src/x86/sysv.S:65
 ffi_call (cif=cif@entry=0xbf9c1c54, fn=0xb5149810 <auth_session_state_changed_cb>, rvalue=0xbf9c1be0, avalue=avalue@entry=0xbf9c1ba0) at ../src/x86/ffi.c:411
 g_cclosure_marshal_generic (closure=0x8f800a0, return_gvalue=0x0, n_param_values=3, param_values=0x8fc6dc0, invocation_hint=0xbf9c1d6c, marshal_data=0x0) at /build/buildd/glib2.0-2.37.3/./gobject/gclosure.c:1454
 g_closure_invoke (closure=0x8f800a0, return_value=return_value@entry=0x0, n_param_values=3, param_values=param_values@entry=0x8fc6dc0, invocation_hint=invocation_hint@entry=0xbf9c1d6c) at /build/buildd/glib2.0-2.37.3/./gobject/gclosure.c:777

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 libunity (Ubuntu):
importance: Undecided → Medium
summary: - scope-runner-dbus.py crashed with SIGSEGV in ffi_call_SYSV()
+ scope-runner-dbus.py crashed with SIGSEGV in
+ auth_session_state_changed_cb()
tags: removed: need-i386-retrace
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in libunity (Ubuntu):
status: New → Confirmed
Michal Hruby (mhr3)
affects: libunity (Ubuntu) → unity-scope-gdrive (Ubuntu)
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.