Bug 684044 - [abrt] rhythmbox-2.90.1-4.git20110207.fc15: g_hash_table_lookup_node: Process /usr/bin/rhythmbox was killed by signal 8 (SIGFPE)
Summary: [abrt] rhythmbox-2.90.1-4.git20110207.fc15: g_hash_table_lookup_node: Process...
Keywords:
Status: CLOSED DUPLICATE of bug 648210
Alias: None
Product: Fedora
Classification: Fedora
Component: rhythmbox
Version: 15
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:b4f6c36babbc8a7ff782b2291d2...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-10 23:28 UTC by Gerard Ryan
Modified: 2012-03-21 15:56 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-03-21 15:56:29 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (39.35 KB, text/plain)
2011-03-10 23:28 UTC, Gerard Ryan
no flags Details

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 ***


Note You need to log in before you can comment on or make changes to this bug.