Version: (using KDE KDE 3.2.2) Installed from: RedHat RPMs Compiler: gcc 3.3.3 OS: Linux On the first time that korganizer is started with a remote file (accessed via ssh -- using the fish protocol) as the default calendar, two problems occur: * The load file dialog appears twice, and the file appears to be being copied twice. * The file copy sometimes fails, and the file is not copied, instead the one from the cache is used. This only occurs on the first load of korganizer after logging in. On second and subsequent loads this problem does not occur.
On Tuesday, 27. July 2004 16:38, Del wrote: > On the first time that korganizer is started with a remote file (accessed > via ssh -- using the fish protocol) as the default calendar, two problems > occur: Yes, but it's not really korganizer loading the file twice. KOrganizer has a little helper program (korgac) for the alarms, which is started together with korganizer if it hasn't been running already. Since this helper app also needs the calendar data, it will just load the standard calendar, and thus thus the fish file is loaded twice, once by korganizer and once by korgac. That also explains why on subsequent restarts of korganizer the file is only loaded once, because korgac (the systray icon!) stays running, so it doesn't need to load the calendar again, it's already done that. Cheers, Reinhold PS: Of course, it would be nice if we could share the calendar data across the different applications accessing the data (i.e. korganizer, korgac, kpilot condui). -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBBmvHTqjEwhXvPN0RAnvXAJ46N/96plnEPPRrSAae8jjHngmoYQCguE7u nPNJc+ZNJaGg/BzQEhsXYTM= =wbTT -----END PGP SIGNATURE-----
This bug causes (a) regular loss of recent calendar events (as the file is not correctly loaded from the server), and (b) periodic loss of all calendar events (as the two fish/korgac/whatever processes both try to overwrite the same file simultaneously, ending up with an empty file). The priority should be changed to reflect the fact that this bug causes data loss.
Reassigning all KOrganizer bug reports and wishes to the newly created korganizer-devel mailing list.
This bug seems not to be a problem anymore using current KDE 4 implementation.