Bug 708675 - [abrt] rhythmbox-0.13.3-1.fc14: g_str_hash: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
Summary: [abrt] rhythmbox-0.13.3-1.fc14: g_str_hash: Process /usr/bin/rhythmbox was ki...
Keywords:
Status: CLOSED DUPLICATE of bug 670050
Alias: None
Product: Fedora
Classification: Fedora
Component: rhythmbox
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:a1244078d933a5bc88e1f6fa8ad...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-28 19:15 UTC by Mike Parker
Modified: 2012-03-20 17:09 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-20 17:09:38 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (59.75 KB, text/plain)
2011-05-28 19:16 UTC, Mike Parker 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Mike Parker 2011-05-28 19:15:55 UTC 
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 61186 bytes
cmdline: rhythmbox '/home/alan/.gvfs/cdda mount on sr0'
component: rhythmbox
Attached file: coredump, 114233344 bytes
crash_function: g_str_hash
executable: /usr/bin/rhythmbox
kernel: 2.6.35.13-91.fc14.i686
package: rhythmbox-0.13.3-1.fc14
rating: 4
reason: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1306609486
uid: 500

How to reproduce
-----
1. Exactly the same as Bug #677241 except that this gave a SIGSEGV rather than a SIGFPE
2.
3.
Comment 1 Mike Parker 2011-05-28 19:16:00 UTC 
Created attachment 501514 [details]
File: backtrace
Comment 2 0000 2012-01-04 00:17:48 UTC 
Package: rhythmbox-0.13.3-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.ドリマム聞いていました
2.クラッシュしました。
3.
Comment 3 abrt-bot 2012-03-20 17:09:38 UTC 
Backtrace analysis found this bug to be similar to bug #670050, closing as duplicate.

Bugs which were found to be similar to this bug: bug #553829, bug #556145, bug #604436, bug #627558, bug #657393, bug #670050, bug #682087, bug #693649, bug #694992

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 670050 ***
Note You need to log in before you can comment on or make changes to this bug.