Bug 364675 – crash in XChat-GNOME IRC Chat:

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 364675 - crash in XChat-GNOME IRC Chat:


Summary:	crash in XChat-GNOME IRC Chat:


Status:	RESOLVED DUPLICATE of bug 361151

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-10-24 11:57 UTC by Frej Soya
Modified:	2006-10-25 05:55 UTC

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

Description Frej Soya 2006-10-24 11:57:09 UTC

What were you doing when the application crashed?



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

Memory status: size: 66121728 vsize: 0 resident: 66121728 share: 0 rss: 21057536 rss_rlim: 0
CPU usage: start_time: 1161690932 rtime: 0 utime: 478 stime: 0 cutime:460 cstime: 0 timeout: 18 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 -1226582352 (LWP 15476)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 78012

Thread 1 (Thread -1226582352 (LWP 15476))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 libgnomeui_segv_handle
at gnome-ui-init.c line 874
#3 <signal handler called>
#4 gtk_xtext_get_type
#5 clipboard_unset
at gtkclipboard.c line 664
#6 selection_clear_event_cb
at gtkclipboard.c line 327
#7 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 84
#8 IA__g_closure_invoke
at gclosure.c line 490
#9 signal_emit_unlocked_R
at gsignal.c line 2440
#10 IA__g_signal_emit_valist
at gsignal.c line 2209
#11 IA__g_signal_emit
at gsignal.c line 2243
#12 gtk_widget_event_internal
at gtkwidget.c line 3911
#13 IA__gtk_selection_owner_set_for_display
at gtkselection.c line 719
#14 IA__gtk_clipboard_clear
at gtkclipboard.c line 690
#15 gtk_xtext_get_type
#16 gtk_xtext_clear
#17 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 84
#18 g_type_class_meta_marshal
at gclosure.c line 567
#19 IA__g_closure_invoke
at gclosure.c line 490
#20 signal_emit_unlocked_R
at gsignal.c line 2478
#21 IA__g_signal_emit_valist
at gsignal.c line 2209
#22 IA__g_signal_emit
at gsignal.c line 2243
#23 gtk_widget_event_internal
at gtkwidget.c line 3911
#24 IA__gtk_propagate_event
at gtkmain.c line 2211
#25 IA__gtk_main_do_event
at gtkmain.c line 1445
#26 gdk_event_dispatch
at gdkevents-x11.c line 2320
#27 IA__g_main_context_dispatch
at gmain.c line 2045
#28 g_main_context_iterate
at gmain.c line 2677
#29 IA__g_main_loop_run
at gmain.c line 2881
#30 IA__gtk_main
at gtkmain.c line 1024
#31 fe_main
#32 main
#0 __kernel_vsyscall

Comment 1 David Trowbridge 2006-10-25 05:55:13 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 361151 ***