Summary: | Unaccepted Google calendar events not shown | ||
---|---|---|---|
Product: | [Applications] korganizer | Reporter: | Chris Spiegel <cspiegel> |
Component: | invitations | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | bake.earmuffs, direx, dvratil, miikka.veijonen, nicolas.fella, sine.nomine |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
this week in korganizer
this week in google cal ui |
Description
Chris Spiegel
2016-04-05 17:23:13 UTC
I am on kde-apps 16.04 with KF 5.21 (Arch Linux) and I am also seeing the same issue, but not only in Google calendars. In all of my calendars (local and CalDAV) the entries which I have not accepted yet are missing. I also made an interesting observation: these events actually show up in Kontact on the overview page (where it shows emails, tasks and calendars in a unified view). This means the events are actually there, KOrganizer just does not display them. This makes me think that the issue is actually unrelated to the calendar provider and rather affects KOrganizer directly. Same with me. I have my calendar almost empty in Korganizer, while in the Overview screen of Kontact the omitted events are and (at least for some of them) I even got reminders. Created attachment 104407 [details]
this week in korganizer
just to illustrate the impact of this bug
Created attachment 104408 [details]
this week in google cal ui
I'd be happy to look for a fix, had I known where. It must be just some if/filter when showing the incidences in the calendar view. Any hints, please? Turns out the events are not shown because they are automatically added to "Open Invitations" virtual search folder which is normally not shown in KOrganizer. At the same time, KOrganizer does not support a single event being present in multiple calendars at once and you guys are simply hit by the case when the "Open Invitations" folder is "above" your calendar folders. This leads to KOrganizer not showing the actual invitation in the real calendar. Git commit f8694fb608ca22418d7430b3a4dec282464a3852 by Daniel Vrátil. Committed on 08/03/2017 at 21:26. Pushed by dvratil into branch 'Applications/16.12'. Don't exclude virtual calendar collections from ETMCalendar KOrganizer adds some events to "Open Invitations" and "Declined Invitations" virtual collections under "Search". Since KOrganizer does not support single event being present in multiple Collections (a limitation in KCalCore really), KOrganizer in some cases does not show unaccepted invitations and there is no way to get to them. This change allows virtual collections to be shown in ETMCalendar, so users can enable those virtual "calendars" in KOrganizer to at least see the invitations, until the underlying issue of multi-instance events is fixed. M +1 -1 src/etmcalendar.cpp https://commits.kde.org/akonadi-calendar/f8694fb608ca22418d7430b3a4dec282464a3852 I'm also facing this bug but using external Exchange (EWS) calendar. The calendar events which are unconfirmed by me are not shown in the EWS calendar and neither in Open Invitations virtual calendar. But Kontact lists them in the summary view. I'm able to browse the missing events in Akonadi Console so they definitely are fetched OK but Korganizer is filtering them out from the original calendar, most likely because they're Open/Declied Invitations. But the Open/Declined Invitations virtual calendars aren't working properly because those events are missing from there also. Korganaizer version: 19.08.3-lp152.1.2 Correction to my comment above: Looks like all meeting requests are missing (accepted, unaccepted) from my calendar. They are fetched OK because I'm able to see them from Akonadi Console but Korganizer isn't showing them but Kontact's Summary / front page is showing them. The only exception is Meeting requests created by myself: they're showing OK in Korganizer. *** This bug has been marked as a duplicate of bug 436812 *** |