Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 617067 - [abrt] crash in liferea-1:1.6.4-1.fc13: raise: Process /usr/bin/liferea was killed by signal 6 (SIGABRT)
[abrt] crash in liferea-1:1.6.4-1.fc13: raise: Process /usr/bin/liferea was k...
Status: CLOSED NEXTRELEASE
Product: Fedora
Classification: Fedora
Component: liferea (Show other bugs)
13
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Steven M. Parrish
Fedora Extras Quality Assurance
abrt_hash:7a19faa9843fe870f6897beee5e...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-22 02:25 EDT by Kuzz
Modified: 2010-10-13 12:42 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-10-13 12:42:18 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (43.92 KB, text/plain)
2010-07-22 02:25 EDT, Kuzz
no flags Details

  None (edit)
Description Kuzz 2010-07-22 02:25:25 EDT
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/liferea --session 102861cb2041d6000127971697300000029380050 --mainwindow-state=hidden
component: liferea
crash_function: raise
executable: /usr/bin/liferea
global_uuid: 7a19faa9843fe870f6897beee5e3110160060be9
kernel: 2.6.33.6-147.fc13.x86_64
package: liferea-1:1.6.4-1.fc13
rating: 4
reason: Process /usr/bin/liferea was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. feed http://habrahabr.ru/rss/blogs/infosecurity/
2.
3.
Comment 1 Kuzz 2010-07-22 02:25:28 EDT
Created attachment 433590 [details]
File: backtrace
Comment 2 Steven M. Parrish 2010-10-13 12:42:18 EDT
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.