[Korganizer-devel] [Bug 276148] korgac and korganizer discrepancy on times

[Stephen Dowdy]

https://bugs.kde.org/show_bug.cgi?id=276148





--- Comment #1 from Stephen Dowdy <sdowdy ucar edu>  2011-06-21 01:37:00 ---
(In reply to comment #0)

Okay, perhaps this is not as simple as i stated.

I am perhaps being confused by newly created and *imported*
'std.ics' entries.  and recurrence may be playing a part.

TZ= and reinit ktimezoned actually do not seem to correct
korgac behaviour and 'kquitapp korgac && korgac' may not
as well.

I think this is perhaps an "Import Calendar" failure.  I
imported my 'std.ics' from Debian Lenny (and Sarge and Etch)
into a clean Debian Squeeze install (new .kde subdir).

But, now that i look at that std.ics AND the records for it
in the new 'std.ics' file, i see that an event that has been
causing me grief is marked in Z-time (and it's recurrent)

I enabled all korganizer/korgac debugging in kdebugdialog, and:

sdowdy at zia$ grep korgac .xsession-errors 
...
korgac(15312)/kdecore (K*TimeZone*) KSystemTimeZonesPrivate::readConfig:
readConfig(): local zone= "US/Mountain"
korgac(15312)/kdecore (K*TimeZone*) KSystemTimeZonesPrivate::readZoneTab:
readZoneTab( "/usr/share/zoneinfo/zone.tab" )
...  (yay, that looks good)
korgac(15312)/kresources KRES::Resource::open: Opening resource "Default
Calendar"
korgac(15312)/kdepimlibs (kcal) KCal::ResourceCached::doOpen: Opening resource
"Default Calendar"
korgac(15312)/kdepimlibs (kcal) KCal::ICalFormat::load:
"/home/sdowdy/.kde/share/apps/korganizer/std.ics"
korgac(15312)/kdepimlibs (kcal) KCal::ICalTimeZoneSource::parse: VTIMEZONE
"US/Mountain"
korgac(15312)/kdepimlibs (kcal) KCal::ICalTimeZoneSource::parse: VTIMEZONE
"US/Mountain"
...  (that looks good)
korgac(15312) AlarmDialog::addIncidence: adding incidence CRIKEY"               
...
kwin(15244) KWin::Client::readUserTimeMapTimestamp: User timestamp, final: 'ID:
41943048 ;WMCLASS: "korgac" : "korgac" ;Caption: "Reminders ? KOrganizer
Reminder Daemon" ' : 628031733

korgac(15312)/kdepimlibs (kcal) KCal::Calendar::appendAlarms: "meeting" ':
"2011-06-20T23:00:00Z"
korgac(15312)/kdepimlibs (kcal) KCal::Calendar::appendAlarms: "CRIKEY" ':
"2011-06-20T17:00:00-06:00"
korgac(15312)/korgac (check) KOAlarmClient::checkAlarms: REMINDER: "meeting"
korgac(15312) AlarmDialog::addIncidence: adding incidence  "meeting"

--- This newly added record "CRIKEY" has TZID directives in the DT{START,END}
bits
BEGIN:VEVENT
DTSTAMP:20110620T224455Z
CREATED:20110620T222329Z
UID:KOrganizer-877547988.372
SEQUENCE:2
LAST-MODIFIED:20110620T224455Z
SUMMARY:CRIKEY
DTSTART;TZID=US/Mountain:20110620T173000
DTEND;TZID=US/Mountain:20110620T193000
TRANSP:OPAQUE
BEGIN:VALARM
DESCRIPTION:
ACTION:DISPLAY
TRIGGER;VALUE=DURATION:-PT30M
END:VALARM
END:VEVENT

This "meeting" event has no TZID, using "Zulu":

BEGIN:VEVENT
DTSTAMP:20110620T224455Z
ORGANIZER;CN="Stephen Dowdy":MAILTO:sdowdy at ucar.edu
CREATED:20110620T224422Z
UID:KOrganizer-1245739618.505
SEQUENCE:1
LAST-MODIFIED:20110620T224422Z
SUMMARY:meeting
DTSTART:20110620T233000Z
DTEND:20110621T003000Z
TRANSP:OPAQUE
BEGIN:VALARM
DESCRIPTION:
ACTION:DISPLAY
TRIGGER;VALUE=DURATION:-PT30M
END:VALARM
END:VEVENT

and it was derived from the following record with a Recurrence Rule (by moving
it
in the korganizer "week view" display 2.5 hours later, and using "This
Occurrence only")

BEGIN:VEVENT
DTSTAMP:20110620T224455Z
ORGANIZER;CN="Stephen Dowdy":MAILTO:sdowdy at ucar.edu
CREATED:20110215T204651Z
UID:libkcal-1486749757.556
SEQUENCE:1
LAST-MODIFIED:20110620T224422Z
SUMMARY:meeting
RRULE:FREQ=WEEKLY;BYDAY=MO
EXDATE;VALUE=DATE:20110620
DTSTART:20110214T220000Z
DTEND:20110214T230000Z
TRANSP:OPAQUE
BEGIN:VALARM
DESCRIPTION:
ACTION:DISPLAY
TRIGGER;VALUE=DURATION:-PT30M
END:VALARM
END:VEVENT


Grrr, but now i logged out, back in without TZ or reinit KTimezoneDaemon
and korgac is working properly for those two events today.  (it did not
when the RRULE record was left as-is, and triggered for 3PM incorrectly,
instead of 2PM as it should have.

This is frustrating, because previously, it would be one hour late.  (So,
i'm suspecting making that one occurrence change didn't affect DST,
and is why it's working, when the original recurring event didn't
work earlier today).

For the Single "meeting" Occurrence record:
sdowdy at zia$ date -d "2011-06-20 23:30:00 GMT"
Mon Jun 20 17:30:00 MDT 2011