gnome-control-center crashed with SIGSEGV in identity_removed_cb()

Bug #1157559 reported by Richard King
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-control-center-signon (Ubuntu)
Confirmed
High
David King

Bug Description

i was setting up the system online accounts and this error occured

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gnome-control-center 1:3.6.3-0ubuntu16
ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3
Uname: Linux 3.8.0-13-generic x86_64
ApportVersion: 2.9.2-0ubuntu1
Architecture: amd64
Date: Wed Mar 20 10:03:28 2013
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2013-03-17 (2 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130317)
MarkForUpload: True
ProcCmdline: gnome-control-center info
SegvAnalysis:
 Segfault happened at: 0x7f0b50dff410: movl $0x0,0x44(%rax)
 PC (0x7f0b50dff410) ok
 source "$0x0" ok
 destination "0x44(%rax)" (0xaaaaaaaaaaaaaaee) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 ?? () from /usr/lib/libaccount-plugin-1.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libsignon-glib.so.1
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in g_simple_async_result_complete()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors:
 gnome-session[2547]: WARNING: Failed to start app: Unable to start application: Failed to execute child process "synaptikscfg" (No such file or directory)
 (dropbox:2704): LIBDBUSMENU-GLIB-WARNING **: About to Show called on an item wihtout submenus. We're ignoring it.
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.4-0ubuntu6.1
 deja-dup 25.5-0ubuntu1
 gnome-control-center-signon 0.1.3bzr13.02.20-0ubuntu1
 gnome-control-center-unity 1.2daily13.02.15-0ubuntu1
 indicator-datetime 12.10.3daily13.03.07-0ubuntu1

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

StacktraceTop:
 identity_removed_cb (identity=<optimized out>, error=0x0, user_data=<optimized out>) at libaccount-plugin/oauth-plugin.c:139
 identity_removed_reply (object=<optimized out>, res=0x7f0b987aab50, userdata=userdata@entry=0x7f0b98515300) at signon-identity.c:1105
 g_simple_async_result_complete (simple=0x7f0b987aab50) at /build/buildd/glib2.0-2.35.8/./gio/gsimpleasyncresult.c:777
 reply_cb (connection=<optimized out>, res=0x7f0b988e2410, user_data=user_data@entry=0x7f0b987aab50) at /build/buildd/glib2.0-2.35.8/./gio/gdbusproxy.c:2632
 g_simple_async_result_complete (simple=0x7f0b988e2410) at /build/buildd/glib2.0-2.35.8/./gio/gsimpleasyncresult.c:777

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 gnome-control-center (Ubuntu):
importance: Undecided → Medium
summary: - gnome-control-center crashed with SIGSEGV in
- g_simple_async_result_complete()
+ gnome-control-center crashed with SIGSEGV in identity_removed_cb()
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-control-center (Ubuntu):
status: New → Confirmed
information type: Private → Public
affects: gnome-control-center (Ubuntu) → gnome-control-center-signon (Ubuntu)
Changed in gnome-control-center-signon (Ubuntu):
importance: Medium → High
Changed in gnome-control-center-signon (Ubuntu):
assignee: nobody → David King (amigadave)
Revision history for this message
Thibault D (thibdrev) wrote :

This bug might be related to bug #1158401

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.