Bug 688483

Summary: [abrt] rhythmbox-0.13.3-1.fc14: __libc_free: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: J.H.M. Dassen (Ray) <rdassen>
Component: rhythmboxAssignee: Bastien Nocera <bnocera>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: bnocera, rbinkhor
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:d32e5fe634f2fd6b26e69debffbcec7609201b9d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 19:49:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description J.H.M. Dassen (Ray) 2011-03-17 08:11:22 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 51570 bytes
cmdline: rhythmbox
component: rhythmbox
Attached file: coredump, 126611456 bytes
crash_function: __libc_free
executable: /usr/bin/rhythmbox
kernel: 2.6.35.11-83.fc14.x86_64
package: rhythmbox-0.13.3-1.fc14
rating: 4
reason: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1300349415
uid: 500

How to reproduce
-----
1. Trying to restart rhythmbox (no switching through KVM involved)
Comment 1 J.H.M. Dassen (Ray) 2011-03-17 08:11:25 UTC 
Created attachment 485945 [details]
File: backtrace
Comment 2 J.H.M. Dassen (Ray) 2011-03-17 10:27:20 UTC 
(In reply to comment #2)
> 1. Trying to restart rhythmbox (no switching through KVM involved)

For completeness: I was restarting after an earlier crash, reported as bug #688481.
Comment 3 abrt-bot 2012-03-20 19:49:54 UTC 
Backtrace analysis found this bug to be similar to bug #698528, closing as duplicate.

Bugs which were found to be similar to this bug: bug #632474, bug #657473, bug #668199, bug #689698, bug #698528

This comment is automatically generated.

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