Bug 677530 - [abrt] rhythmbox-0.13.2-1.fc14: gst_play_sink_reconfigure: Process /usr/bin/rhythmbox was killed by signal 6 (SIGABRT)
Summary: [abrt] rhythmbox-0.13.2-1.fc14: gst_play_sink_reconfigure: Process /usr/bin/r...
Keywords:
Status: CLOSED DUPLICATE of bug 730561
Alias: None
Product: Fedora
Classification: Fedora
Component: rhythmbox
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:bee750c1fbc8467886b5f6dce7b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-15 05:58 UTC by Orion Caspar
Modified: 2012-03-20 17:40 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-20 17:40:25 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (44.79 KB, text/plain)
2011-02-15 05:59 UTC, Orion Caspar 		no flags Details
View All

Description Orion Caspar 2011-02-15 05:58:05 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: rhythmbox /media/only_music/music_2/nutcracker.mid
component: rhythmbox
crash_function: gst_play_sink_reconfigure
executable: /usr/bin/rhythmbox
kernel: 2.6.35.10-74.fc14.x86_64
package: rhythmbox-0.13.2-1.fc14
rating: 4
reason: Process /usr/bin/rhythmbox was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1297748514
uid: 500

How to reproduce
-----
1.
2.
3.
sudden crash.
Comment 1 Orion Caspar 2011-02-15 05:59:09 UTC 
Created attachment 478764 [details]
File: backtrace
Comment 2 Orion Caspar 2011-02-17 22:31:58 UTC 
Package: rhythmbox-0.13.2-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.
2.
3.
sudden crash.
Comment 3 abrt-bot 2012-03-20 17:40:25 UTC 
Backtrace analysis found this bug to be similar to bug #730561, closing as duplicate.

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 730561 ***
Note You need to log in before you can comment on or make changes to this bug.