The kwin_wayland crash when logging out in https://bugzilla.redhat.com/show_bug.cgi?id=2001135 is fixed in kwin-5.22.5-3.fc35. Thanks.

5.13.4 still has the black screen problem when starting Plasma and GNOME on Wayland involving the amdgpu driver that I reported for previous 5.13 kernels at https://bugzilla.redhat.com/show_bug.cgi?id=1981039 I found that the first bad commit was in the 5.13 merge window using git bisect: 1f928f51593ca07e2b125ca862fcff687e9e498b drm/amdgpu: Use physical translation mode to access page table

This problem seems similar to that reported by @gbcox Adding amdgpu.dc=0 to the kernel command line allowed Plasma and GNOME on Wayland to run correctly. The default regression tests passed.

rng-tools-6.13-2.git.d207e0b6.fc34 and jitterentropy-3.0.2-2.git.409828cf.fc34 have lower versions than rng-tools-6.13.git.d207e0b6-1.fc34 and jitterentropy-3.0.2.git.d18d5863-1.fc34 previously in updates-testing according to dnf. I reported this problem in more detail at https://bugzilla.redhat.com/show_bug.cgi?id=1983847

rng-tools-6.13-2.git.d207e0b6.fc34 and jitterentropy-3.0.2-2.git.409828cf.fc34 have lower versions than rng-tools-6.13.git.d207e0b6-1.fc34 and jitterentropy-3.0.2.git.d18d5863-1.fc34 previously in updates-testing according to dnf. I reported this problem in more detail at https://bugzilla.redhat.com/show_bug.cgi?id=1983847

The dnf error in #1973894 didn't happen when I updated to rng-tools-6.13-2.fc34 and jitterentropy-3.0.2-1.fc34 from koji. rngd started normally with jitter entropy during the following boots according to systemctl status rngd. Thanks.

The dnf errors in https://bugzilla.redhat.com/show_bug.cgi?id=1972982 were fixed by the addition of KF 5.83.0 after I downloaded this update with bodhi updates download --updateid=FEDORA-2021-dcc1ce9423 A dnf error libksysguard-5.22.1-1.fc34.x86_64 conflicts with ksysguard-backend < 5.21.90 provided by ksysguard-backend-5.21.5-1.fc34.x86_64 occurred when I tried to update https://bugzilla.redhat.com/show_bug.cgi?id=1973378 The changes in https://src.fedoraproject.org/rpms/ksysguard/c/b3df63abc1e2cc692e16344b13db4fcf5c000080?branch=f34 look like they put the obsoletes and provides lines in the %description section of ksysguard.spec. ksysguard-5.22.0-2.fc34 doesn't obsolete ksysguard-backend < 5.21.90-2 and provide ksysguard-backend = %{version}-%{release} as a result https://koji.fedoraproject.org/koji/rpminfo?rpmID=26567885 I could update working around that error by adding --best --allowerasing which removed ksysguard-backend. Plasma 5.21.1 seems to be running alright after that.

Plasma 5.21.2 on Wayland has run reasonably well. The ksysguard transaction test errors didn't happen with 5.21.2 https://bugzilla.redhat.com/show_bug.cgi?id=1933510#c2. Menus often didn't appear when first selected in Firefox Nightly 87.0a1-88.0a1 on Wayland in Plasma 5.21.0-5.21.2, but they've appeared normally with 5.21.2 https://bugzilla.mozilla.org/show_bug.cgi?id=1693317 System Settings 5.21.0 on Wayland aborted when clearing history of activities with a failed dbus assertion which was fixed in 5.21.2 https://bugzilla.redhat.com/show_bug.cgi?id=1930440

drkonqi crashed when trying to enter information about crashes with 5.21.2 and earlier, but they might be fixed with 5.21.3 https://bugzilla.redhat.com/show_bug.cgi?id=1930946 plasmashell 5.20.90-5.21.2 on Wayland crashed most of the time when changing Global theme in System settings, and a fix was written but doesn't appear to have been merged yet. https://bugzilla.redhat.com/show_bug.cgi?id=1924980

Firefox 86.0-88.0a1 menu items under the cursor usually haven't been highlighted in Plasma 5.21.2 and earlier, which doesn't happen in GNOME 40 beta https://bugzilla.redhat.com/show_bug.cgi?id=1936092 Flickering of right-click popup menus with multiple simultaneously highlighted entries in Thunderbird on Wayland has happened in Plasma 5.21.2 and earlier but not in GNOME https://bugzilla.redhat.com/show_bug.cgi?id=1936224

dnf showed a transaction test error that the files from ksysguard-plugins-5.21.1-3.fc34.x86_64 conflict with ksysguard-libs-5.21.1-2.fc34.x86_64 https://bugzilla.redhat.com/show_bug.cgi?id=1933510#c2

kstars-3.4.3-4.fc33 fixed the crash when starting in #1881915. kstars has run normally. Thanks.

I was setting up a Firefox build environment in F33 using the instructions at https://firefox-source-docs.mozilla.org/setup/linux_build.html dnf errors occurred while python3 bootstrap.py was running the following command, sudo dnf install autoconf213 nodejs which npm redhat-rpm-config

Problem 1: cannot install the best candidate for the job - nothing provides libuv >= 1:1.39.0 needed by nodejs-1:14.10.0-1.fc33.x86_64 Problem 2: package npm-1:6.14.8-1.14.10.0.1.fc33.x86_64 requires nodejs = 1:14.10.0-1.fc33, but none of the providers can be installed - cannot install the best candidate for the job - nothing provides libuv >= 1:1.39.0 needed by nodejs-1:14.10.0-1.fc33.i686 - nothing provides libuv >= 1:1.39.0 needed by nodejs-1:14.10.0-1.fc33.x86_64

libuv-1.39.0-1.fc33 might need to be added to this update https://koji.fedoraproject.org/koji/buildinfo?buildID=1607495

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.