The abrt-server errors in #1860616 haven't been happening since the abrt-2.14.4-2.fc33 update at FEDORA-2020-59e144acee The traces have shown up in gnome-abrt for crashes which happened after that update. This update fixed the dnf error because gnome-abrt-1.3.6-3.fc33.x86_64 requires libreport-gtk.so.0 and libreport-gtk-2.14.0-6.fc33 provides libreport-gtk.so.1 in #1876015 for the update at FEDORA-2020-ef47dbae61 Thanks.

I tried to submit a crash with gnome-abrt. The process failed because the retrace server couldn't be reached and the option for processing the trace locally wasn't offered. --- Running report_uReport --- Failed to upload uReport to the server 'https://retrace.fedoraproject.org/faf' with curl: Could not resolve host: retrace.fedoraproject.org Error: curl_easy_perform: Couldn't resolve host name ('report_uReport' exited with 1)

I downloaded this update using the bodhi cli. This update should likely be submitted for testing in bodhi since it is just in the pending state and wasn't included in the latest updates-testing push.

I tried to upgrade to this update, but a dnf error indicated that gnome-abrt-1.3.6-3.fc33.x86_64 requires libreport-gtk.so.0. libreport-gtk-2.14.0-6.fc33 provides libreport-gtk.so.1. I reported this error in more detail at https://bugzilla.redhat.com/show_bug.cgi?id=1876015

This update fixed the problem with lzo not starting when running lzop 1807737 and openvpn 1802299. Thanks.

The udev-configure-printer aborts in #1764663 were fixed in this update. Thanks.

5.3.8 has run as before. The default tests passed except for paxtest.

5.3.5 has run like previous 5.3 kernels. paxtest had the error "Main executable randomisation (PIE) randomness is less than 28 bits (26)". The other default tests passed or skipped. The ethernet transmit queue time outs in #1733837 and the wifi errors in #1733723 and #1760658 have still happened with 5.3.5.

I ran sudo dnf upgrade --refresh, and I got problems with the qt5 5.12.5 update involving "qt5-qtnetworkauth-5.12.4-2.fc31.x86_64 requires libQt5Core.so.5(Qt_5.12.4_PRIVATE_API)(64bit), but none of the providers can be installed" which I reported at https://bugzilla.redhat.com/show_bug.cgi?id=1757945

qt5-qtnetworkauth-5.12.5 might need to be built for F31 and added to this update. Many of the KDE PIM applications and libraries depend on qt5-qtnetworkauth, so one can't upgrade to qt 5.12.5 without qt5-qtnetworkauth-5.12.5 if KDE PIM is installed.

firefox 69 and thunderbird 68 (from koji) have run normally with nss 3.46 and nspr 4.22.

dnf-4.2.7-2 has run normally. I didn't see the crashes in #1727343 again with libdnf-0.35.1-2. Thanks.

The problem with the menus in konsole, okular, kate, etc. not appearing sometimes reported in #1732187 is fixed by this update. Plasma and various KDE applications have run normally. Thanks.

5.1.17 has run mostly alright. My system became much slower to respond when I tried to install the firefox-debuginfo-68.0-4 rpm. Plasma crashed, and I selected restart from sddm. There was a kernel panic involving do_exit.cold after the power down systemd target which I hadn't seen before. I could report that with more details.

I haven't seen the segmentation faults in plasmashell reported in #1723017 and #1723018 after updating to qt5-qtwayland-5.12.4-3 in two days of using Plasma on Wayland. Thanks for the update.

I saw a segmentation fault in PackageKit in libdnf::Repo::Impl::detachLibsolvRepo at /usr/src/debug/libdnf-0.35.1-1.fc30.x86_64/libdnf/repo/Repo.cpp:1347 I reported the crash in #1727343 Should that report be reassigned to libdnf?

60.7.2 has run normally.

5.1.12 has run normally. paxtest had the error "Main executable randomisation (PIE) randomness is less than 28 bits (25)". The other default tests passed.

@adamwill I didn't see the post-install scriptlet error for libvirt-daemon-driver-network-5.1.0-8, but that error showed up when the post-uninstall scriptlet of libvirt-daemon-driver-network-5.1.0-7 ran. I think that scriptlet error is fixed in 5.1.0-8. The error in #1699051 didn't show up in my journal after upgrading to 5.1.0-7. Thanks. I haven't tested libvirtd 5.1.0-8.

5.1.5 has run normally. The default tests passed or skipped.

I noticed the following error in the post-install scriptlet of libvirt-daemon-driver-network-5.1.0-7 when I ran sudo dnf upgrade --refresh (with updates-testing enabled)

Upgrading : libvirt-daemon-driver-network-5.1.0-7.fc30.i686 4/62 Running scriptlet: libvirt-daemon-driver-network-5.1.0-7.fc30.i686 4/62 /var/tmp/rpm-tmp.4QVoaS: line 1: fg: no job control warning: %post(libvirt-daemon-driver-network-5.1.0-7.fc30.i686) scriptlet failed, exit status 1

Error in POSTIN scriptlet in rpm package libvirt-daemon-driver-network

That scriplet appears to reload firewalld as follows %post daemon-driver-network %if %{with_firewalld} %firewalld_reload %endif

I have firewalld running, but libvirtd isn't running.

5.0.17 has run normally. The default tests passed or skipped.

5.0.14 has run normally.