Bug 306249 - Calendar resource displays main calendar multiple times
Summary: Calendar resource displays main calendar multiple times
Status: RESOLVED WORKSFORME
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Google Resource (show other bugs)
Version: 4.9
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Daniel Vrátil
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-04 13:19 UTC by Andreas Cord-Landwehr
Modified: 2013-03-21 07:22 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot of duplicated calendar resources (80.39 KB, image/png)
2012-09-04 13:19 UTC, Andreas Cord-Landwehr
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Cord-Landwehr 2012-09-04 13:19:57 UTC
Created attachment 73645 [details]
Screenshot of duplicated calendar resources

Problem Description:
1. I created a google resource, added my calendar, everything worked fine
2. Google Germany asked its users to switch from USER@googlemail.com to USER@gmail.com mail addresses; I did so
3. the calendar stopped displaying my events
4. I removed the google resource (akonadi control)
5. I re-added the akonadi google resource and added selected the USER@gmail.com calendar
6. the calendar appeared twice in the calendar listing

I could reproduce the behavior on another system with the same google account. If you need more information/testing, please tell so.
Comment 1 Daniel Vrátil 2012-09-04 19:18:43 UTC
Could you please open Akonadi Console, go to Browser tab, right-click the duplicated collections -> Folder Properties -> Internals and provide what are their Remote Identifers?
Comment 2 Andreas Cord-Landwehr 2012-09-05 08:11:11 UTC
The collection that is duplicated in KOrganizer calendar list appears only once in akonadi console. The remote identifier for that collection is cordlandwehr@gmail.com (and hence should be correct).
Comment 3 Daniel Vrátil 2012-09-05 09:05:45 UTC
Hmm, that might indicate a KOrganizer or Akonadi model bug. If it's only once in Akonadi Console, then the Akonadi resource provided correct information. 

I actually forgot to ask whether it is reliably reproducible after restarting KOrganizer and/or Akonadi (akonadictl restart).
Comment 4 Andreas Cord-Landwehr 2012-09-05 09:54:02 UTC
Restarting Akonadi and/or KOrganizer has no effect to the bug.
Comment 5 Andreas Cord-Landwehr 2013-03-21 07:22:32 UTC
Using libkgapi 0.4.4 and KDEPIM 4.10.1 packages fixes the problem for me.
So I am closing this/my bug as WORKSFORME.