Bug 695293 - [abrt] xchat-gnome-0.26.1-14.fc14: _gtk_rbtree_find_offset: Process /usr/bin/xchat-gnome was killed by signal 11 (SIGSEGV)
Summary: [abrt] xchat-gnome-0.26.1-14.fc14: _gtk_rbtree_find_offset: Process /usr/bin/...
Keywords:
Status: CLOSED DUPLICATE of bug 695289
Alias: None
Product: Fedora
Classification: Fedora
Component: xchat-gnome
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:36aa5b903f7a91f634553d15fb2...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-11 10:47 UTC by Peter Green
Modified: 2014-03-17 03:27 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-12 02:33:14 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (19.08 KB, text/plain)
2011-04-11 10:47 UTC, Peter Green 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Peter Green 2011-04-11 10:47:07 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 19541 bytes
cmdline: xchat-gnome
comment: Re-connected to irc.freenode.org and joined a channel.
component: xchat-gnome
Attached file: coredump, 30429184 bytes
crash_function: _gtk_rbtree_find_offset
executable: /usr/bin/xchat-gnome
kernel: 2.6.35.11-83.fc14.x86_64
package: xchat-gnome-0.26.1-14.fc14
rating: 4
reason: Process /usr/bin/xchat-gnome was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1302518399
uid: 500

How to reproduce
-----
1. The application had been idling for a long time, but not connected to any network (my laptop was asleep).
2. I reconnected to irc.freenode.org
3. I then joined the #rvm channel.
4. The channel loaded, but then the app crashed.
Comment 1 Peter Green 2011-04-11 10:47:09 UTC 
Created attachment 491201 [details]
File: backtrace
Comment 2 Bill Nottingham 2011-04-12 02:33:14 UTC 

*** This bug has been marked as a duplicate of bug 695289 ***
Note You need to log in before you can comment on or make changes to this bug.