Bug 434473 – crash in XChat-GNOME IRC Chat: Clicked the bottom bar t...

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 434473 - crash in XChat-GNOME IRC Chat: Clicked the bottom bar t...


Summary:	crash in XChat-GNOME IRC Chat: Clicked the bottom bar t...


Status:	RESOLVED DUPLICATE of bug 353946

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-04-30 01:32 UTC by siroverload
Modified:	2007-05-17 16:04 UTC

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

Description siroverload 2007-04-30 01:32:57 UTC

What were you doing when the application crashed?
Clicked the bottom bar to bring Xchat to the front of the screen 


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

Memory status: size: 95219712 vsize: 0 resident: 95219712 share: 0 rss: 26640384 rss_rlim: 0
CPU usage: start_time: 1177164024 rtime: 0 utime: 72677 stime: 0 cutime:67134 cstime: 0 timeout: 5543 it_real_value: 0 frequency: 29

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 -1226643792 (LWP 7522)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 131360

Thread 1 (Thread -1226643792 (LWP 7522))

#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 strlen
from /lib/tls/i686/cmov/libc.so.6
#5 g_strdup
from /usr/lib/libglib-2.0.so.0
#6 g_value_dup_string
from /usr/lib/libgobject-2.0.so.0
#7 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#8 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#9 sexy_url_label_set_markup
from /usr/lib/libsexy.so.2
#10 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#11 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#12 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#16 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#18 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#19 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#20 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#21 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#22 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#23 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#24 fe_main
#25 main
#0 __kernel_vsyscall

Comment 1 Marc-Andre Lureau 2007-05-17 16:04:21 UTC

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 353946 ***