Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2127618 ** Information from BlockerBugs App:
Commented but haven't voted yet: kparal, coremodule
The votes have been last counted at 2022-09-30 16:41 UTC and the last processed comment was #comment-819400
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 behaviour is not good, but files still can be managed which, in my opinion, does not violate the criterion for basic functionality.
FinalBlocker -1
I agree. This isn't basic functionality.
We're still a week and a half away from freeze, but since I'm thinking about it now, I'll give a
FinalFE +1
in case it's not fixed before 4 October.
The problem is somewhat worse than it seems; nautilus will actually continually re-generate the thumbnail, over and over, causing heavy CPU usage as long as it's open.
I'm at least:
Causing heavy CPU usage is bad. So I agree at least:
I asked for some details in the upstream ticket. Honestly, if one or more CPU core runs at 100% for the whole time that Nautilus is open, that might very well be worth a blocker. Depends on how many systems are affected.
I'm with @kparal on this one. Delaying blocker decision.
FinalBlocker -1 FinalFreezeException +1
AGREED AcceptedFinalFE
Discussed during the 2022-09-26 blocker review meeting: [0]
The decision to delay the classification of this as a blocker bug and accept is as an "AcceptedFreezeException (Final)" was made in order to gather more info on how bad the CPU load issue is. We agree that the lack of thumbnails is an annoying cosmetic issue but not serious enough to block on. It's definitely serious enough (and in a component of the Workstation live, so not fully fixable with an update) to grant an FE.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-09-26/f37-blocker-review.2022-09-26-16.01.txt
The following votes have been closed:
This one is pretty bad, but I'd say it falls just below my threshold of badness for it to block Fedora release. So:
Based on my CPU test I think I'm also just:
Blocking 40% of CPU while the folder is open is bad, but not really catastrophic, I don't think. If it was 100%, or it persisted after leaving the folder, I'd be +1.
AGREED RejectedFinalBlocker
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F37 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.