Bug 709772

Summary: [abrt] rhythmbox-0.13.3-1.fc14: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Natasha Paiva <nattynpaiva>
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:ce958c224bfdb970d66a3d1eb749b497cc448ca4
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 15:04:25 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 Natasha Paiva 2011-06-01 15:28:26 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 54042 bytes
cmdline: rhythmbox
component: rhythmbox
Attached file: coredump, 100274176 bytes
crash_function: gst_stream_get_other_pad_from_pad
executable: /usr/bin/rhythmbox
kernel: 2.6.35.13-91.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: 1306941623
uid: 500

How to reproduce
-----
1. I just tried to start Rhythmbox
2. Then, the music does not play.
3.
Comment 1 Natasha Paiva 2011-06-01 15:28:28 UTC 
Created attachment 502303 [details]
File: backtrace
Comment 2 Joel Uckelman 2011-06-05 14:03:45 UTC 
Package: rhythmbox-2.90.1-10.git20110502.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)


Comment
-----
Crashed while trying to start playback from Play Queue.
Comment 3 abrt-bot 2012-03-20 15:04:25 UTC 
Backtrace analysis found this bug to be similar to bug #706751, closing as duplicate.

This comment is automatically generated.

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