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
2 months, 3 weeks
What's loading Dolphin?
by Mark ＠ GMail
Every time I start Fedora it loads Dolphin, which I don't want.
Where should I look for it doing that (so I can stop it)?
I also notice that, even though I've closed it, there's still a (small)
dolphin process running... what's that about?
Thanks in advance
Mark
1 year, 6 months
KDE on RHEL 8
by Syam Krishnan
Hi
What is the recommended method to install KDE on RHEL 8?
I tried adding EPEL repo and did:
yum groupinstall "KDE Plasma Workspaces"
But this fails with:
================
Error:
Problem 1: conflicting requests
- nothing provides xmessage needed by
plasma-workspace-5.18.4.1-2.el8.x86_64
Problem 2: package sddm-breeze-5.18.4.1-2.el8.noarch requires
plasma-workspace = 5.18.4.1-2.el8, but none of the providers can be
installed
- conflicting requests
- nothing provides xmessage needed by
plasma-workspace-5.18.4.1-2.el8.x86_64
Problem 3: package plasma-desktop-5.18.4.1-2.el8.1.x86_64 requires
plasma-workspace >= 5.18, but none of the providers can be installed
- conflicting requests
- nothing provides xmessage needed by
plasma-workspace-5.18.4.1-2.el8.x86_64
Problem 4: package kde-print-manager-19.12.3-2.el8.x86_64 requires
plasma-workspace, but none of the providers can be installed
- conflicting requests
- nothing provides xmessage needed by
plasma-workspace-5.18.4.1-2.el8.x86_64
================
Do I need to do anything else to install KDE off EPEL? or is there
another source?
Thanks
Syam
1 year, 7 months
Introducing myself
by Fernando Santos
Hi there,
my name is Fernando. I'm from Brazil. I'm currently a Fedora Ambassador,
but I want to contribute to the Plasma/KDE's Spin.
I'm working as a software developer at FIOCRUZ, the organization that makes
vaccines for many diseases and viruses.
So, how can I help the Plasma/KDE Spin to build and test the latest release
of Qt and KDE framework. How to empower the Fedora's KDE/Plasma community
with the 2Fs -> Features and First??
I need a guide, I need someone to show how to make things at Plasma/KDE
better.
Can you help me??
--
*Fernando "ferox" dos Santos*
*Especialista em Tecnologias Open Source*
*Desenvolvedor*
*http://ferox.eti.br <http://ferox.eti.br>*
*https://fedoraproject.org/wiki/User:Ferox
<https://fedoraproject.org/wiki/User:Ferox>*
1 year, 7 months
Fedora 33 Beta Secure boot issue
by Alex Thomas
Thought I would try the beta out on my laptop again (had tried it on
test week, but had to revert due to platform.io not working) Getting
error of : " Secure Boot Image failed to verify with * ACCESS DENIED*
"
It worked on the btrfs test week, so I am unsure what went wrong.
Laptop is Lenovo T440p.
I filed a bug, but the best component I could find was Grub2.
https://bugzilla.redhat.com/show_bug.cgi?id=1883609
1 year, 7 months
KRunner question
by Todd Hesla
A couple weeks ago I upgraded from Fedora 28 to Fedora 32 (with KDE in both).
Unfortunately, KRunner now comes up with the clipboard contents in the text box,
whereas before upgrading, it always came up with an empty box.
How can I get KRunner to come up with an empty text box (rather than with the
clipboard contents)?
--
Todd Hesla
1 year, 7 months
Plasma + sddm
by Frédéric
Hi,
I'm running Plasma + sddm on F31. Since a week, I try to use the
computer with multiple users and then I log off before the other user
logs in. When I log off, the screen just freezes. I can switch to a
console screen with Ctrl+Alt+F2 and kill all processes of the first
user (systemd, agent, sddm_helper) until I get the login screen again.
Very annoying.
Is there a way to make it work?
Kind regards,
F
1 year, 8 months
Selecting user using mouse on SDDM screen
by Syam Krishnan
Hello,
Is it possibe to select a user using the mouse from SDDM login screen? It
shows available users in big circles (with photos), but the only way to
select a user is to use left and right arrow keys. There is no effect of
clicking on the circles. I thought its a quirk of the default Fedora theme
and tried another from 'get new theme'. But that too has the same behaiour.
Is this a theme thing? Or does SDDM interface only support selection by
keyboard?
I feel the UI makes us instinctiely think that selection can be made by
clicking.
--
Regards,
Syam
syamcr(a)gmail.com
1 year, 8 months
