Bug 374120 – crash in XChat-GNOME IRC Chat: entering information for...

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 374120 - crash in XChat-GNOME IRC Chat: entering information for...


Summary:	crash in XChat-GNOME IRC Chat: entering information for...


Status:	RESOLVED DUPLICATE of bug 359761

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-12 01:30 UTC by vegenaut
Modified:	2006-11-12 01:37 UTC

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

Description vegenaut 2006-11-12 01:30:01 UTC

What were you doing when the application crashed?
entering information for a new server


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

Memory status: size: 189358080 vsize: 189358080 resident: 23470080 share: 14807040 rss: 23470080 rss_rlim: -1
CPU usage: start_time: 1163273125 rtime: 1009 utime: 958 stime: 51 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 47584233934400 (LWP 9749)]
(no debugging symbols found)
0x00002b470d81eeef in waitpid () from /lib/libpthread.so.0

+ Trace 85631

Thread 1 (Thread 47584233934400 (LWP 9749))

#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 navigation_model_get_server
#4 irc_network_save
#5 irc_network_editor_new
#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 g_closure_invoke
from /usr/lib64/libgobject-2.0.so.0
#11 g_signal_chain_from_overridden
from /usr/lib64/libgobject-2.0.so.0
#12 g_signal_emit_valist
from /usr/lib64/libgobject-2.0.so.0
#13 g_signal_emit
from /usr/lib64/libgobject-2.0.so.0
#14 gtk_button_set_alignment
from /usr/lib64/libgtk-x11-2.0.so.0
#15 g_closure_invoke
from /usr/lib64/libgobject-2.0.so.0
#16 g_signal_chain_from_overridden
from /usr/lib64/libgobject-2.0.so.0
#17 g_signal_emit_valist
from /usr/lib64/libgobject-2.0.so.0
#18 g_signal_emit
from /usr/lib64/libgobject-2.0.so.0
#19 gtk_button_released
from /usr/lib64/libgtk-x11-2.0.so.0
#20 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib64/libgtk-x11-2.0.so.0
#21 g_closure_invoke
from /usr/lib64/libgobject-2.0.so.0
#22 g_signal_chain_from_overridden
from /usr/lib64/libgobject-2.0.so.0
#23 g_signal_emit_valist
from /usr/lib64/libgobject-2.0.so.0
#24 g_signal_emit
from /usr/lib64/libgobject-2.0.so.0
#25 gtk_widget_get_default_style
from /usr/lib64/libgtk-x11-2.0.so.0
#26 gtk_propagate_event
from /usr/lib64/libgtk-x11-2.0.so.0
#27 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#28 _gdk_events_init
from /usr/lib64/libgdk-x11-2.0.so.0
#29 g_main_context_dispatch
from /usr/lib64/libglib-2.0.so.0
#30 g_main_context_check
from /usr/lib64/libglib-2.0.so.0
#31 g_main_loop_run
from /usr/lib64/libglib-2.0.so.0
#32 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#33 fe_main
#34 main
#0 waitpid
from /lib/libpthread.so.0

Comment 1 David Trowbridge 2006-11-12 01:37:30 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 359761 ***