rhythmbox-metadata crashed with SIGSEGV in type_get_qdata_L()

[Ted Gould]

Scanning through my library.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: rhythmbox 2.90.1~20110908-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Tue Sep 27 22:15:05 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f4b596bdcb7 <g_type_check_value+311>: mov (%rax),%ecx
 PC (0x7f4b596bdcb7) ok
 source "(%rax)" (0x00000001) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 type_get_qdata_L (quark=1, node=0x7f4b50333e60) at /build/buildd/glib2.0-2.30.0/./gobject/gtype.c:3611
 type_check_is_value_type_U (type=<optimized out>) at /build/buildd/glib2.0-2.30.0/./gobject/gtype.c:4093
 g_type_check_value (value=<optimized out>) at /build/buildd/glib2.0-2.30.0/./gobject/gtype.c:4126
 gst_value_init_and_copy () from /usr/lib/libgstreamer-0.10.so.0
 gst_structure_copy () from /usr/lib/libgstreamer-0.10.so.0
Title: rhythmbox-metadata crashed with SIGSEGV in type_get_qdata_L()
UpgradeStatus: Upgraded to oneiric on 2011-06-17 (102 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev sambashare tape video

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #855877, 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.