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, 6 months
Compose key stopped working
by Emmett Culley
I have the compose key set to Scroll lock, but is seems to ignored. I've tried setting a different compose key, but that did not work either.
If I type Compose o o I expected a degree symbol to get printed, but instead all I see in oo
Nothing I've found on on Google tells me anything I haven't already tried.
window manager = sddm (X11)
KDE on Fedora 34 fully updated.
2 years, 1 month
plasmashell crashes on right click in menu
by Matthew Lavigne
Posting here as a question before I bug this (first time back on Plasma in
a long time).
F34 current
Looks like plasma-5.22.3-1 (plasma-desktop-5.22.3-1.fc34.x86_64)
Issue: When looking to add items to the taskbar (similar to Cinnamon) I
select the application that I want to add and right click.... Immediately
plasmashell goes away. It does restart. Frustrating in that there has to
be a way to move apps to the panels to have access to them without pinning
but either I am missing it or doing something wrong.
From a terminal did the following:
killall plasmashell
plasmashell&
Take the above action and get this in the shell:
trying to show an empty dialog
file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/LeaveButtons.qml:69:5:
QML ToolBu
tton: Binding loop detected for property "display"
QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
file:///usr/share/plasma/plasmoids/org.kde.plasma.printmanager/contents/ui/PopupDialog.qml:91:17:
Unabl
e to assign [undefined] to QString
file:///usr/lib64/qt5/qml/org/kde/plasma/components/ModelContextMenu.qml:
38:1: QML ModelContextMenu: Accessible must be attached to an Item
trying to show an empty dialog
KCrash: Attempting to start /usr/bin/plasmashell
KCrash: Application 'plasmashell' crashing...
KCrash: Attempting to start /usr/libexec/drkonqi
Tried with an existing user that has had a live home dir for a long time
and with a new user (only ever logged into Plasma)
Looking to see if I am missing something prior to putting in a bug. Any
thoughts?
Matthew
2 years, 1 month
Updated KDE Plasma Desktop ready for testing on CentOS Stream 8
by Troy Dawson
An updated qt5 in CentOS Stream 8 allowed us to update KDE Plasma Desktop.
I believe everything is in place and ready for use and/or testing.
This is for CentOS Stream 8 only, at this time.
===How to Install [1]
= Install epel-release
dnf install
https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm
= Enable PowerTools
dnf config-manager --enable powertools
= Install KDE
dnf group install kde-desktop-environment
or
dnf group install kde-desktop
(Optional) dnf group install kde-apps
(Optional) dnf group install kde-media
(Optional) dnf group install kde-education
(Optional) dnf install okular
(Optional) dnf group install kde-software-development
(Optional) dnf group install kf5-software-development
=== KNOWN PACKAGE ISSUES
== UNINSTALLABLE PACKAGES
* kaccounts-providers - no signon-ui
* kigo - no gnugo
* lokalize - no translate-toolkit , needs rebuilding on python3
== UNBUILT PACKAGES
* polkit-qt5 - need branch and build of polkit-qt-1
* kde-gtk-config - needs sassc
* digikam - can't find opencv despite it being installed
== UN-UPDATED PACKAGES (but still install and run)
* kpmcore - would need a newer util-linux than available in RHEL 8
* kde-partitionmanager - would need a newer kpmcore
Feel free to install and test.
Troy Dawson
[1] - https://fedoraproject.org/wiki/SIGs/KDE/EPEL#Installation
2 years, 2 months
Re: [CentOS-devel] Updated KDE Plasma Desktop ready for testing on
CentOS Stream 8
by Troy Dawson
On Wed, Jul 28, 2021 at 9:18 AM Simon Matter <simon.matter(a)invoca.ch> wrote:
> > First off, thank you very much for that.
> > That is perhaps the best "Here is my environment" anyone has ever sent
> me.
> >
> > The problem is that you don't have the epel-next repo anywhere.
>
> I wasn't aware of epel-next, is it the EPEL for CentOS Stream or what
> exactly?
>
>
Yes.
It is supposed to be layered on top of the regular epel repository because
it doesn't have all the epel packages.
epel-next builds off centos-stream instead of RHEL, like regular epel
does. It only has those packages that need to be rebuilt in stream due to
some library or version update.
In this case, qt5 was updated in stream from 5.12 to 5.15, thus all the kde
desktop needed to be rebuilt (and we updated kde as well). Once RHEL 8.5
is released, I will rebuild all those packages on normal epel8 and we won't
need them in the epel-next repository.
If you are running centos-stream, and do a
dnf install epel-release
you should automatically get epel-next-release.
But it looks like if you are doing a kickstart install, that doesn't work,
so it will have to be listed.
https://fedoraproject.org/wiki/EPEL_Next
Thanks,
> Simon
>
> > At the very least you need to have "epel-next-release" in
> > kickstarts/8/base.ks
> > If you wanted the newer kde packages installed during install you need to
> > add the epel-next repo to kickstarts/8/base-repo.ks
> > I believe it should be
> > repo --name=epel-next --mirrorlist=
> >
> https://mirrors.fedoraproject.org/metalink?repo=epel-next-$releasever&arc...
> > or possibly just
> > repo --name=epel-next --mirrorlist=
> >
> https://mirrors.fedoraproject.org/metalink?repo=epel-next-$releasever&arc...
> >
> > Hope this helps.
> > Troy
> >
> > On Wed, Jul 28, 2021 at 3:13 AM Massi aka Ergosum
> > <massi.ergosum(a)gmail.com>
> > wrote:
> >
> >> Il giorno mar 27 lug 2021 alle ore 17:24 Troy Dawson
> >> <tdawson(a)redhat.com> ha scritto:
> >> >
> >> > I've been able to install, and update all of the packages listed here.
> >> > So, unless you are able to give more details about how your machine is
> >> setup, there isn't much I can help with.
> >> >
> >>
> >> A "fresh install" means an image build using the following kickstarts:
> >> [1]
> >> [2].
> >> I'm using repos listed here [3].
> >>
> >> I'm still investigating, but I suspect I'm not using the latest
> >> versions.
> >>
> >> Thanks
> >> Massimiliano
> >>
> >> [1] https://github.com/mbugni/centos-remix
> >> [2]
> >>
> https://github.com/mbugni/centos-remix/blob/master/kickstarts/8/l10n/kde-...
> >> [3]
> >>
> https://github.com/mbugni/centos-remix/blob/master/kickstarts/8/base-repo.ks
> >> _______________________________________________
> >> kde mailing list -- kde(a)lists.fedoraproject.org
> >> To unsubscribe send an email to kde-leave(a)lists.fedoraproject.org
> >> Fedora Code of Conduct:
> >> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> >> List Archives:
> >>
> https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org
> >> Do not reply to spam on the list, report it:
> >> https://pagure.io/fedora-infrastructure
> >>
> > _______________________________________________
> > CentOS-devel mailing list
> > CentOS-devel(a)centos.org
> > https://lists.centos.org/mailman/listinfo/centos-devel
> >
>
>
> _______________________________________________
> CentOS-devel mailing list
> CentOS-devel(a)centos.org
> https://lists.centos.org/mailman/listinfo/centos-devel
>
>
2 years, 2 months
Some JPGs on the desktop don't preview
by Jonathan Ryshpan
My desktop is set to preview, but there are some small files, JPGs
generated by screen shots, which are generally (but now always) not
previewed. This is not much of a problem but it is irritating. Any
ideas on how to investigate?
The system:
Operating System: Fedora 34
KDE Plasma Version: 5.22.3
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.2
Kernel Version: 5.13.4-200.fc34.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4600
--
Sincerely Jonathan Ryshpan <jonrysh(a)pacbell.net>
If God lived on earth, people would break all
his windows.
2 years, 2 months
Wrong program starts when run from Dolphin
by Jonathan Ryshpan
I have build an old version of audacity (audacity-2.4) from source and
placed the executable in ~/bin. When I start audacity from the command
line (say):
$ audacity-2.4 98.03.14-a.aup
everything runs as it should. But when attempt to start audacity-2.4
from dolphin clicking
dolphin->98.03.14-a.aup->rt-click/Open With->Other Application-
>audacity-2.4
the program started is audacity not audacity-2.4 . Similarly it's not
possible to start audacity-2.4 from the Start Button on the Panel.
I don't have the problem with xv, which I also build from source and
placed in ~/bin .
What's happening?
--
Sincerely Jonathan Ryshpan <jonrysh(a)pacbell.net>
We are Pentium of Borg. Division is futile.
You will be approximated. -- Joe Klemmer
2 years, 2 months
New Discover
by Jonathan Ryshpan
When Discover reports an upgrade with system implications (say a new
kernel) and the user allows the upgrade (by clicking the appropriate
button):
1. Discover downloads the files for the upgrade
2. Discover requests a reboot. After the user allows the reboot
3. Discover reboots the system
4. Discover installs the new kernel (or whatever)
5. Discover reboots the system (again)
What is the reason for the additional reboot before installing the new
kernel (step 3)?
--
Sincerely Jonathan Ryshpan <jonrysh(a)pacbell.net> Dance, as if nobody's
watching, Love, as if you've never been hurt, Sing, as if no one can
hear you, Work, as if you don't need the money, Live, as if heaven is
on earth. -- Rumi
2 years, 2 months