rhythmbox-metadata crashed with SIGSEGV in g_type_check_value()

[eris23]

Rhythmbox was indexing new songs. No music was being played.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: rhythmbox 2.97-1ubuntu5
ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
Date: Sat Oct 6 17:07:10 2012
ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120312)
ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7ff6ee7fd2fc <g_type_check_value+108>: cmpq $0x0,(%rax)
 PC (0x7ff6ee7fd2fc) ok
 source "$0x0" ok
 destination "(%rax)" (0x6c8948d0245c8948) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 g_type_check_value () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 gst_value_init_and_copy (dest=0x7fffbab35418, src=0x7ff6d40b3658) at gstvalue.c:4007
 gst_structure_copy (structure=0x7ff6e40b70a0) at gststructure.c:312
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 gst_structure_id_set_valist_internal (structure=0x1f91220, fieldname=1, varargs=0x7fffbab35538) at gststructure.c:642
Title: rhythmbox-metadata crashed with SIGSEGV in g_type_check_value()
UpgradeStatus: Upgraded to quantal on 2012-10-03 (3 days ago)
UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo video

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