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, 2 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
2 years, 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
2 years, 8 months
Future of shared-mime-info in Fedora
by Miro Hrončok
Hello Fedorans, Bastien,
I have noticed that the shared-mime-info package was orphaned couple days ago.
Bastien, AFAIK you were the primary point of contact in Fedora and I also see
you are the RHEL 8 default bugzilla assignee.
Considering the following commit:
https://gitlab.freedesktop.org/xdg/shared-mime-info/-/commit/6f4947b01
I've disregarded the idea the the package was orphaned by accident.
I also see that GNOME mime types have been moved away from the package (on
rawhide only):
https://src.fedoraproject.org/rpms/shared-mime-info/c/da05922d10
https://src.fedoraproject.org/rpms/gnome-desktop3/c/9909d22b
I always considered shared-mime-info an important package, however I don't see
it in comps. Maybe it is no longer that important?
A repoquery reveals ~50 packages that require it including PackageKit, Thunar
(Xfce), some NetworkManager packages, kdelibs (KDE)...
A recursive repoquery yields ~ 6650 packages.
I've taken the orphaned package for now to avoid any disruption (and a totally
unreadable orphans report), but I don't really understand the Fedora package, it
has a manually created source without any comment explaining where is this from:
https://src.fedoraproject.org/rpms/shared-mime-info/blob/master/f/mimeapp...
Bastien, could you please give me a hint about this file? Thanks
---------
The package technically has 8 co-maintainers and a sig, but I don't put much
hopes into the crowd there considering they haven't touched the package in years.
Are there any interested Fedora packages that understand mime info better than I do
---------
PS There is an interesting file-ownership problem reported in Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1486468 - I plan to discuss this
later on the packaging mailing list as well.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
2 years, 9 months
Re: Proposal to Add: Log In/Out Blocker Criteria
by Kamil Paral
On Wed, Aug 12, 2020 at 4:25 PM Kamil Paral <kparal(a)redhat.com> wrote:
> I'd accept the criterion as proposed (because we need it now), and do the
> reorganization later (possibly when this cycle is over and we have more
> time to bikeshed about best criterion layout). I'm fine with either adding
> to the existing criterion (mine version) or creating a standalone criterion
> (Geoff's version), just note that the standalone version would still need
> to get tweaked (remove "multiple user accounts", etc).
>
In accordance with the discussion during the last QA meeting, I've put my
proposed changes live:
https://fedoraproject.org/w/index.php?title=Fedora_33_Beta_Release_Criter...
2 years, 9 months
dnfdragora icon update
by Ed Greshko
Just a comment.
I was a bit surprised today when dnfdragora and dnfdragora-updater were updated and the icon
has been changed.
I'm sure I'll get used to it, but I wish a color other than red was chosen. I'm predisposed to
think that red is an indication that something is amiss or needs attention.
--
The key to getting good answers is to ask good questions.
2 years, 9 months
"Software updates" Plasma notifications not hiding
by Iñaki Ucar
Hi,
It turns out that "Software updates" notifications are the only ones
that do not hide after 5 seconds in my system, and it's quite
annoying. Does anyone else have this problem? Any idea on how to fix
this?
Thanks,
--
Iñaki Úcar
2 years, 9 months
A question about konsole.
by George R Goffe
Hi,
I'm having a little trouble with konsole and filename completion and am looking for information on how konsole shows alarms. Specifically, when attempting to use filename completion on a file that doesn't exist. I'm not seeing any flashing or hearing any bells (audio system is broken).
Any help/hints/tips/suggestions would be greatly appreciated.
Thanks in advance.
Best regards,
George...
2 years, 9 months
Authorization supplicant timed out errors
by S Bob
All;
I am having my wifi connection reset throughout the day. I get a popup
message that says :
*Wireless interface (wlp82s0)*
*Authorization supplicant timed out*
This happens every 2 - 4 hours, it's new but I'm not sure I can point to
a specific update
Thanks in advance
2 years, 9 months
