Description of problem: This is a tracker bug for the upstream issue (https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/905). It mainly serves the Blocker review purposes. If you want to add a comment to it, you probably should update the upstream issue first. Version-Release number of selected component (if applicable): gnome-calendar-43.1-2.fc37.x86_64 How reproducible: Always
Proposed as a Blocker for 37-final by Fedora user lruzicka using the blocker tracking app because: And one more basic functionality.
I don't have a gitlab account. I don't know anything about gnome-calendar, but here is a guess about what is wrong from the comments on the bug. In one of the Gitlab comments on the bug, someone said "The duplicates disappears if we kill /usr/bin/gnome-calendar --gapplication-service". So, gnome-calendar is running as a service, ane when the user closes the app, the service doesn't shut down. From what happens in the bug, the service must keep a list of all the events and that list is used by the app to draw the events in week mode. When the app is restarted and connects to the service, the bug would happen if the app reloaded the events from the calendar database and added them to the service. The service keeps what was there the last time the app closed, so it would get an additional copy of each event (from the external database) each time the app restarted (like in the bug). If you stop the service (reboot,r log out of the linux user, or kill the service), and then start gnome-calendar, it would be back to showing just one entry for each calendar event. And the extra copy would be added again every time the app was stopped and restarted. If that's it, it would be easy to fix for someone who knew the code.
(In reply to wayne6001 from comment #2) Please ignore my comment. I got a gnome gitlab account and commented there.
I tested the new RC iso (Fedora-Workstation-Live-x86_64-37-1.7.iso) and i can't reproduce the bug. This compose have gnome-calendar-43.1-3.fc37
Discussed at the 2022-11-07 blocker/FE review meeting: https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2022-11-07/ . This was rejected as a blocker due to the fairly moderate impact of the bug (the events are *there*, just...multiple times), and the apparent difficulty in clearly reproducing it. We decided these factors meant it's not a clear "basic functionality" failure.
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. 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 '37'. 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 37 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 37 entered end-of-life (EOL) status on None. Fedora Linux 37 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.