646806 - A bug with displaying meetings and meeting requests

Status: RESOLVED INCOMPLETE

(Calendar :: General, defect)

Description

[Adi Spivak]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Ubuntu/10.10 Chromium/10.0.648.133 Chrome/10.0.648.133 Safari/534.16
Build Identifier: 1.0b2

Today is march 31th, tomorrow on april 1st ar 2 am israel daylight saving time goes into affect and the clocks will move 1 hour ahead (it will be 3am instead of 2am).
all meetings in the calendar after today appears as if they are 1 hour to early then they should be. this is not represented in our zimbra server web interface.
however, this, i believe is the smaller issue.
a meeting request sent today for the 5th, display an error in thunderbird saying "this message contains an event that this version of lightning cannot process" although they were sent from the same lightning+thunderbird version.
this error appears both on my linux and windows.
if i save the ICS file and try to manually import it to my calendar, lightning freezes and will not change the display (will stay on the same date view even when you change it), however, this behaviur is only restricted to my linux machine, as my windows machine imported the event perfectly.



Reproducible: Always

Steps to Reproduce:
1.send a meeting request 
2.
3.
Actual Results:  
error: this message contains an event that this version of lightning cannot process

Expected Results:  
add to calendar button

Comment 1

[Stefan Sitter [:ssitter]]

What timezone do you use? Could the display problem be related to Bug 504299?

Please check Tools > Error Console when opening the event invitation. Maybe Lightning reported some warning or error messages.

On any kind of import problem Lightning will freeze/hang itself, i.e. the views will not update anymore. This is a known issue. Only workaround is restarting Thunderbird.

Comment 2

[Adi Spivak]

there is no errors on the error console. 
there are some no updates found warnings but no errors at all.

Comment 3

[Martin Schröder [:mschroeder]]

The bug reporter is gone and no information was given that could help to reproduce the issue now.