Summary: | Applying two changes in a row in the event editor fails with "Only resources can modify remote identifiers" | ||
---|---|---|---|
Product: | [Applications] korganizer | Reporter: | Rickard Westman <rwestman> |
Component: | incidence editors | Assignee: | David Faure <faure> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | faure, sander |
Priority: | NOR | ||
Version: | 5.7.3 | ||
Target Milestone: | --- | ||
Platform: | Kubuntu | ||
OS: | Linux | ||
Latest Commit: | https://commits.kde.org/incidenceeditor/7ba473fef78978aee6cdda0cdcead3fa65d3c62b | Version Fixed In: | |
Sentry Crash Report: | |||
Attachments: | untested incidenceeditor fetchscope patch |
Description
Rickard Westman
2019-05-26 20:03:06 UTC
> You then have to cancel out of the dialog to exit it.
That came out wrong - I meant that you have to cancel out of the editor since pressing "OK" (re-)triggers the problem.
*** Bug 408898 has been marked as a duplicate of this bug. *** I think I fixed this in https://phabricator.kde.org/D16917 which landed in akonadi commit fbcd065c0dbb, part of tag v18.11.90, i.e. the Applications 18.12 release. (This report comes from KOrganizer 5.7.3 which Applications/17.12.3.) I'm just not 100% sure it's fully fixed though, because I had that error message on 03-Jan-2020. But today I can't reproduce it, no matter what I try (with or without the resource running, etc). Puzzling... Nowadays, if I could find a way to reproduce this error, I would try itemFetchScope().setFetchRemoteIdentification(false); like I did in FatCRM. Hmm maybe one solution is to revert the D16917 patch to trigger the error more easily... Created attachment 127267 [details]
untested incidenceeditor fetchscope patch
Git commit 7ba473fef78978aee6cdda0cdcead3fa65d3c62b by David Faure. Committed on 11/04/2020 at 07:45. Pushed by dfaure into branch 'release/20.04'. Fix "Only resources can modify remote identifiers" when re-editing event Summary: ... before the resource had time to create it and notify korganizer about it. This seems to be a better fix than akonadi commit fbcd065c0dbb, which for some reason isn't enough (I had the error again in January 2020). Test Plan: Create event in korganizer, double-click it immediately, change something, click OK. Reviewers: dvratil Reviewed By: dvratil Differential Revision: https://phabricator.kde.org/D28559 M +1 -0 src/editoritemmanager.cpp https://commits.kde.org/incidenceeditor/7ba473fef78978aee6cdda0cdcead3fa65d3c62b |