Bug 352385 – crash in Gossip Instant Messenger:

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 352385 - crash in Gossip Instant Messenger:


Summary:	crash in Gossip Instant Messenger:


Status:	RESOLVED FIXED

Product:	gossip
Classification:	Deprecated
Component:	General
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Gossip Maintainers
QA Contact:	Gossip Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-08-22 13:16 UTC by Wouter Bolsterlee (uws)
Modified:	2006-08-22 18:38 UTC

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

Description Wouter Bolsterlee (uws) 2006-08-22 13:16:43 UTC

Version: 0.15

What were you doing when the application crashed?



Distribution: Debian testing/unstable
Gnome Release: 2.15.90 2006-08-07 (JHBuild)
BugBuddy Version: 2.15.92

Memory status: size: 48107520 vsize: 0 resident: 48107520 share: 0 rss: 22974464 rss_rlim: 0
CPU usage: start_time: 1156249126 rtime: 0 utime: 707 stime: 0 cutime:669 cstime: 0 timeout: 38 it_real_value: 0 frequency: 0

Backtrace was generated from '/opt/gnome-2-16/bin/gossip'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1229146400 (LWP 28594)]
0xb71081fe in __waitpid_nocancel () from /lib/tls/libpthread.so.0

+ Trace 70815

Thread 1 (Thread -1229146400 (LWP 28594))

#0 __waitpid_nocancel
from /lib/tls/libpthread.so.0
#1 libgnomeui_segv_handle
at gnome-ui-init.c line 867
#2 <signal handler called>
#3 raise
from /lib/tls/libc.so.6
#4 abort
from /lib/tls/libc.so.6
#5 IA__g_logv
at gmessages.c line 497
#6 IA__g_log
at gmessages.c line 517
#7 IA__g_return_if_fail_warning
at gmessages.c line 532
#8 gossip_time_to_string_local
at gossip-time.c line 86
#9 gossip_log_get_date_readable
at gossip-log.c line 1116
#10 log_window_entry_search_activate_cb
at gossip-log-window.c line 377
#11 IA__g_cclosure_marshal_VOID__VOID
at gmarshal.c line 77
#12 IA__g_closure_invoke
at gclosure.c line 490
#13 signal_emit_unlocked_R
at gsignal.c line 2438
#14 IA__g_signal_emitv
at gsignal.c line 2109
#15 gtk_binding_entry_activate
at gtkbindings.c line 535
#16 binding_match_activate
at gtkbindings.c line 955
#17 gtk_bindings_activate_list
at gtkbindings.c line 1089
#18 IA__gtk_bindings_activate_event
at gtkbindings.c line 1166
#19 gtk_widget_real_key_press_event
at gtkwidget.c line 3645
#20 gtk_entry_key_press
at gtkentry.c line 1969
#21 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 83
#22 g_type_class_meta_marshal
at gclosure.c line 567
#23 IA__g_closure_invoke
at gclosure.c line 490
#24 signal_emit_unlocked_R
at gsignal.c line 2476
#25 IA__g_signal_emit_valist
at gsignal.c line 2207
#26 IA__g_signal_emit
at gsignal.c line 2241
#27 gtk_widget_event_internal
at gtkwidget.c line 3901
#28 IA__gtk_window_propagate_key_event
at gtkwindow.c line 4671
#29 gtk_window_key_press_event
at gtkwindow.c line 4701
#30 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 83
#31 g_type_class_meta_marshal
at gclosure.c line 567
#32 IA__g_closure_invoke
at gclosure.c line 490
#33 signal_emit_unlocked_R
at gsignal.c line 2476
#34 IA__g_signal_emit_valist
at gsignal.c line 2207
#35 IA__g_signal_emit
at gsignal.c line 2241
#36 gtk_widget_event_internal
at gtkwidget.c line 3901
#37 IA__gtk_propagate_event
at gtkmain.c line 2161
#38 IA__gtk_main_do_event
at gtkmain.c line 1421
#39 gdk_event_dispatch
at gdkevents-x11.c line 2320
#40 IA__g_main_context_dispatch
at gmain.c line 2043
#41 g_main_context_iterate
at gmain.c line 2675
#42 IA__g_main_loop_run
at gmain.c line 2879
#43 IA__gtk_main
at gtkmain.c line 1000
#44 main
at gossip-main.c line 201
#0 __waitpid_nocancel
from /lib/tls/libpthread.so.0

Comment 1 Richard Hult 2006-08-22 14:16:28 UTC

I'll take a look tonight (the reason it crashes is because gnome 2.15 is currently running with critical warnings so a warning aborts apps).

Comment 2 Wouter Bolsterlee (uws) 2006-08-22 14:30:57 UTC

The crash occurred when I tried to search my history/logs for some text.

Btw, ignoring warnings will causes crashes/malfunctioning in the long term, so fixing it is good ;)

Comment 3 Richard Hult 2006-08-22 14:36:25 UTC

Really? I had nooo idea;)

Seriously, we do keep gossip warning free but there are bugs of course.

Comment 4 Martyn Russell 2006-08-22 14:40:27 UTC

It is our fault Galago is perfect and we don't know how to use it yet, I think that's why it keeps going BOOM BOOM BOOM! :D

Comment 5 Wouter Bolsterlee (uws) 2006-08-22 14:50:43 UTC

I'm not sure what you meant to say, but this crash is not galago-related since I don't have support for it compiled into gossip :)

Comment 6 Martyn Russell 2006-08-22 14:55:15 UTC

I know it might not be, but GALAGO problems are a key contender for the issues we are seeing with critical warnings.

Comment 7 Richard Hult 2006-08-22 18:38:24 UTC

Small bug introduced by recent UTC fixes, thanks for noticing. Fixed in CVS.