Changing a recurring event does not work as expected. When I drag the edge of the event in the calendar view to change the time span, I'm asked - as expected - if this should be applied to all events or only current one. If I click any of these answers nothing is changed. If I alternatively enter the "edit mode" I can change the event and apply these changes, but don't get offered to apply these changes to only the current event. Just can apply the changes to all events. Reproducible: Always Steps to Reproduce: 1. create a DAV calendar resource 2. create a recurring event 3. change it by pulling the edges 4. apply the changes 5. change it by entering the edit mode 6. apply the changes Actual Results: Nothing happens or changes are applied to all events respectively. Expected Results: It always should be offered to apply the changes only to current event and these changes also should be applied to the current event. On my system I'm running: Plasma 5.7.2 Applications 16.04.3 Qt 5.7.0
I'm seeing the same problem, using Radicale as my CalDAV server. I can create a recurring event and it appears as a new .ics file in the server database. I can drag an item (the first item in my test) to a new date, and select "Only this item" in the resulting popup. It appears to work; the korganizer display shows that one item moved to the new date. Refreshing the containing folder has no new effect -the moved item is where I moved it to, the others remain where they were. However: 1) the ,ics file on the Radicale server is untouched 2) if I exit korganizer and restart it, the moved item reverts to its original date. There are no messages on the console from korganizer, and there are no messages in the Radicale server log. It looks like the change never got propogated to Radicale. I'm using Gentoo linux, KDE Frameworks 5.54.0 Qt 5.11.3 (built against 5.11.3) The xcb windowing system korganizer 5.10.3
I also have problems with recurring events, that I believe may have the same root cause as this issue. When editing the title of a single event in a recurring series in a different application (Thunderbird, SOGo, whatever), I'm able to make changes to a single event in that series, so that a each single event in a recurring series can have a unique title. However, when I open this same calendar in Korganizer, the changes made to the individual events in a series are not shown, and instead all events show their original title and no changes to individual events are shown.
(In reply to Aaron Burnett from comment #2) > I also have problems with recurring events, that I believe may have the same > root cause as this issue. > > When editing the title of a single event in a recurring series in a > different application (Thunderbird, SOGo, whatever), I'm able to make > changes to a single event in that series, so that a each single event in a > recurring series can have a unique title. However, when I open this same > calendar in Korganizer, the changes made to the individual events in a > series are not shown, and instead all events show their original title and > no changes to individual events are shown. Oh...and my system: Gentoo Linux KDE Frameworks 5.115.0 Qt 5.15.12 Korganizer 5.24.5 (23.08.5)
(In reply to Aaron Burnett from comment #3) > (In reply to Aaron Burnett from comment #2) > > I also have problems with recurring events, that I believe may have the same > > root cause as this issue. > > > > When editing the title of a single event in a recurring series in a > > different application (Thunderbird, SOGo, whatever), I'm able to make > > changes to a single event in that series, so that a each single event in a > > recurring series can have a unique title. However, when I open this same > > calendar in Korganizer, the changes made to the individual events in a > > series are not shown, and instead all events show their original title and > > no changes to individual events are shown. > > Oh...and my system: > > Gentoo Linux > KDE Frameworks 5.115.0 > Qt 5.15.12 > Korganizer 5.24.5 (23.08.5) Actually, I may need to retract this. It seems like it eventually started working after a delay. I will test this more and report back if I can make it break consistently.
Aaron, I wouldn't hold your breath - note the dates on this bug... The KDE developers have bigger, or more fun, fish to fry - AFAICT to do with Wayland and Qt6 Actually, I think it's been working OK for me over the past few years.