Bug 665120

Summary: [abrt] rhythmbox-0.13.1-2.fc14: new_profile_response_callback: Process /usr/bin/rhythmbox was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Justin Willmert <justin>
Component: rhythmboxAssignee: Bastien Nocera <bnocera>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: bnocera
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:d90cffebf188482b85a6074fba604f4c9a6385aa
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-30 11:50:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Justin Willmert 2010-12-22 19:42:22 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: rhythmbox '/home/justin/.gvfs/cdda mount on sr0'
component: rhythmbox
crash_function: new_profile_response_callback
executable: /usr/bin/rhythmbox
kernel: 2.6.35.9-64.fc14.x86_64
package: rhythmbox-0.13.1-2.fc14
rating: 4
reason: Process /usr/bin/rhythmbox was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1293045957
uid: 500

How to reproduce
-----
1. Opened rip settings.
2. Attempted to add new ripping profile.
3. Rhythmbox crashed.
Comment 1 Justin Willmert 2010-12-22 19:42:25 UTC 
Created attachment 470293 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-30 11:50:51 UTC 
Backtrace analysis found this bug to be similar to bug #662408, closing as duplicate. This bug seems to belong to component gtk2.

Bugs which were found to be similar to this bug: 
  gnome-packagekit: bug #678944
  totem: bug #539872, bug #560796, bug #588744, bug #602818, bug #627081, bug #645820, bug #658877, bug #662408

This comment is automatically generated.

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