[Kde-pim] [urgentish] How to fix CalDAV syncing?

Matija Šuklje hook at fsfe.org
Mon Jul 6 17:36:07 BST 2015


Hullo,

I’m writing you regarding a very annoying and persisting bug in Akonadi. I 
tried getting help on #akonadi IRC channel, but people seem to busy to check 
that.

I have all my calendars – including my FSFE/work one – on my private ownCloud 
and am obviously using Akonadi to sync with my KDE.

This is where the “urgency” for my plea comes from – I’m unable to access my 
work calendar and ToDo list, which as you can imagine is a show-stopper for 
me. I hope someone on this list can help me with a solution or a workaround.

The bug I’m experiencing looks a tiny bit similar to:
https://bugs.kde.org/show_bug.cgi?id=328734

What happens is that every now and again, one or several of the calendars 
(and/or contacts) resources on ownCloud stop syncing with Akonadi. Since the 
sync works fine with my Jolla phone, I suspect the issue is on KDE’s side.

How this looks in practice is that suddenly and without warning items from 
some calendars are missing in KOrganizer, Zanshin, EventList and even Akonadi 
Console.

What I already tried to do, that before worked, but since the latest update 
doesn’t:
 •	in Akonadi Console: toggle offline; abort activity; restart resource; 
	toggle online
 •	in Akonadi Console: restart Akonadi server
 •	restarting KDE/X
 •	restarting the computer (yes, I’m getting desperate!)

…all to no avail.

What I did notice though is that there are a few errors reported in the 
Akonadi Console server test:

 • 	in Akonadi:
Executable "akonadi_nepomuk_feeder" for agent "akonadi_nepomuk_feeder" could 
not be found! 
Executable "akonadi_folderarchive_agent" for agent 
"akonadi_folderarchive_agent" could not be found! 

 •	in MySQL/MariaDB, there are several lines like:

150706 16:39:59 [ERROR] Native table 'performance_schema'.'users' has the 
wrong structure

and:

2015-07-06 16:40:09 7f8caa889700 InnoDB: Error: page 772 log sequence number 
317014304236
InnoDB: is in the future! Current system log sequence number 316942841648.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.

I’m running KDE 4.14.5 on Mageia if that’s of any concern.

Any idea on how to fix this would be welcome.

I’m currently thinking of creating a new user and slowly migrating all my 
stuff from my current home directory into the new one. This would be quite 
painful for me, because I have substantially modified my KDE/Plasma with 
customs settings, activities, keybindings etc., but I’m willing to take that 
on if there is no better suggestion.


cheers,
Matija
-- 
Legal Coordinator & Coordinator Slovenia
Free Software Foundation Europe
www: http://fsfe.org       █▉   || priv. www: http://matija.suklje.name
e-mail: hook at fsfe.org    █▉█▉█▉ || priv. e-mail: matija at suklje.name
xmpp: hook at jabber.fsfe.org ▉▉   || priv. xmpp: matija.suklje at gabbler.org
sip: matija_suklje at ippi.fr      || gsm: +386 40 690 890
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20150706/c1596330/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/


More information about the kde-pim mailing list