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 269294 - evolution freezes when accessing echange calendar
evolution freezes when accessing echange calendar
Status: RESOLVED OBSOLETE
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.0.1
Other other
: Normal critical
: 2.0.4
Assigned To: Connector Maintainer
Ximian Connector QA
Depends on:
Blocks: 270414
 
 
Reported: 2004-11-09 22:20 UTC by Terry
Modified: 2005-11-26 18:53 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Terry 2004-11-09 22:20:18 UTC
Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:

Evolution freezes when I access the exchange calendar but not my local
calendar.  This is on Fedora Core 3:
evolution-webcal-1.0.10-1
evolution-data-server-1.0.2-3
evolution-2.0.2-3
evolution-connector-2.0.2-1

Steps to reproduce the problem:
1.   Open evolution
2.   Notice life is good
3.   Access exchange calendar

Actual Results:
Evolution freezes (no crash)

Expected Results:
Open calendar

How often does this happen? 

Every time
Additional Information:

I can access my calendar fine via OWA.


Evolution BT:

(gdb) thread apply all bt

Thread 7 (Thread -158147664 (LWP 20374))

  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 pthread_cond_wait
    from /lib/tls/libpthread.so.0
  • #2 e_msgport_wait
    from /usr/lib/evolution/2.0/libeutil.so.0
  • #3 e_thread_busy
    from /usr/lib/evolution/2.0/libeutil.so.0
  • #4 start_thread
    from /lib/tls/libpthread.so.0
  • #5 clone
    from /lib/tls/libc.so.6

Thread 6 (Thread -168637520 (LWP 20375))

  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 pthread_cond_wait
    from /lib/tls/libpthread.so.0
  • #2 e_msgport_wait
    from /usr/lib/evolution/2.0/libeutil.so.0
  • #3 e_thread_busy
    from /usr/lib/evolution/2.0/libeutil.so.0
  • #4 start_thread
    from /lib/tls/libpthread.so.0
  • #5 clone
    from /lib/tls/libc.so.6

Thread 5 (Thread -179127376 (LWP 20376))

  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 __read_nocancel
    from /lib/tls/libpthread.so.0
  • #2 camel_stub_marshal_free
    from /usr/lib/evolution/2.0/camel-providers/libcamelexchange.so
  • #3 camel_stub_marshal_free
    from /usr/lib/evolution/2.0/camel-providers/libcamelexchange.so
  • #4 camel_stub_marshal_free
    from /usr/lib/evolution/2.0/camel-providers/libcamelexchange.so
  • #5 camel_stub_marshal_decode_uint32
    from /usr/lib/evolution/2.0/camel-providers/libcamelexchange.so
  • #6 camel_stub_get_type
    from /usr/lib/evolution/2.0/camel-providers/libcamelexchange.so
  • #7 start_thread
    from /lib/tls/libpthread.so.0
  • #8 clone
    from /lib/tls/libc.so.6

Thread 4 (Thread -189776976 (LWP 20393))

  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 pthread_cond_wait
    from /lib/tls/libpthread.so.0
  • #2 e_msgport_wait
    from /usr/lib/evolution/2.0/libeutil.so.0
  • #3 e_thread_busy
    from /usr/lib/evolution/2.0/libeutil.so.0
  • #4 start_thread
    from /lib/tls/libpthread.so.0
  • #5 clone
    from /lib/tls/libc.so.6

Thread 3 (Thread -200660048 (LWP 20435))

  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 poll
    from /lib/tls/libc.so.6
  • #2 g_main_context_acquire
    from /usr/lib/libglib-2.0.so.0
  • #3 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #4 link_thread_io_context
    from /usr/lib/libORBit-2.so.0
  • #5 ??
    from /usr/lib/libglib-2.0.so.0
  • #6 ??
  • #7 g_static_private_free
    from /usr/lib/libglib-2.0.so.0

Thread 4 (Thread -153359440 (LWP 20370))

  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 poll
    from /lib/tls/libc.so.6
  • #2 g_main_context_acquire
    from /usr/lib/libglib-2.0.so.0
  • #3 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #4 link_thread_io_context
    from /usr/lib/libORBit-2.so.0
  • #5 ??
    from /usr/lib/libglib-2.0.so.0
  • #6 ??
  • #7 g_static_private_free
    from /usr/lib/libglib-2.0.so.0

Comment 1 Terry 2004-11-11 23:23:40 UTC
It should be noted that I am NOT seeing any resource increases as
depicted in bug#268246.
Comment 2 Terry 2004-12-02 23:09:32 UTC
Backtrace was generated from
'/usr/local:/opt/gnome:/usr/libexec/evolution-exchange-storage'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 1097352064 (LWP 11371)]
[New Thread 1100606384 (LWP 11372)]
[Thread debugging using libthread_db enabled]
[New Thread 1097352064 (LWP 11371)]
[New Thread 1100606384 (LWP 11372)]
[Thread debugging using libthread_db enabled]
[New Thread 1097352064 (LWP 11371)]
[New Thread 1100606384 (LWP 11372)]
0xffffe410 in ?? ()

Thread 1 (Thread 1097352064 (LWP 11371))

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #5 libgnomeui_segv_handle
    from /opt/gnome/lib/libgnomeui-2.so.0
  • #6 <signal handler called>
  • #7 e_cal_recur_generate_instances_of_rule
    at e-cal-recur.c line 700
  • #8 e_cal_recur_generate_instances
    at e-cal-recur.c line 637
  • #9 func_occur_in_time_range
    at e-cal-backend-sexp.c line 339
  • #10 e_sexp_term_eval
    at e-sexp.c line 710
  • #11 term_eval_and
    at e-sexp.c line 255
  • #12 e_sexp_term_eval
    at e-sexp.c line 700
  • #13 e_sexp_eval
    at e-sexp.c line 1304
  • #14 e_cal_backend_sexp_match_comp
    at e-cal-backend-sexp.c line 987
  • #15 match_object
    at e-cal-backend-exchange.c line 864
  • #16 g_hash_table_foreach
    from /opt/gnome/lib/libglib-2.0.so.0
  • #17 start_query
    at e-cal-backend-exchange.c line 897
  • #18 e_cal_backend_start_query
    at e-cal-backend.c line 642
  • #19 impl_EDataCalView_start
    at e-data-cal-view.c line 251
  • #20 _ORBIT_skel_small_GNOME_Evolution_Calendar_CalView_start
    at Evolution-DataServer-Calendar-common.c line 21
  • #21 ORBit_POAObject_invoke
    from /opt/gnome/lib/libORBit-2.so.0
  • #22 ORBit_OAObject_invoke
    from /opt/gnome/lib/libORBit-2.so.0
  • #23 ORBit_small_invoke_adaptor
    from /opt/gnome/lib/libORBit-2.so.0
  • #24 ORBit_POAObject_handle_request
    from /opt/gnome/lib/libORBit-2.so.0
  • #25 ORBit_POAObject_invoke_incoming_request
    from /opt/gnome/lib/libORBit-2.so.0
  • #26 giop_thread_queue_process
    from /opt/gnome/lib/libORBit-2.so.0
  • #27 giop_mainloop_handle_input
    from /opt/gnome/lib/libORBit-2.so.0
  • #28 link_source_dispatch
    from /opt/gnome/lib/libORBit-2.so.0
  • #29 g_main_context_dispatch
    from /opt/gnome/lib/libglib-2.0.so.0
  • #30 g_main_context_iterate
    from /opt/gnome/lib/libglib-2.0.so.0
  • #31 g_main_loop_run
    from /opt/gnome/lib/libglib-2.0.so.0
  • #32 bonobo_main
    from /opt/gnome/lib/libbonobo-2.so.0
  • #33 main
    at main.c line 205
  • #0 ??

Comment 3 Terry 2004-12-15 16:54:40 UTC
Is this of any help at all?

(gdb) thread apply all bt

Thread 3 (Thread 48741296 (LWP 3959))

  • #0 clone
    from /lib/tls/libc.so.6
  • #1 ??

Thread 2 (Thread 25156528 (LWP 3818))

  • #0 __nptl_create_event
    from /lib/tls/libpthread.so.0
  • #1 pthread_create
    from /lib/tls/libpthread.so.0
  • #2 ??
    from /usr/lib/libgthread-2.0.so.0
  • #3 ??
  • #4 ??
  • #5 g_static_private_free
    from /usr/lib/libglib-2.0.so.0
  • #6 g_thread_create_full
    from /usr/lib/libglib-2.0.so.0
  • #7 g_static_rw_lock_free
    from /usr/lib/libglib-2.0.so.0
  • #8 g_thread_pool_push
    from /usr/lib/libglib-2.0.so.0
  • #9 giop_thread_request_push_key
    from /usr/lib/libORBit-2.so.0
  • #10 ORBit_POAObject_post_invoke
    from /usr/lib/libORBit-2.so.0
  • #11 ORBit_POAObject_post_invoke
    from /usr/lib/libORBit-2.so.0
  • #12 ORBit_handle_request
    from /usr/lib/libORBit-2.so.0
  • #13 giop_connection_handle_input
    from /usr/lib/libORBit-2.so.0
  • #14 link_connection_set_max_buffer
    from /usr/lib/libORBit-2.so.0
  • #15 link_servers_move_io_T
    from /usr/lib/libORBit-2.so.0
  • #16 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #17 g_main_context_acquire
    from /usr/lib/libglib-2.0.so.0
  • #18 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #19 link_thread_io_context
    from /usr/lib/libORBit-2.so.0
  • #20 ??
    from /usr/lib/libglib-2.0.so.0
  • #21 ??
  • #22 g_static_private_free
    from /usr/lib/libglib-2.0.so.0
  • #23 ??
  • #24 ??
  • #25 ??
  • #26 ??
  • #27 ??
    from /usr/lib/libsoftokn3.so
  • #28 ??

Thread 1 (Thread -151155808 (LWP 3817))

  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 poll
    from /lib/tls/libc.so.6
  • #2 g_main_context_acquire
    from /usr/lib/libglib-2.0.so.0
  • #3 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #4 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #5 main

Comment 4 Terry 2004-12-15 20:07:30 UTC
I just did something that turned interesting results.  If I receive a
meeting request via email, it gives me the option to accept or
decline.  If I accept, it adds it to my exchange calendar (as it
should) but it works.  However, I still cannot _view_ my exchange
calendar.

Thanks!
Comment 5 Terry 2004-12-20 17:05:35 UTC
1) I did NOT have any appointments with attachments
2) I DID have several appointments created with Outlook and OWA and
Evolution

I removed all of my recurring appointments.  Did not fix my problem.
I removed all old appointments (176 items).  This fixed my problem.

Based on these discoveries, I believe it has something to do with an
outlook created item.

I still have offline copies of these items for reference.
Comment 6 Sarfraaz Ahmed 2005-01-25 12:31:44 UTC
Yes, the stack does show that this is related to #70414 and this
occurs for detatched events created through OWA. The fix for #70414
should solve this. If you could build exchange and test this, it would
be great. [ You might have to wait for 2.0.4 to be released to get the
rpms ]
Comment 7 Poornima 2005-11-26 18:53:49 UTC
Closing this bug at present as Reporter has not updated since last 10 months. 
Reporter can reopen the bug if this bug is reproducible in 2.0.4 or any 
evolution release after 2.0.4.