Bug 204968 - regression: korganizer fails to save new calendar entry for whole day
Summary: regression: korganizer fails to save new calendar entry for whole day
Status: RESOLVED FIXED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: 4.3
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-24 13:00 UTC by Marc Schiffbauer
Modified: 2009-10-08 01:16 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Schiffbauer 2009-08-24 13:00:28 UTC
Version:            (using KDE 4.3.0)
OS:                Linux
Installed from:    Gentoo Packages

When I doubleclick free room in the top area of a day in the weekly view I can add a new event without time, so it is valid for the complete day. When doing it this way it works fine.

But sometimes there are events for the whole day already so there is no free room in the top area I can doubleclick, so I must use another way of adding the new event:

Then I 
* mark some time in this particular day, so that the dialog for adding an event 
  opens automatically (This a a configuration setting I have enabled).
* I enter the Summary information
* I disable the "time associated" field so the event is floating
* I click OK and choose the calendar to add it to (The default one in this case)

-> This does NOT work (anymore!)! The new event is NOT there. It will just not be saved anywhere. This is reproducable.
Comment 1 Marc Schiffbauer 2009-08-24 13:07:27 UTC
Update:

The new events DO show up! But only after some time (I closed kontact and started korganizer to switch app language etc... and now after some time all my events are there now, so this seems some update- or display-bug somewhere or something.

The calendar I try to add the event to is in an IMAP folder (dimap) (on a kolab server)
Comment 2 Allen Winter 2009-10-08 01:16:16 UTC
yes, this is a display bug.  Should be fixed in KDE 4.3.2.