GNOME Bugzilla – Bug 555899
Recurring appointments cannot be all day
Last modified: 2010-06-10 05:44:05 UTC
Please describe the problem: When creating an all day appointment, if you flag it as "recurring", it undoes the "all-day" aspect of it and sets beginning and end times of "00:00". Steps to reproduce: 1. Open the "create new appointment" dialog. Provide any name you like. 2. Click the "All Day Event" button and save the appointment. 3. View the events in "List" format and observe there is a date for the appointment, but no time. 4. Double-click on the event to open it. 5. Click the "Recurrence" button. 6. Check the "This appointment recurs" checkbox and increase the number of occurrences to 2. 7. Click save. Actual results: The appointment now has a time as well as a date. Expected results: The appointment should still only list the date. Does this happen every time? Yes Other information: The events still appear as all day events in the day view. Also, change to the start/end times of recurring all day events is discarded.
I can confirm this behaviour. When editing, the 'all-day' property is lost. This is especially when setting birthday reminders.
Confirming on actual master (~2.30.0), still there.
*** Bug 613864 has been marked as a duplicate of this bug. ***
*** Bug 614090 has been marked as a duplicate of this bug. ***
Note that this is against bug #352801, though from my point of view, if the time matches user's timezone, then there is no need to show start and end time it a day view, it's midnight anyway, thus show it as an all day event. It'll not change the editing dialog, somehow.
Please try with fixes from bug #611646, it seems to work correctly with them. (Version 2.30.1+ or 2.31.1+) Thanks in advance. Nonetheless, the possible fix(es) from bug #352801 may also change the behaviour, when one gets to it, but that's a question for an implementer of that bug.
Looks like all day events still have problem. I have configured a webcal of GNOME3 schedule {webcal://www.gnome.org/start/unstable/schedule.ics} but events are shown on next day in compare to actual date with wrong timings. For example, GNOME 2.31.1 tarball is due on May 3 but event is shown at May 4 and duration is shown as 4:30 am to 5:29 am.
It's correct. > DTSTART:20100503T230000Z > DTEND:20100503T235959Z Even this is "almost" the whole day event (note the DTEND is not inclusive, thus this ends just one second before the midnight), then the times are specified in UTC, thus they are shifted to your timezone, and it ends the same time all around the world. Being specified only with the date, then they would be a real whole day event, being the same day, but different time around the world.