Bug 234305 - Multiple gcal (google calendar) akonadi calendars duplicate data from only one
Summary: Multiple gcal (google calendar) akonadi calendars duplicate data from only one
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: GoogleData Resource (show other bugs)
Version: 1.0.0
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Adenilson Cavalcanti
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-14 02:14 UTC by Brad Allen
Modified: 2017-01-07 22:36 UTC (History)
7 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 Brad Allen 2010-04-14 02:14:11 UTC
Version:           4.4.2 (using 4.4.2 (KDE 4.4.2), Gentoo)
Compiler:          x86_64-pc-linux-gnu-gcc
OS:                Linux (x86_64) release 2.6.31.12-rt20-rtulmo

I just added gcal akonadi calendars to korganizer.

I have two gmail accounts.  Each has a main calendar of
its own.  Each shares calendars with the other.
One has a second calendar for itself.  (Personal, job #1 sharing personal account,
job #2 with its own login.)

Ok, so I try to import calendars with akonadi and gcal.

Problem #1:  I can't chooes the 2nd calendar (job #1) from the personal gmail account.  Just can't select it.

Problem #2:  the names offered by this system for naming in akonadi are super generic; I'd rather give some names that include stuff like my calendar names.

Problem #3:  main problem I'm reporting here:  the main personal calendar, the first one I added, comes in fine.  I see that I have a dentist appointment.  The other calendar which should come in fine, job #2 with its own gmail login, doesn't show any unique stuff; instead, it just shows up in korganizer as 100% = duplicates of my personal calendar.  All the calendars I'm looking at in korganizer come from akonadi; there's only two, as described above.

The color of the entries is the same as the color I assigned to my personal calendar (I assign unique colors to all calendars).  So, it may be a korganizer bug, since when I first installed the calendars, they didn't have colors; I had to configure those colors in korganizer.  Since the colors come from korganizer, I think the source of the duplication and omission (substitution of wrong calendar data for 2nd calendar) is something related to koranizer, otherwise why would the color be the same as the other calendar?

(I doubt it's suddenly deciding to use the color I assigned to it on the other servers.)


The above is a bug.  I don't know where it is.  (Note to self:  make feature requests for distributing calendar colors, and another feature request for storing the akonadi calendar data locally with backups so that corruption of the other side doesn't lose my data.)


I noticed when the gmail sources weren't working, the calendar data was 100% missing.  Why doesn't it duplicate the information locally, as a backup?  I hardly want a remote failure to put me in the dark.  Is that the design of korganizer, not to sync duplicate stores, but indeed to only have one store?
Comment 1 Ingo Ratsdorf 2010-08-09 01:32:22 UTC
Hi,

I have a similar problem.
Have only one account with multiple calendars (one private, one shared, etc). When I use secondary calendar login email (xxxxx@groups.google.com), it nicely accept the url and login but downloads exactly the same data as for my primary calendar.
So what we see here is support for ONE PRIMARY calendar only, nothing else.
Comment 2 naguz 2010-09-11 23:39:09 UTC
Yes, part of your problems seems to be related to this bug: http://bugs.kde.org/show_bug.cgi?id=233671

Who has been silently ignored for a whopping five months. We'll have to see if my recent bitching incurs a five-more-months penalty or some desperately needed attention.
Comment 3 Sergio Martins 2011-10-30 21:59:35 UTC
Please use the Akonadi DAV resource in KDE 4.7
Comment 4 Ingo Ratsdorf 2011-10-30 22:37:45 UTC
Do we know for sure that groupdav resource works with google?
AFAIK googles caldav support is pretty crippled and not standard conform.
Also Akonadi groupdav does not provide a configuratiuon wizard for google, maybe for a good reason?

Regards,
Ingo

----------------Original message-----------------
From: "Sergio Martins" iamsergio@gmail.com
To: ingo@envirology.co.nz
Date: Sun, 30 Oct 2011 21:59:36 +0000
-------------------------------------------------


> https://bugs.kde.org/show_bug.cgi?id=234305
>
>
>
>
>
> --- Comment #3 from Sergio Martins <iamsergio gmail com> 2011-10-30 21:59:35
> ---
> Please use the Akonadi DAV resource in KDE 4.7
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are a voter for the bug.
> You are on the CC list for the bug.
>
Comment 5 Sergio Martins 2011-10-30 23:17:04 UTC
(In reply to comment #4)
> Do we know for sure that groupdav resource works with google?
> AFAIK googles caldav support is pretty crippled and not standard conform.
> Also Akonadi groupdav does not provide a configuratiuon wizard for google,
> maybe for a good reason?

Been using it successfully for months now.

Grégory, do you know any bugs we might have regarding google?
Comment 6 Grégory Oestreicher 2011-10-31 23:01:39 UTC
> Grégory, do you know any bugs we might have regarding google?

I'm not a Google Calendar user, but the main bug I know of (spotted many 
months ago, not sure if it's still here) is with secondary calendars and 
attendees: if you create an event in a secondary calendar with attendees then 
they will be deleted and replaced with a single attendee corresponding to the 
calendar ID.

Cheers,
Grégory
Comment 7 Denis Kurz 2016-09-24 20:43:03 UTC
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 8 Denis Kurz 2017-01-07 22:36:17 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.