Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=1880752
Commented but haven't voted yet: sumantrom, augenauf, kalev, catanzaro
The votes have been last counted at 2020-09-27 19:52 UTC and the last processed comment was #comment-688534
To learn how to vote, see: https://pagure.io/fedora-qa/blocker-review
FinalBlocker +1
Hmm, I'm not sure whether I'd classify this as a basic Nautilus functionality. First, I wonder how many people actually know that there's a preview functionality hidden on the space bar. I always thought it was a very obscure and mostly unknown thing. Second, lacking a spacebar preview in a file manager doesn't seem to be a big loss. You still have a thumbnail preview. If thumbnails were broken, that would be much more visible, and it would cause real inconvenience, like having a hard time to find one particular picture in a folder with many. That would be much closer to "basic functionality" than the spacebar preview. This bug feels more like CommonBugs than a Blocker to me.
Please share your opinions, thanks.
I agree with @kparal that the basic functionality is very questionable here. I never knew this was even possible. Furthermore, this problem, in my opinion, does not prevent the application from being used correctly for manipulating files which I consider to be basic functionality of a file manager. The reported issue is a cosmetic flaw to me.
FinalBlocker -1
Agree with @kparal and @lruzicka - that function is way too unknown and unimportant to be a release blocker...
It has been confirmed by the Workstation WG that this behaviour is not blocking for Fedora 33. See the original bug for more info.
Thanks @lruzicka for the update. I'll reset the vote so that we can vote again with the WG guidance on mind.
REVOTE FinalBlocker
It doesn't make sense to me to block on this when Workstation WG themselves don't consider it a basic functionality.
I submitted this as a Beta FE as we have a fix now. Can I have some Beta FE votes as well, please?
I would suggest voting BetaFE +1, FinalBlocker -1.
tbh I don't think this is anywhere near important enough for BetaFE. It's safe -- the risk of breaking other components is almost zero -- so there's not really any harm to sneaking it in. But it's also just not a very important bug, and can be easily fixed with an update post-beta.
"not a very important bug" per the standards of a beta release, when the bug is going to be fixed with an update anyway. I would be concerned about this issue if we didn't have an update pending to fix it. But we do. :)
BetaFE +1
Today's update of sushi-3.34.0-4.fc33.x86_64 fixed the issue (at least on my test system)
@augenauf please give karma on https://bodhi.fedoraproject.org/updates/FEDORA-2020-4cfd52878a
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F33 is no longer tracked by BlockerBugs, closing this ticket.
Login to comment on this ticket.