Bug 650448

Summary: [abrt] clementine-0.5.3-1.fc14: raise: Process /usr/bin/clementine was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: kaiser_715
Component: clementineAssignee: Orcan Ogetbil <oget.fedora>
Status: CLOSED DEFERRED QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: oget.fedora
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:3142c61d3bb2342e9dcee521681fd2fd80e0fa9a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-04 14:55:09 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 kaiser_715 2010-11-06 14:17:17 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: clementine
component: clementine
crash_function: raise
executable: /usr/bin/clementine
kernel: 2.6.35.6-48.fc14.i686
package: clementine-0.5.3-1.fc14
rating: 4
reason: Process /usr/bin/clementine was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1289046137
uid: 500
Comment 1 kaiser_715 2010-11-06 14:17:20 UTC 
Created attachment 458323 [details]
File: backtrace
Comment 2 Orcan Ogetbil 2010-11-06 14:41:34 UTC 
Hi. What were you doing when the crash happened? How can I reproduce this crash?
Comment 3 kaiser_715 2010-11-06 15:15:38 UTC 
(In reply to comment #2)
> Hi. What were you doing when the crash happened? How can I reproduce this
> crash?

Hi, had just started running muy computer when i tried to open clementine, but i just didn't work (i couldn't even open the application). Sorry but i don't know how you could reproduce the crash :S
Comment 4 Orcan Ogetbil 2012-02-04 14:55:09 UTC 
Closing the bug since Fedora 14 is EOL and we have more recent version of this software in the active Fedora releases. Please try, e.g. Fedora 16, to see if the problem persists.