Bug 121245 - accepted event is not shown in the calendar until korganizer is restarted. deleting event does nothing.
Summary: accepted event is not shown in the calendar until korganizer is restarted. de...
Status: RESOLVED WORKSFORME
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: 3.5
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-02 19:32 UTC by jpa
Modified: 2011-03-12 12:31 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 jpa 2006-02-02 19:32:23 UTC 
Version:           3.5 (using KDE 3.5.0-4.2.el3.kde, )
Compiler:          gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-53)
OS:                Linux (x86_64) release 2.4.21-37.ELsmp

Upon receiving an event from another kontact (also on kde3.5),
accepting the event in the mail does not cause the event to show up in the calendar.
Restarting kontact/korganizer will then show the newly accepted event.

Event deletion  (r-click, delete) does not delete the event, not even in the 
/home/jpabgrall/.kde/share/apps/korganizer/std.ics
so restarting korganizer does not help for deletion.

Receiving a confirmation (accept or decline) and "adding" it to the calendar does not show up until korganizer is restarted.

* Some extra environment info:
 - the ~/.kde is from a kde3.4 (could there be some config migration issue?)
 - the machine is running ldap and korganizer complains about 
    "No such map passwd.byname. Reason: No such map in server's domain"
--
jpa
Comment 1 jpa 2006-02-02 20:03:51 UTC 
found a non-ldap system. problem still there.
Comment 2 jpa 2006-02-02 20:24:20 UTC 
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.
--
Comment 3 jpa 2006-02-02 23:23:07 UTC 
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.
Comment 4 Reinhold Kainhofer 2006-11-02 19:30:12 UTC 
Reassigning all KOrganizer bug reports and wishes to the newly created 
korganizer-devel mailing list.
Comment 5 Sergio Martins 2011-03-12 12:31:30 UTC 
This is working since I remember now.