Bug 605604 - [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: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Steven M. Parrish
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c898687813c966e2c384d994542...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-18 11:14 UTC by Abhishek Singh
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:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Abhishek Singh 2010-06-18 11:14:38 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: liferea
comment: Open liferea, from the notification icon, right click and choose to "update all". After the update is complete, try clicking on a new item from any of the feed. This does not happen everytime, and have faced this problem only once till now.
component: liferea
crash_function: raise
executable: /usr/bin/liferea
global_uuid: c898687813c966e2c384d994542c726430f19b72
kernel: 2.6.33.5-124.fc13.x86_64
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)

How to reproduce
-----
1. Update all the feeds.
2. Try to click/read on a new updated item.

Comment 1 Steven M. Parrish 2010-07-13 22:26:36 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 2 Steven M. Parrish 2010-10-13 16:41:37 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.