Bug 616537 - [abrt] crash in liferea-1:1.6.4-1.fc12: raise: Process /usr/bin/liferea was killed by signal 6 (SIGABRT)
[abrt] crash in liferea-1:1.6.4-1.fc12: raise: Process /usr/bin/liferea was k...
Status: CLOSED NEXTRELEASE
Product: Fedora
Classification: Fedora
Component: liferea (Show other bugs)
12
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Steven M. Parrish
Fedora Extras Quality Assurance
abrt_hash:eeb46a64b8a38c5a34ad226cc74...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-20 14:09 EDT by Bob
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:05 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 (27.61 KB, text/plain)
2010-07-20 14:09 EDT, Bob
no flags Details

  None (edit)
Description Bob 2010-07-20 14:09:45 EDT
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: liferea
component: liferea
crash_function: raise
executable: /usr/bin/liferea
global_uuid: eeb46a64b8a38c5a34ad226cc7447c4319f8d898
kernel: 2.6.32.16-141.fc12.x86_64
package: liferea-1:1.6.4-1.fc12
rating: 4
reason: Process /usr/bin/liferea was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. Not consistent enough to reliably reproduce.
2. Seems most common when Liferea is busy doing something, e.g., sending a Web address to the browser, and I interact with the Liferea GUI.
3. When this happens, the GUI becomes totally nonresponsive.  Recovery requires killing the Liferea tasks externally, e.g., using "kill".
Comment 1 Bob 2010-07-20 14:09:47 EDT
Created attachment 433232 [details]
File: backtrace
Comment 2 Steven M. Parrish 2010-10-13 12:42:05 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.