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 634147 - crash in io_error, e2k_context_send_message at e2k-context.c line 929
crash in io_error, e2k_context_send_message at e2k-context.c line 929
Status: RESOLVED DUPLICATE of bug 603368
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.30.x
Other All
: Normal critical
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
Depends on:
Blocks:
 
 
Reported: 2010-11-06 07:12 UTC by wolcendo
Modified: 2011-01-06 11:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.29/2.30



Description wolcendo 2010-11-06 07:12:03 UTC
What were you doing when the application crashed?
Started.

Distribution: Debian squeeze/sid
Gnome Release: 2.30.2 2010-07-17 (Debian)
BugBuddy Version: 2.30.0

System: Linux 2.6.32-5-686-bigmem #1 SMP Sat Oct 30 23:25:58 UTC 2010 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10707000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Crux
GTK+ Modules: gnomebreakpad

Memory status: size: 199655424 vsize: 199655424 resident: 34004992 share: 22597632 rss: 34004992 rss_rlim: 18446744073709551615
CPU usage: start_time: 1289027483 rtime: 222 utime: 197 stime: 25 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

[Thread debugging using libthread_db enabled]
[New Thread 0xac94fb70 (LWP 1044)]
[New Thread 0xac990b70 (LWP 1032)]
[New Thread 0xad2f0b70 (LWP 1031)]
[New Thread 0xadaf1b70 (LWP 1027)]
[New Thread 0xb33a3b70 (LWP 1023)]
[New Thread 0xb3ba4b70 (LWP 1022)]
[New Thread 0xb43a5b70 (LWP 1021)]
[New Thread 0xb4cffb70 (LWP 1020)]
[New Thread 0xb560bb70 (LWP 1019)]
0xb7704424 in __kernel_vsyscall ()

Thread 4 (Thread 0xad2f0b70 (LWP 1031))

  • #0 __kernel_vsyscall
  • #1 __lll_lock_wait
    from /lib/i686/cmov/libpthread.so.0
  • #2 _L_lock_748
    from /lib/i686/cmov/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/i686/cmov/libpthread.so.0
  • #4 segv_redirect
    at main.c line 298
  • #5 <signal handler called>
  • #6 io_error
    at soup-message-io.c line 200
  • #7 read_metadata
    at soup-message-io.c line 323
  • #8 io_read
    at soup-message-io.c line 820
  • #9 IA__g_cclosure_marshal_VOID__VOID
    at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/gobject/gmarshal.c line 77
  • #10 IA__g_closure_invoke
    at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/gobject/gclosure.c line 767
  • #11 signal_emit_unlocked_R
    at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/gobject/gsignal.c line 3248
  • #12 IA__g_signal_emit_valist
    at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/gobject/gsignal.c line 2981
  • #13 IA__g_signal_emit
    at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/gobject/gsignal.c line 3038
  • #14 soup_socket_disconnect
    at soup-socket.c line 1146
  • #15 soup_connection_disconnect
    at soup-connection.c line 615
  • #16 clear_current_request
    at soup-connection.c line 403
  • #17 soup_connection_set_state
    at soup-connection.c line 681
  • #18 soup_message_io_stop
    at soup-message-io.c line 161
  • #19 soup_message_io_cleanup
    at soup-message-io.c line 94
  • #20 soup_message_io_finished
    at soup-message-io.c line 173
  • #21 soup_message_send_request
    at soup-message-client-io.c line 150
  • #22 soup_connection_send_request
    at soup-connection.c line 714
  • #23 soup_session_send_queue_item
    at soup-session.c line 1208
  • #24 process_queue_item
    at soup-session-sync.c line 267
  • #25 send_message
    at soup-session-sync.c line 327
  • #26 soup_session_send_message
    at soup-session.c line 1659
  • #27 e2k_context_send_message
    at e2k-context.c line 929
  • #28 e2k_context_propfind
    at e2k-context.c line 1711
  • #29 e_folder_exchange_propfind
    at e-folder-exchange.c line 672
  • #30 get_folder_online
    at camel-exchange-utils.c line 1204
  • #31 camel_exchange_utils_get_folder
    at camel-exchange-utils.c line 2235
  • #32 camel_exchange_folder_construct
    at camel-exchange-folder.c line 1075
  • #33 exchange_get_folder
    at camel-exchange-store.c line 451
  • #34 camel_store_get_folder
    from /usr/lib/libcamel-provider-1.2.so.14
  • #35 mail_tool_uri_to_folder
    at mail-tools.c line 334
  • #36 get_folder_exec
    at mail-ops.c line 1245
  • #37 mail_msg_proxy
    at mail-mt.c line 471
  • #38 g_thread_pool_thread_proxy
    at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/glib/gthreadpool.c line 315
  • #39 g_thread_create_proxy
    at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/glib/gthread.c line 1893
  • #40 start_thread
    from /lib/i686/cmov/libpthread.so.0
  • #41 clone
    from /lib/i686/cmov/libc.so.6

	Inferior 1 [process 1018] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


---- Critical and fatal warnings logged during execution ----

** libsoup **: set_current_request: assertion `priv->cur_req == NULL' failed 


----------- .xsession-errors ---------------------
Got OpenWrt 0.993177 0
Got OpenWrt 0.978907 0
Got OpenWrt 0.978907 0
Got OpenWrt 0.989690 0
Got OpenWrt 0.986150 0
Got OpenWrt 0.989690 0
Got OpenWrt 0.986150 0
Got OpenWrt 0.989690 0
Got OpenWrt 0.989690 0
Got OpenWrt 0.978907 0
Got OpenWrt 0.978907 Got Event! 33, -1
error : unterminated entity reference         related
error : unterminated entity reference         related
(evolution:1018): libsoup-CRITICAL **: set_current_request: assertion `priv->cur_req == NULL' failed
--------------------------------------------------
Comment 1 Akhil Laddha 2010-11-06 13:07:32 UTC
may be related to bug 603368
Comment 2 Milan Crha 2011-01-06 11:51:18 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 bug 603368 ***