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