| Summary: |
When creating a new event fails - because of calendar backend problem - the event is discarded after showing error message |
| Product: |
[Applications] Merkuro
|
Reporter: |
Ben Opp <ben.opp> |
| Component: |
general | Assignee: |
Claudio Cambra <claudio.cambra> |
| Status: |
REPORTED
---
|
|
|
| Severity: |
normal
|
CC: |
ben.opp, carl, thomas
|
| Priority: |
NOR
|
Keywords: |
usability |
| Version First Reported In: |
22.08.1 | |
|
| Target Milestone: |
--- | |
|
| Platform: |
Manjaro | |
|
| OS: |
Linux | |
|
|
Latest Commit:
|
|
Version Fixed/Implemented In:
|
|
|---|
|
Sentry Crash Report:
|
|
| |
|---|
| Attachments: |
Screenshot of error message
|
Created attachment 152961 [details] Screenshot of error message SUMMARY *** When creating a new event fails (because of calendar backend problem), only error message is shown, event discarded *** STEPS TO REPRODUCE 1. Have a calendar synced to some cloud, but the backend is unavailable or something is wrong with it. 2. create a new event for that calendar. 3. Click "Add" in the Add Event dialogue. 4. I get an error message saying "Error creating the calendar entry. Error message is "Invalid parent collection". 5. Hit OK on that. The "Add Event" dialogue is gone. OBSERVED RESULT I spent a few minutes typing in the details of that event, maybe searching the location on the map, editing the description, adding reminders etc. Now, because of the backend error, I have to type it all again, the information is gone. EXPECTED RESULT I get notified of the backend error, but the "Add Event" window stays open. Ideally, I get to opportunity to save it locally, even though it cannot be synced to the cloud. I get the chance to investigate the backend problem without having to retype everything when it's fixed. Instead, the locally saved event would just get synced at the next opportunity. Else, I can choose a different calendar/backend to save the event to. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.15.72-1MANJARO kernel, Wayland (available in About System) KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION Backend used in this case is Etesync with kdepim-addons. The Bug is not about the backend probelm, but how Kalendar handles it.