rhythmbox-metadata crashed with SIGSEGV in g_type_check_value() | while scanning music library for the first time

[Harald Höller]

While scanning the music library for the first time, rhytmbox crashed. I am using Ubuntu 12.04 beta with all recent updates.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: rhythmbox 2.96-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Thu Apr 12 10:47:57 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7faf53c87414 <g_type_check_value+52>: testb $0x8,0x16(%rbx)
 PC (0x7faf53c87414) ok
 source "$0x8" ok
 destination "0x16(%rbx)" (0x7faf00000016) 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 () from /usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0
 gst_structure_copy () from /usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0
Title: rhythmbox-metadata crashed with SIGSEGV in g_type_check_value()
UpgradeStatus: No upgrade log present (probably fresh install)
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 #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.