Release criteria proposal: networking requirements
by Adam Williamson
Hi folks!
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
networking criteria.
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.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
1 year, 9 months
Add options to display configuration?
by S Bob
All;
I'm running Fedora 33 on an LG Gram 17.
I have a BenQ EX2780Q External Monitor.
If I go to System Settings --> Display and Monitor I can set the
external monitor to a range of resolutions, however the resolution I
want is not on the list.
I have a script I can run as root to set the resolution I want:
#!/bin/bash
# cvt 2160 1200 60
xrandr --newmode "2160x1200_60.00" 217.25 2160 2312 2536 2912 1200
1203 1213 1245 -hsync +vsync
xrandr --addmode HDMI-1 "2160x1200_60.00"
xrandr --output HDMI-1 --mode "2160x1200_60.00"
However, I would like the 2160x1200 setting to be added to the list in
System Settings --> Display and Monitor permanently, how do I do this?
Can I add an xorg.conf file? If so does anyone have any simple examples?
Thanks
in advance
2 years, 9 months
User directories not present in fresh F34 KDE install
by Jorma Penala
The default user directories seem to be missing from F34 KDE spin. After fresh install from latest compose, the only directory present is Desktop. One has to run xdg-user-dirs-update manually to generate Documents, Music etc.
2 years, 9 months
No login screen after update for VMWare Fusion fedora 33 VM
by Barry Scott
I updated my VM and I no logged have a login screen.
The only thing I have spotted at the moment is a problem with sddm-helper.
# systemctl status sddm
● sddm.service - Simple Desktop Display Manager
Loaded: loaded (/usr/lib/systemd/system/sddm.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2021-01-23 16:30:10 GMT; 47s ago
Docs: man:sddm(1)
man:sddm.conf(5)
Main PID: 934 (sddm)
Tasks: 4 (limit: 5828)
Memory: 84.7M
CPU: 448ms
CGroup: /system.slice/sddm.service
├─934 /usr/bin/sddm
└─937 /usr/libexec/Xorg -nolisten tcp -auth /var/run/sddm/{30741cdf-5986-4495-a598-b44f1a9f322d} -background none -noreset -displayfd 16 -seat >
Jan 23 16:30:10 vmf33.chelsea.private systemd[1]: Started Simple Desktop Display Manager.
Jan 23 16:30:11 vmf33.chelsea.private sddm-helper[943]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=995) by (uid=0)
Jan 23 16:30:15 vmf33.chelsea.private sddm[934]: Auth: sddm-helper exited with 11
Any one else seeing this?
I attempted to roll back the transaction but dnf history
rollback did nothing and did not report an error either.
I did try rolling back parts of the update to did not manage
to find what might have been the cause.
Barry
2 years, 9 months
sddm auto-resize in VM (F34)
by Ed Greshko
I installed Fedora-KDE-Live-x86_64-34-20210212 in a qemu VM.
I am unable to get the guest to auto-resize when I expand the console window. I am also unable to
select an alternate display size with system-settings or xrandr (using plasma on X11). If I select
Virtio as the video card I can use system-settings to select a reasonable size but still unable to
get auto-resize to work.
With the Workstation version of F34 auto-resize works as desired.
So, I installed gdm on the F34 spin and now auto-resize works. It therefore seems a problem
with sddm. I didn't locate a BZ to address this. Is this a known issue being worked?
Ed
--
People who believe they don't make mistakes have already made one.
2 years, 9 months
repo disabled, F34 Test
by Ed Greshko
Is there any reason why the fedora.repo is disabled in the F34 test spins?
--
People who believe they don't make mistakes have already made one.
2 years, 9 months
