Bug 690730 - [abrt] rhythmbox-0.13.3-1.fc14: _dbus_abort: Process /usr/bin/rhythmbox was killed by signal 6 (SIGABRT)
Summary: [abrt] rhythmbox-0.13.3-1.fc14: _dbus_abort: Process /usr/bin/rhythmbox was k...
Keywords:
Status: CLOSED DUPLICATE of bug 726394
Alias: None
Product: Fedora
Classification: Fedora
Component: rhythmbox
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:de4bb2f097f640f72cc7ecd3050...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-25 08:06 UTC by liuerfire
Modified: 2012-03-21 16:01 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-21 16:01:54 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (63.70 KB, text/plain)
2011-03-25 08:06 UTC, liuerfire 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description liuerfire 2011-03-25 08:06:19 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 65232 bytes
cmdline: rhythmbox
component: rhythmbox
Attached file: coredump, 118403072 bytes
crash_function: _dbus_abort
executable: /usr/bin/rhythmbox
kernel: 2.6.35.11-83.fc14.i686
package: rhythmbox-0.13.3-1.fc14
rating: 4
reason: Process /usr/bin/rhythmbox was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1300958980
uid: 500

How to reproduce
-----
1.i see video on youtube, it happened
2.
3.
Comment 1 liuerfire 2011-03-25 08:06:22 UTC 
Created attachment 487498 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-21 16:01:54 UTC 
Backtrace analysis found this bug to be similar to bug #726394, closing as duplicate. This bug seems to belong to component gtk2, avahi or dbus.

Bugs which were found to be similar to this bug: 
  rhythmbox: bug #726394
  seahorse: bug #556550, bug #592532, bug #635856

This comment is automatically generated.

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