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

[krumbi]

x hang up, only by init 6 I was able to restart

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 i686
NonfreeKernelModules: wl
ApportVersion: 2.8-0ubuntu4
Architecture: i386
CrashCounter: 1
Date: Sat Feb 16 10:29:30 2013
ExecutablePath: /usr/lib/i386-linux-gnu/indicator-sync/indicator-sync-service
InstallationDate: Installed on 2012-10-21 (117 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
MarkForUpload: True
ProcCmdline: /usr/lib/i386-linux-gnu/indicator-sync/indicator-sync-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb7607cf7 <g_type_check_instance_is_a+87>: testb $0x4,0xe(%ecx)
 PC (0xb7607cf7) ok
 source "$0x4" ok
 destination "0xe(%ecx)" (0x67726f3a) 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/i386-linux-gnu/libgobject-2.0.so.0
 g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? ()
Title: indicator-sync-service crashed with SIGSEGV in g_type_check_instance_is_a()
UpgradeStatus: Upgraded to raring on 2013-02-04 (11 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[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 #1123924, 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.