Bug 356647 – Crasher: Disconnect the error handler in the accounts dialog

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 356647 - Crasher: Disconnect the error handler in the accounts dialog


Summary:	Crasher: Disconnect the error handler in the accounts dialog


Status:	RESOLVED FIXED

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

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

URL:
Whiteboard:

Duplicates:	357490 (view as bug list)
Depends on:
Blocks:

Reported:	2006-09-18 23:36 UTC by Keywan Najafi Tonekaboni
Modified:	2006-09-24 18:06 UTC

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

Description Keywan Najafi Tonekaboni 2006-09-18 23:36:42 UTC

What were you doing when the application crashed?
I had problems with my internet connection. I think gossip got in trouble by its new autoconnect feature...


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 23519232 vsize: 0 resident: 91684864 share: 0 rss: 91684864 rss_rlim: 0
CPU usage: start_time: 473 rtime: 0 utime: 1158611586 stime: 0 cutime:1447 cstime: 0 timeout: 1368 it_real_value: 0 frequency: 79

Backtrace was generated from '/usr/local/bin/gossip'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 805601104 (LWP 4893)]
0x0e9b8334 in __waitpid_nocancel () from /lib/libpthread.so.0

+ Trace 72698

Thread 1 (Thread 805601104 (LWP 4893))

#0 __waitpid_nocancel
from /lib/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 g_type_check_instance_cast
from /usr/lib/libgobject-2.0.so.0
#4 accounts_dialog_model_get_selected
at gossip-accounts-dialog.c line 598
#5 accounts_dialog_protocol_error_cb
at gossip-accounts-dialog.c line 1277
#6 libgossip_marshal_VOID__OBJECT_OBJECT_POINTER
at libgossip-marshal.c line 238
#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 session_protocol_error
at gossip-session.c line 611
#12 libgossip_marshal_VOID__OBJECT_POINTER
at libgossip-marshal.c line 313
#13 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#17 jabber_error
at gossip-jabber.c line 729
#18 jabber_connection_open_cb
at gossip-jabber.c line 763
#19 _lm_connection_failed_with_error
from /usr/lib/libloudmouth-1.so.0
#20 _lm_connection_succeeded
from /usr/lib/libloudmouth-1.so.0
#21 g_io_channel_unix_get_fd
from /usr/lib/libglib-2.0.so.0
#22 g_io_channel_unix_get_fd
from /usr/lib/libglib-2.0.so.0
#23 g_io_channel_unix_get_fd
from /usr/lib/libglib-2.0.so.0
#24 g_io_channel_unix_get_fd
from /usr/lib/libglib-2.0.so.0
#25 g_io_channel_unix_get_fd
from /usr/lib/libglib-2.0.so.0
#26 g_io_channel_unix_get_fd
from /usr/lib/libglib-2.0.so.0
#27 g_io_channel_unix_get_fd
from /usr/lib/libglib-2.0.so.0
#28 g_io_channel_unix_get_fd
from /usr/lib/libglib-2.0.so.0
#29 g_io_channel_unix_get_fd
from /usr/lib/libglib-2.0.so.0
#0 __waitpid_nocancel
from /lib/libpthread.so.0

Comment 1 Richard Hult 2006-09-19 06:56:16 UTC

It's not related to autoconnect, I think I know what's wrong. I'll take a look tonight.

Comment 2 Richard Hult 2006-09-19 16:25:13 UTC

Fixed in CVS, thanks.

Comment 3 Martyn Russell 2006-09-24 18:06:15 UTC

*** Bug 357490 has been marked as a duplicate of this bug. ***