Summary: | KOrganizer's FreeBusy export adds some FREEBUSY elements that span the whole period | ||
---|---|---|---|
Product: | [Applications] korganizer | Reporter: | Reinhold Kainhofer <reinhold> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | andreas.knuepfer, bug+kde, glua, jerome.pouiller, karsten.elfenbein, smartins |
Priority: | NOR | ||
Version: | 4.2.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
Sample output of KOrganizer's F/B export, highlighting several wrong FREEBUSY props
an other broken publish of freebusy information KOrganizer freebusy report |
Description
Reinhold Kainhofer
2009-02-17 12:55:28 UTC
Created attachment 31399 [details]
Sample output of KOrganizer's F/B export, highlighting several wrong FREEBUSY props
Can you still reproduce this? I went to Schedule->Mail Free busy... and everything was ok, with KDE 4.2.3 Created attachment 37573 [details]
an other broken publish of freebusy information
this is from kde 4.3.1
I'm afraid I have the same strange behavior with KOrganizer Version 4.3.2 on Kubuntu 9.10. An example is attached below where the first 20 FREEBUSY lines are wrong ones. Created attachment 39201 [details]
KOrganizer freebusy report
freebusy report where the first 20 freebusy lines span over the whole report period by mistake
I see the same problem with Korganizer version 4.4.5 on OpenSuSE 11.3. I got it. Bug appears when you have recurrent event in your calendar. Korganizer whole period of recurrence as busy. To be more exact, Korganizer export recurrent event two times. One is busy period indeed. The other one is the whole period of recurrence of event. This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input. |