Bug 323970 - kontact summery for korganizer does not include google calendar events
Summary: kontact summery for korganizer does not include google calendar events
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: summary (show other bugs)
Version: 4.11
Platform: Kubuntu Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-24 14:33 UTC by John
Modified: 2017-01-07 22:15 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John 2013-08-24 14:33:28 UTC
Using only "google calendar and tasks" as the calendar for korganizer results in not reminders being sent and nothing showing up in the kontact summery window for korganizer. Switched plugins from Akarodi to the "google calendar and tasks" as Akarodi stopped functions with the 4.11 update.

Reproducible: Always

Steps to Reproduce:
1. Add a google calendar
2. Triple check all options and make sure korganizer reminder is running
3. add a reminder with notification
4. check summery and wait for notification to be sent. Neither happens
Actual Results:  
No events are shown and no reminders sent.

Expected Results:  
Events should be shown in the kontact summery and reminders sent.

This worked in previous versions with the Akarodi plugin.
Comment 1 John 2013-08-24 14:36:27 UTC
Meant Akonadi not Akaroid.
Comment 2 matze 2013-10-30 13:43:46 UTC
Same issue with my installation from the Arch repos.
Comment 3 Laurent Montel 2014-04-09 07:50:39 UTC
Still valid ?
Comment 4 Denis Kurz 2016-09-24 19:21:52 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 5 Denis Kurz 2017-01-07 22:15:38 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.