Bug 388430 – crash in XChat-GNOME IRC Chat:

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 388430 - crash in XChat-GNOME IRC Chat:


Summary:	crash in XChat-GNOME IRC Chat:


Status:	RESOLVED INCOMPLETE

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

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

URL:
Whiteboard:

Duplicates:	395814 (view as bug list)
Depends on:
Blocks:

Reported:	2006-12-21 22:28 UTC by david
Modified:	2007-01-14 22:21 UTC

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

Description david 2006-12-21 22:28:13 UTC

What were you doing when the application crashed?



Distribution: Gentoo Base System version 1.12.8
Gnome Release: 2.16.2 2006-11-20 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 150114304 vsize: 150114304 resident: 35098624 share: 20635648 rss: 35098624 rss_rlim: -1
CPU usage: start_time: 1166738528 rtime: 12296 utime: 12246 stime: 50 cutime:7 cstime: 1 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 47944108546768 (LWP 23891)]
0x00002b9ada4a3a95 in waitpid () from /lib/libpthread.so.0

+ Trace 96086

Thread 1 (Thread 47944108546768 (LWP 23891))

#0 waitpid
from /lib/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 raise
from /lib/libc.so.6
#4 abort
from /lib/libc.so.6
#5 dbus_malloc
from /usr/lib64/libdbus-1.so.2
#6 dbus_watch_handle
from /usr/lib64/libdbus-1.so.2
#7 dbus_connection_get_data
from /usr/lib64/libdbus-1.so.2
#8 dbus_connection_setup_with_g_main
from /usr/lib/libdbus-glib-1.so.2
#9 xchat_plugin_init
from /usr/lib64/xchat-gnome/plugins/netmonitor.so
#10 plugin_add
#11 plugin_load
#12 load_plugin
#13 preferences_page_plugins_new
#14 preferences_page_plugins_new
#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_cell_renderer_toggle_new
from /usr/lib/libgtk-x11-2.0.so.0
#20 gtk_tree_view_column_focus_cell
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_tree_view_column_cell_is_visible
from /usr/lib/libgtk-x11-2.0.so.0
#22 gtk_tree_view_get_hadjustment
from /usr/lib/libgtk-x11-2.0.so.0
#23 gtk_marshal_BOOLEAN__VOID
from /usr/lib/libgtk-x11-2.0.so.0
#24 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#26 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#27 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#28 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#29 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#30 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#31 gdk_add_client_message_filter
from /usr/lib/libgdk-x11-2.0.so.0
#32 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#33 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#34 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#35 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#36 fe_main
#37 main
#0 waitpid
from /lib/libpthread.so.0

Comment 1 David Trowbridge 2006-12-21 22:51:05 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

Comment 2 David Trowbridge 2007-01-12 20:55:08 UTC

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

Comment 3 David Trowbridge 2007-01-14 22:21:12 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!