Bug 913697 - [abrt] xchat-gnome-0.26.2-9.git40c5bf988.fc18: find_root: Process /usr/bin/xchat-gnome was killed by signal 11 (SIGSEGV)
Summary: [abrt] xchat-gnome-0.26.2-9.git40c5bf988.fc18: find_root: Process /usr/bin/xc...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xchat-gnome
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:38d5d4ff3e33cd9d7bf10999887...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-21 20:00 UTC by Randy Barlow
Modified: 2014-03-17 03:33 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 19:22:33 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (26.31 KB, text/plain)
2013-02-21 20:00 UTC, Randy Barlow
no flags Details
File: build_ids (5.45 KB, text/plain)
2013-02-21 20:00 UTC, Randy Barlow
no flags Details
File: cgroup (130 bytes, text/plain)
2013-02-21 20:00 UTC, Randy Barlow
no flags Details
File: core_backtrace (3.44 KB, text/plain)
2013-02-21 20:00 UTC, Randy Barlow
no flags Details
File: dso_list (13.67 KB, text/plain)
2013-02-21 20:00 UTC, Randy Barlow
no flags Details
File: environ (1.83 KB, text/plain)
2013-02-21 20:00 UTC, Randy Barlow
no flags Details
File: limits (1.29 KB, text/plain)
2013-02-21 20:00 UTC, Randy Barlow
no flags Details
File: maps (65.47 KB, text/plain)
2013-02-21 20:00 UTC, Randy Barlow
no flags Details
File: open_fds (2.31 KB, text/plain)
2013-02-21 20:00 UTC, Randy Barlow
no flags Details
File: proc_pid_status (938 bytes, text/plain)
2013-02-21 20:00 UTC, Randy Barlow
no flags Details
File: smolt_data (2.78 KB, text/plain)
2013-02-21 20:00 UTC, Randy Barlow
no flags Details
File: var_log_messages (324 bytes, text/plain)
2013-02-21 20:00 UTC, Randy Barlow
no flags Details

Description Randy Barlow 2013-02-21 20:00:13 UTC
Description of problem:
I noticed that the label in the left hand pane (where it shows the IRC networks and channels) for Freenode looked really freaky (i.e., didn't say "Freenode" but something else that I cannot recall), so I clicked on it to see what was happening, and then xchat-gnome crashed.

Version-Release number of selected component:
xchat-gnome-0.26.2-9.git40c5bf988.fc18

Additional info:
backtrace_rating: 4
cmdline:        xchat-gnome
crash_function: find_root
executable:     /usr/bin/xchat-gnome
kernel:         3.7.9-201.fc18.x86_64
remote_result:  NOTFOUND
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 find_root at gsequence.c:1568
 #1 node_get_length at gsequence.c:1789
 #2 g_sequence_get_length at gsequence.c:1254
 #3 gtk_list_store_get_iter at gtkliststore.c:440
 #4 gtk_tree_view_set_model at gtktreeview.c:10856
 #5 fe_set_current at fe-gnome.c:1146
 #6 selection_changed at navigation-tree.c:301
 #11 _gtk_tree_selection_internal_select_node at gtktreeselection.c:1427
 #13 gtk_tree_view_real_set_cursor at gtktreeview.c:12595
 #14 gtk_tree_view_button_press at gtktreeview.c:2797

Comment 1 Randy Barlow 2013-02-21 20:00:17 UTC
Created attachment 700794 [details]
File: backtrace

Comment 2 Randy Barlow 2013-02-21 20:00:19 UTC
Created attachment 700795 [details]
File: build_ids

Comment 3 Randy Barlow 2013-02-21 20:00:21 UTC
Created attachment 700796 [details]
File: cgroup

Comment 4 Randy Barlow 2013-02-21 20:00:24 UTC
Created attachment 700797 [details]
File: core_backtrace

Comment 5 Randy Barlow 2013-02-21 20:00:28 UTC
Created attachment 700798 [details]
File: dso_list

Comment 6 Randy Barlow 2013-02-21 20:00:30 UTC
Created attachment 700799 [details]
File: environ

Comment 7 Randy Barlow 2013-02-21 20:00:35 UTC
Created attachment 700800 [details]
File: limits

Comment 8 Randy Barlow 2013-02-21 20:00:36 UTC
Created attachment 700801 [details]
File: maps

Comment 9 Randy Barlow 2013-02-21 20:00:40 UTC
Created attachment 700802 [details]
File: open_fds

Comment 10 Randy Barlow 2013-02-21 20:00:43 UTC
Created attachment 700803 [details]
File: proc_pid_status

Comment 11 Randy Barlow 2013-02-21 20:00:45 UTC
Created attachment 700804 [details]
File: smolt_data

Comment 12 Randy Barlow 2013-02-21 20:00:49 UTC
Created attachment 700805 [details]
File: var_log_messages

Comment 13 Fedora End Of Life 2013-12-21 11:35:56 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 14 Fedora End Of Life 2014-02-05 19:22:33 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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