Bug 693649

Summary: [abrt] rhythmbox-0.13.3-1.fc14: g_str_hash: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: bugzillamail
Component: rhythmboxAssignee: Bastien Nocera <bnocera>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: bnocera
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:3d1893be213655792dddc931884d67154a3feda5
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 17:09:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description bugzillamail 2011-04-05 08:16:45 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 67157 bytes
cmdline: rhythmbox '/home/zeuz/.gvfs/cdda mount on sr0'
component: rhythmbox
Attached file: coredump, 162410496 bytes
crash_function: g_str_hash
executable: /usr/bin/rhythmbox
kernel: 2.6.35.11-83.fc14.x86_64
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: 1301991163
uid: 500

How to reproduce
-----
1. I first started rhythmbox, then vlc
2. Did some tests with speaker-test with various numbers of channels
3. rhythmbox crashed as I closed it
Comment 1 bugzillamail 2011-04-05 08:16:48 UTC 
Created attachment 489937 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-20 17:09:47 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 #694992, bug #708675

This comment is automatically generated.

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