Bug 383230 – crash in XChat-GNOME IRC Chat: loading it up, but I jus...

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 383230 - crash in XChat-GNOME IRC Chat: loading it up, but I jus...


Summary:	crash in XChat-GNOME IRC Chat: loading it up, but I jus...


Status:	RESOLVED DUPLICATE of bug 368796

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-12-07 02:33 UTC by startswithz
Modified:	2006-12-07 02:45 UTC

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

Description startswithz 2006-12-07 02:33:18 UTC

What were you doing when the application crashed?
loading it up, but I just set up beryl to autoload when I start my X session so that is probably the main problem


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

Memory status: size: 96985088 vsize: 0 resident: 96985088 share: 0 rss: 23859200 rss_rlim: 0
CPU usage: start_time: 1165458707 rtime: 0 utime: 296 stime: 0 cutime:288 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 -1227188560 (LWP 4782)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 92204

Thread 1 (Thread -1227188560 (LWP 4782))

#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 g_type_check_instance_cast
from /usr/lib/libgobject-2.0.so.0
#5 navigation_tree_create_new_channel_entry
#6 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#7 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#8 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#9 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#11 _gtk_tree_selection_internal_select_node
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_tree_selection_select_path
from /usr/lib/libgtk-x11-2.0.so.0
#13 navigation_tree_create_new_channel_entry
#14 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-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 David Trowbridge 2006-12-07 02:45:27 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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