On Fri, Feb 10, 2023 at 5:52 PM Adam Williamson <awilliam(a)redhat.com&gt; wrote: You'll find out with tomorrow's compose as linux-firmware-20230210-147.fc38 has my upstreamed changes.

On Fri, 2023-02-17 at 14:45 -0500, Ben Cotton wrote: This went under the limit for like two days when the linux-firmware change landed, but then bounced back over it recently. I didn't yet get time to check out why, too much fire. I actually fixed this a few days ago, we can probably close it. I've done that. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw(a)fosstodon.org https://www.happyassassin.net

The current target release date is the early target date (2023-03-14). The Go/No-Go meeting will be Thursday! Action summary ==================== Accepted blockers ----------------- 1. distribution — Workstation boot x86_64 image exceeds maximum size — POST ACTION: gdb maintainers to remove the 'Recommends' for gcc-gdb-plugin from gdb 2. crypto-policies — Insecure installed RPMs (like Google Chrome) prevent system updates in F38, can't be removed — NEW ACTION: Upstream to implement MR #129 Proposed blockers ----------------- 1. gnome-session — reboot/poweroff/logout from GNOME are 60 seconds delayed without 3D acceleration — NEW ACTION: Maintainers to diagnose issue 2. gnupg2 — revert the RFC4880bis from defaults — NEW ACTION: Maintainers to revert inclusion of RFC4880bis 3. initial-setup — User creation and root password setting do not work on minimal install, so cannot log into installed system — NEW ACTION: Maintainers to diagnose issue 4. kernel — Black screen when amdgpu started during 6.2-rc1 boot with AMD IOMMU enabled — NEW ACTION: Maintainers to package update which includes upstream patches 5. mutter — XWayland apps steal focus — NEW ACTION: Maintainers to build update with upstream merge request 6. sddm — Virtual keyboard (on-screen) not working at sddm-wayland-plasma — NEW ACTION: Maintainers to diagnose issue Bug-by-bug detail ============= Accepted blockers ----------------- 1. distribution — https://bugzilla.redhat.com/show_bug.cgi?id=2149246 — POST Workstation boot x86_64 image exceeds maximum size Changes to linux-firmware briefly brought the Worktation image below the limit. Removing the recommendation (in gdb) of gcc-gdb-plugin, which is "largely broken", should reduce the image size below limits. 2. crypto-policies — https://bugzilla.redhat.com/show_bug.cgi?id=2170878 — NEW Insecure installed RPMs (like Google Chrome) prevent system updates in F38, can't be removed Some third-party repos (including Google Chrome) that sign packages with SHA-1 cannot be uninstalled, which breaks upgrades. This was designated a blocker by FESCo. Work is in progress upstream to allow RPM to permit SHA-1 in the default policy while third-party repos update to a supported hash function: https://gitlab.com/redhat-crypto/fedora-crypto-policies/-/merge_requests/129 Proposed blockers ----------------- 1. gnome-session — https://bugzilla.redhat.com/show_bug.cgi?id=2174753 — NEW reboot/poweroff/logout from GNOME are 60 seconds delayed without 3D acceleration On machines (physical and virtual) without 3D acceleration, clicking the reboot/poweroff/logout buttons has no apparent effect for 60 seconds. A second click or using command line commands works immediately. 2. gnupg2 — https://bugzilla.redhat.com/show_bug.cgi?id=2175155 — NEW revert the RFC4880bis from defaults GnuPG 2.4.0 made a potentially-incompatible change. A PR is pending to revert this: https://src.fedoraproject.org/rpms/gnupg2/pull-request/15 3. initial-setup — https://bugzilla.redhat.com/show_bug.cgi?id=2175244 — NEW User creation and root password setting do not work on minimal install, so cannot log into installed system On the Minimial image only, initial-setup silently fails to create a user. This results in a system with no usable user account. 4. kernel — https://bugzilla.redhat.com/show_bug.cgi?id=2156691 — NEW Black screen when amdgpu started during 6.2-rc1 boot with AMD IOMMU enabled Kernel 6.2.0 introduced an issue that causes the system to hang when booting with amdgpu. There are upstream patches targeted for 6.2.2 that contain a candidate fix. 5. mutter — https://bugzilla.redhat.com/show_bug.cgi?id=2173985 — NEW XWayland apps steal focus Alt+Tab switching, as well as (sometimes) clicking on windows does not focus the window. This seems to largely affect Wine, Java, and Chromium applications. This may have been introduced by upstream commit a68b8e95. Upstream MR #2841 has a fix for Chrome and Electron apps. 6. sddm — https://bugzilla.redhat.com/show_bug.cgi?id=2174563 — NEW Virtual keyboard (on-screen) not working at sddm-wayland-plasma The virtual keyboard at the login screen does not appear when you click the appropriate button. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

The current target is the early target date (18 April). Action summary ==================== Accepted blockers ----------------- 1. fcoe-utils — anaconda failed to detect the fcoe target(only affects ixgbe) — NEW ACTION: Maintainer to diagnose issue NEEDINFO: cleech 2. gnome-calendar — After a few searches, search no longer works and cpu is at 100% — VERIFIED ACTION: none 3. gnome-maps — A quick movement breaks tile rendering, gets you banned at the server — VERIFIED ACTION: none 4. gnome-shell — Logout/reboot/poweroff timeout leaves the session in a broken state, doesn't perform the action — POST ACTION: Maintainer to build an update that contains upstream MR #2696 5. gtk4 — With GTK 4.9.1 , Nautilus' target for "Move To" or "Copy To" operations is unexpected and can be invalid — VERIFIED ACTION: none 6. kernel — The kernel sometimes does not initialize SimpleDRM when booting in basic graphics mode on BIOS, causing SDDM to fail — NEW ACTION: Everyone to agree on a suitable workaround 7. mutter — Session crash when reverting Display settings — VERIFIED ACTION: none 8. mutter — Crash when using Win+P shortcut — VERIFIED ACTION: none 9. nautilus — Dragging files is Nautilus doesn't work as expected, quick movements result in a selection box instead — VERIFIED ACTION: none 10. openssh — Update hostkey migration to support OSTree systems and dynamically detect hostkey location — POST ACTION: fedora-release and openssh maintainers to merge pending pull requests 11. sddm — Virtual keyboard (on-screen) not working at sddm-wayland-plasma — NEW ACTION: Maintainers to diagnose issue or revert to using X11 12. shim — Live image made with BOOTX64.EFI from latest shim-x64-15.6-2 fails to boot on some boards — NEW ACTION: kernel upstream to merge NX support Proposed blockers ----------------- 1. f38-backgrounds — The default wallpaper isn't listed among available wallpapers — VERIFIED ACTION: none 2. gnome-abrt — crash data are erased occasionally — NEW ACTION: Maintainer to diagnose issue 3. gnome-calendar — Crash/Hang when clicking a modified Google event right after editing it (due to the preview popover) — NEW ACTION: Upstream to diagnose issue 4. ibus — ibus: XFree(): ibus-x11 killed by SIGABRT — MODIFIED ACTION: QA or reporter to verify FEDORA-2023-e0df9e598e 5. mutter — Fullscreen mode is broken for many games — POST ACTION: Maintainer to create an update the contains upstream MR #2910 6. xdg-desktop-portal-kde — xdg-desktop-portal-kde is launching and crashing when SDDM launches the Wayland greeter — NEW ACTION: Maintainer to diagnose issue Bug-by-bug detail ============= Accepted blockers ----------------- 1. fcoe-utils — https://bugzilla.redhat.com/show_bug.cgi?id=2171350 — NEW anaconda failed to detect the fcoe target(only affects ixgbe) The installer does not detect attached FCOE storage using ixgbe. SELInux warnings appear, but it runs in passive mode, so that is not the root cause. 2. gnome-calendar — https://bugzilla.redhat.com/show_bug.cgi?id=2177992 — VERIFIED After a few searches, search no longer works and cpu is at 100% Several searches result in full CPU and memory utilization, even after closing the application. FEDORA-2023-35421ab32a contains a verified fix. 3. gnome-maps — https://bugzilla.redhat.com/show_bug.cgi?id=2177995 — VERIFIED A quick movement breaks tile rendering, gets you banned at the server Some actions in gnome-maps that involve animations result in being temporarily banned by the server. FEDORA-2023-b3146555f6 contains a verified fix for the blocking behavior. Additional non-blocking behavior remains to be fixed: https://gitlab.gnome.org/GNOME/gnome-maps/-/issues/546 4. gnome-shell — https://bugzilla.redhat.com/show_bug.cgi?id=2177853 — POST Logout/reboot/poweroff timeout leaves the session in a broken state, doesn't perform the action When a user lets the logout/reboot/poweroff confirmation timeout, everything is grayed out and the mouse can't click on anything, but the keyboard can still be used. Upstream MR https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2696 contains a candidate fix. 5. gtk4 — https://bugzilla.redhat.com/show_bug.cgi?id=2173891 — NEW With GTK 4.9.1 , Nautilus' target for "Move To" or "Copy To" operations is unexpected and can be invalid Copying or moving a file to a directory that is not empty results in failure. Empty directory targets work. FEDORA-2023-b6f25977ef contains a verified fix. 6. sddm — https://bugzilla.redhat.com/show_bug.cgi?id=2176782 — NEW The kernel sometimes does not initialize SimpleDRM when booting in basic graphics mode on BIOS, causing SDDM to fail In BIOS mode only, sddm results in a blank screen when using basic graphics mode. This is the result of a SimpleDRM device not being created. gdm uses a fallback to x11 in this scenario, so it works. Configuring GRUB to use a gfxterm for BIOS boots may be a workaround. The proposed `vga=normal` workaround does not appear to work. 7. mutter — https://bugzilla.redhat.com/show_bug.cgi?id=2175809 — VERIFIED Session crash when reverting Display settings Applying a change to Display settings and then reverting (or pressing Escape when presented with the revert dialog) results in a crash. Letting the dialog window time out does not crash. FEDORA-2023-6cec60a347 contains a verified fix. 8. mutter — https://bugzilla.redhat.com/show_bug.cgi?id=2177982 — VERIFIED Crash when using Win+P shortcut Using Win+P to switch between displays configuration crashes gnome-shell. FEDORA-2023-6cec60a347 contains a verified fix. 9. nautilus — https://bugzilla.redhat.com/show_bug.cgi?id=2176766 — VERIFIED Dragging files is Nautilus doesn't work as expected, quick movements result in a selection box instead In order to successfully drag-and-drop a file, you must first hold the mouse still with the left button pressed for ~half a second. FEDORA-2023-287e6e502b contains a verified fix. 10. openssh — https://bugzilla.redhat.com/show_bug.cgi?id=2172956 — POST Update hostkey migration to support OSTree systems and dynamically detect hostkey location rpm-ostree systems don't run RPM scriptlets on upgrade, which could result in an upgrade locking users out of remote machines. Package pull requests https://src.fedoraproject.org/rpms/fedora-release/pull-request/253 and https://src.fedoraproject.org/rpms/openssh/pull-request/45 contain a candidate fix. 11. sddm — https://bugzilla.redhat.com/show_bug.cgi?id=2174563 — NEW Virtual keyboard (on-screen) not working at sddm-wayland-plasma The virtual keyboard at the login screen does not appear when you click the appropriate button. This appears to be a Wayland-specific issue; reverting to X11 allows the keyboard to work as expected. 12. shim — https://bugzilla.redhat.com/show_bug.cgi?id=2113005 — NEW Live image made with BOOTX64.EFI from latest shim-x64-15.6-2 fails to boot on some boards UEFI LoadOptions that start with NUL cause boot failure. This is fixed upstream in https://github.com/rhboot/shim/pull/505 but the SecureBoot signing process requires NX support in the kernel, which is still pending upstream. Proposed blockers ----------------- 1. f38-backgrounds — https://bugzilla.redhat.com/show_bug.cgi?id=2178172 — VERIFIED The default wallpaper isn't listed among available wallpapers The default background is correctly applied, but if the users switches to a different wallpaper, the default is not visible in the selection. FEDORA-2023-359dafca1d contains a verified fix. 2. gnome-abrt — https://bugzilla.redhat.com/show_bug.cgi?id=2177153 — NEW crash data are erased occasionally It appears that abrt is removing report data when disk usage exceeds a threshold, but it's not clear why the reporter is expericing this worse than others. There may be some user experience improvements to make. In any case, the vote looks likely to be for rejecting this as a blocker. 3. gnome-calendar — https://bugzilla.redhat.com/show_bug.cgi?id=2177993 — NEW Crash/Hang when clicking a modified Google event right after editing it (due to the preview popover) Clicking on a remote event immediately after editing it results in either a crash or an unresponsive window. Waiting a few seconds before clicking results in expected behavior. 4. ibus — https://bugzilla.redhat.com/show_bug.cgi?id=2156108 — MODIFIED ibus: XFree(): ibus-x11 killed by SIGABRT Typing is sometimes "sluggish" with frequent pauses. Eventually ibus crashes. FEDORA-2023-e0df9e598e contains a candidate fix. 5. mutter — https://bugzilla.redhat.com/show_bug.cgi?id=2178167 — POST Fullscreen mode is broken for many games Many games fail to work in fullscreen and if they launch in fullscreen, they may not be usable at all. Upstream MR https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2910 contains a candidate fix. 6. xdg-desktop-portal-kde — https://bugzilla.redhat.com/show_bug.cgi?id=2178971 — NEW xdg-desktop-portal-kde is launching and crashing when SDDM launches the Wayland greeter When the greeter launches, xdg-desktop-portal-kde also launches and crashes. This appears to only happen on Wayland. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

The current target is the early target date (18 April). Action summary ==================== Accepted blockers ----------------- 1. kernel — anaconda failed to detect the fcoe target(only affects ixgbe) — NEW ACTION: Maintainers to diagnose issue NEEDINFO: lnie 2. plasma-workspace — Logging out of Plasma 5.27.3 on Wayland as the second user on the system resulted in a black screen — NEW ACTION: Maintainers to diagnose issue 3. shim — Live image made with BOOTX64.EFI from latest shim-x64-15.6-2 fails to boot on some boards — NEW ACTION: kernel upstream to merge NX support Proposed blockers ----------------- 1. abrt — crash data are erased occasionally — VERIFIED ACTION: (none) 2. Podman — shadow-utils installations fails with “cap_set_file failed” in toolbox/podman on F38 host ACTION: Maintainers to diagnose issue Bug-by-bug detail ============= Accepted blockers ----------------- 1. kernel — https://bugzilla.redhat.com/show_bug.cgi?id=2171350 — NEW anaconda failed to detect the fcoe target(only affects ixgbe) The installer does not detect attached FCOE storage using ixgbe. The device ends up in "NO-CARRIER state DORNMANT". 2. plasma-workspace — https://bugzilla.redhat.com/show_bug.cgi?id=2179591 — NEW Logging out of Plasma 5.27.3 on Wayland as the second user on the system resulted in a black screen In some cases, a race condition prevents a user on a system from logging out successfully. This appears to be an SELinux issue filed as RHBZ 2181010 for which FEDORA-2023-624eb88729 contains a verified fix. It seems that a failure of dbus-:1.2-org.kde.LogoutPrompt@0.service causes the sddm session to not be restarted. 3. shim — https://bugzilla.redhat.com/show_bug.cgi?id=2113005 — NEW Live image made with BOOTX64.EFI from latest shim-x64-15.6-2 fails to boot on some boards UEFI LoadOptions that start with NUL cause boot failure. This is fixed upstream in https://github.com/rhboot/shim/pull/505 but the SecureBoot signing process requires NX support in the kernel, which is still pending upstream. Proposed blockers ----------------- 1. abrt — https://bugzilla.redhat.com/show_bug.cgi?id=2177153 — VERIFIED MaxCrashReportsSize claims to be 5000 MB but is 1000 MB abrt is using a smaller size limit than the hard-coded default of 5000 MB. FEDORA-2023-eb09dd6406 containes a verified fix. 2. podman — https://bugzilla.redhat.com/show_bug.cgi?id=2183034 — NEW packages with file capabilities fail to install in podman on F38 host DNF update in a freshly-created f38 toolbox fails. The issue seems to only happen on F38 hosts; shadow-utlis is updatable in an F36 and F37 container and host using podman 4.4.1. Suspected issue is a change in Podman between 4.4.2 -> 4.4.3 or a different config file in F38. This does not appear to be specific to the shadow-utils package. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis