Created attachment 1875406 [details] screencast Description of problem: As shown in the screencast,after add two events,nothing happens when I try to add a third event Version-Release number of selected component (if applicable): gnome-calendar-42.0-1.fc36.x86_64 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 1875407 [details] journal
Proposed as a Blocker for 36-final by Fedora user lnie using the blocker tracking app because: seems affects: https://fedoraproject.org/wiki/Fedora_36_Final_Release_Criteria#Default_application_functionality
I can't reproduce with gnome-calendar-42.0-1.fc36.x86_64 on a VM or bare metal.
i can not reproduce the issue
I can't reproduce this bug reliably with three events,but I can reproduce it easily with fourth events on VM. Actually,as shown in the screencast1,it's not nothing happens,calendar added the event,but failed to add it to all days I set. for example,if I add the fourth event like this:05/11/2022,12:00---08/11/2022,14:00,the calendar doesn't show the event in July page. It won't show up even after a reboot.And I see this crash[1] several times,while I check(screencast2). But I can't reproduce easily on a bare metal,though gnome-calendar dosn't work well either,some times even worse. As shown in the screencast3,I only add one event named “one”,but it looks like there are three "one" events. [1]https://bugzilla.redhat.com/show_bug.cgi?id=2066212
Created attachment 1875568 [details] screencast1
Created attachment 1875569 [details] screencast2
Created attachment 1875570 [details] screencast3
Created attachment 1875571 [details] journal from the VM
Created attachment 1875575 [details] journal from bare metal
Here is my event settings which produces this bug: event one:05/11/2022 0:01 --> 09/11/2022 01:01 event two:05/11/2022 07：00 --> 10/11/2022 08:00 event three:05/11/2022 09:00 --> 08/11/2022 09:30 event four: 05/11/2022 12:00 --> 08/11/2022 14:00
(In reply to lnie from comment #11) > Here is my event settings which produces this bug: > event one:05/11/2022 0:01 --> 09/11/2022 01:01 > event two:05/11/2022 07：00 --> 10/11/2022 08:00 > event three:05/11/2022 09:00 --> 08/11/2022 09:30 > event four: 05/11/2022 12:00 --> 08/11/2022 14:00 I cannot reproduce this in a cleanly installed F35 upgraded to F36 that runs in a virtual machine.
Created attachment 1875584 [details] Four events added to the calendar
okay,the fourth events can be shown if you click the +2 button,as shown in the attached screenshot,I think it's not a good UI but not a blocker. What's blocker thing is here,I'm finally able to find a pretty reliable reproducer(I have a feeling that adding a periodically event is pretty unreliable)^^ add a daily event like: 09/01/2022 0:00-01:00 -> 09/01/2022 0:00-01:00 Repeat:daily Try to add another event like: 09/01/2022 0:00-01:00 -> 09/01/2022 16:00-17:00 Repeat:daily,but find only the first day is added. I believe you can reproduce it easily on bare metal or VM.
Created attachment 1875625 [details] screencast
Created attachment 1875626 [details] screenshot
(In reply to Lukas Ruzicka from comment #13) > Created attachment 1875584 [details] > Four events added to the calendar You need to check the second page,as I mentioned in comment5,only July page is affected
I still can't reproduce either the behavior in comment 5 or comment 14.
(In reply to Ben Cotton from comment #18) > I still can't reproduce either the behavior in comment 5 or comment 14. Would you please take one minute to upload the video that you failed to reproduce #comment14? So that I can tell you why you failed,as I'm pretty sure this can be easily reproduced. Here is the reproducer without typo: add a daily event like: 09/01/2022 00:00 -> 09/01/2022 01:00 Repeat:daily Try to add another event like: 09/01/2022 16:00 -> 09/01/2022 17:00 Repeat:daily
In today's Go/No-Go meeting, we agreed to reject this as a blocker. Other testers have been unable to reproduce this bug and it falls outside of "basic functionality" https://meetbot.fedoraproject.org/fedora-meeting/2022-04-28/f36-final-go_no_go-meeting.2022-04-28-17.01.log.html#l-364
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.