Bug 658221

Summary: [abrt] liferea-1:1.6.5-1.fc14: _gtk_rbtree_node_find_offset: Process /usr/bin/liferea was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Robert Elliott <rh-bugz>
Component: lifereaAssignee: Steven M. Parrish <smparrish>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: smparrish
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:22912e0638e24f9335a4597b573839f0b45488a0
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 15:12:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Robert Elliott 2010-11-29 17:26:00 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: liferea
comment: This has been happening on and off pretty much since I started using liferea, but it's quite sporadic. I can't nail down any specific circumstances, but it always happens when I try to PgDn past the bottom message in the Unread Messages list.
component: liferea
crash_function: _gtk_rbtree_node_find_offset
executable: /usr/bin/liferea
kernel: 2.6.35.6-48.fc14.i686
package: liferea-1:1.6.5-1.fc14
rating: 4
reason: Process /usr/bin/liferea was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1291050106
uid: 500

How to reproduce
-----
1. Scrolling through new messages (sorted by date, newest at top)
2. Using PgDn to get to oldest message, and went over the cliff, as it were, PgDning beyond oldest message
3. Boom
Comment 1 Robert Elliott 2010-11-29 17:26:07 UTC 
Created attachment 463537 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-20 15:12:55 UTC 
Backtrace analysis found this bug to be similar to bug #725616, closing as duplicate. This bug seems to belong to component gtk2 or glib2.

Bugs which were found to be similar to this bug: 
  pidgin: bug #680701, bug #725616

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 725616 ***