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 590772 - crash in connection_disconnected at soup-session.c line 981
crash in connection_disconnected at soup-session.c line 981
Status: RESOLVED INCOMPLETE
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.28.x
Other All
: High critical
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
: 594937 624390 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-08-04 19:32 UTC by Russell Harrison
Modified: 2011-05-03 23:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description Russell Harrison 2009-08-04 19:32:26 UTC
What were you doing when the application crashed?
Starting Evolution after a previous crash


Distribution: Fedora release 11 (Leonidas)
Gnome Release: 2.26.3 2009-07-07 (Red Hat, Inc)
BugBuddy Version: 2.26.0

System: Linux 2.6.29.6-213.fc11.i686.PAE #1 SMP Tue Jul 7 20:59:29 EDT 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10601901
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Fedora
GTK+ Modules: canberra-gtk-module, pk-gtk-module, gnomebreakpad

Memory status: size: 117764096 vsize: 117764096 resident: 25698304 share: 11354112 rss: 25698304 rss_rlim: 18446744073709551615
CPU usage: start_time: 1249414317 rtime: 37 utime: 29 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/libexec/evolution/2.26/evolution-exchange-storage'

[Thread debugging using libthread_db enabled]
[New Thread 0xb6dffb70 (LWP 4472)]
[New Thread 0xb4dfdb70 (LWP 4469)]
[New Thread 0xb43fcb70 (LWP 4435)]
[New Thread 0xb61ffb70 (LWP 4409)]
[New Thread 0xb7bf8b70 (LWP 4334)]
0x0019c424 in __kernel_vsyscall ()

Thread 5 (Thread 0xb61ffb70 (LWP 4409))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 382
  • #3 IA__g_spawn_command_line_sync
    at gspawn.c line 694
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 <signal handler called>
  • #7 handlers_find
    at gsignal.c line 530
  • #8 signal_handlers_foreach_matched_R
    at gsignal.c line 2523
  • #9 IA__g_signal_handlers_disconnect_matched
    at gsignal.c line 2673
  • #10 connection_disconnected
    at soup-session.c line 981
  • #11 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #12 IA__g_closure_invoke
    at gclosure.c line 767
  • #13 signal_emit_unlocked_R
    at gsignal.c line 3247
  • #14 IA__g_signal_emit_valist
    at gsignal.c line 2980
  • #15 IA__g_signal_emit
    at gsignal.c line 3037
  • #16 soup_connection_disconnect
    at soup-connection.c line 579
  • #17 clear_current_request
    at soup-connection.c line 336
  • #18 soup_message_io_stop
    at soup-message-io.c line 154
  • #19 soup_message_io_cleanup
    at soup-message-io.c line 90
  • #20 soup_message_io_finished
    at soup-message-io.c line 166
  • #21 soup_message_send_request
    at soup-message-client-io.c line 131
  • #22 soup_connection_send_request
    at soup-connection.c line 656
  • #23 soup_session_send_queue_item
    at soup-session.c line 925
  • #24 process_queue_item
    at soup-session-sync.c line 251
  • #25 send_message
    at soup-session-sync.c line 311
  • #26 soup_session_send_message
    at soup-session.c line 1329
  • #27 e2k_context_send_message
    at e2k-context.c line 917
  • #28 e2k_context_propfind
    at e2k-context.c line 1701
  • #29 e_folder_exchange_propfind
    at e-folder-exchange.c line 651
  • #30 open_calendar
    at e-cal-backend-exchange.c line 496
  • #31 open_calendar
    at e-cal-backend-exchange-calendar.c line 583
  • #32 e_cal_backend_sync_open
    at e-cal-backend-sync.c line 187
  • #33 _e_cal_backend_open
    at e-cal-backend-sync.c line 707
  • #34 e_cal_backend_open
    at e-cal-backend.c line 613
  • #35 impl_Cal_open
    at e-data-cal.c line 80
  • #36 _ORBIT_skel_small_GNOME_Evolution_Calendar_Cal_open
    at Evolution-DataServer-Calendar-common.c line 44
  • #37 ORBit_POAObject_invoke
    at poa.c line 1148
  • #38 ORBit_OAObject_invoke
    at orbit-adaptor.c line 340
  • #39 ORBit_small_invoke_adaptor
    at orbit-small.c line 846
  • #40 ORBit_POAObject_handle_request
    at poa.c line 1357
  • #41 ORBit_POAObject_invoke_incoming_request
    at poa.c line 1427
  • #42 giop_thread_queue_process
    at giop.c line 792
  • #43 giop_request_handler_thread
    at giop.c line 502
  • #44 g_thread_pool_thread_proxy
    at gthreadpool.c line 265
  • #45 g_thread_create_proxy
    at gthread.c line 635
  • #46 start_thread
    at pthread_create.c line 297
  • #47 clone
    at ../sysdeps/unix/sysv/linux/i386/clone.S line 130


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

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


----------- .xsession-errors (7 sec old) ---------------------
(evolution:4318): e-table-WARNING **: Value from the table model is 2, the states we support are [0..2)
(evolution:4318): e-table-WARNING **: Value from the table model is 2, the states we support are [0..2)
(evolution:4318): e-table-WARNING **: Value from the table model is 2, the states we support are [0..2)
(evolution:4318): e-table-WARNING **: Value from the table model is 2, the states we support are [0..2)
(evolution:4318): e-table-WARNING **: Value from the table model is 2, the states we support are [0..2)
--------------------------------------------------
Comment 1 Akhil Laddha 2010-07-15 03:26:22 UTC
*** Bug 624390 has been marked as a duplicate of this bug. ***
Comment 2 Milan Crha 2011-03-16 15:11:10 UTC
This seems to be deep in libsoup. Could you try with newer version of it, please? By the way, what was the version of libsoup where you had this, please?
Comment 3 Milan Crha 2011-03-16 15:21:49 UTC
*** Bug 594937 has been marked as a duplicate of this bug. ***