I had a similar problem on Fedora 26 which seems to have gone away after
I killed the evolution-calendar-factory process.

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.

  Failed to open local calendar with "Timeout was reached"

Status in evolution package in Ubuntu:

Bug description:
  After booting into a GNOME session, Evolution was started. Mail
  appeared as expected. When the Calendar section was opened, none of
  the calendars opened including the local calendar. A blue report was
  printed under the toolbar with the error that it could not open the
  local calendar as "Timeout was reached." It seems odd that there
  should be a timeout issue when accessing local data. The local
  calendar is stored on the save drive and mount point as the OS and

  Closing and reopening Evolution did not resolve the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evolution 3.26.1-1
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jan 26 09:12:29 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/evolution
  InstallationDate: Installed on 2017-08-12 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
   PATH=(custom, no user)
  SourcePackage: evolution
  UpgradeStatus: Upgraded to artful on 2017-10-21 (96 days ago)

To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to