Korganizer: Cannot select resource for new events

[Christian Schürer-Waldheim]

Binary package hint: kdepim

1.) Description: Ubuntu karmic (development branch), Release: 9.10
2.) Installed version: korganizer 4:4.3.1-0ubuntu1

In Kontact/Korganizer, I have several calendars (local ics resources via akonadi). I was used to being asked to which resource I want to add a new event. This is not done now any more - new events are always added to one calendar resource. This makes using different resources for different purposes useless.

[Alvin (alvind)]

Confirmed. (This is also the case in older vrsions of (K)ubuntu).
Could it be that the resources take alphabetical priority? I can no longer add new events to an akonadi_ical_resource_x. Everything is added to akonadi_gcal_resource_x.

[Alvin (alvind)]

Probably very closely related:
When changing an event in akonadi_ical_resource_x, the event is *moved* to akonadi_gcal_resource_x.
Should this be filed as a separate bug?

[Christian Schürer-Waldheim (quincunx)]

I've somehow "solved" this bug by accident. It's probably a feature that you can select an akonadi resource as default. This feature seems to be new and any random resource got default when it was introduced for the first time. If a default resource is selected, any new event (or note etc.) is added to this one without confirmation. This feature might be good meant, but if I can't change the resource for an event any more, it doesn't really help much.

You can deselect the default resource in akonadi - just click on the root akonadi entry in kontatc's calendar resources view and select "edit". Then you will see the available resources and can deselect the one which is set as default. After you have done that, kontact will ask you again which resource to use when you create a new event.

[Christian Schürer-Waldheim (quincunx)]

It seems as if Kontact in KDE SC 4.4 finally has the possibility to copy/move entries from one resource to another. But nevertheless one resource shouldn't silently be the default place for new entries.

[Harald Sitter (apachelogger)]

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!