Wrong date day icon display and one day before events day in month view

[MK]

All day events display one day too early in month view.

Create an all day event on 27th March 2015, move month view and the dot is against 26th March. Can be corrected by changing all day event to span 27th to 28th March but now event displays over two days on day view. Icon displays wrong date: next day date

[Kunal Parmar (pkunal-parmar)]

i tested and confirmed the behavior, seems issue related to EDS

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Merlijn Sebrechts (merlijn-sebrechts)]

This only happens after creating an event yourself. The google calendar all-day events show on the correct date.

[MK (milan-korecky)]

Thanks for info. BR. Milan

----- Původní zpráva -----
Od:"Merlijn Sebrechts" <email address hidden>
Odesláno:‎13. ‎5. ‎2015 11:31
Komu:"<email address hidden>" <email address hidden>
Předmět:[Bug 1437305] Re: Wrong date day icon display and one day beforeevents day in month view

This only happens after creating an event yourself. The google calendar
all-day events show on the correct date.

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1437305

Title:
  Wrong date day icon display and one day before events day in month
  view

Status in Calendar application for Ubuntu devices:
  Confirmed
Status in qtorganizer5-eds package in Ubuntu:
  Confirmed

Bug description:
  All day events display one day too early in month view.

  Create an all day event on 27th March 2015, move month view and the
  dot is against 26th March. Can be corrected by changing all day event
  to span 27th to 28th March but now event displays over two days on day
  view. Icon displays wrong date: next day date

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1437305/+subscriptions

[Alexander Dobetsberger (masternoob)]

> This only happens after creating an event yourself. The google calendar all-day events show on the correct date.

Synced google calendar events are displayed correctly in month view but wrong in week view on my phone.

[Renato Araujo Oliveira Filho (renatofilho)]

I can not reproduce it using the C++ library on my unit tests.

Looking at the saved event I noticed some problems.

This is an event saved by calendar app:

BEGIN:VEVENT
UID:20150611T123231Z-4234-1000-4111-1@rento-ubuntu
DTSTAMP:20150611T123231Z
DTSTART;VALUE=DATE:20150611
DTEND;VALUE=DATE:20150611
X-LIC-ERROR;X-LIC-ERRORTYPE=VALUE-PARSE-ERROR:Can't parse as RECUR value
 in RRULE property. Removing entire property: ERROR: No Value
SUMMARY:new all day 11
CREATED:20150611T123231Z
LAST-MODIFIED:20150611T123231Z
BEGIN:VALARM
X-EVOLUTION-ALARM-UID:20150611T123231Z-4234-1000-4111-2@rento-ubuntu
ACTION:AUDIO
TRIGGER;VALUE=DURATION;RELATED=START:-PT15M
END:VALARM
BEGIN:VALARM
X-EVOLUTION-ALARM-UID:20150611T123231Z-4234-1000-4111-3@rento-ubuntu
ACTION:DISPLAY
TRIGGER;VALUE=DURATION;RELATED=START:-PT15M
END:VALARM
END:VEVENT

This is an event saved by my unit test:

BEGIN:VEVENT
UID:20150610T194020Z-24821-1000-2179-64@rento-ubuntu
DTSTAMP:20150606T161617Z
DTSTART;VALUE=DATE:20150610
DTEND;VALUE=DATE:20150611
TRANSP:TRANSPARENT
SEQUENCE:2
SUMMARY:ALLDAY
CLASS:PUBLIC
CREATED:20150610T194029Z
LAST-MODIFIED:20150610T194029Z
END:VEVENT

There is two main differences:

1 - the end date in the event saved by the calendar event is the same as start date (I believe we should use the next day date as end date)

2 - The recurrence value is broken (please check if you are trying to set any recurrence value while saving the event)

[Ubuntu Phone Apps Jenkins Bot (ubuntu-phone-apps-jenkins-bot)]

Fix committed into lp:ubuntu-calendar-app at revision 671, scheduled for release in ubuntu-calendar-app, milestone rtm14

[Phil UK (tr7man)]

I have just performed an update of this calendar app with the latest update sent out today and this appears to of resolved the issue of the double dots. I have performed a sync and the dots have not returned. I can only take it that this issue has been resolved, thanks to the hard work of the app development team. Cheers guys.