Bug 680701 - [abrt] pidgin-2.7.9-1.fc14: _gtk_rbtree_node_find_offset: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
Summary: [abrt] pidgin-2.7.9-1.fc14: _gtk_rbtree_node_find_offset: Process /usr/bin/pi...
Keywords:
Status: CLOSED DUPLICATE of bug 725616
Alias: None
Product: Fedora
Classification: Fedora
Component: pidgin
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Stu Tomlinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:706598a4d831fbb4cde9b23c821...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-27 06:48 UTC by foo.hazard
Modified: 2012-03-20 15:13 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-20 15:13:05 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (48.10 KB, text/plain)
2011-02-27 06:49 UTC, foo.hazard
no flags Details

Description foo.hazard 2011-02-27 06:48:32 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 49255 bytes
cmdline: pidgin
component: pidgin
Attached file: coredump, 102846464 bytes
crash_function: _gtk_rbtree_node_find_offset
executable: /usr/bin/pidgin
kernel: 2.6.35.11-83.fc14.x86_64
package: pidgin-2.7.9-1.fc14
rating: 4
reason: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1298784934
uid: 500

How to reproduce
-----
1. Focus on Pidgin main window.
2. Press PgDn on keyboard.
3. List of contacts started going down, and then Pidgin crashed.

Comment 1 foo.hazard 2011-02-27 06:49:47 UTC
Created attachment 481215 [details]
File: backtrace

Comment 2 abrt-bot 2012-03-20 15:13:05 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: 
  liferea: bug #658221
  pidgin: bug #725616

This comment is automatically generated.

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


Note You need to log in before you can comment on or make changes to this bug.