Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2131723 ** Information from BlockerBugs App:
Commented but haven't voted yet: memento
The votes have been last counted at 2022-10-21 07:28 UTC and the last processed comment was #comment-822274
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
FinalBlocker -1
For me this is a bit beyond 'basic functionality', honestly. I'm OK with shipping with this and fixing it with an update.
Agree with Adam.
Agree
I'm holding off on a vote until I hear back from my query on the BZ. I need to know if the issue is limited to Nautilus or if something is wrong in samba.
we do not know which Samba runs on this one specific share - it could even be malconfigured, so this is why I am voting against the blocker.
I think this is beyond basic functionality in Nautilus. At the same time, I'd be open to creating a separate release criterion for operating network drives, I think that's quite important. Currently:
At the same time, I'd be open to creating a separate release criterion for operating network drives
Yeah, why not. That could be indeed a good criterion for the Fedora Server.
FinalBlocker 0
I'm not entirely convinced this isn't "basic functionality", but I won't try to push that argument. I have nominated the underlying samba update that fixes this particular bug as an FE.
The fix is proposed as an FE in #984.
AGREED RejectedFinalBlocker
The following votes have been closed:
To me it was a tried and true regression, using Samba servers on Fedora Linux 36 worked fine and they did not on Fedora Linux 37, I use those daily for work. Servers here never changed since Fedora Linux 36.
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.