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

Bug #1206305 reported by Evan Huus
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
indicator-sync (Ubuntu)
New
Undecided
Unassigned

Bug Description

I had just logged in, didn't do anything when this and several others popped up.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: indicator-sync 12.10.5daily13.06.19-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-5.15-generic 3.10.2
Uname: Linux 3.10.0-5-generic x86_64
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
Date: Sat Jul 27 09:13:34 2013
ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-sync/indicator-sync-service
ExecutableTimestamp: 1371609285
InstallationDate: Installed on 2011-09-24 (671 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2)
MarkForUpload: True
ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sync/indicator-sync-service
ProcCwd: /home/eapache
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/zsh
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
Signal: 5
SourcePackage: indicator-sync
StacktraceTop:
 ?? ()
 g_simple_async_result_complete (simple=0xe3da00) at /build/buildd/glib2.0-2.37.3/./gio/gsimpleasyncresult.c:777
 complete_in_idle_cb (data=0xe3da00) at /build/buildd/glib2.0-2.37.3/./gio/gsimpleasyncresult.c:789
 g_main_dispatch (context=0xe3bdc0) at /build/buildd/glib2.0-2.37.3/./glib/gmain.c:3058
 g_main_context_dispatch (context=context@entry=0xe3bdc0) at /build/buildd/glib2.0-2.37.3/./glib/gmain.c:3634
Title: indicator-sync-service crashed with signal 5 in g_simple_async_result_complete()
UpgradeStatus: Upgraded to saucy on 2013-06-08 (49 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare wireshark

Revision history for this message
Evan Huus (eapache) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1196314, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
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.