Bug 184622 - KOrganizer's FreeBusy export adds some FREEBUSY elements that span the whole period
Summary: KOrganizer's FreeBusy export adds some FREEBUSY elements that span the whole ...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: 4.2.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-17 12:55 UTC by Reinhold Kainhofer
Modified: 2017-01-07 22:17 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Sample output of KOrganizer's F/B export, highlighting several wrong FREEBUSY props (8.89 KB, text/calendar)
2009-02-17 12:57 UTC, Reinhold Kainhofer 		Details
an other broken publish of freebusy information (809 bytes, application/octet-stream)
2009-10-14 11:20 UTC, Karsten 		Details
KOrganizer freebusy report (1.63 KB, text/plain)
2009-12-21 09:10 UTC, Andreas Knüpfer 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Reinhold Kainhofer 2009-02-17 12:55:28 UTC 
Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    Ubuntu Packages

KOrganizer's F/B export is broken: 
It always adds tons (currently 66) entries like FREEBUSY:20090217T105239Z/20090617T105239Z at the beginning of the F/B data. These span the whole F/B interval and thus make the F/B totally useless, since all the time will be marked busy.

My calendar does not have any corresponding events that span the whole (4-month) period, but still the F/B object contains FREEBUSY props that span the whole period. For example:

DTSTART:20090217T114331Z
DTEND:20090617T114331Z
FREEBUSY:20090217T114331Z/20090617T114331Z
FREEBUSY:20090217T114331Z/20090617T114331Z
FREEBUSY:20090217T114331Z/20090617T114331Z
FREEBUSY:20090217T114331Z/20090617T114331Z
FREEBUSY:20090217T114331Z/20090617T114331Z
FREEBUSY:20090217T114331Z/20090617T114331Z
[...]
Comment 1 Reinhold Kainhofer 2009-02-17 12:57:07 UTC 
Created attachment 31399 [details]
Sample output of KOrganizer's F/B export, highlighting several wrong FREEBUSY props
Comment 2 Sergio Martins 2009-05-13 10:12:46 UTC 
Can you still reproduce this?

I went to Schedule->Mail Free busy... and everything was ok, with KDE 4.2.3
Comment 3 Karsten 2009-10-14 11:20:35 UTC 
Created attachment 37573 [details]
an other broken publish of freebusy information

this is from kde 4.3.1
Comment 4 Andreas Knüpfer 2009-12-21 09:07:16 UTC 
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.
Comment 5 Andreas Knüpfer 2009-12-21 09:10:46 UTC 
Created attachment 39201 [details]
KOrganizer freebusy report

freebusy report where the first 20 freebusy lines span over the whole report period by mistake
Comment 6 Schelte Bron 2010-08-04 22:03:20 UTC 
I see the same problem with Korganizer version 4.4.5 on OpenSuSE 11.3.
Comment 7 Jerôme Pouiller 2011-01-28 12:02:50 UTC 
I got it.

Bug appears when you have recurrent event in your calendar. Korganizer whole period of recurrence as busy.
Comment 8 Jerôme Pouiller 2011-01-28 12:12:43 UTC 
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.
Comment 9 Denis Kurz 2016-09-24 18:44:36 UTC 
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.
Comment 10 Denis Kurz 2017-01-07 22:17:52 UTC 
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.