After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 782249 - When creating an event in a calendar connected to Nextcloud UTC time is used resulting in time mismatch of the event
When creating an event in a calendar connected to Nextcloud UTC time is used ...
Status: RESOLVED OBSOLETE
Product: gnome-calendar
Classification: Applications
Component: General
3.24.x
Other Linux
: Normal major
: 3.26
Assigned To: GNOME Calendar maintainers
GNOME Calendar maintainers
Depends on:
Blocks:
 
 
Reported: 2017-05-05 21:58 UTC by Tomas Kaluza
Modified: 2017-12-21 19:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Description of the bug (267.45 KB, image/png)
2017-09-28 10:18 UTC, Simon Baconnais
Details

Description Tomas Kaluza 2017-05-05 21:58:30 UTC
I am using a calendar on my Nextcloud server. It works like a charm both on the web interface and as a integrated calendar on my android phone.

I integrated my nextcloud accound using the Online accounts. I am able to see all the events using gnome-calendar, but when I try to create an event let's say at 15:00, it gets created at 13:00. It seems that for some reason gnome-calendar uses UTC time ignoring my timezone settings.

I do not experience this issue neither on the web interface nor when adding an event using my android phone.

Let me know if I can provide additional information.
Comment 1 Georges Basile Stavracas Neto 2017-05-08 10:16:04 UTC
(In reply to Tomas Kaluza from comment #0)

> It seems that for some reason gnome-calendar uses UTC time ignoring my
> timezone settings.

It is very much the oposite: Calendar always uses your current local timezone when creating a timed event. I noticed this issue in the past, and what I saw was that nextCloud was ignoring the passed timezone and storing the event as UTC.

Maybe out timezone string isn't compatible with nextCloud's one? Indeed, more information would be required to have this issue fixed soon. Appearently, you're on GMT+2, right?
Comment 2 Tomas Kaluza 2017-05-08 12:00:54 UTC
Yes, correct, my timezone is GMT+2. What other information can I provide, to help?
Comment 3 Øyvind Stegard 2017-05-10 20:19:17 UTC
I'm also on TZ GMT+2 (+1 during winter, +2 during summer). Imported an ICS calendar feed from work, and all times are off by two hours in Gnome Calendar (wrong by +2 hours).

Here's some info from the ical file  (cannot disclose all):
[...]
BEGIN:VTIMEZONE
TZID:Central Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T030000
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T020000
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
[...]

And sample timestamps from an event which is displayed at the wrong time i Gnome Calendar:
DTSTART;TZID=Central Europe Standard Time:20170511T121500
DTEND;TZID=Central Europe Standard Time:20170511T140000


The same calendar feed is shown with correct times when imported into Google Calendar.
Comment 4 Simon Baconnais 2017-09-28 10:17:44 UTC
Same problem here.

I imported ICS file into Nextcloud calendar. Times are ok with any calendar app, but not with Gnome Calendar ...
Comment 5 Simon Baconnais 2017-09-28 10:18:24 UTC
Created attachment 360589 [details]
Description of the bug
Comment 6 Simon Baconnais 2017-09-28 10:19:32 UTC
I added a picture showing the difference between Evolution calendar and Gnome Calendar (named "Description of the bug")
Comment 7 simon 2017-10-23 09:21:26 UTC
Problem remain using Gnome Calendar 3.26 (Ubuntu 17.10)
Comment 8 Georges Basile Stavracas Neto 2017-11-24 22:20:41 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-calendar/issues/143.