GNOME Bugzilla – Bug 352801
cannot set timezone for all-day event
Last modified: 2015-08-12 05:07:35 UTC
set up a new all day appointment. make the editor display the timezone option (this already sucks because i have to click twice - bug 347248). change the timezone, for example to UTC. (i have europe/berlin in my evo preferences which is UTC+0200.) save the appointment. actual result: see that the appointment will be a "normal" all day appointment from 0AM to 0AM). expected result: the appointment should begin at 2AM and end at 2AM, because it is not in my timezone. also try to re-edit the appointment, see that the timezone data was not saved at all - it's reset to eureope/berlin. this blocks generating a valid ics file for me - guess the workaround would be to change the evolution timezone in the preferences everytime. evo 2.7.92.
All day events do not have the timezone associated with them.
hmm... arguments? (i think we discussed this on irc, however, i will have the same problem again in 6 weeks, and it took me hours to workaround it the last time.) sorry, i'm pretty defiant here (and i'm one of those reopening folks that always annoyed me when i was the evo bugmaster, hehe). can you explain to me what's the difference between a 24hours event, and an all-day event? tia. :-) if there is none, then all-day means that something's going on the entire day, in a specific timezone, for 24 hours, from 00:00 to 23:59. without having a timezone, it would be a 24hours-event somewhere within an undefined range of 47 hours total.
There is a similar bug there https://bugs.launchpad.net/bugs/152917
I'll try to check your improvement later this day. have to do my day job right now ;-)
sorry wrong bu
Bumping version to a stable release.
This issue is still unresolved in Ubuntu Hardy (Evolution 2.22.1). The problem was encountered with Exchange all-day events (including anniversaries).
I agree that the all day event needs a timezone associated with it. Will get this fixed around this week.
*** Bug 347248 has been marked as a duplicate of this bug. ***
(In reply to comment #8) > I agree that the all day event needs a timezone associated with it. Will get > this fixed around this week. How is it going, chen? :)
So the date says haven touched this yet :(
http://tools.ietf.org/html/rfc5545.html#section-3.2.19 The "TZID" property parameter MUST NOT be applied to DATE properties and DATE-TIME or TIME properties whose time values are specified in UTC. And because Evolution's all day event uses DATE, then you cannot store timezone there. Question for a change, of course.
And to mention, the bug #555899 is somehow related to this.
Please try with fixes from bug #611646, it seems to work correctly with them. (Version of 2.30.1+ or 2.31.1+) Thanks in advance. Nonetheless, the possible fix(es) from bug #555899 may also change the behaviour, when one gets to it, but that's a question for an implementer of that bug.
err, damn, comment #14 was supposed to go to bug #555899, I'm sorry.
I'd be fine with INVALID due to comment 12, if somebody knows how to file bug reports against RFCs. :)
I do not know how to file bugs against RFCs, but maybe it's on purpose. the DATE might be treated as a floating time, that means it's the date in whichever timezone user views the event. If you want the timezone information, then set the event from 0:00 to 0:00 instead, then it'll cover "the day in the certain timezone. If you think an option to influence the behaviour of the "all day" flag would be helpful, then it can be added, it would only influence newly created events, though, as I'd not change already saved all-day events on edit.