Last Comment Bug 353307 - UTC allday events sometimes shown in wrong day in agenda
: UTC allday events sometimes shown in wrong day in agenda
Status: RESOLVED DUPLICATE of bug 365034
: dataloss
Product: Calendar
Classification: Client Software
Component: Lightning Only (show other bugs)
: Trunk
: All All
: -- normal (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
:
:
Mentors:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-09-19 04:00 PDT by Sebastian Schwieger
Modified: 2007-05-15 06:36 PDT (History)
0 users
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---


Attachments

Description Sebastian Schwieger 2006-09-19 04:00:36 PDT
I had some allday events in my calendar that don't contain timezone information in DTSTART and DTEND. Those are still shown correctly in the views but are wrong in agenda tree (todays event is shown for tomorrow).

Steps to reproduce:
1. import or create allday event that is stated in UTC format(see example below) or Europe/London 
2. change your timezone to Europe/Berlin
3. restart

Result: allday event is correct in the views (19.09.) but wrong in the agenda tree (Tomorrow)

Example:

BEGIN:VEVENT
CREATED:20060126T152941Z
LAST-MODIFIED:20060126T152941Z
DTSTAMP:20060126T152941Z
UID:uuid1127806490852
SUMMARY:Hausdienst
CLASS:PUBLIC
DTSTART;VALUE=DATE:20060224
DTEND;VALUE=DATE:20060225
PERCENT-COMPLETE:0
X-LIC-ERROR;X-LIC-ERRORTYPE=VALUE-PARSE-ERROR:No value for STATUS 
 property. Removing entire property:
CATEGORIES:Business
END:VEVENT

using Thunderbird2.0a and Lightning 2006091606 (WindowsXP)
Comment 1 Sebastian Schwieger 2006-09-19 04:23:49 PDT
Sorry for confusion: the above example is actually not the one for 19.09. the correct example is following. Additionally, I would like to mention that this event has been created with Sunbird0.3a. So this is an upgrade issue.

BEGIN:VEVENT
CREATED:20060426T072000Z
LAST-MODIFIED:20060426T072009Z
DTSTAMP:20060426T072008Z
UID:uuid1146036009010
SUMMARY:Hausdienst
PRIORITY:0
CLASS:PUBLIC
DTSTART;VALUE=DATE:20060919
DTEND;VALUE=DATE:20060920
END:VEVENT
Comment 2 Dan Mosedale (:dmose) 2006-09-22 18:20:52 PDT
This could cause someone to miss an event, so we should at least consider making it block.
Comment 3 Dan Mosedale (:dmose) 2006-09-28 15:18:15 PDT
Too late in the cycle to block; marking as blocking0.3-.
Comment 4 Stefan Sitter 2006-09-30 11:05:35 PDT
Confirmed per Bug 354946 Comment #2.
Comment 5 Martin Schröder [:mschroeder] 2007-01-26 12:35:04 PST
This is a duplicate of bug 365034, which has a patch attached.

*** This bug has been marked as a duplicate of bug 365034 ***

Note You need to log in before you can comment on or make changes to this bug.