Bug 684044

Summary: [abrt] rhythmbox-2.90.1-4.git20110207.fc15: g_hash_table_lookup_node: Process /usr/bin/rhythmbox was killed by signal 8 (SIGFPE)
Product: [Fedora] Fedora Reporter: Gerard Ryan <fedora>
Component: rhythmboxAssignee: Bastien Nocera <bnocera>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: bnocera
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:b4f6c36babbc8a7ff782b2291d2b0c3816c33d86
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-21 15:56:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Gerard Ryan 2011-03-10 23:28:13 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 40291 bytes
cmdline: rhythmbox '/home/galileo/Music/Podcasts/TuxRadar Linux Podcast (Ogg)/tuxradar_s03e05.ogg'
component: rhythmbox
Attached file: coredump, 1272090624 bytes
crash_function: g_hash_table_lookup_node
executable: /usr/bin/rhythmbox
kernel: 2.6.38-0.rc8.git0.1.fc15.x86_64
package: rhythmbox-2.90.1-4.git20110207.fc15
rating: 4
reason: Process /usr/bin/rhythmbox was killed by signal 8 (SIGFPE)
release: Fedora release 15 (Lovelock)
time: 1299798944
uid: 500

How to reproduce
-----
1. I opened rhythmbox through gpodder, with a 500gb external drive connected (on which my music library resides)
2. The progress/loading bar indicated that something was happening for a long time
3. This crash happened when I tried to quit the application.

Comment 1 Gerard Ryan 2011-03-10 23:28:16 UTC
Created attachment 483602 [details]
File: backtrace

Comment 2 abrt-bot 2012-03-21 15:56:29 UTC
Backtrace analysis found this bug to be similar to bug #648210, closing as duplicate.

Bugs which were found to be similar to this bug: bug #574999, bug #637711, bug #648210, bug #655592, bug #672021, bug #676278, bug #698735

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 648210 ***