Bug 365779 – crash in XChat-GNOME IRC Chat: just disconnecting and e...

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 365779 - crash in XChat-GNOME IRC Chat: just disconnecting and e...


Summary:	crash in XChat-GNOME IRC Chat: just disconnecting and e...


Status:	RESOLVED DUPLICATE of bug 359766

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-10-27 15:08 UTC by kenn
Modified:	2006-10-27 16:23 UTC

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

Description kenn 2006-10-27 15:08:53 UTC

What were you doing when the application crashed?
just disconnecting and exiting from XChat...



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

Memory status: size: 165187584 vsize: 165187584 resident: 30695424 share: 14671872 rss: 30695424 rss_rlim: -1
CPU usage: start_time: 1161960423 rtime: 4064 utime: 3971 stime: 93 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 48003663961664 (LWP 4779)]
(no debugging symbols found)
0x00002ba8b57c3eb5 in waitpid () from /lib/libpthread.so.0

+ Trace 78846

Thread 1 (Thread 48003663961664 (LWP 4779))

#0 waitpid
from /lib/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 gtk_xtext_buffer_show
#4 conversation_panel_set_current
#5 navigation_tree_create_new_channel_entry
#6 g_closure_invoke
from /usr/lib64/libgobject-2.0.so.0
#7 g_signal_chain_from_overridden
from /usr/lib64/libgobject-2.0.so.0
#8 g_signal_emit_valist
from /usr/lib64/libgobject-2.0.so.0
#9 g_signal_emit
from /usr/lib64/libgobject-2.0.so.0
#10 gtk_tree_selection_select_path
from /usr/lib64/libgtk-x11-2.0.so.0
#11 navigation_tree_create_new_channel_entry
#12 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib64/libgtk-x11-2.0.so.0
#13 g_closure_invoke
from /usr/lib64/libgobject-2.0.so.0
#14 g_signal_chain_from_overridden
from /usr/lib64/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /usr/lib64/libgobject-2.0.so.0
#16 g_signal_emit
from /usr/lib64/libgobject-2.0.so.0
#17 gtk_widget_get_default_style
from /usr/lib64/libgtk-x11-2.0.so.0
#18 gtk_propagate_event
from /usr/lib64/libgtk-x11-2.0.so.0
#19 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#20 _gdk_events_init
from /usr/lib64/libgdk-x11-2.0.so.0
#21 g_main_context_dispatch
from /usr/lib64/libglib-2.0.so.0
#22 g_main_context_check
from /usr/lib64/libglib-2.0.so.0
#23 g_main_loop_run
from /usr/lib64/libglib-2.0.so.0
#24 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#25 fe_main
#26 main
#0 waitpid
from /lib/libpthread.so.0

Comment 1 Karsten Bräckelmann 2006-10-27 16:23:36 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 359766 ***