Bug 328396 - korganizer/akonadi fails to display calendars
Summary: korganizer/akonadi fails to display calendars
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: groupware (show other bugs)
Version: 4.11.3
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-03 17:51 UTC by Anders Lund
Modified: 2018-01-31 17:01 UTC (History)
4 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 Anders Lund 2013-12-03 17:51:45 UTC
I have my calendars in owncloud, and in korganizer I have one owncloud resource with two calendars.

However, my events does not show. They did, and then they dissapeared. Very often, when I open korganizer, the two calendars are not checked, meaning not displayed. When enabling them, sometimes my events are missing.

All my other clients - ownclound and webdav calendars using caldavsync in android, updates and syncs my calendars fine.

Reproducible: Sometimes
Comment 1 Sergio Martins 2013-12-03 21:00:26 UTC
In akonadiconsole, second tab, after you click on your calendar, do they appear ?
Comment 2 Anders Lund 2013-12-04 06:58:36 UTC
Yes. They also appear in the bottom left panel in korganizer.
My suspicion is that akonadi dropped the IDs and the content, which appears to happen relatively often.
Comment 3 Anders Lund 2013-12-04 07:15:15 UTC
Btw, this experience with akonadi dropping collections is not new. It happens with my addressbooks,  which are also stored in owncloud as well.

My addressbooks are usually recreated, but I often experience that autocompletion in kmail does not work. I suspect akonadi is using an internal id, which becomes invalid when the collection ID is renewed (this actually happens, confirmed by checking collection IDs in akonadiconsole)

I live currently in an area with very poor internet connection, and the small bandwidth is often under big pressure since I work at a school with a lot of young people.
Comment 4 mau 2014-09-30 13:58:33 UTC
Same here for 4.11 - 4.14.1, so I can confirm it (unfortunately).

Poor Internet Connection cannot be the cause at least for me, because I'm using a MySQL- (for akonadi) and an owncloud-server both running on the same host.
Comment 5 Denis Kurz 2017-06-23 19:58:29 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 6 Anders Lund 2017-06-23 20:50:26 UTC
Due to the instability, I rely very little on korganizer these days,
but I believe the situation has improved, since it was a long time
since I experienced my calendars being completely dropped.

PĆ„ Fri, 23 Jun 2017 19:58:29 +0000
Denis Kurz <bugzilla_noreply@kde.org> skrev:
> https://bugs.kde.org/show_bug.cgi?id=328396
> 
> Denis Kurz <kdenis@posteo.de> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>          Resolution|---                         |WAITINGFORINFO
>              Status|UNCONFIRMED                 |NEEDSINFO
> 
> --- Comment #5 from Denis Kurz <kdenis@posteo.de> ---
> This bug has never been confirmed for a KDE PIM version that is based
> on KDE Frameworks (5.x). Those versions differ significantly from the
> old 4.x series. Therefore, I plan to close it in around two or three
> months. In the meantime, it is set to WAITINGFORINFO to give
> reporters the oportunity to check if it is still valid. As soon as
> someone confirms it for a recent version (at least 5.1, ideally even
> more recent), I'll gladly reopen it.
> 
> Please understand that we lack the manpower to triage bugs reported
> for versions almost two years beyond their end of life.
>
Comment 7 Denis Kurz 2018-01-31 17:01:20 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.

As a sidenote, I think KOrganizer is quite stable these days. I've been using it as a daily driver for years, and encounter crashes only very very rarely. Might profit from a UI/UX overhaul, though.