Summary: | Recurrent tasks disappear even though open-ended | ||
---|---|---|---|
Product: | [Applications] kontact | Reporter: | Graham P Davis <gpd> |
Component: | calendar | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | hacker |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Graham P Davis
2007-09-27 17:51:50 UTC
I am not quite sure, if this is the suitable place to add my description to, but as far as I found my way round the site, this is the most like it. Some recurrent events in the Kalendar have repeatedly disappeared spontanously and without any regularity or predictability, not always immediately in the normal display, but alwas in the printing preview of a week's timetable. There is no telling, which events will disappear, and it is not always the case, but two in three times at least. The recurring dates I am talking about are short spans of time on one day, repeated weekly with numerous exceptions in certain weeks. They are supposed to compose a more or less regular weekly work schedule with the same general routine every week and frequent exceptions in detail. There are about 30 such recurring dates in my schedule. Opening the events (they can be found again when you look at another week) it turns out that the dates have been changed. The original entry has of course got the same date in the "beginning" and "end" line and lasts about 45 minutes or so. The changed date has got a "beginning" close to the current date (but hardly ever the current date as such) while having kept the original date in the "end" line. Of course, the dates "end before they begin" then, and the programme is telling me that in ever the same amazement. Everything else is unchanged so things can be restored by inserting the original date again every time it happens. To do this, one has to remember the original entries, of course. - But then, this is exactly what a calendar should help you to avoid, isn't it... P.S.: My entries are not open ended, but end after something like ten months. So, as far as I can see, the open end cannot be the cause of the problem. This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months. Crikey, I'd forgotten I'd reported this problem. I'm sorry to say that I've no idea whether the problem still occurs as I switched to Lightning some years ago. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input. |