Bug 690542 - [abrt] rhythmbox-2.90.1-5.git20110316.fc15: rhythmdb_entry_set_internal: Process /usr/bin/rhythmbox was killed by signal 6 (SIGABRT)
Summary: [abrt] rhythmbox-2.90.1-5.git20110316.fc15: rhythmdb_entry_set_internal: Proc...
Keywords:
Status: CLOSED DUPLICATE of bug 698968
Alias: None
Product: Fedora
Classification: Fedora
Component: rhythmbox
Version: 15
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:44b8e220af3aafdfeccdbf953be...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-24 15:53 UTC by Giovanni Campagna
Modified: 2012-03-20 17:28 UTC (History)
1 user (show)

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

Attachments (Terms of Use)
File: backtrace (108.33 KB, text/plain)
2011-03-24 15:53 UTC, Giovanni Campagna 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Giovanni Campagna 2011-03-24 15:53:36 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 110934 bytes
cmdline: rhythmbox --sm-client-id 10299a9e7ee67b5fd7130046697769433100000013110042
component: rhythmbox
Attached file: coredump, 178601984 bytes
crash_function: rhythmdb_entry_set_internal
executable: /usr/bin/rhythmbox
kernel: 2.6.38-1.fc15.x86_64
package: rhythmbox-2.90.1-5.git20110316.fc15
rating: 4
reason: Process /usr/bin/rhythmbox was killed by signal 6 (SIGABRT)
release: Fedora release 15 (Lovelock)
time: 1300974142
uid: 500

How to reproduce
-----
Happens reproducibly when Jamendo finished loading the database.
Comment 1 Giovanni Campagna 2011-03-24 15:53:40 UTC 
Created attachment 487381 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-20 17:28:48 UTC 
Backtrace analysis found this bug to be similar to bug #698968, closing as duplicate.

This comment is automatically generated.

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