indicator-sync-service crashed with SIGSEGV in g_type_check_instance_is_a()

[Edson T. Marques]

It crashes after system initialization, after login.

I'm using gnome-shell and I put the Empathy to run/start at the session manager.
I have a external HD connected on the USB port.
I was running Firefox and the message appeared during it's load.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: indicator-sync 12.10.5daily13.01.25-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7
Uname: Linux 3.8.0-6-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
Date: Tue Feb 19 08:03:20 2013
ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-sync/indicator-sync-service
InstallationDate: Installed on 2013-02-15 (3 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130215)
MarkForUpload: True
ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sync/indicator-sync-service
SegvAnalysis:
 Segfault happened at: 0x7fb57687400c <g_type_check_instance_is_a+60>: testb $0x4,0x16(%rdi)
 PC (0x7fb57687400c) ok
 source "$0x4" ok
 destination "0x16(%rdi)" (0x614d65766f6d6566) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: indicator-sync
StacktraceTop:
 g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? ()
Title: indicator-sync-service crashed with SIGSEGV in g_type_check_instance_is_a()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

[Apport retracing service (apport)]

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 #1121896, 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.