Bug 236096

Summary: Publishing free/busy information does not work
Product: [Applications] korganizer Reporter: Sabine Faure <sabine>
Component: generalAssignee: Christian Mollekopf <mollekopf>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: faure, mollekopf
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Sabine Faure 2010-05-03 00:15:39 UTC
Version:            (using Devel)
Compiler:          gcc 4.3.2 
OS:                Linux
Installed from:    Compiled sources

As user 1:
- Launch Korg
- Go to Settings menu/Configure KOrganizer...
- Click on 'Free/Busy' icon and check the 'Puclish you free/busy information automatically' check box
- Click on 'Ok'
- Create a new event (Event A) for next Monday between 6:00 and 8:00 in a Kolab calendar

As user 2:
- Launch KOrg
- Go to Settings menu/Configure KOrganizer...
- Click on 'Free/Busy' icon and go to 'Retrieve' tab
- Check the two check boxes ('Retrieve other peiples'free/busy information automatically' and 'Use full email address for retrieval')
- Fill in the 'Server Information' details
- Check the 'Remember password' check box
- Click on 'Ok' 
- Create a new event (Event B) and go to the attendees tab to add user 1 as a new attendee

No red section is displayed for next Monday between 6:00 and 8:00 for user 1 whereas it should be. 

Note: I already tested the retrieve part with already existing event and it works so I am confident that this problem is due to the publish part.

Trunk, Svn Rev 1121836
Comment 1 David Faure 2010-05-03 00:46:11 UTC
kmail <= 4.4 had code in KMailICalIfaceImpl::triggerKolabFreeBusy which would trigger an update of the freebusy information on the (kolab 2) server: all that needs to be done is a KIO::get on https://$USER@$HOST/freebusy/trigger/$USER/$FOLDER.pfb
after uploading events into the imap folder $FOLDER (e.g. "Calendar/Public")
$USER is dfaure@kdab.com in my case (full email).

I suppose this has to be done by the akonadi kolab resource now?
Comment 2 Denis Kurz 2016-09-24 18:53:18 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 3 Denis Kurz 2017-01-07 22:17:11 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.