Bug 682776

Summary: [abrt] rhythmbox-2.90.1-4.git20110207.fc15: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Brian Millett <bmillett>
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:b0bf46842ed59950658f110b54055c6f5016fd24
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 17:06: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:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Brian Millett 2011-03-07 15:06:57 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 45285 bytes
cmdline: rhythmbox
component: rhythmbox
Attached file: coredump, 91549696 bytes
executable: /usr/bin/rhythmbox
kernel: 2.6.38-0.rc6.git6.1.fc15.x86_64
package: rhythmbox-2.90.1-4.git20110207.fc15
rating: 3
reason: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
release: Fedora release 15 (Lovelock)
time: 1299509764
uid: 500

How to reproduce
-----
1.
2.launch rhymbox
3.
Comment 1 Brian Millett 2011-03-07 15:06:59 UTC 
Created attachment 482697 [details]
File: backtrace
Comment 2 Brian Millett 2011-03-11 18:09:06 UTC 
Package: rhythmbox-2.90.1-4.git20110207.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)


How to reproduce
-----
1.
2.launch rhythmbox
3.
Comment 3 abrt-bot 2012-03-20 17:06:04 UTC 
Backtrace analysis found this bug to be similar to bug #718118, closing as duplicate.

Bugs which were found to be similar to this bug: bug #682916, bug #693059, bug #707194, bug #718118

This comment is automatically generated.

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