Bug 421569 – crash in XChat-GNOME IRC Chat: serververbindung in der ...

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 421569 - crash in XChat-GNOME IRC Chat: serververbindung in der ...


Summary:	crash in XChat-GNOME IRC Chat: serververbindung in der ...


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:	2007-03-22 18:09 UTC by msc79
Modified:	2007-03-23 09:36 UTC

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

Description msc79 2007-03-22 18:09:19 UTC

What were you doing when the application crashed?
serververbindung in der linken spalte mit rechtsklick->disconnect beendet


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

Memory status: size: 84234240 vsize: 0 resident: 84234240 share: 0 rss: 23601152 rss_rlim: 0
CPU usage: start_time: 1174586907 rtime: 0 utime: 226 stime: 0 cutime:219 cstime: 0 timeout: 7 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 -1226529104 (LWP 6245)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 121206

Thread 1 (Thread -1226529104 (LWP 6245))

#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 navigation_tree_create_new_channel_entry
#5 navigation_tree_create_new_channel_entry
#6 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-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_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#14 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#15 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#16 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#17 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#18 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#19 fe_main
#20 main
#0 __kernel_vsyscall

Comment 1 David Trowbridge 2007-03-23 09:36:09 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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