Bug 369177 – crash in XChat-GNOME IRC Chat: I was autoconnected to t...

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 369177 - crash in XChat-GNOME IRC Chat: I was autoconnected to t...


Summary:	crash in XChat-GNOME IRC Chat: I was autoconnected to t...


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:	2006-11-02 01:19 UTC by Mark Drago
Modified:	2006-11-02 01:21 UTC

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

Description Mark Drago 2006-11-02 01:19:10 UTC

What were you doing when the application crashed?
I was autoconnected to the irc.ubuntu.com IRC server.  I removed it from the list of servers on the left by right clicking on it and clicking 'disconnect' and then right-clicking and choosing 'close'.  The side bar then only said <none>.  Upon right-clicking <none> xchat-gnome crashed.  The only other change I made to the preferences were that I chose to connect to Freenode at startup and to connect to one channel on freenode.  I also entered my nickserv password for freenode.  This crash happened the first time I ran xchat-gnome so I'm pretty sure that that is all I did.


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

Memory status: size: 79138816 vsize: 0 resident: 79138816 share: 0 rss: 19484672 rss_rlim: 0
CPU usage: start_time: 1162430131 rtime: 0 utime: 662 stime: 0 cutime:623 cstime: 0 timeout: 39 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 -1226418512 (LWP 5161)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 81699

Thread 1 (Thread -1226418512 (LWP 5161))

#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 gtk_xtext_buffer_show
#5 conversation_panel_set_current
#6 navigation_tree_create_new_channel_entry
#7 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#8 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#9 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#12 _gtk_tree_selection_internal_select_node
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_tree_selection_select_path
from /usr/lib/libgtk-x11-2.0.so.0
#14 navigation_tree_create_new_channel_entry
#15 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#16 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#20 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#22 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#23 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#24 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#25 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#26 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#27 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#28 fe_main
#29 main
#0 __kernel_vsyscall

Comment 1 David Trowbridge 2006-11-02 01:21:27 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 ***