Bug 592828 - [abrt] crash in liferea-1:1.6.2-2.fc12: raise: Process /usr/bin/liferea was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in liferea-1:1.6.2-2.fc12: raise: Process /usr/bin/liferea was k...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: liferea
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Steven M. Parrish
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:f6af059566cc05e2098ec560b89...
: 593842 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-17 06:30 UTC by gael
Modified: 2010-10-13 16:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-10-13 16:41:48 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (17.70 KB, text/plain)
2010-05-17 06:30 UTC, gael 		no flags Details
View All

Description gael 2010-05-17 06:30:08 UTC 
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: liferea
component: liferea
crash_function: raise
executable: /usr/bin/liferea
global_uuid: f6af059566cc05e2098ec560b893d64cd3e918c0
kernel: 2.6.32.11-99.fc12.i686.PAE
package: liferea-1:1.6.2-2.fc12
rating: 4
reason: Process /usr/bin/liferea was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)
Comment 1 gael 2010-05-17 06:30:10 UTC 
Created attachment 414459 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 10:35:04 UTC 
*** Bug 593842 has been marked as a duplicate of this bug. ***
Comment 3 Steven M. Parrish 2010-07-13 22:26:42 UTC 
Liferea 1.6.4 has been pushed to stable.  Please upgrade to this latest version and see if it corrects this issue.  If there is no update to this bug within 30 days will close as WORKSFORME.

Thanks
Comment 4 Steven M. Parrish 2010-10-13 16:41:48 UTC 
Liferea 1.6.5 has been submitted for testing on F12/F13/F14.  Closing this bug for now.  Please install the new update and if the problem returns feel free to reopen this report with additional information
Note You need to log in before you can comment on or make changes to this bug.