Etesync does not have support for the latest version of Kontact, also installing kdepim-runtime-etesync from the PPA does not work.

Open
  • Is something wrong?
#312 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend, desktop

Research direction

Start by checking the Kontact 6.1.1 compatibility report and the documented Kontact setup instructions linked in the issue. The syslog shows the installed Akonadi resource fails to load because a KF5 library is missing; determine whether this integration is maintained by this repository and identify the supported installation path. Done means the issue has a clear compatibility or support answer and, if applicable, the documented setup works.

Written by the indexing model from the issue text.

Description

In previous versions etesync was available simply by adding an Etesync Sync Groupware Resource under Add Calendar. That option has been removed in the latest version of Kontact (6.1.1).

Also, the instructions listed in the documentation no longer work either: https://www.etesync.com/user-guide/kontact/

I installed the PPA from the instructions page: deb http://download.opensuse.org/repositories/home:/fawz:/libetebase/xUbuntu_22.04/ then I installed the package kdepim-runtime-etesync.

Now I do have the the option to add an Eyesync Groupware Resource however nothing happens when I try to add it.

I see this error in the syslog:

org.kde.pim.akonadicontrol: Agent instance "akonadi_etesync_resource: has no interface!
/usr/bin/akonadi_etesync_resource: error while loading shared libraries: libKF5AdonadiAgentBase.so.5: cannot open shared object file: No such file or directory.

So it Etesync simply not available any longer on this platform? Was there any notification that this was being removed?

Dominant language
Python
Stars
332
Forks
61
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from etesync/etesync-dav

All issues in etesync/etesync-dav

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.