Bug 358095 – crash in XChat-GNOME IRC Chat: Xchat-gnome crashed when...

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 358095 - crash in XChat-GNOME IRC Chat: Xchat-gnome crashed when...


Summary:	crash in XChat-GNOME IRC Chat: Xchat-gnome crashed when...


Status:	RESOLVED DUPLICATE of bug 356624

Product:	xchat-gnome
Classification:	Other
Component:	general
Version:	0.13
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	xchat-gnome maintainers
QA Contact:	xchat-gnome maintainers

URL:
Whiteboard:

Duplicates:	364822 379225 (view as bug list)
Depends on:
Blocks:

Reported:	2006-09-28 06:51 UTC by knutfunkel
Modified:	2006-11-25 18:16 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description knutfunkel 2006-09-28 06:51:37 UTC

What were you doing when the application crashed?
Xchat-gnome crashed when I tried to connect to quakenet. Xchat-gnome tried to display all the channels in quakenet in a separate window. I killed xchat-gnome with killall.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 39714816 vsize: 0 resident: 39714816 share: 0 rss: 16687104 rss_rlim: 0
CPU usage: start_time: 1159426162 rtime: 0 utime: 86 stime: 0 cutime:78 cstime: 0 timeout: 8 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/xchat-gnome'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226791248 (LWP 8517)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 73451

Thread 1 (Thread -1226791248 (LWP 8517))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 navigation_tree_create_new_channel_entry
#5 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#6 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#7 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#8 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#9 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#10 _gtk_tree_selection_internal_select_node
from /usr/lib/libgtk-x11-2.0.so.0
#11 gtk_tree_view_scroll_to_cell
from /usr/lib/libgtk-x11-2.0.so.0
#12 _gtk_tree_view_column_autosize
from /usr/lib/libgtk-x11-2.0.so.0
#13 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#14 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#15 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#19 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#20 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#22 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#23 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#24 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#25 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#26 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#27 fe_main
#28 main
#0 __kernel_vsyscall

Comment 1 Guillaume Desmottes 2006-09-28 09:30:49 UTC

I don't have any problem to connect on Quakenet.
Do you have this crash each time you try to connect on this server?

Comment 2 David Trowbridge 2006-09-30 22:37:28 UTC

Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Comment 3 André Klapper 2006-10-24 22:07:18 UTC

*** Bug 364822 has been marked as a duplicate of this bug. ***

Comment 4 David Trowbridge 2006-10-26 05:29:34 UTC

Actually....
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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

Comment 5 Guillaume Desmottes 2006-11-25 18:16:17 UTC

*** Bug 379225 has been marked as a duplicate of this bug. ***