Version: 3.5.5 (using KDE 3.5.5, Kubuntu (edgy) 4:3.5.5-0ubuntu3) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.17-10-386 I have my schoolroster in Kalendar. When i change a class, which recurrs every week, from monday to wednesday by dragging it there. It moves the one event im dragging, ask me if i want to move only this one or all. When i click to move all of the affected events it just alters the time and not the day. So the event i drag gets moved fine. But the events in the next weeks keep showing on monday with the time of wednesday. When i look at the properties of the event the date is set at wednesday but it shows still on monday. I tried restarting the app but that didnt help. Also i tried it with other events offcoarse. Since my entire schoolroster changed. But it happens on all days with all events. This is kinda annoying because i cannot move around classes easily now. When i change a event to a different time on the same day it just works fine.
Confirmed in KDE4, I did not have this problem in KDE3. In KDE4, when dragging a recurring event (and selecting all occurrences) from one day/time to another day/time, only the time is changed, not the day. In my case, as opposed to the OP, even the first even does not have it's day changed. There is no difference when trying events in the past or in the future. Recurring all-day events are also affected. That is, I cannot change the date on which they occur. Non-recurring events are handled fine, that is, the time and date are changed as expected.
Looks like a DUP of 172464, except the fact that the first event is actually moved. On my tests no event is moved.
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 korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
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.