desktop-packages team mailing list archive

Thread
Date
[Bug 643746] Re: Evolution Exchange Calendar Very Slow

To: desktop-packages@xxxxxxxxxxxxxxxxxxx
From: Launchpad Bug Tracker <643746@xxxxxxxxxxxxxxxxxx>
Date: Tue, 23 Aug 2011 04:18:10 -0000
Reply-to: Bug 643746 <643746@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx
[Expired for evolution (Ubuntu) because there has been no activity for
60 days.]

** Changed in: evolution (Ubuntu)
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/643746

Title:
  Evolution Exchange Calendar Very Slow

Status in “evolution” package in Ubuntu:
  Expired

Bug description:
  Binary package hint: evolution

  This may be an evolution-exchange problem instead but I figured it was
  best to start at the top and drill down once we have more information.
  Basically, I am having extremely slow responses when I try to view my
  calendar in Evolution.  I started the client with "evolution
  --disable-eplugin" from the command prompt and here's the warning
  coming out on stderr:

  (evolution:2982): libecal-WARNING **: Cannot get cal from factory: Did
  not receive a reply. Possible causes include: the remote application
  did not send a reply, the message bus security policy blocked the
  reply, the reply timeout expired, or the network connection was
  broken.

  (evolution:2982): calendar-modules-CRITICAL **:
  memo_shell_sidebar_set_default: assertion `client != NULL' failed

  (evolution:2982): libecal-WARNING **: Cannot get cal from factory: Did
  not receive a reply. Possible causes include: the remote application
  did not send a reply, the message bus security policy blocked the
  reply, the reply timeout expired, or the network connection was
  broken.

  (evolution:2982): calendar-modules-CRITICAL **:
  e_memo_shell_sidebar_add_source: assertion `client != NULL' failed

  (evolution:2982): libecal-WARNING **: Cannot get cal from factory: Did
  not receive a reply. Possible causes include: the remote application
  did not send a reply, the message bus security policy blocked the
  reply, the reply timeout expired, or the network connection was
  broken.

  (evolution:2982): calendar-modules-CRITICAL **:
  task_shell_sidebar_set_default: assertion `client != NULL' failed

  (evolution:2982): libecal-WARNING **: Cannot get cal from factory: Did
  not receive a reply. Possible causes include: the remote application
  did not send a reply, the message bus security policy blocked the
  reply, the reply timeout expired, or the network connection was
  broken.

  (evolution:2982): calendar-modules-CRITICAL **:
  e_task_shell_sidebar_add_source: assertion `client != NULL' failed

  (evolution:2982): libecal-WARNING **: Cannot get cal from factory: Did
  not receive a reply. Possible causes include: the remote application
  did not send a reply, the message bus security policy blocked the
  reply, the reply timeout expired, or the network connection was
  broken.

  (evolution:2982): calendar-modules-CRITICAL **:
  e_task_shell_sidebar_add_source: assertion `client != NULL' failed

  (evolution:2982): calendar-gui-CRITICAL **:
  e_cal_model_set_time_range: assertion `start >= 0 && end >= 0' failed

  (evolution:2982): libecal-CRITICAL **: time_to_gdate_with_zone:
  assertion `time != -1' failed

  (evolution:2982): libecal-CRITICAL **: time_to_gdate_with_zone:
  assertion `time != -1' failed

  (evolution:2982): GLib-CRITICAL **: g_date_subtract_days: assertion
  `g_date_valid (d)' failed

  (evolution:2982): GLib-CRITICAL **: g_date_compare: assertion
  `g_date_valid (lhs)' failed

  (evolution:2982): GLib-CRITICAL **: g_date_get_year: assertion
  `g_date_valid (d)' failed

  (evolution:2982): GLib-CRITICAL **: g_date_get_month: assertion
  `g_date_valid (d)' failed

  (evolution:2982): GLib-CRITICAL **: g_date_get_day: assertion
  `g_date_valid (d)' failed

  (evolution:2982): GLib-CRITICAL **: g_date_get_year: assertion
  `g_date_valid (d)' failed

  (evolution:2982): GLib-CRITICAL **: g_date_get_month: assertion
  `g_date_valid (d)' failed

  (evolution:2982): GLib-CRITICAL **: g_date_get_day: assertion
  `g_date_valid (d)' failed

  (evolution:2982): libecal-WARNING **: Cannot get cal from factory: Did
  not receive a reply. Possible causes include: the remote application
  did not send a reply, the message bus security policy blocked the
  reply, the reply timeout expired, or the network connection was
  broken.

  (evolution:2982): calendar-modules-CRITICAL **:
  cal_shell_sidebar_set_default: assertion `client != NULL' failed

  (evolution:2982): libecal-WARNING **: Cannot get cal from factory: Did
  not receive a reply. Possible causes include: the remote application
  did not send a reply, the message bus security policy blocked the
  reply, the reply timeout expired, or the network connection was
  broken.

  (evolution:2982): calendar-modules-CRITICAL **:
  e_cal_shell_sidebar_add_source: assertion `client != NULL' failed

  (evolution:2982): libecal-WARNING **: Cannot get cal from factory: Did
  not receive a reply. Possible causes include: the remote application
  did not send a reply, the message bus security policy blocked the
  reply, the reply timeout expired, or the network connection was
  broken.

  (evolution:2982): calendar-modules-CRITICAL **:
  e_cal_shell_sidebar_add_source: assertion `client != NULL' failed

  (evolution:2982): libecal-WARNING **: Cannot get cal from factory: Did
  not receive a reply. Possible causes include: the remote application
  did not send a reply, the message bus security policy blocked the
  reply, the reply timeout expired, or the network connection was
  broken.

  (evolution:2982): calendar-modules-CRITICAL **:
  e_cal_shell_sidebar_add_source: assertion `client != NULL' failed

  The first error seems to indicate that it is unable to connect to the
  exchange server but all other connection (email read and send) to the
  host work fine. I also have noticed that the gnome-calender on my home
  bar is very slow in responding. This may be related.

  ASE

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: evolution 2.30.3-1ubuntu3
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic i686
  Architecture: i386
  Date: Mon Sep 20 13:56:23 2010
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100113)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: evolution

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/643746/+subscriptions