Bug 682087

Summary: [abrt] rhythmbox-2.90.1-4.git20110207.fc15: g_str_hash: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: David Le Sage <dlesage>
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, mcepl, mcepl
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:6692dfea0dfab1855a63314bf4e700bf17e35696
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 17:10:04 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 David Le Sage 2011-03-04 03:56:27 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 66059 bytes
cmdline: rhythmbox cdda://sr0/
component: rhythmbox
Attached file: coredump, 165953536 bytes
crash_function: g_str_hash
executable: /usr/bin/rhythmbox
kernel: 2.6.38-0.rc6.git4.1.fc15.x86_64
package: rhythmbox-2.90.1-4.git20110207.fc15
rating: 4
reason: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
release: Fedora release 15 (Lovelock)
time: 1299211068
uid: 500

How to reproduce
-----
1. Inserted a CD.  Rythmbox launched automatically.
2. I clicked exit and Rhythmbox crashed immediately.

Comment 1 David Le Sage 2011-03-04 03:56:30 UTC
Created attachment 482212 [details]
File: backtrace

Comment 2 Matěj Cepl 2011-03-13 19:57:14 UTC
Package: rhythmbox-2.90.1-4.git20110207.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)


How to reproduce
-----
1.just starting up RB
2.
3.


Comment
-----
the window shown up, but after a second or two, it vanished

Comment 3 abrt-bot 2012-03-20 17:10:04 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 #693649, bug #694992, bug #708675

This comment is automatically generated.

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