The sddm background was white after logging out of Plasma in the image Fedora-KDE-Live-x86_64-Rawhide-20221001.n.1.iso https://bugzilla.redhat.com/show_bug.cgi?id=2131638 Only the user icon and the password box and button could be seen. Most of the text wasn't visible because it was in white by default in the Breeze Fedora theme. This problem might be related to the f37-backgrounds-37.0.1-1.fc38 change from png to webp format backgrounds. A journal error showed that the png default background /usr/share/backgrounds/default.png couldn't be opened when the sddm white background problem happened. sddm-greeter[2556]:file:///usr/share/sddm/themes/01-breeze-fedora/Background.qml:21:5: QML Image: Cannot open file:///usr/share/backgrounds/default.png

/usr/share/backgrounds/default.png didn't exist on the live image Fedora-KDE-Live-x86_64-Rawhide-20221001.n.1.iso This problem might happen in F37 as well if /usr/share/backgrounds/default.png is still set for the sddm Breeze Fedora theme. @tseewald reported the sddm white background problem in F37 at the Qt 5.15.6 update https://bodhi.fedoraproject.org/updates/FEDORA-2022-d8cd3b01b7#comment-2732423

@tseewald I've seen the white SDDM background problem, but it was due to the Breeze Fedora SDDM theme background being set to a file which no longer existed instead of the xdg-desktop-portal-kde crashes with Qt 5.15.6 I reported at https://bugzilla.redhat.com/show_bug.cgi?id=2129479 I fixed the white SDDM background in System Settings > Startup and Shutdown > Login Screen (SDDM) > Change Background icon > Load from file and selected a background from /usr/share/wallpapers/F37/contents/images/ with the resolution of my screen. Selecting the Breeze theme in the Login Screen (SDDM) page also fixed this problem for me in the past.

libjxl-0.7.0-1.fc37 wasn't updated from libjxl-0.7.0rc-1.fc37 since dnf showed The same or higher version of libjxl is already installed, cannot update it. I reported this problem at https://bugzilla.redhat.com/show_bug.cgi?id=2129592

xdg-desktop-portal-kde crashed when run by sddm during boot with Qt 5.15.6 as reported at https://bugzilla.redhat.com/show_bug.cgi?id=2129479

The test image with this update 02007780-Fedora-KDE-Live-x86_64-FEDORA-2022-6f3ca6889e.iso has sddm-x11 installed https://bugzilla.redhat.com/show_bug.cgi?id=2110801#c14 sddm was running on X in QEMU/KVM VMs with that image in which I logged out of Plasma normally a few times. Updating a F37 KDE Plasma installation with this update left sddm-wayland-plasma installed, so plasma-workspace-5.25.4-2.fc37 kept sddm on Wayland if it was already installed which might be intended. Plasma on Wayland has run normally otherwise.

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

@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

rngd was denied using the setgid capability by SELinux after this update which made rngd.service fail to start. I reported this problem at https://bugzilla.redhat.com/show_bug.cgi?id=2058914

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.

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.