Created attachment 1875359 [details] bug demonstration video Description of problem: When I delete multiple events in gnome-calendar, they appear all to be deleted. But after I reopen the app, all but the last one reappear. They were not deleted, just pretended. This only happens if you delete the next event before the notification bar for the previous deletion is still visible. Version-Release number of selected component (if applicable): gnome-calendar-42.0-1.fc36.x86_64 How reproducible: always Steps to Reproduce: 1. create several events 2. delete all those events in a quick-ish manner (if you wait until the notification bar disappears before you next deletion, you'll not trigger this bug) 3. close and reopen gnome-calendar 4. see that all but the last one event reappeared
Proposing for a Final blocker discussion due to: https://fedoraproject.org/wiki/Fedora_36_Final_Release_Criteria#Default_application_functionality
I am able to reproduce this on Fedora-Workstation-36-1.1.aarch64.raw.xz. Like Kamil says, if you don't delete the events before the notification bar at the bottom that says "Event deleted" disappears, this bug does not happen. However, if you delete all the events while the notification bar at the bottom is still showing, then upon closing and reopening gnome-calendar, all but the last event you deleted will still be shown.
When trying to reproduce the behaviour as Kamil described, I can see this, too. The event will not deleted if the deletion attempt is performed while the "Event deleted" message with the "Undo" button is still visible. However, if you dismiss the message using the "x" button on the right and delete the next event, it will be correctly deleted. So this might feel like a protection from deleting an event being given some grace time to think it over. This would make a total sense to me. The only problem I am seeing is that when I do it as described, another message is shown saying "Another event deleted" which in this case is not true.
In today's Go/No-Go meeting, we agreed to accept this as a freeze exception but reject it as a blocker. This does not violate the "Basic Functionality" criterion but is worth fixing if possible https://meetbot.fedoraproject.org/fedora-meeting/2022-04-28/f36-final-go_no_go-meeting.2022-04-28-17.01.log.html#l-327
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.
This seems to be fixed in gnome-calendar-44.1-1.fc38.x86_64