[kronolith] Display problems with "all day" events

Wed Jan 16 15:54:46 UTC 2013

Hi,

my (shared) calendar contains multiple "all day" events, an example as  
stored in the Kolab back-end:

--- cute here ---
<?xml version=3D"1.0" encoding=3D"UTF-8"?>
<event version=3D"1.0">
    <uid>50f53316-4260-46d0-bb6a-40b4c0a86604</uid>
    <body></body>
    <categories></categories>
    <creation-date>2013-01-15T10:44:38Z</creation-date>
    <last-modification-date>2013-01-16T13:36:16Z</last-modification-date>
    <sensitivity>public</sensitivity>
    <product-id>Horde_Kolab_Format_Xml-2.0.2 (api version: 1)</product-id>
    <summary>au=C3=9Fer Haus</summary>
    <location>bei Hannover</location>
    <start-date>2013-01-18</start-date>
    <alarm>15</alarm>
    <horde-alarm-methods>a:0:{}</horde-alarm-methods>
    <show-time-as>busy</show-time-as>
    <end-date>2013-01-18</end-date>
    <attendee>
      <display-name>att1</display-name>
      <smtp-address>att1 at company.com</smtp-address>
      <status>none</status>
      <request-response>false</request-response>
      <role>required</role>
    </attendee>
    <attendee>
      <display-name>att2</display-name>
      <smtp-address>att2 at company.com</smtp-address>
      <status>none</status>
      <request-response>false</request-response>
      <role>required</role>
    </attendee>
</event>
--- cut here ---

In my kronolith calendar view (and portal summary), that entry is  
correctly displayed as an all-day event on Jan 18.
For another user, which has the same time zone configured in his user  
settings (Europe/Berlin), the event is displayed as starting on Jan  
18, 1 AM and ending Jan 19, 0:59 AM.

Where does this 1 hour shift come from? Hadn't it been the same time  
zone settings, it might have been explained by time zone offsets, but  
in this case?

Interestingly, another (multi-day all-day) event from the same  
calendar is displayed correctly both in my kronolith and that user's  
kronolith. Might it be that some variable is not initialized with  
every event read, leaving some old "hour value" behind when a full day  
event (just date, no time) is retrieved via the Kolab driver?

With regards,
Jens