Version: (using KDE Devel) Installed from: Compiled sources Compiler: gcc version 3.4.3 (Mandrakelinux 10.2 3.4.3-7mdk) OS: Linux Not sure if this is a bug or a wish, but here it goes: When creating a new remote file resource, if the user has write access to the folder, uncheck the read only check box and type a valid file name for the new calendar file, the resource will be created, but will complain that the file does not exist. The correct solution, in my opinion, is either create the file, or not accept the creation of the resource, asking for an existing file. To create the resource and not be able to use it seems to me a bug. Creating the file would be preferred for a writable resource, but for a read only resource, a check if the file exist would be nice.
That hit me too... (I simply ssh'd to the machine and touched the file, but I conveniently forgot that it was actually a bug in koreganizer ;-) Reinhold
Yes, that is exactly what I did...
Reassigning all KOrganizer bug reports and wishes to the newly created korganizer-devel mailing list.
Dear reporter, the resources handling got redone for KF5 and KF6 based PIM applications. If you still encounter the issues you had in the past, please report them to the current maintained and updated PIM applications you use Thanks a lot!