dracut-shutdown.service failed due to dracut-initramfs-restore errors opening initrd when rebooting or shutting down with dracut-056-1.fc36. I reported this problem at https://bugzilla.redhat.com/show_bug.cgi?id=2071306
A dnf problem indicated that qt5-qtimageformats-5.15.2-5.fc36.x86_64 requires libjasper.so.4()(64bit), but jasper-libs-3.0.2-1.fc36.x86_64 provides libjasper.so.6()(64bit) https://koji.fedoraproject.org/koji/rpminfo?rpmID=29769393 I reported the problem at https://bugzilla.redhat.com/show_bug.cgi?id=2064018
@adamwill The Sleep, Restart, Shut down, and Other options were always visible in sddm on X for the last few years, so it is a change in behaviour at least. I've had to click on the Virtual keyboard, Keyboard layout, or Desktop session boxes to see and use those options in sddm on Wayland, which is counterintuitive to me as those functions seem unrelated.
The Sleep, Restart, Shut down, and Other options disappeared each time the Password box was selected such as less than a second after sddm on Wayland started or when I clicked on the Password box. Clicking on the Virtual Keyboard, Keyboard layout and Desktop session boxes made the Sleep, Restart, Shut down, and Other options reappear until I clicked on the Password box. The Virtual Keyboard still didn't show up when I clicked its box. Clicking on Keyboard layout and Desktop session boxes made the menus open without the flickering problem at https://bugzilla.redhat.com/show_bug.cgi?id=2054016. The keyboard layout can be changed, but its setting didn't persist on the next boot. Clicking the login button in sddm on Wayland with a correct password logged in to Plasma on Wayland each time using plasma-workspace-5.24.2-3.fc36 and sddm-0.19.0^git20220228.c257a40-3.fc36 and with an incorrect password showed Login failed. https://bugzilla.redhat.com/show_bug.cgi?id=2059837
The logout of Plasma to the console login prompt problem due to the sddm-greeter crash when logging in hasn't happened with sddm-0.19.0^git20220228.c257a40-2.fc36 https://bugzilla.redhat.com/show_bug.cgi?id=2057419 The sddm segmentation fault when logging in as the second user on the system hasn't happened since sddm-0.19.0^git20220224.5ad9f19-1.fc36 https://bugzilla.redhat.com/show_bug.cgi?id=2056308
The Sleep, Restart, Shut down, and Other options were missing from sddm on Wayland except briefly when starting, clicking on the Virtual keyboard, Keyboard layout, Desktop session, login button, or when logging in https://bugzilla.redhat.com/show_bug.cgi?id=2058468 The virtual keyboard doesn't appear at all when clicking on its box, and when I clicked on the Keyboard layout and Desktop session boxes, the screen was flickering https://bugzilla.redhat.com/show_bug.cgi?id=2054016 and https://bugzilla.redhat.com/show_bug.cgi?id=2055627 Clicking the login button in sddm on Wayland didn't log in to Plasma on Wayland most of the time as I reported at https://bugzilla.redhat.com/show_bug.cgi?id=2059837 Clicking on the login button with an incorrect password entered didn't show an error message Login failed most of the time. sddm on Wayland using the Weston compositor from sddm-wayland-generic resulted in a black screen shortly after starting https://bugzilla.redhat.com/show_bug.cgi?id=2058947
The systemd-resolved-250.3-5.fc36.x86_64 posttrans scriptlet failed because /etc/resolv.conf existed when ln failed to created that symbolic link. I reported the error in more detail at https://bugzilla.redhat.com/show_bug.cgi?id=2058388
5.15.14 doesn't sleep properly on a laptop with an integrated Radeon R5 GPU, and the system becomes unresponsive with a black screen as I reported at https://bugzilla.redhat.com/show_bug.cgi?id=2039621 I bisected between 5.15.13 and 5.15.14, and the first bad commit was 3c196f05666610912645c7c5d9107706003f67c3 drm/amdgpu: always reset the asic in suspend (v2) Alex Deucher wrote a patch at https://gitlab.freedesktop.org/drm/amd/-/issues/1858#note_1217823 I built 5.15.14 after applying 0001-drm-amdgpu-don-t-do-resets-on-APUs-which-don-t-suppo.patch, and that kernel slept and woke up normally. 5.15.14 has run correctly otherwise.
vid.stab-1.1.0-18.20201110gitf9166e9.fc35 provides libvidstab.so.1.2()(64bit) https://koji.fedoraproject.org/koji/rpminfo?rpmID=28575114 but ffmpeg-libs-4.4.1-4.fc35.x86_64 from rpmfusion requires libvidstab.so.1.1()(64bit) resulting in the dnf problem at https://bugzilla.rpmfusion.org/show_bug.cgi?id=6178 mlt-6.26.1-3.fc35.x86_64 from fedora also requires libvidstab.so.1.1()(64bit) though I don't have it installed.
Booting with grub2-2.06-9.fc35 and UEFI Secure Boot enabled resulted in Error: Verification Failed: (0x1A) Security Violation. I reported this problem at https://bugzilla.redhat.com/show_bug.cgi?id=2030940
There's a dnf error with kwin when trying to update. kwin, plasma-workspace, plasma-breeze, kde-cli-tools, kde-gtk-config, kdeplasma-addons, khotkeys, kmenuedit, kscreen, ksystemstats, plasma-browser-integration, plasma-desktop, plasma-integration, plasma-systemmonitor, plasma-systemsettings, powerdevil, and maybe other Plasma packages are missing from the update. 5.23.2 F35 builds of those packages don't appear in koji. I reported this problem at https://bugzilla.redhat.com/show_bug.cgi?id=2018846
I updated to zram-generator-1.0.1-3.fc35 from https://koji.fedoraproject.org/koji/buildinfo?buildID=1848938 which ran normally without the errors in https://bugzilla.redhat.com/show_bug.cgi?id=2017497 zram-generator-1.0.1-3.fc35 might need to be added to this or another update.
sddm-0.19.0-18.fc35 showed Plasma (Wayland) and GNOME on Wayland normally in its Desktop sessions list. I've logged into Plasma on Wayland as usual with it. Thanks. Since the latest patch removes the lines with /etc/sddm/hide-wayland-sessions from 61-sddm-plasmawayland.rules https://src.fedoraproject.org/rpms/sddm/c/52dc921f03abf4524bb2ca249ef28cf78b8c0e4a?branch=f35 Zbigniew's problem at https://bugzilla.redhat.com/show_bug.cgi?id=1966653 might also be fixed by it.
I ran sudo dnf offline-upgrade download (with updates-testing enabled) then sudo dnf offline-upgrade reboot in a Fedora 35 KDE Plasma installation. The update included zram-generator-1.0.1-1.fc35. On the boot after the update, I pressed Esc while the plymouth screen was shown. Errors like "Failed to start Create swap on /dev/zram0." were shown repeatedly on the screen. The journal showed errors which I reported at https://bugzilla.redhat.com/show_bug.cgi?id=2017497
I ran sudo dnf offline-upgrade download with updates-testing enabled then sudo dnf offline-upgrade reboot in a Fedora 35 KDE Plasma spin installation with the GNOME desktop group installed. The update included sddm-0.19.0-17.fc35 and had the following warning: /etc/sddm.conf created as /etc/sddm.conf.rpmnew On the next boot the Desktop Session: option showed GNOME Classic instead of Plasma (Wayland) which I had been using. Plasma (Wayland) and GNOME on Wayland weren't in the list of desktop sessions anymore. sddm-0.19.0-17.fc35 didn't allow logging in to the Plasma on Wayland desktop session as a result. I downgraded to sddm-0.19.0-16 and rebooted. Plasma (Wayland) and GNOME on Wayland were in the desktop sessions list again. I reported this problem at https://bugzilla.redhat.com/show_bug.cgi?id=2016788
I ran sudo dnf offline-upgrade download in a Fedora 35 KDE Plasma installation with updates-testing enabled. dnf problems with llvm-13.0.0-4.fc35, doxygen, mesa, and annobin-plugin-clang were shown which prevented the update of llvm. doxygen-1:1.9.1-11.fc35.x86_64 requires libclang-cpp.so.13.0()(64bit), and clang-libs-13.0.0-3.fc35 provides libclang-cpp.so.13()(64bit) https://koji.fedoraproject.org/koji/rpminfo?rpmID=28089067 mesa-dri-drivers-21.2.3-6.fc35.x86_64 requires libLLVM-13.so.0()(64bit), and llvm-libs-13.0.0-4.fc35 provides libLLVM-13.so()(64bit) https://koji.fedoraproject.org/koji/rpminfo?rpmID=28085618 annobin-plugin-clang looks to have the same problem as mesa. I reported these problems in more detail at https://bugzilla.redhat.com/show_bug.cgi?id=2014283
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.
I ran sudo dnf offline-upgrade download with updates-testing enabled in a Fedora 35 KDE Plasma installation with nodejs-1:16.5.0-2.fc35 and libuv-1:1.41.1-2.fc35 installed. dnf errors indicated that nothing provides libuv >= 1:1.42.0 needed by nodejs-1:16.8.0-1.fc35.x86_64 which I reported at https://bugzilla.redhat.com/show_bug.cgi?id=2002095 I updated to libuv-1.42.0-2.fc35 from https://koji.fedoraproject.org/koji/buildinfo?buildID=1827408 I updated nodejs without errors after that. libuv-1.42.0-2.fc35 might need to be added to this update.
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.