rhythmbox crashed with SIGFPE in g_hash_table_lookup()

[Sean Fitzpatrick]

Not really sure what went wrong, if anything, but Apport generated this crash report and it doesn't seem to match any of the existing ones. I opened Rhythmbox (first run since updating to 14.04 beta), searched for a track (it was on the radio, I knew it was in my library, but I couldn't remember who the composer was), and then closed the program. Everything seemed to work correctly but the crash report came up as soon as I closed Rhythmbox.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: rhythmbox 3.0.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
Uname: Linux 3.13.0-23-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Apr 6 18:58:58 2014
ExecutablePath: /usr/bin/rhythmbox
InstallationDate: Installed on 2014-01-04 (92 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
LogAlsaMixer:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined
   Playback channels: Mono
   Mono: Playback [on]
ProcCmdline: rhythmbox
Signal: 8
SourcePackage: rhythmbox
StacktraceTop:
 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 rb_refstring_new () from /usr/lib/librhythmbox-core.so.8
 ?? () from /usr/lib/librhythmbox-core.so.8
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 start_thread (arg=0x7f61d884e700) at pthread_create.c:312
Title: rhythmbox crashed with SIGFPE in g_hash_table_lookup()
UpgradeStatus: Upgraded to trusty on 2014-04-06 (0 days ago)
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 #1203530, 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.