Bug 622210 - [abrt] crash in rhythmbox-0.12.8-4.fc13: gst_adder_sink_event: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in rhythmbox-0.12.8-4.fc13: gst_adder_sink_event: Process /usr/b...
Keywords:
Status: CLOSED DUPLICATE of bug 599188
Alias: None
Product: Fedora
Classification: Fedora
Component: rhythmbox
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:9c03882ee43d054d04ae3acac80...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-08 05:29 UTC by Saikat Guha
Modified: 2010-11-08 19:17 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-08 19:17:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (74.23 KB, text/plain)
2010-08-08 05:29 UTC, Saikat Guha
no flags Details

Description Saikat Guha 2010-08-08 05:29:23 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: rhythmbox
comment: Rhythmbox was playing files on my iPhone in the background. It randomly crashed.
component: rhythmbox
crash_function: gst_adder_sink_event
executable: /usr/bin/rhythmbox
global_uuid: 9c03882ee43d054d04ae3acac80f58e13183cdb7
kernel: 2.6.33.6-147.2.4.fc13.x86_64
package: rhythmbox-0.12.8-4.fc13
rating: 4
reason: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1.Play music in the background off of an iPhone
2.Non deterministric crash

Comment 1 Saikat Guha 2010-08-08 05:29:27 UTC
Created attachment 437408 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-08 19:17:41 UTC

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

Comment 3 Karel Klíč 2010-11-08 19:17:41 UTC
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #599188.

Sorry for the inconvenience.


Note You need to log in before you can comment on or make changes to this bug.