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

(edit)
Clone Of:
(edit)
Last Closed: 2010-10-13 16:42:05 UTC

Attachments (Terms of Use)
File: backtrace (27.61 KB, text/plain)
2010-07-20 18:09 UTC, Bob 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Bob 2010-07-20 18:09:45 UTC 
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 18:09:47 UTC 
Created attachment 433232 [details]
File: backtrace
Comment 2 Steven M. Parrish 2010-10-13 16:42:05 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.