So at this week's blocker review meeting, the fact that we don't have
explicit networking requirements in the release criteria really started
to bite us. In the past we have squeezed networking-related issues in
under other criteria, but for some issues that's really difficult,
notably VPN issues. So, we agreed we should draft some explicit
This turns out to be a big area and quite hard to cover (who'd've
thought!), but here is at least a first draft for us to start from. My
proposal would be to add this to the Basic criteria. I have left out
some wikitext stuff from the proposal for clarity; I'd add it back in
on actually applying the proposed changes. It's just formatting stuff,
nothing that'd change the meaning. Anyone have thoughts, complaints,
alternative approaches, supplements? Thanks!
=== Network requirements ===
Each of these requirements apply to both installer and installed system
environments. For any given installer environment, the 'default network
configuration tools' are considered to be those the installer documents
as supported ways to configure networking (e.g. for anaconda-based
environments, configuration via kernel command line options, a
kickstart, or interactively in anaconda itself are included).
==== Basic networking ====
It must be possible to establish both IPv4 and IPv6 network connections
using DHCP and static addressing. The default network configuration
tools for the console and for release-blocking desktops must work well
enough to allow typical network connection configuration operations
without major workarounds. Standard network functions such as address
resolution and connections with common protocols such as ping, HTTP and
ssh must work as expected.
Footnote titled "Supported hardware": Supported network hardware is
hardware for which the Fedora kernel includes drivers and, where
necessary, for which a firmware package is available. If support for a
commonly-used piece or type of network hardware that would usually be
present is omitted, that may constitute a violation of this criterion,
after consideration of the [[Blocker_Bug_FAQ|hardware-dependent-
issues|normal factors for hardware-dependent issues]]. Similarly,
violations of this criteria that are hardware or configuration
dependent are, as usual, subject to consideration of those factors when
determining whether they are release-blocking
==== VPN connections ====
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
VNC servers with typical configurations.
Footnote title "Supported servers and 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. As a general
principle, the more people are likely to use affected servers and the
less complicated the configuration required to hit the bug, the more
likely it is to be a blocker.
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
I've a strange behaviour in my live remix when I try to set language
using System settings > Regional settings > Language. I just get
"American English" and "British English" and nothing else.
I know there is a bug  in language settings.
Is this behaviour due to the bug or I'm missing something?
Does anyone know where the language list sourced from?
According to https://bugs.kde.org/show_bug.cgi?id=427777 it should be
possible to switch users from the KDE lock screen, however I don't seem
to have this functionality.
Related question: is it possible to have two different DEs on different
virtual consoles (if necessary with two distinct users)? For example,
one with KDE and another with Gnome. I know this used to be possible in
some previous iterations of KDE/Plasma, but there may be limitations
due to SDDM.
I really, really don't like the glaring red close window button that the
Breeze theme uses in F34. Is there a way to revert to the gray button
that I had in F33?
In Soviet Russia, Google searches you!
I've recently tried running some Windows Steam games under Linux, using
Steam's Proton compatibility layer. Under F33 I had some success with a
few of them, but under F34 things have been less reliable. One game
(Skyrim SE) crashes immediately, while another (Edith Finch) will run
for a few minutes very smoothly, then suddenly freeze the entire UI so
badly that I need to log in from another machine to kill the desktop
session. I can't even switch to another virtual console.
All this has been with KDE/Plasma/X11, but when I log in under
Gnome/X11 everything seems to work correctly, at least so far.
Has anyone seen this kind of problem with Plasma?