Bug 170050 - start and end date are mixed up in "edit history"
Summary: start and end date are mixed up in "edit history"
Status: RESOLVED WORKSFORME
Alias: None
Product: ktimetracker
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Thorsten Staerk
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-29 18:45 UTC by Thomas Jarosch
Modified: 2008-12-23 14:50 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
test case according to what you said (643 bytes, text/calendar)
2008-12-23 14:49 UTC, Thorsten Staerk 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Jarosch 2008-08-29 18:45:48 UTC 
Version:           4.0.0 (using 4.1.00 (KDE 4.1.0), 4.1.0-5.fc9 Fedora)
Compiler:          gcc
OS:                Linux (i686) release 2.6.25.14-108.fc9.i686

Hello,

looks like the start and end time in "edit history" of ktimetracker are somehow mixed up, using KDE 4.1.0, the end time is always before the start time :-)

Screenshot of the issue can be found here:
http://bugs.kde.org/attachment.cgi?id=27132

Thomas
Comment 1 Thorsten Staerk 2008-08-30 09:49:48 UTC 
first step to analyze this is to see if the time stamps in the iCal file correspond to these data. Can you do this or attach the iCal file?
Comment 2 Thomas Jarosch 2008-08-31 12:20:19 UTC 
It seems to only affect data imported from karm, newly tracked time for the same task shows correctly.

Consider this event:
BEGIN:VEVENT
DTSTAMP:20080830T144702Z
X-KDE-karm-duration:407
CREATED:20080601T122730Z
UID:libkcal-1130402401.835
LAST-MODIFIED:20080601T122730Z
SUMMARY:irgendwas
CATEGORIES:KArm
RELATED-TO:libkcal-186136581.392
DTSTART:20080601T122042Z
DTEND:20080601T122729Z
TRANSP:OPAQUE
END:VEVENT

It is shown as:
Startdate 2008-06-01 14:20:42
EndDate 2008-06-01 12:27:29

Feels like the timezone calculation during upgrade is messed up??
Comment 3 Thorsten Staerk 2008-08-31 20:01:54 UTC 
Waaah! Yes, the timezone, I forgot this. Clearly a bug. Feel free to look into it, I might be able to next weekend.
Comment 4 Thorsten Staerk 2008-12-23 14:49:33 UTC 
Created attachment 29579 [details]
test case according to what you said
Comment 5 Thorsten Staerk 2008-12-23 14:50:20 UTC 
The attached file is made according to your description. I can verify start and enddate do NOT get mixed up with it.