| Summary: | Unable to create new todo items (possibly due to multiple calendars?) | ||
|---|---|---|---|
| Product: | [Applications] zanshin | Reporter: | Kenny D <kenny> |
| Component: | general | Assignee: | Kevin Ottens <ervin> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | mbensi |
| Priority: | NOR | ||
| Version First Reported In: | 0.5.0 | ||
| Target Milestone: | already done | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Kenny D
2018-04-25 14:39:56 UTC
This is surprising, it should just "take the first one it can write to" by default or your favorite one if you selected such a thing (in the source view, select one and click the small star icon at the bottom). I use it with several CalDav calendars just fine, so I wonder what's the root cause of your issue there. Could we somehow get an idea of what's displayed in your Sources tree? Setting one to favourite/default made the error go away \o/ I notice that it is now in bold, previously none were. Maybe that would be the issue? That's the thing... it shouldn't since in that case it'd just pick a "random" one for you... but for some reason in your case it'd picked one it didn't like. I really wonder why. I have 2 enabled sources and one disabled, all from nextcloud To see if it had previously tried to use the disabled one I disabled the one I have set to default but there was no error and it still created a new todo in that source. Does enabling/disabling only effect visibility of things in it? Yes, it's really only about visibility. Could you try them one after another as default and see if it fails with any of those three? They all behave fine. Is there anyway to unset a default source? I only seem to be able to change to a different one now I have one set Yes, just kill the defaultCollection key in your zanshinrc config file. I have now tried deleting the default source a few times and it still seems to be creating tasks fine so I'm now a bit at a loss what the initial problem was hmm... Yes, I'm at a loss what it could have been either... if we can't reproduce though we won't get closer to an explanation I'm afraid. yep, agreed Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |