Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2177992 Information from BlockerBugs App: <img alt="2177992" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2177992" />
Commented but haven't voted yet: kparal
The votes have been last counted at 2023-03-15 23:19 UTC and the last processed comment was #comment-847072
To learn how to vote, see: https://pagure.io/fedora-qa/blocker-review A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)
BetaBlocker +1
BetaBlocker
FinalBlocker
BetaFE
FinalFE
0Day
PreviousRelease
+1
0
-1
The criterion for this would be: https://fedoraproject.org/wiki/Fedora_38_Final_Release_Criteria#Default_application_functionality
Searching is a pretty basic feature, I think. This is only made worse by the fact that after few searches you get a permanent 100% load on one core, which continues even after you've closed Calendar. That means your battery life will be seriously reduced, and general users won't even be aware of it/be able to fix it.
FinalBlocker +1
I'm not sure about the "basic functionality" part on its own, but the fact that the CPU usage doesn't drop when Calendar is closed is enough to make me solidly
I'm not sure about the "basic functionality" part on its own, but the fact that the CPU usage doesn't drop when Calendar is closed is enough to make me solidly FinalBlocker +1
This was a key observation for me. Churning through the user's battery is even worse than a crash.
FinalBlocker +1 AGREED AcceptedFinalBlocker
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F38 is no longer tracked by BlockerBugs, closing this ticket.
Login to comment on this ticket.