Bug 384526 – crash in XChat-GNOME IRC Chat: clicking on a link in a ...

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 384526 - crash in XChat-GNOME IRC Chat: clicking on a link in a ...


Summary:	crash in XChat-GNOME IRC Chat: clicking on a link in a ...


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:	2006-12-10 21:43 UTC by ostostost
Modified:	2006-12-10 22:07 UTC

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

Description ostostost 2006-12-10 21:43:17 UTC

What were you doing when the application crashed?
clicking on a link in a topic


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

Memory status: size: 227860480 vsize: 227860480 resident: 29192192 share: 15122432 rss: 29192192 rss_rlim: -1
CPU usage: start_time: 1165757463 rtime: 2662 utime: 2364 stime: 298 cutime:0 cstime: 8 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 47014938361424 (LWP 5154)]
(no debugging symbols found)
0x00002ac280d8ceef in waitpid () from /lib/libpthread.so.0

+ Trace 93143

Thread 1 (Thread 47014938361424 (LWP 5154))

#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 strlen
from /lib/libc.so.6
#4 g_strdup
from /usr/lib64/libglib-2.0.so.0
#5 g_value_dup_string
from /usr/lib64/libgobject-2.0.so.0
#6 g_signal_emit_valist
from /usr/lib64/libgobject-2.0.so.0
#7 g_signal_emit
from /usr/lib64/libgobject-2.0.so.0
#8 sexy_url_label_set_markup
from /usr/lib64/libsexy.so.2
#9 ??
#10 ??
#11 ??
#12 ??
#13 sexy_url_label_set_markup
from /usr/lib64/libsexy.so.2
#14 _gtk_marshal_BOOLEAN__BOXED
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_widget_get_default_style
from /usr/lib64/libgtk-x11-2.0.so.0
#20 gtk_propagate_event
from /usr/lib64/libgtk-x11-2.0.so.0
#21 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#22 _gdk_events_init
from /usr/lib64/libgdk-x11-2.0.so.0
#23 g_main_context_dispatch
from /usr/lib64/libglib-2.0.so.0
#24 g_main_context_check
from /usr/lib64/libglib-2.0.so.0
#25 g_main_loop_run
from /usr/lib64/libglib-2.0.so.0
#26 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#27 fe_main
#28 main
#0 waitpid
from /lib/libpthread.so.0

Comment 1 David Trowbridge 2006-12-10 22:07:22 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 353946 ***