Bug 361419 - Unaccepted Google calendar events not shown
Summary: Unaccepted Google calendar events not shown
Status: RESOLVED DUPLICATE of bug 436812
Alias: None
Product: korganizer
Classification: Applications
Component: invitations (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-05 17:23 UTC by Chris Spiegel
Modified: 2022-02-21 23:00 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
this week in korganizer (96.05 KB, image/png)
2017-03-06 13:47 UTC, Martin Kyral
Details
this week in google cal ui (19.32 KB, image/png)
2017-03-06 13:47 UTC, Martin Kyral
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Spiegel 2016-04-05 17:23:13 UTC
Version is 15.12.3, which was not available in the list.

I have a couple of GMail calendars set up with Akonadi/KOrganizer. However, the only events that KOrganizer shows on the calendar are those which I have accepted an invitation to.  Unaccepted invitations are not displayed.  Once I accept the invitation elsewhere (e.g. in Thunderbird), it shows up in KOrganizer after synchronizing.

These events are not completely lost, because they show up in the Kontact summary.  Clicking on them takes you to the calendar, but unlike for accepted events, the event itself doesn't pop up; the only thing that happens is a notification sound.  The events are still not on the calendar.

Reproducible: Always

Steps to Reproduce:
1. Add a GMail calendar to KOrganizer
2. Get somebody to send you an invitation to an event

Actual Results:  
The event shows up in the Kontact summary, but not the KOrganizer calendar.  It doesn't matter which view (Day, Week, Agenda, Month, Timeline); it's nowhere to be found.

Expected Results:  
The event shows up in both the summary and calendar.  I am able to accept the invitations.

This is not a duplicate of #360030 as that is an intermittent error.  I never see the events on the calender (and always seem them in the summary list).

This appears unrelated to #355908, as I applied the relevant patch to libkgapi and the behavior is still the same.
Comment 1 Dan 2016-05-04 15:16:49 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.
Comment 2 Martin Kyral 2017-02-16 09:01:36 UTC
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.
Comment 3 Martin Kyral 2017-03-06 13:47:08 UTC
Created attachment 104407 [details]
this week in korganizer

just to illustrate the impact of this bug
Comment 4 Martin Kyral 2017-03-06 13:47:37 UTC
Created attachment 104408 [details]
this week in google cal ui
Comment 5 Martin Kyral 2017-03-06 13:58:17 UTC
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?
Comment 6 Daniel Vrátil 2017-03-06 23:17:50 UTC
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.
Comment 7 Daniel Vrátil 2017-03-08 21:28:01 UTC
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
Comment 8 Miikka 2019-12-10 17:28:49 UTC
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
Comment 9 Miikka 2019-12-12 17:29:55 UTC
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.
Comment 10 Nicolas Fella 2022-02-21 23:00:36 UTC

*** This bug has been marked as a duplicate of bug 436812 ***