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 324487 - Connector crashes during renew_subscription
Connector crashes during renew_subscription
Status: RESOLVED OBSOLETE
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
unspecified
Other All
: Normal critical
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
: 301175 322748 323847 326900 365243 437602 438899 506554 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-12-19 12:25 UTC by Sushma Rai
Modified: 2008-11-13 06:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Sushma Rai 2005-12-19 12:25:50 UTC
Steps to reproduce:
1. Start Evolution and keep idle.
2. 
3. 


Stack trace:

Thread 1 (Thread 1100297888 (LWP 1446))

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #5 libgnomeui_segv_handle
    at gnome-ui-init.c line 786
  • #6 <signal handler called>
  • #7 soup_connection_disconnect
    at soup-connection.c line 657
  • #8 socket_disconnected
    at soup-connection.c line 399
  • #9 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #10 IA__g_closure_invoke
    at gclosure.c line 490
  • #11 signal_emit_unlocked_R
    at gsignal.c line 2449
  • #12 IA__g_signal_emit_valist
    at gsignal.c line 2208
  • #13 IA__g_signal_emit
    at gsignal.c line 2252
  • #14 soup_socket_disconnect
    at soup-socket.c line 944
  • #15 socket_read_watch
    at soup-socket.c line 1038
  • #16 g_io_unix_dispatch
    at giounix.c line 162
  • #17 IA__g_main_context_dispatch
    at gmain.c line 1913
  • #18 g_main_context_iterate
    at gmain.c line 2544
  • #19 IA__g_main_loop_run
    at gmain.c line 2748
  • #20 bonobo_main
    at bonobo-main.c line 312
  • #21 main
    at main.c line 238
  • #0 ??
  • #7 soup_connection_disconnect
    at soup-connection.c line 657
$1 = {parent = {g_type_instance = {g_class = 0x0}, ref_count = 0, qdata =
0xaaaaaaaa}}


Other information:
libsoup Version: 2.2.90
/home/sush/opt/gnome214/lib/libsoup-2.2.so.8
Comment 1 Sushma Rai 2005-12-19 12:27:10 UTC
Evolution version is 2.5.3
Comment 2 Sushma Rai 2005-12-19 13:06:38 UTC
"** (evolution-exchange-storage:1446): WARNING **: renew_subscription: 7 Connection terminated unexpectedly"

error message is printed on the exchange-storage console.
Comment 3 Sushma Rai 2006-01-04 05:36:27 UTC
Happes always.
and bug #323847 looks similar to this.
Comment 4 Sushma Rai 2006-01-04 05:39:28 UTC
Looks like libsoup issue.
Comment 5 Sushma Rai 2006-01-10 11:49:03 UTC
*** Bug 322748 has been marked as a duplicate of this bug. ***
Comment 6 Sushma Rai 2006-01-14 06:34:22 UTC
*** Bug 326900 has been marked as a duplicate of this bug. ***
Comment 7 Sushma Rai 2006-01-17 11:19:33 UTC
*** Bug 323847 has been marked as a duplicate of this bug. ***
Comment 8 Sushma Rai 2006-02-13 13:12:45 UTC
*** Bug 301175 has been marked as a duplicate of this bug. ***
Comment 9 Kjartan Maraas 2006-02-15 08:52:21 UTC
Got this today too. The crash was in evolution-data-server though and the version is 1.5.90. libsoup 2.2.7 is what I've got.

(gdb) bt
  • #0 ??
  • #1 ??
    from /lib/libc.so.6
  • #2 do_system
    at ../sysdeps/posix/system.c line 164
  • #3 __libc_system
    at ../sysdeps/posix/system.c line 206
  • #4 system
    at pt-system.c line 29
  • #5 gnome_segv_handler
    at server.c line 114
  • #6 <signal handler called>
  • #7 soup_connection_disconnect
    at soup-connection.c line 632
  • #8 socket_disconnected
    at soup-connection.c line 377
  • #9 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #10 IA__g_closure_invoke
    at gclosure.c line 490
  • #11 signal_emit_unlocked_R
    at gsignal.c line 2438
  • #12 IA__g_signal_emit_valist
    at gsignal.c line 2197
  • #13 IA__g_signal_emit
    at gsignal.c line 2241
  • #14 soup_socket_disconnect
    at soup-socket.c line 919
  • #15 socket_read_watch
    at soup-socket.c line 1013
  • #16 g_io_unix_dispatch
    at giounix.c line 162
  • #17 IA__g_main_context_dispatch
    at gmain.c line 1916
  • #18 g_main_context_iterate
    at gmain.c line 2547
  • #19 IA__g_main_loop_run
    at gmain.c line 2751
  • #20 bonobo_main
    at bonobo-main.c line 312
  • #21 main
    at server.c line 400
  • #22 __libc_start_main
  • #23 _start

Comment 10 Kjartan Maraas 2006-02-15 08:53:30 UTC
Btw, I do not have the connector installed so maybe this needs to be retitled to something more generic.
Comment 11 Dan Winship 2006-05-26 21:14:54 UTC
is this bug still happening? there was a rash of dups for a while and then
they stopped...
Comment 12 Sushma Rai 2006-05-29 11:49:44 UTC
I still see this, mostly when Evolution is idle and then I try to
do some operaton it crashes (randomly).
Comment 13 André Klapper 2006-09-11 11:19:14 UTC
i still see this, evolution 2.7.92 from cvs head. updated line numbers:

crashed while downloading email:

Backtrace was generated from '/opt/evo-cvs/libexec/evolution-data-server-1.8'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1224149328 (LWP 3531)]
[New Thread -1288471648 (LWP 3560)]
[New Thread -1229456480 (LWP 3532)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1224149328 (LWP 3531))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libc.so.6
  • #2 do_system
    from /lib/libc.so.6
  • #3 system
    from /lib/libc.so.6
  • #4 system
    from /lib/libpthread.so.0
  • #5 gnome_segv_handler
    at server.c line 114
  • #6 <signal handler called>
  • #7 soup_connection_disconnect
    at soup-connection.c line 699
  • #8 socket_disconnected
    at soup-connection.c line 433
  • #9 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #10 IA__g_closure_invoke
    at gclosure.c line 490
  • #11 signal_emit_unlocked_R
    at gsignal.c line 2438
  • #12 IA__g_signal_emit_valist
    at gsignal.c line 2197
  • #13 IA__g_signal_emit
    at gsignal.c line 2241
  • #14 soup_socket_disconnect
    at soup-socket.c line 974
  • #15 socket_read_watch
    at soup-socket.c line 1068
  • #16 g_io_unix_dispatch
    at giounix.c line 162
  • #17 g_main_dispatch
    at gmain.c line 2045
  • #18 IA__g_main_context_dispatch
    at gmain.c line 2596
  • #19 g_main_context_iterate
    at gmain.c line 2677
  • #20 IA__g_main_loop_run
    at gmain.c line 2881
  • #21 bonobo_main
    at bonobo-main.c line 311
  • #22 main
    at server.c line 393
  • #0 __kernel_vsyscall

Comment 14 Karsten Bräckelmann 2006-10-26 13:50:26 UTC
*** Bug 365243 has been marked as a duplicate of this bug. ***
Comment 15 Dan Winship 2006-11-03 16:35:46 UTC
As per a long-ago discussion with Parag and Harish, I'm moving the soup connector bugs to the Evolution Exchange product, because I have no way of reproducing these bugs myself, so if they stay filed against libsoup, they're never going to get fixed.
Comment 16 Veerapuram Varadhan 2006-11-21 19:49:35 UTC
(In reply to comment #15)
> As per a long-ago discussion with Parag and Harish, I'm moving the soup
> connector bugs to the Evolution Exchange product, because I have no way of
> reproducing these bugs myself, so if they stay filed against libsoup, they're
> never going to get fixed.
> 
Dan: Any idea where it could be failing?
Comment 17 Veerapuram Varadhan 2006-11-21 19:52:08 UTC
(In reply to comment #13)
> i still see this, evolution 2.7.92 from cvs head. updated line numbers:
> 
> crashed while downloading email:
> 
> Backtrace was generated from '/opt/evo-cvs/libexec/evolution-data-server-1.8'
> 
Can you attach Evolution and evolution-exchange traces as well?  The traces show only libsoup calls and it is quite difficult to analyse such traces. 
Comment 18 André Klapper 2006-11-27 17:44:43 UTC
i'm getting this one here (evo 2.9.2cvs) without even using evolution-exchange:

Backtrace was generated from '/media/hda4-reiser/built/gnome-cvs-head/libexec/evolution-data-server-1.10'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1222830416 (LWP 3817)]
[New Thread -1278493792 (LWP 3857)]
[New Thread -1227785312 (LWP 3822)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1222830416 (LWP 3817))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libc.so.6
  • #2 do_system
    from /lib/libc.so.6
  • #3 system
    from /lib/libc.so.6
  • #4 system
    from /lib/libpthread.so.0
  • #5 gnome_segv_handler
    at server.c line 114
  • #6 <signal handler called>
  • #7 soup_connection_disconnect
    at soup-connection.c line 699
  • #8 socket_disconnected
    at soup-connection.c line 433
  • #9 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #10 IA__g_closure_invoke
    at gclosure.c line 490
  • #11 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #12 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #13 IA__g_signal_emit
    at gsignal.c line 2243
  • #14 soup_socket_disconnect
    at soup-socket.c line 974
  • #15 socket_read_watch
    at soup-socket.c line 1068
  • #16 g_io_unix_dispatch
    at giounix.c line 162
  • #17 g_main_dispatch
    at gmain.c line 2049
  • #18 IA__g_main_context_dispatch
    at gmain.c line 2600
  • #19 g_main_context_iterate
    at gmain.c line 2681
  • #20 IA__g_main_loop_run
    at gmain.c line 2885
  • #21 bonobo_main
    at bonobo-main.c line 311
  • #22 main
    at server.c line 393
  • #0 __kernel_vsyscall

Comment 19 Daniel Gryniewicz 2007-05-11 02:34:04 UTC
*** Bug 437602 has been marked as a duplicate of this bug. ***
Comment 20 Daniel Gryniewicz 2007-05-16 13:43:54 UTC
*** Bug 438899 has been marked as a duplicate of this bug. ***
Comment 21 Pedro de Medeiros 2007-12-31 10:34:07 UTC
*** Bug 506554 has been marked as a duplicate of this bug. ***
Comment 22 Akhil Laddha 2008-08-11 05:32:50 UTC
can anyone reproduce this on current stable evolution 2.22.3, thanks.
Comment 23 André Klapper 2008-08-11 09:03:32 UTC
Akhil: Was that a question?
And 2.22.3 is NOT current stable.
Comment 24 Akhil Laddha 2008-08-11 09:18:01 UTC
ah..you meant i should mention 2.22.3.1 ?  I feel user will automatically try in current one what ever version he has. Anyway next time i will try to put correct one.
Comment 25 Akhil Laddha 2008-11-13 06:26:03 UTC
Please feel free to reopen this bug if the problem still occurs with a newer
version of GNOME 2.24.1, thanks.