In Korganizer I have one account configured that contains five agenda's. I was very happy to see that the Pim Events Plugin was launched in plasma 5. Only it gives very inaccurate output. When I change something in Korganizer in one agenda, THEN that agenda is rendered by the Pim Events Plugin, but all other agenda's aren't. After a reboot even this agenda is not shown. Until I change something in it again. Strange thing is that is makes no difference to re-read or restart Korganizer. Reproducible: Always Steps to Reproduce: 1. setup a CalDAV calendar in Korganizer 2. activate it in Pim Events Plugin 3. reboot (or perhaps start plasmashell again) Actual Results: The Pim Events Plugin shows NO events Expected Results: The Pim Events Plugin should follow Korganizer faithfully and accurately.
I must perhaps add that it is a Gmail calendar. I find Korganizer very reliable when I read that as CalDAV.
CC'ing Dan as kdepim maintainer
I just installed plasma 5.8.1 and the pim events plugin seems to show a little more results suddenly. I would not at all call it dependable but perhaps it is a slight progression.
Git commit c921a14e0a30e13342e94cce74d4ad1bbb3a64c5 by Daniel Vrátil. Committed on 14/10/2016 at 00:04. Pushed by dvratil into branch 'Applications/16.08'. PimEventsPlugin: switch from ETMCalendar to custom EventModel It is hard to tame the ETMCalendar to list only the right events and listen only to the right changes while not keeping everything loaded in the memory all the time. The EventModel is a lightweight bridge between Akonadi and the CalendarBase. It inserts and removes data from the CalendarBase based on currently enabled collections and handles updates. This solves various issues with populating the model initially, listening to the correct changes and it also reduces memory usage by not keeping events from disabled calendars in memory. Related: bug 369606 FIXED-IN: 5.3.3 M +1 -0 plugins/plasma/pimeventsplugin/CMakeLists.txt M +27 -34 plugins/plasma/pimeventsplugin/akonadipimdatasource.cpp M +2 -7 plugins/plasma/pimeventsplugin/akonadipimdatasource.h M +1 -1 plugins/plasma/pimeventsplugin/autotests/CMakeLists.txt A +178 -0 plugins/plasma/pimeventsplugin/eventmodel.cpp [License: GPL (v2+)] C +29 -20 plugins/plasma/pimeventsplugin/eventmodel.h [from: plugins/plasma/pimeventsplugin/akonadipimdatasource.h - 051% similarity] M +3 -3 plugins/plasma/pimeventsplugin/pimcalendarsmodel.cpp M +1 -1 plugins/plasma/pimeventsplugin/pimeventsplugin.h http://commits.kde.org/kdepim-addons/c921a14e0a30e13342e94cce74d4ad1bbb3a64c5
Fixed-in: 5.3.3 is great news! Thank you for your great work! Just out of curiousity: what application has this release number 5.3.3? Will it take long to be ready for "general consuption"?
I had these problems too; after a necessary KDE Config reset it works now for me with these settings I have two calendar accounts: "owncloud" and "Birthdays & Anniversaries" korganizer: settings: Time and Date, Holidays: set to (bavaria for me) shown caledars: owncloud/"standard" and "Birthdays & Anniversaries" not shown: owncloud/contact birthdays digital clock: calendar: all = holidays and PIM events holidays: none PIM events Plugin chosen: "Birthdays & Anniversaries" ans owncloud/"standard" PIM events Plugin not chosen: owncloud/contact birthdays and search result: I can see all in my digital clock: - holidays (which seems to depend from regional language setting in systemsettings, because with american english as language, digital clock shows Columbus Day as holiday but korganizer shows correctly "Allerheiligen"?!?) - Birthdays of my contacts - and of course events of my Standard Owncloud calendar
Great Wulf! I had that too, one or two times. Only on my systems it never survived a reboot of the system.
No problem here with reboot/relogin; but I got a plasma update from 5.8.1 to 5.8.2 (Arch) on 20161018 - I don't know wether this is the reason
Today I recieved plasma 5.8.4 on my Neon KDE box. The problem is 100% fixed! And btw.: speaking about an elegant ui! Thanks!
*** Bug 368161 has been marked as a duplicate of this bug. ***
*** Bug 372914 has been marked as a duplicate of this bug. ***
*** Bug 373143 has been marked as a duplicate of this bug. ***
*** Bug 375310 has been marked as a duplicate of this bug. ***
*** Bug 375592 has been marked as a duplicate of this bug. ***