indicator-sync-service crashed with signal 5 in g_simple_async_result_complete()

[Richard Chadwick]

just booting into the system

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: indicator-sync 12.10.5daily13.06.19-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-0.7-generic 3.10.0-rc7
Uname: Linux 3.10.0-0-generic i686
ApportVersion: 2.10.2-0ubuntu3
Architecture: i386
Date: Fri Jun 28 21:29:59 2013
ExecutablePath: /usr/lib/i386-linux-gnu/indicator-sync/indicator-sync-service
InstallationDate: Installed on 2013-05-05 (55 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
MarkForUpload: True
ProcCmdline: /usr/lib/i386-linux-gnu/indicator-sync/indicator-sync-service
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
Signal: 5
SourcePackage: indicator-sync
StacktraceTop:
 ?? ()
 g_simple_async_result_complete () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: indicator-sync-service crashed with signal 5 in g_simple_async_result_complete()
UpgradeStatus: Upgraded to saucy on 2013-06-14 (16 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 on_got_bus (o=0x0, res=0x91c50e0, user_data=user_data@entry=0x8057348 <sync_service>) at sync-service.c:599
 g_simple_async_result_complete (simple=0x91c50e0) at /build/buildd/glib2.0-2.37.3/./gio/gsimpleasyncresult.c:777
 complete_in_idle_cb (data=data@entry=0x91c50e0) at /build/buildd/glib2.0-2.37.3/./gio/gsimpleasyncresult.c:789
 g_idle_dispatch (source=source@entry=0x91cb518, callback=0xb75e3220 <complete_in_idle_cb>, user_data=0x91c50e0) at /build/buildd/glib2.0-2.37.3/./glib/gmain.c:5235
 g_main_dispatch (context=0x91cdc70) at /build/buildd/glib2.0-2.37.3/./glib/gmain.c:3058

[Launchpad Janitor (janitor)]

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

[Charles Kerr (charlesk)]

This is ameliorated by lp:~charlesk/indicator-sync/warn-on-dbus-failure but that doesn't fully explain why getting the bus is failing in the first place.