I got the following errors when I ran sudo dnf upgrade --refresh

Problem 1: cannot install the best update candidate for package authselect-libs-1.0-3.fc28.i686 - nothing provides systemctl needed by authselect-libs-1.0.1-1.fc28.i686 Problem 2: package authselect-1.0.1-1.fc28.i686 requires authselect-libs(x86-32) = 1.0.1-1.fc28, but none of the providers can be installed - cannot install the best update candidate for package authselect-1.0-3.fc28.i686 - nothing provides systemctl needed by authselect-libs-1.0.1-1.fc28.i686 Problem 3: package authselect-compat-1.0.1-1.fc28.i686 requires authselect(x86-32) = 1.0.1-1.fc28, but none of the providers can be installed - package authselect-1.0.1-1.fc28.i686 requires authselect-libs(x86-32) = 1.0.1-1.fc28, but none of the providers can be installed - cannot install the best update candidate for package authselect-compat-1.0-3.fc28.i686 - nothing provides systemctl needed by authselect-libs-1.0.1-1.fc28.i686 ... Skipping packages with broken dependencies: authselect i686 1.0.1-1.fc28 updates-testing 57 k authselect-compat i686 1.0.1-1.fc28 updates-testing 33 k authselect-libs i686 1.0.1-1.fc28 updates-testing 116 k

authselect-libs-1.0.1-1 requires systemctl. Making authselect-libs-1.0.1-1 require /usr/bin/systemctl as provided by systemd-0:238-9.git0e0aa59.fc28 might resolve the error.

This version has been running as usual. checksec --kernel shows GCC stack protector support: Disabled while the kernel configuration has the strong stack protector enabled (which also happened with 1.7.4-6). I described that issue in more detail in the following bugzilla entry. https://bugzilla.redhat.com/show_bug.cgi?id=1632412

The upstream URL was updated to https://github.com/slimm609/%{name}.sh in checksec.spec for F28, but the upstream link on https://src.fedoraproject.org/rpms/checksec is still http://www.trapkit.de/tools/checksec.html

This version runs normally. The default tests passed or skipped. The tools directory had some changed files in the 4.18.9 and 4.18.8 diffstats e.g. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/?id=v4.18.9&id2=v4.18.8&dt=2 , but kernel-tools packages don't appear to have been built on Koji for those versions.

This version has been running as usual. The default tests passed or skipped.

This version has been running normally. All the default tests passed or skipped.

This update displays various PDF files normally.

The Fedora Updates Policy mentions that KDE SIG was given an exception for stable releases https://fedoraproject.org/wiki/Updates_Policy Standard support for the Qt 5.10 branch ends on October 30, 2018, while the 5.11 branch is supported for a year after its release on May 22 according to https://en.wikipedia.org/wiki/Qt_version_history

The dnf error I mentioned with pipewire-0.2.3 and xdg-desktop-portal-kde-5.13.4-2 has been reported by a few others https://bugzilla.redhat.com/show_bug.cgi?id=1626133 https://bugzilla.redhat.com/show_bug.cgi?id=1626823 FEDORA-2018-973e14809c

This version has been running normally.

Firefox and Thunderbird have been working normally with this update.

I haven't seen any new denials with this update. The denials involving boltd, gdm, polkit, and dbus after gdm and lightdm start which I reported aren't happening with this update. https://bugzilla.redhat.com/show_bug.cgi?id=1625786

I haven't seen any new denials with this update. The denials involving boltd, gdm, polkit, and dbus after gdm and lightdm start which I reported aren't happening with this update. https://bugzilla.redhat.com/show_bug.cgi?id=1625786

This version has been running normally. The cachedrop test failed once with the error "Can't free dentries and inodes". I saw that error on most runs from 4.17.14 to 4.17.19, while I didn't see any cachedrop errors from 4.17.2 to 4.17.12. I've submitted the test logs for those versions. All other tests passed or skipped.

I installed cura-lulzbot on F28. cura-lulzbot started without problems after about 3 minutes, and its interface functioned fine. I don't have a 3d printer to test cura-lulzbot with.

Of course those using just the updates repo could skip the pipewire-0.2.3 update or just enable updates testing to upgrade to it and xdg-desktop-portal-kde-5.13.4-4. I'm sorry about the mixup.

The kalzium interface issue was because of abnormal configuration settings in ~/.config/kalziumrc which I fixed by renaming that file. All the parts of kalzium interface are visible to me, and those I've tested are functional. I opened a few molecules in kalzium's molecular editor which I suppose uses avogadro2-libs which all appeared correctly. So I'll give +1 for kalzium and its use of avogadro2-libs.

xdg-desktop-portal-kde-5.13.4-4 depends on libQt5Core.so.5(Qt_5.11) so moving xdg-desktop-portal-kde-5.13.4-4 to stable without the rest of this update would just lead to other dnf errors. I don't know how to get around that other than a rebuild of xdg-desktop-portal-kde-5.13.4 with Qt 5.10.1.

The issue I mentioned with kalzium was caused by unintentionally abnormal configuration settings in ~/.config/kalziumrc and is now resolved; that problem was unrelated to the Qt 5.11.1 or kf5 5.48 updates. A user has reported the same dnf error I saw after pipewire-0.2.3 was pushed to stable, so a way to get xdg-desktop-portal-kde-5.13.4-4 into stable more quickly than the rest of this update might be advisable.

This version has been functioning normally for me. I noted selinux denials between boltd, polkit, gdm, and dbus when booting with gdm enabled, and when I stopped gdm and started lightdm the denial of send_msg between polkit and boltd occurred many times. When I disabled gdm, enabled lightdm, and rebooted I didn't see any denials I think since lightdm didn't start boltd. I filed the following bugzilla entry which describes these denials in more detail. https://bugzilla.redhat.com/show_bug.cgi?id=1625786

The issue with kalzium's interface I referred to was still present after I downgraded to Qt 5.10.1, and so the problem is most likely not in Qt 5.11.1 but maybe in some other package such as in kf5*5.48.

I've been running this version for the last few days which I downloaded from Koji, and it has been running normally.