We've branched F38 from Rawhide, so it's time to start everyone's favorite Friday email from Ben! The F38 Beta freeze begins on 21 February. The current target release date is the early target date (2023-03-14).
Action summary ====================
Accepted blockers -----------------
1–3. distribution — {Workstation,Everything,Server} boot x86_64 image exceeds maximum size — ASSIGNED ACTION: Relevant Teams to reduce image size or increase the limit
Proposed blockers -----------------
1. anaconda — installer fails to boot in text mode or rescue mode with systemd 253 — MODIFIED ACTION: Maintainers to build an update that includes upstream PR
2. grub2 — ext4 filessystem support missing — NEW ACTION: Maintainer to diagnose issue NEEDINFO: ausil
3. kwin — kwin_wayland often crashed when used as the sddm Wayland compositor and logging out of Plasma resulting in a black screen — NEW ACTION: Maintainer to diagnose issue
4. mesa — KDE crashes on start with mesa-23.0.0~rc3-3.fc38 — ASSIGNED ACTION: Maintainer to diagnose issue
Bug-by-bug detail =============
Accepted blockers -----------------
1–3. distribution — {Workstation,Everything,Server} boot x86_64 image exceeds maximum size — ASSIGNED https://bugzilla.redhat.com/show_bug.cgi?id=2149246 https://bugzilla.redhat.com/show_bug.cgi?id=2151495 https://bugzilla.redhat.com/show_bug.cgi?id=2151497
Image sizes exceed the specified limits. The choices are to either shrink the image by removing packages or to riase the limits.
Proposed blockers -----------------
1. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2165433 — MODIFIED installer fails to boot in text mode or rescue mode with systemd 253
anaconda is writing systemd units to an unexpected area. Upstream PR 4534 contains a candidate fix: https://github.com/rhinstaller/anaconda/pull/4534
2. grub2 — https://bugzilla.redhat.com/show_bug.cgi?id=2166412 — NEW ext4 filessystem support missing
Between grub2-2.06-76 and grub2-2.06-78, grub2 apparently lost the ability to detect ext4 filesystems.
3. kwin — https://bugzilla.redhat.com/show_bug.cgi?id=2168034 — NEW kwin_wayland often crashed when used as the sddm Wayland compositor and logging out of Plasma resulting in a black screen
Logging out of Plasma sometimes triggers a kwin crash. This may be limited to running in a virtual machine.
4. mesa — https://bugzilla.redhat.com/show_bug.cgi?id=2164667 — ASSIGNED KDE crashes on start with mesa-23.0.0~rc3-3.fc38
A recent mesa update caused both GNOME and KDE to crash on start. Update FEDORA-2023-40b973fa06 fixed GNOME, but KDE is still seeing this issue. The root cause is still uncertain.
On Fri, 2023-02-10 at 08:47 -0500, Ben Cotton wrote:
Accepted blockers
1–3. distribution — {Workstation,Everything,Server} boot x86_64 image exceeds maximum size — ASSIGNED ACTION: Relevant Teams to reduce image size or increase the limit
Accepted blockers
1–3. distribution — {Workstation,Everything,Server} boot x86_64 image exceeds maximum size — ASSIGNED https://bugzilla.redhat.com/show_bug.cgi?id=2149246 https://bugzilla.redhat.com/show_bug.cgi?id=2151495 https://bugzilla.redhat.com/show_bug.cgi?id=2151497
Image sizes exceed the specified limits. The choices are to either shrink the image by removing packages or to riase the limits.
Well...not entirely. What I'm hoping we do to resolve this is get the linux-firmware changes from upstream:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/... https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/... https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/... https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/...
that *should* save a significant amount of space, hopefully enough to get the images back undersize.
On Fri, Feb 10, 2023 at 5:52 PM Adam Williamson awilliam@redhat.com wrote:
On Fri, 2023-02-10 at 08:47 -0500, Ben Cotton wrote:
Accepted blockers
1–3. distribution — {Workstation,Everything,Server} boot x86_64 image exceeds maximum size — ASSIGNED ACTION: Relevant Teams to reduce image size or increase the limit
Accepted blockers
1–3. distribution — {Workstation,Everything,Server} boot x86_64 image exceeds maximum size — ASSIGNED https://bugzilla.redhat.com/show_bug.cgi?id=2149246 https://bugzilla.redhat.com/show_bug.cgi?id=2151495 https://bugzilla.redhat.com/show_bug.cgi?id=2151497
Image sizes exceed the specified limits. The choices are to either shrink the image by removing packages or to riase the limits.
Well...not entirely. What I'm hoping we do to resolve this is get the linux-firmware changes from upstream:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/... https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/... https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/... https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/...
that *should* save a significant amount of space, hopefully enough to get the images back undersize.
You'll find out with tomorrow's compose as linux-firmware-20230210-147.fc38 has my upstreamed changes.
The F38 Beta freeze begins on 21 February. The current target release date is the early target date (2023-03-14).
Action summary ====================
Accepted blockers -----------------
1. distribution — Workstation boot x86_64 image exceeds maximum size — ASSIGNED ACTION: Workstation WG to reduce image size or increase the limit
Proposed blockers -----------------
1. glusterfs — libglusterd0 prevents upgrades to Fedora 38 — NEW ACTION: Maintainer to diagnose issue
2. kwin — kwin_wayland often crashed when used as the sddm Wayland compositor and logging out of Plasma resulting in a black screen — NEW ACTION: Maintainer to diagnose issue
Bug-by-bug detail =============
Accepted blockers -----------------
1. distribution — https://bugzilla.redhat.com/show_bug.cgi?id=2149246 — ASSIGNED Workstation boot x86_64 image exceeds maximum size
Changes to linux-firmware briefly brought the Worktation image below the limit. However, the Fedora-38-20230216.n.0 went above the limit again.
Proposed blockers -----------------
1. glusterfs — https://bugzilla.redhat.com/show_bug.cgi?id=2169401 — NEW libglusterd0 prevents upgrades to Fedora 38
libglusterd0, which is preinstalled in F37 Workstation, is not provided by anything in the F38 repos, so upgrades fail.
2. kwin — https://bugzilla.redhat.com/show_bug.cgi?id=2168034 — NEW kwin_wayland often crashed when used as the sddm Wayland compositor and logging out of Plasma resulting in a black screen
Logging out of Plasma sometimes triggers a kwin crash. This may be limited to running in a virtual machine.
On Fri, 2023-02-17 at 14:45 -0500, Ben Cotton wrote:
The F38 Beta freeze begins on 21 February. The current target release date is the early target date (2023-03-14).
Action summary
Accepted blockers
- distribution — Workstation boot x86_64 image exceeds maximum size — ASSIGNED
ACTION: Workstation WG to reduce image size or increase the limit
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.
Proposed blockers
- glusterfs — libglusterd0 prevents upgrades to Fedora 38 — NEW
ACTION: Maintainer to diagnose issue
I actually fixed this a few days ago, we can probably close it. I've done that.
The current target release date is the early target date (2023-03-14).
Action summary ====================
Accepted blockers -----------------
1. distribution — Workstation boot x86_64 image exceeds maximum size — ASSIGNED ACTION: Workstation WG to reduce image size or increase the limit
2. kwin — kwin_wayland often crashed when used as the sddm Wayland compositor and logging out of Plasma resulting in a black screen — ON_QA ACTION: QA to verify FEDORA-2023-81ff51758d
Proposed blockers -----------------
1. gdb — Can't open file anon_inode:i915.gem which was expanded to anon_inode:i915.gem during file-backed mapping note processing — NEW ACTION: Maintainer to diagnose issue
2. pkgconf — Don't depend on system-rpm-config — ON_QA ACTION: QA to verify FEDORA-2023-766817d642
Bug-by-bug detail =============
Accepted blockers -----------------
1. distribution — https://bugzilla.redhat.com/show_bug.cgi?id=2149246 — ASSIGNED Workstation boot x86_64 image exceeds maximum size
Changes to linux-firmware briefly brought the Worktation image below the limit. However, the Fedora-38-20230216.n.0 went above the limit again.
2. kwin — https://bugzilla.redhat.com/show_bug.cgi?id=2168034 — ON_QA kwin_wayland often crashed when used as the sddm Wayland compositor and logging out of Plasma resulting in a black screen
Logging out of Plasma sometimes triggers a kwin crash. FEDORA-2023-81ff51758d contains a candidate fix.
Proposed blockers -----------------
1. gdb — https://bugzilla.redhat.com/show_bug.cgi?id=2172342 — NEW Can't open file anon_inode:i915.gem which was expanded to anon_inode:i915.gem during file-backed mapping note processing
Reporting a bug with gnome-abrt fails because no fram and no thread found in the backtrace that gdb produces.
2. pkgconf — https://bugzilla.redhat.com/show_bug.cgi?id=2172406 — ON_QA Don't depend on system-rpm-config
pkgconf pulls in ~22 new packages as a runtime dependency, which don't appear to be strictly necessary. FEDORA-2023-766817d642 contains a candidate fix.
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.
F38 Beta is go, so it's time to look at final blockers. 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
2. gtk4 — With GTK 4.9.1 , Nautilus' target for "Move To" or "Copy To" operations is unexpected and can be invalid — NEW ACTION: Upstream to diagnose issue
3. sddm — Virtual keyboard (on-screen) not working at sddm-wayland-plasma — NEW ACTION: Maintainers to diagnose issue or revert to using X11
Proposed blockers -----------------
1. anaconda — Anaconda Rawhide warning does not switch to selected language — ON_QA ACTION: QA to verify FEDORA-2023-6cfa0fe11e
2. gnome-boxes — Boxes seem to end up in a loop when trying to create a new VM — ON_QA ACTION: QA to verify gnome-boxes-44~rc-1.fc38
3. gnome-contacts — Contacts merge incorrectly — NEW ACTION: Upstream to confirm expected behavior
4. gnome-photos — crash when using color adjustment sliders — NEW ACTION: Upstream to diagnose issue
5. gnome-photos — Memory exhaustion when editing a cropped photo — NEW ACTION: Upstream to diagnose issue
6. gnome-photos — unable to add a new picture to an album after delete and undo the delete option — NEW ACTION: lnie to file upstream issue NEEDINFO: lnie
7. mutter — Session crash when reverting Display settings — POST ACTION: Upstream to merge MR 2901
8. nautilus — Dragging files is Nautilus doesn't work as expected, quick movements result in a selection box instead — NEW ACTION: Upstream to fix issue
9. sddm — SDDM doesn't start in basic graphics mode in BIOS mode — NEW ACTION: Maintainer to diagnose issue
10. totem — totem crashes everytime when users try to delete a video — NEW ACTION: lnie to file upstream issue NEEDINFO: lnie
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. 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. Filed upstream as https://gitlab.gnome.org/GNOME/gtk/-/issues/5438
3. 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.
Proposed blockers -----------------
1. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2165762 — ON_QA Anaconda Rawhide warning does not switch to selected language
After switching language from an auto-detected language, some elements of the installer do not switch. Update FEDORA-2023-6cfa0fe11e contains a candidate fix.
2, gnome-boxes — https://bugzilla.redhat.com/show_bug.cgi?id=2175708 — ON_QA Boxes seem to end up in a loop when trying to create a new VM
Creating new VMs results in an infinite loop. Existing VMs can launch successfully. Fixed in upstream commit 26e51a32, which in gnome-boxes-44~rc-1.fc38.
3. gnome-contacts — https://bugzilla.redhat.com/show_bug.cgi?id=2176166 — NEW Contacts merge incorrectly
Merging contacts can result in one of the contacts still existing-but-empty, or other unexpected states. This appears to be an issue with the UI being unintuitive. Filed upstream as https://gitlab.gnome.org/GNOME/gnome-contacts/-/issues/300 with several related issues filed to make the UI clearer.
4. gnome-photos — https://bugzilla.redhat.com/show_bug.cgi?id=2176038 — NEW crash when using color adjustment sliders
Adjusting color on jpeg (not png) images can result in the application crashing. There is question about whether or not this constitutes "basic functionality". Filed upstream as https://gitlab.gnome.org/GNOME/gnome-photos/-/issues/209
5. gnome-photos — https://bugzilla.redhat.com/show_bug.cgi?id=2176043 — NEW Memory exhaustion when editing a cropped photo
When Shadows or Highlights sliders are changed on a cropped photo (but not uncropped photos), gnome-photos goes into an infinite cycle consuming CPU and memory until killed by the OOM killer. This behavior is observed at least as far back as F36. Filed upstream as https://gitlab.gnome.org/GNOME/gnome-photos/-/issues/205
6. gnome-photos — https://bugzilla.redhat.com/show_bug.cgi?id=2176732 — NEW unable to add a new picture to an album after delete and undo the delete option
Deleting an album and then un-deleting does not appear to fully undelete it.
7. mutter — https://bugzilla.redhat.com/show_bug.cgi?id=2175809 — POST 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. Upstream MR contains a candidate fix: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2901
8. nautilus — https://bugzilla.redhat.com/show_bug.cgi?id=2176766 — NEW 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.
9. sddm — https://bugzilla.redhat.com/show_bug.cgi?id=2176782 — NEW SDDM doesn't start in basic graphics mode in BIOS mode
In BIOS mode only, sddm results in a blank screen when using basic graphics mode. This may be the result of a SimpleDRM device not being created.
10. totem — https://bugzilla.redhat.com/show_bug.cgi?id=2176726 — NEW totem crashes everytime when users try to delete a video
Deleting a video results in an application crash, but only when there is only one video.
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.
The current target is the early target date (18 April).
Action summary ====================
Accepted blockers -----------------
1. crypto-policies — Insecure installed RPMs (like Google Chrome) prevent system updates in F38, can't be removed — ASSIGNED ACTION: Maintainers to propose solution for this case
2. kernel — anaconda failed to detect the fcoe target(only affects ixgbe) — NEW ACTION: Maintainers to diagnose issue
3. kernel — The kernel sometimes does not initialize SimpleDRM when booting in basic graphics mode on BIOS, causing SDDM to fail — POST ACTION: lorax maintainers to review and merge PR 1317
4. 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 NEEDIFNO: dbelyavs
5. sddm — Virtual keyboard (on-screen) not working at sddm-wayland-plasma — NEW ACTION: Maintainers to diagnose issue or revert to using X11 NEEDINFO: ngompa13
6. 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 — NEW ACTION: Maintainer to diagnose issue
2. accountservice — GDM takes "long" before allowing mouse moves and showing the user list. — MODIFIED ACTION: QA to verfiy FEDORA-2023-a5af7d5db0
3. gnome-shell — gnome-shell crashes and sysops happens when users logout — NEW ACTION: Upstream to complete work on MR 2722
4. gnome-software — Incorrect priority order of app sources — MODIFIED ACTION: QA to verify FEDORA-2023-49b5dec107
5. kwin — Logging out of Plasma 5.27.3 on Wayland as the second user on the system resulted in a black screen — NEW ACTION: selinux-policy maintainers to create an update that contains upstream PR 1628
Bug-by-bug detail =============
Accepted blockers -----------------
1. crypto-policies — https://bugzilla.redhat.com/show_bug.cgi?id=2170878 — ASSIGNED Insecure installed RPMs (like Google Chrome) prevent system updates in F38, can't be removed
A fix to let RPM use a separate crytpo policy has not covered all cases. Certain AnyDesk RPMs were apparently signed outside the window when the certificate was valid.
2. 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".
3. kernel — https://bugzilla.redhat.com/show_bug.cgi?id=2176782 — POST 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. Setting `vga=791` in grub appears to work. Pending lorax PR adds this for basic graphics mode on BIOS: https://github.com/weldr/lorax/pull/1317
4. 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.
5. 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. The keyboard works and the button enables/disables the keyboard, but does not bring up the keyboard
6. 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 — NEW 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. This seems likely to be an integer overflow.
2. accountservice — https://bugzilla.redhat.com/show_bug.cgi?id=2180768 — MODIFIED GDM takes "long" before allowing mouse moves and showing the user list.
When wtmp is modified during boot, accountservice would have a blocking wait for 10 seconds. Update FEDORA-2023-a5af7d5db0 contains a candidate fix to enable high priority reload requests.
3. gnome-shell — https://bugzilla.redhat.com/show_bug.cgi?id=2180277 — NEW gnome-shell crashes and sysops happens when users logout
Logging out sometimes causes a crash. It may be caused by trying to exit with open windows. An upstream MR contains work-in-progress fixes: https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2722/
4. gnome-software — https://bugzilla.redhat.com/show_bug.cgi?id=2181367 — MODIFIED Incorrect priority order of app sources
Contrary to FESCo's requirement for the Unfiltered Flathub Change, flatpaks from Flathub sometimes take priority over Fedora RPMs. FEDORA-2023-49b5dec107 contains a candidate fix.
5. kwin — 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 the second user on a system from logging out successfully. This appears to be an SELinux issue filed as RHBZ 2181010. An upstream PR contains a candidate fix: https://github.com/fedora-selinux/selinux-policy/pull/1628
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.
The current target is the early target date (18 April).
Action summary ====================
Accepted blockers -----------------
1. 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. fedora-release — Fedora 38 Final needs a non-prerelease fedora-release package and fedora-repos with updates-testing disabled — MODIFIED ACTION: QA to verify update FEDORA-2023-ae8bf65eea
Bug-by-bug detail =============
Accepted blockers -----------------
1. 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. fedora-release — https://bugzilla.redhat.com/show_bug.cgi?id=2185122 — MODIFIED Fedora 38 Final needs a non-prerelease fedora-release package and fedora-repos with updates-testing disabled
Currently fedora-release and fedora-repos are in a pre-release state. Update https://bodhi.fedoraproject.org/updates/FEDORA-2023-ae8bf65eea contains a candidate fix.