gnome-contacts-search-provider crashed with signal 5 in g_variant_new_va()

[Baldrick]

Happened after Empathy or thunderbird was launched, sorry can't remember which.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gnome-contacts 3.6.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2
Uname: Linux 3.8.0-12-generic i686
ApportVersion: 2.9.1-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Sat Mar 16 08:16:25 2013
ExecutablePath: /usr/lib/gnome-contacts/gnome-contacts-search-provider
InstallationDate: Installed on 2013-03-07 (8 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130306)
MarkForUpload: True
ProcCmdline: /usr/lib/gnome-contacts/gnome-contacts-search-provider
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_NZ:en
 LANG=en_NZ.UTF-8
Signal: 5
SourcePackage: gnome-contacts
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_variant_new_va () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_variant_new () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: gnome-contacts-search-provider crashed with signal 5 in g_variant_new_va()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
XsessionErrors:
 gnome-session[1851]: WARNING: Application 'gnome-shell.desktop' killed by signal 11
 (process:6091): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed
 (thunderbird:6091): GLib-CRITICAL **: g_variant_new_string: assertion `string != NULL' failed
 (gnome-shell:2413): Clutter-WARNING **: Actor '<searchEntry>[<StEntry>:0xa28a1b0]' should not be mapped if parent '<overview>[<StWidget>:0x9dbc5b0]'is not visible

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