Bug 616673 - [abrt] crash in liferea-1:1.6.4-1.fc13: raise: Process /usr/bin/liferea was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in liferea-1:1.6.4-1.fc13: raise: Process /usr/bin/liferea was k...
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: liferea (Show other bugs)
(Show other bugs)
Version: 13
Hardware: i686 Linux
low
medium
Target Milestone: ---
Assignee: Steven M. Parrish
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ec0078319d3a759b44abcf31814...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-21 07:12 UTC by Szabo Akos
Modified: 2010-10-13 16:42 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-10-13 16:42:01 UTC
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 (15.35 KB, text/plain)
2010-07-21 07:12 UTC, Szabo Akos
no flags Details

Description Szabo Akos 2010-07-21 07:12:32 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/liferea --session 1041dc0eb6368f6eca127798691762152600000015960039 --mainwindow-state=hidden
comment: Using as usual. Nothing extra. I use about 15 feeds
component: liferea
crash_function: raise
executable: /usr/bin/liferea
global_uuid: ec0078319d3a759b44abcf31814de60ae22ed038
kernel: 2.6.35-0.31.rc4.git4.fc14.i686
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. Autostart liferea
2. crash
3.

Comment 1 Szabo Akos 2010-07-21 07:12:34 UTC
Created attachment 433313 [details]
File: backtrace

Comment 2 Steven M. Parrish 2010-10-13 16:42:01 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.