Bug 650448 - [abrt] clementine-0.5.3-1.fc14: raise: Process /usr/bin/clementine was killed by signal 6 (SIGABRT)
Summary: [abrt] clementine-0.5.3-1.fc14: raise: Process /usr/bin/clementine was killed...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Fedora
Classification: Fedora
Component: clementine
Version: 14
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Orcan Ogetbil
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:3142c61d3bb2342e9dcee521681...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-06 14:17 UTC by kaiser_715
Modified: 2012-02-04 14:55 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-02-04 14:55:09 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (27.50 KB, text/plain)
2010-11-06 14:17 UTC, kaiser_715 		no flags Details
View All

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.
Note You need to log in before you can comment on or make changes to this bug.