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

[John Lenton]

No idea.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: indicator-sync 12.10.5daily13.01.25-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-7.14-generic 3.8.0
Uname: Linux 3.8.0-7-generic i686
ApportVersion: 2.8-0ubuntu4
Architecture: i386
CrashCounter: 1
Date: Tue Feb 19 22:47:26 2013
ExecutablePath: /usr/lib/i386-linux-gnu/indicator-sync/indicator-sync-service
InstallationDate: Installed on 2010-10-09 (867 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928.1)
MarkForUpload: True
ProcCmdline: /usr/lib/i386-linux-gnu/indicator-sync/indicator-sync-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, user)
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: indicator-sync
StacktraceTop:
 type_check_is_value_type_U (type=<optimized out>) at /build/buildd/glib2.0-2.35.8/./gobject/gtype.c:4133
 g_type_check_is_value_type (type=3075502080) at /build/buildd/glib2.0-2.35.8/./gobject/gtype.c:4162
 ?? ()
Title: indicator-sync-service crashed with SIGSEGV in type_check_is_value_type_U()
UpgradeStatus: Upgraded to raring on 2012-06-19 (248 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare video

[Apport retracing service (apport)]

StacktraceSource:
 #0 0xb753acf7 in type_check_is_value_type_U (type=<optimized out>) at /build/buildd/glib2.0-2.35.8/./gobject/gtype.c:4133
   [Error: /build/buildd/glib2.0-2.35.8/./gobject/gtype.c was not found in source tree]
 #1 g_type_check_is_value_type (type=3075502080) at /build/buildd/glib2.0-2.35.8/./gobject/gtype.c:4162
   [Error: /build/buildd/glib2.0-2.35.8/./gobject/gtype.c was not found in source tree]
 #2 0x09f3e318 in ?? ()
StacktraceTop:
 type_check_is_value_type_U (type=<optimized out>) at /build/buildd/glib2.0-2.35.8/./gobject/gtype.c:4133
 g_type_check_is_value_type (type=3075502080) at /build/buildd/glib2.0-2.35.8/./gobject/gtype.c:4162
 ?? ()

[Launchpad Janitor (janitor)]

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