Summary: | accepted event is not shown in the calendar until korganizer is restarted. deleting event does nothing. | ||
---|---|---|---|
Product: | [Applications] korganizer | Reporter: | jpa <no_mayl> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | smartins |
Priority: | NOR | ||
Version: | 3.5 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
jpa
2006-02-02 19:32:23 UTC
found a non-ldap system. problem still there. After manually removing the event from the /home/jpabgrall/.kde/share/apps/korganizer/std.ics and restarting korganizer, the event was still there. Apparently cached in /home/jpabgrall/.kde/share/apps/korganizer/libkcal-1221210209.922 (one libkcal-* per broken event) deleting that file made the event go away. -- It would seem that the korganizer from 3.4 wold deal with a single file in ~/.kde/share/apps/korganizer/std.ics But the new korganizer picks up any file (including kdebug crash file if it exists in that dir causing korganizer to fail to load the local-dir calendar!). The new korganizer generates the libkcal-* files (1 per event)... I tried deleting the std.ics, re-importing it into a different location,... still got issues with deleting an event. Reassigning all KOrganizer bug reports and wishes to the newly created korganizer-devel mailing list. This is working since I remember now. |