rhythmbox crashed with SIGSEGV in _int_free()

[Sasa Paporovic]

I am on Ubuntu12.04 64bit updated to 17.4.2012.

I have played .wav files from harddrive with rythembox. Then paused them and switches in rhythmbox to the cd entry(cd was already in cd/dvd drive). There I double clicked on one of the track entries of the cd(number 6) to start the playing. On this rhythembox crashed.

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
ApportVersion: 2.0.1-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Tue Apr 17 14:36:49 2012
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64+mac (20120328)
ProcCmdline: rhythmbox
ProcEnviron:
 PATH=(custom, no username)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fc0bdf1f031 <_int_free+209>: mov 0x8(%rdx),%rsi
 PC (0x7fc0bdf1f031) ok
 source "0x8(%rdx)" (0x200000410) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 _int_free (av=0x7fc0be256720, p=0x287d780, have_lock=0) at malloc.c:4005
 g_variant_type_info_get () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_variant_new_from_data () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: rhythmbox crashed with SIGSEGV in _int_free()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout 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 #968624, 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.