Bug 398022 – crash in XChat-GNOME IRC Chat: I was closing the server...

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 398022 - crash in XChat-GNOME IRC Chat: I was closing the server...


Summary:	crash in XChat-GNOME IRC Chat: I was closing the server...


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:

Depends on:
Blocks:

Reported:	2007-01-18 14:49 UTC by najjstroem-
Modified:	2007-01-18 14:50 UTC

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

Description najjstroem- 2007-01-18 14:49:47 UTC

What were you doing when the application crashed?
I was closing the server so no server in server list were apperared!


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 129122304 vsize: 0 resident: 129122304 share: 0 rss: 59338752 rss_rlim: 0
CPU usage: start_time: 1169130538 rtime: 0 utime: 5497 stime: 0 cutime:5303 cstime: 0 timeout: 194 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 -1226287440 (LWP 29392)]
[New Thread -1249932384 (LWP 29545)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 103262

Thread 1 (Thread -1226287440 (LWP 29392))

#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_selection_select_path
from /usr/lib/libgtk-x11-2.0.so.0
#12 navigation_tree_create_new_channel_entry
#13 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#14 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#18 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#19 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#20 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#21 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#22 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#23 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#24 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#25 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#26 fe_main
#27 main
#0 __kernel_vsyscall

Comment 1 Guillaume Desmottes 2007-01-18 14:50:58 UTC

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 ***