Bug 684514 - [abrt] rhythmbox-2.90.1-4.git20110207.fc15: __libc_message: Process /usr/bin/rhythmbox was killed by signal 6 (SIGABRT)
Summary: [abrt] rhythmbox-2.90.1-4.git20110207.fc15: __libc_message: Process /usr/bin/...
Keywords:
Status: CLOSED DUPLICATE of bug 700112
Alias: None
Product: Fedora
Classification: Fedora
Component: rhythmbox
Version: 15
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c04c8baecfea30a8f5c462c5804...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-13 08:53 UTC by Patsev Anton
Modified: 2012-03-20 15:48 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-20 15:48:57 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (66.88 KB, text/plain)
2011-03-13 08:53 UTC, Patsev Anton
no flags Details

Description Patsev Anton 2011-03-13 08:53:11 UTC
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 68482 bytes
cmdline: rhythmbox
component: rhythmbox
Attached file: coredump, 283222016 bytes
crash_function: __libc_message
executable: /usr/bin/rhythmbox
kernel: 2.6.38-0.rc8.git0.1.fc15.i686.PAE
package: rhythmbox-2.90.1-4.git20110207.fc15
rating: 4
reason: Process /usr/bin/rhythmbox was killed by signal 6 (SIGABRT)
release: Fedora release 15 (Lovelock)
time: 1300005519
uid: 500

How to reproduce
-----
1. Run Rhythmbox
2. Press on Radio
3.

Comment 1 Patsev Anton 2011-03-13 08:53:14 UTC
Created attachment 483962 [details]
File: backtrace

Comment 2 Patsev Anton 2011-03-13 08:55:04 UTC
3. Close Rhythmbox
4. rhythmbox was killed by signal 6

Comment 3 abrt-bot 2012-03-20 15:48:57 UTC
Backtrace analysis found this bug to be similar to bug #700112, closing as duplicate.

Bugs which were found to be similar to this bug: bug #694951, bug #700112

This comment is automatically generated.

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


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