Bug 281012 - the .ics file seems to be incorrect
Summary: the .ics file seems to be incorrect
Status: RESOLVED DUPLICATE of bug 206734
Alias: None
Product: ktimetracker
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: Thorsten Staerk
URL:
Keywords:
: 280930 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-08-29 18:56 UTC by Alex
Modified: 2011-09-29 11:52 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In: 4.8
Sentry Crash Report:


Attachments
produced ics (2.55 KB, text/calendar)
2011-09-28 19:52 UTC, Alex
Details
produced ics (without opening it with korganizer afterwards) (4.48 KB, text/calendar)
2011-09-28 19:55 UTC, Alex
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alex 2011-08-29 18:56:01 UTC
Version:           unspecified (using KDE 4.7.0) 
OS:                Linux

when opened in calendar apps (korganizer / thunderbird lightning), even short tasks (few minutes) are logged as 2 hours. 

In the .ics file is the COMMENT-field repeated a lot for some tasks.

i.e.:
BEGIN:VEVENT
CREATED:20110829T184135Z
COMMENT:sample
COMMENT:sample
COMMENT:sample
COMMENT:sample
X-KDE-ktimetracker-duration:3600
DTSTAMP:20110829T183550Z
UID:libkcal-497914265.915
LAST-MODIFIED:20110829T183512Z
SUMMARY:SPAM-Filter einrichten
CATEGORIES:KDE-Zeitplaner
RELATED-TO:libkcal-334290328.965
DTSTART:20110829T155839
DTEND:20110829T165839
TRANSP:OPAQUE
END:VEVENT

other events even have 33 times the title of the block (not the title of the task, but the title of the current time block).

I copy the description from bug 280930: 
i opened it in korganizer, now the Backup-Task is 2 hours from 2011-08-27 16:05
to 18:05.

A Task with 8 Minutes at 26.08. at evening is displayed as 11:56 - 14:03, which
is approximate +2 hours + +8 minutes.

Reproducible: Always

Steps to Reproduce:
-

Actual Results:  
-

Expected Results:  
-
Comment 1 Thorsten Staerk 2011-09-28 09:45:47 UTC
Here is how I understand your bug report

1. start with a fresh file (delete /home/user/.kde/share/apps/ktimetracker/ktimetracker.ics)
2. start ktimetracker
3. add a task A
4. start the timer for task A
5. after a second or so stop the timer for task A
6. quit ktimetracker
7. look at the ics file (/home/user/.kde/share/apps/ktimetracker/ktimetracker.ics)
8. find that there is exactly one VEVENT:
 # cat ktimetracker.ics | grep -i vevent
 BEGIN:VEVENT
 END:VEVENT
9. find that DTSTART and DTEND differ for more than just "a second or so"
Comment 2 Thorsten Staerk 2011-09-28 09:49:10 UTC
I cannot reproduce, here is what I get:

DTSTART;TZID=Europe/Berlin:20110928T114054
DTEND:20110928T114055Z

If the problem persists, please re-open this bug and add the information what distribution you are using, what version of kdepim, kdepimlibs and if the error persists for a fresh user.
Comment 3 Alex 2011-09-28 19:52:46 UTC
Created attachment 64044 [details]
produced ics
Comment 4 Alex 2011-09-28 19:55:16 UTC
Created attachment 64045 [details]
produced ics (without opening it with korganizer afterwards)
Comment 5 Alex 2011-09-28 19:57:44 UTC
I think it's still not working for me.

i did it until step 8.

Result for DTSTART/DTEND:

DTSTART;TZID=Europe/Berlin:20110928T214713
DTEND:20110928T214720Z

i copied the file and opened it in korganizer. Its now a task from 21:47 to 23:47.
The second attachment is the original which was never touched by korganizer


i think maybe the timezone info is missing from the DTEND line?

other stuff i noticed:
- what are the many RDATE lines about?
- timezones +1, +2 and +3 are mentioned. which is really used?
Comment 6 Alex 2011-09-28 20:00:43 UTC
Distribution: Arch
ktimetracker: 4.7.0
kde: 4.7.1
extra/kdepim-libkdepim 4.7.1-2
extra/kdepimlibs 4.7.1-1

what timezones are you testing in? Can you try with CEST or just with a few different timezones?
Comment 7 Thorsten Staerk 2011-09-29 04:14:47 UTC
I am in CEST, however yesterday I found the same bug reported two times by other people and fixed it. Thanks for awaking me with your report. Please test the latest code!

*** This bug has been marked as a duplicate of bug 206734 ***
Comment 8 Thorsten Staerk 2011-09-29 11:52:53 UTC
*** Bug 280930 has been marked as a duplicate of this bug. ***