Bug 598667 - [abrt] crash in liferea-1:1.6.3-1.fc13: raise: Process /usr/bin/liferea was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in liferea-1:1.6.3-1.fc13: raise: Process /usr/bin/liferea was k...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: liferea
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Steven M. Parrish
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:8d55aaf0dbf58372d8d052bc32d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-01 19:59 UTC by Dwayne Bailey
Modified: 2010-10-13 16:41 UTC (History)
1 user (show)

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

Attachments (Terms of Use)
File: backtrace (42.39 KB, text/plain)
2010-06-01 20:00 UTC, Dwayne Bailey 		no flags Details
View All

Description Dwayne Bailey 2010-06-01 19:59:59 UTC 
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: liferea
component: liferea
crash_function: raise
executable: /usr/bin/liferea
global_uuid: 8d55aaf0dbf58372d8d052bc32d4ee45671824fb
kernel: 2.6.33.5-112.fc13.i686.PAE
package: liferea-1:1.6.3-1.fc13
rating: 4
reason: Process /usr/bin/liferea was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
Comment 1 Dwayne Bailey 2010-06-01 20:00:07 UTC 
Created attachment 418795 [details]
File: backtrace
Comment 2 Steven M. Parrish 2010-06-05 02:30:35 UTC 
Please report this upstream at liferea.sf.net



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers
Comment 3 Steven M. Parrish 2010-07-13 22:26:28 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:26 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.