Bug 331157

Summary:	upload free busy information does nothing on network
Product:	[Applications] korganizer	Reporter:	Johannes Vogel <kde>
Component:	general	Assignee:	kdepim bugs <pim-bugs-null>
Status:	RESOLVED UNMAINTAINED
Severity:	major	CC:	nine
Priority:	NOR
Version First Reported In:	4.11.3
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Johannes Vogel 2014-02-15 14:23:19 UTC

watching the traffic with Wireshark shows no traffic
http://myserver/freebusy.php writes get_defined_vars() to a /tmp/file for debugging. the file wouldn't create either.

Reproducible: Always

Steps to Reproduce:
1. Schedule -> Upload Free Busy Information brings an error "please fill in.."
2. Configure a URL in configuration panel (http://myserver/freebusy.php)
3. Schedule -> Upload Free Busy Information brings nothing


Actual Results:  
nothing happens

Expected Results:  
Some traffic on the network interface (looking by sniffer) and some PUT data on the server.

Comment 1 nine 2014-10-30 11:38:26 UTC

I can confirm this bug on version 4.14.2 (using openSUSE packages).

I added a Server URL like this webdavs://www.companyname.example/calendar in the settings and filled in the Username and Password fields. Clicking "Schedule/Upload Free Busy Information" does not seem to do anything. Server logs do not record any communication attempts and tcpdump shows no traffic at all.

I've read that with a Kolab groupware server, one does not need the publish free/busy information feature as it's integrated there. I do use a Kolab Groupware Server (legacy) resource for storing my calendar data in my IMAP account. However I do not have a Kolab server. Could it be that korganizer thinks that since I do use a Kolab Groupware Server resource, it does not need to publish free/busy information? That would be a simple but wrong assumption.

Comment 2 Denis Kurz 2017-06-23 19:56:18 UTC

This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.

Comment 3 Denis Kurz 2018-01-31 17:14:36 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.