gnome-control-center crashed after log in to google

[jorge cob]

this happened after loggin in to google using two-step authentication

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gnome-control-center 1:3.6.3-0ubuntu24
ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11
Uname: Linux 3.8.0-23-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
Date: Sat Jun 1 12:06:47 2013
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2012-04-06 (421 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
MarkForUpload: True
ProcCmdline: gnome-control-center credentials
SegvAnalysis:
 Segfault happened at: 0x7f7965bb71a9 <g_object_ref+9>: mov (%rdi),%rax
 PC (0x7f7965bb71a9) ok
 source "(%rdi)" (0x00000001) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 tp_proxy_pending_call_cancel () from /usr/lib/x86_64-linux-gnu/libtelepathy-glib.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libtelepathy-glib.so.0
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
Title: gnome-control-center crashed with SIGSEGV in g_object_ref()
UpgradeStatus: Upgraded to raring on 2013-04-26 (36 days ago)
UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.4-0ubuntu6.1
 deja-dup 26.0-0ubuntu1
 gnome-control-center-signon 0.1.6bzr13.04.05-0ubuntu1.1
 gnome-control-center-unity 1.2daily13.04.09-0ubuntu1
 indicator-datetime 12.10.3daily13.03.26-0ubuntu1

[Apport retracing service (apport)]

StacktraceTop:
 g_object_ref (_object=0x1) at /build/buildd/glib2.0-2.36.0/./gobject/gobject.c:2884
 tp_proxy_pending_call_cancel (pc=0x7f796856faa0) at proxy-methods.c:340
 tp_connection_invalidated (self=0x7f79685a8040) at connection.c:1297
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x7fffe0841590, fn=fn@entry=0x7f7927ca8470 <tp_connection_invalidated>, rvalue=0x7fffe08414f0, avalue=avalue@entry=0x7fffe0841470) at ../src/x86/ffi64.c:522

[Sebastien Bacher (seb128)]

The bug hasn't seen any activity in years and there has been no recent similar reports, the code also changed quite a lot since and it's likely the issue doesn't exist anymore. Closing, feel free to open a new report if you still get problems in recent Ubuntu versions