The information provided here suggests that the communication to the akonadi server remains functional (we can see the ASAP communication for the mark as read operation),
but for some reason the UI doesn't update.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jun 28 2016
Jun 27 2016
Actually this seems to be a misinterpretation of the RFC https://tools.ietf.org/html/rfc5545#section-3.8.5.3
Issue confirmed, applies to invitation and local event.
Can't reproduce in most recent version.
Both should be fixed by now.
We sometimes missed sync intervals, and failed to synchronize collections that are only referenced, but not enabled.
It seems impossible to
Jun 22 2016
It shouldn't be possible that mLastChecks contains something too recent since it's initialized from currentDateTime()....
That was after changing the interval and restarting akonadi
Resuming timer timer: Starting timer: QDateTime("Wed Jun 22 16:10:51 2016") 300000 IntervalCheck, collectionExpired: 24 Resuming timer timer:
As a workaround it was suggested to restart akonadi on kontact start, or with a menu option, so users have at least a possibility to fix the issue themselves without restarting their system.
One theory would be that the notification mechanism breaks down, so regular fetches etc. keep working, but kontact no longer reacts to changes.
Jun 20 2016
This ticket now tracks the problem of the event that isn't shown.
It apparently does work sometimes, but not reliably.
Jun 13 2016
Jun 10 2016
Jun 9 2016
Move the exclude string to the back and commit.
Jun 8 2016
The problem is:
- The user has his own identity and that of a delegator configured
- The user creates an event with his own identity as organizer and the delegator as attendee in his own calendar
- Because the delegator is recognized as one of the own identities, the event is (in this case incorrectly) filtered from the own calendar.