Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2388442 ** Information from BlockerBugs App:
The votes have been last counted at 2025-08-25 15:24 UTC and the last processed comment was #comment-983221
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
I think OpenVPN with 2FA is a fairly common configuration (at least it's in use around here pretty regularly). This bug apparently also requires the password prompt to need to display "wide" characters, but I don't love not accepting a bug as a blocker just because of a user's preferred language.
Violation of the VPN connections basic criteria.
BetaBlocker +1 BetaFE +1
I agree with the above, tools should work even if national languages are used.
Yeah, we should probably not disregard the just because it doesn't appear in English. It would be nice to know more precisely which languages it affects, but Cyrillic is definitely widely used.
However, because this is a conditional violation (just some languages are affected, and 2FA must be used), I think it would make sense to target Final instead of Beta.
FinalBlocker +1 BetaBlocker 0
I'm not sure "wide" is actually accurate. AIUI, standard Cyrillic characters are not wide glyphs. CJK glyphs are the most commonly used sets that are generally considered "wide". It's possible this really affects anything outside of ASCII, or something, which would only make it a stronger candidate.
The criterion here is Basic:
"Using the default network configuration tools for the console and for release-blocking desktops, it must be possible to establish a working connection to common OpenVPN, openconnect-supported and vpnc-supported VPN servers with typical configurations. ... As there are many different VPN server applications and configurations, blocker reviewers must use their best judgment in determining whether violations of this criterion are likely to be encountered commonly enough to block a release, and if so, at which milestone."
so we're on subjective judgment here. I think I'd agree with @kparal that Final blocker is the most appropriate here. But I'm also voting BetaFE since we have a fix and it'd be great to get it in Beta.
FinalBlocker +1 BetaFE +1
I'm gonna count lruzicka's BetaBlocker vote as also good for BetaFE, and also say:
AGREED AcceptedBetaFE
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F43 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.