Bug 111420 - retrieving free busy lists from shared folder
Summary: retrieving free busy lists from shared folder
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: 3.3.2
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-24 14:36 UTC by Martin Koehn
Modified: 2017-01-07 22:09 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Koehn 2005-08-24 14:36:15 UTC 
Version:           3.3.2 (using KDE KDE 3.3.2)
Installed from:    Compiled From Sources
Compiler:          gcc 3.2 
OS:                Linux

Hi,

we have a shared folder in which all free-busy lists shall be stored. The path for retrieving free/busy-Lists in Korganizer is set to file://<localpath>/. KOrganizer either trys to use smb for reading the list if a server is set or assumes the URL to be invalid.

The reason seems to be that in FreeBusyManager::freeBusyUrl( ... ) it is assumed that the URL always must have a host name and that this hostname must be at least a part of the email adress. (The reason for the latter is absolutely not clear to me.)

A workaround is to manually generate the freebusyurl-File, nut this should not be the final solution, right?

Best regards,
Martin Köhn
Comment 1 Martin Koehn 2005-08-31 09:09:47 UTC 
Hi,

as extension: i also checked the latest version from the cvs (freebusymanager.cpp/.h). The problems should be the same as there are no changes in the relevant parts of the file.

Regards,
Martin Köhn
Comment 2 Reinhold Kainhofer 2006-11-02 19:32:55 UTC 
Reassigning all KOrganizer bug reports and wishes to the newly created 
korganizer-devel mailing list.
Comment 3 Denis Kurz 2016-09-24 18:47:33 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 4 Denis Kurz 2017-01-07 22:09:38 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.