Ahead of the F42 Beta Blocker meeting[1] on Monday, April 7 and the F42 Final Go/No-Go meeting[2] on Thursday, April 10, please review the below report on current F42 Final blockers[3]. Your help discussing, voting on and resolving any outstanding bugs would be greatly appreciated.
Action summary ==================== Accepted blockers ----------------- 1. cockpit — [cockpit-storage] does not properly clean RAID arrays upon deletion, causing issues when recreating an array with the same name and disks — NEW ACTION: Maintainers to diagnose issue 2. gnome-abrt — GNOME Abrt no longer translated — NEW ACTION: Upstream to diagnose issue 3. gnome-shell — Fedora 42 beta unable to shutdown despite "No inhibitors" — NEW ACTION: Upstream to diagnose issue Proposed blockers ----------------- 1. distribution — Fedora 42: Server boot aarch64 image exceeds maximum size — ASSIGNED ACTION: QA to verify the new size increase satisfies the maximum blocking size requirement 2. fedora-release — Fedora KDE Plasma Desktop Edition is not correctly identified at /etc/os-release — POST ACTION: QA to verify fix https://src.fedoraproject.org/rpms/fedora-release/pull-request/374 3. fedora-release — fedora-release package need to be rebuild to include a series of changes for final F42 release — NEW ACTION: Maintainer to fix issue 4. gnome-abrt — Can't open settings to adjust Bugzilla apikeye — NEW ACTION: A workaround has been suggested, QA to verify that this meets Final release criteria 5. libdnf — libdnf (DNF4) should read DNF5 repo overrides — NEW ACTION: A workaround has been suggested, QA to verify that this meets Final release criteria and is documented in Common Bugs 6. mdadm — [live] Can't reuse existing RAID partitioning — POST ACTION: QA to verify fix https://github.com/md-raid-utilities/mdadm/pull/159 Bug-by-bug detail ============= Accepted blockers ----------------- 1. cockpit — https://bugzilla.redhat.com/show_bug.cgi?id=2357214 — NEW [cockpit-storage] does not properly clean RAID arrays upon deletion, causing issues when recreating an array with the same name and disks When a test sets up a RAID 0 (striped) device called SOMERAID — it shows up as 30 GiB. That RAID is deleted and replaced with a RAID 1 (mirrored) device using the same name, SOMERAID, which is now only 15 GiB. During the second setup, the system (via parted/libparted) still thinks the device is 30 GiB, not 15 GiB. It tries to "fix" the partition table using this outdated size info and fails to write to the device, resulting in errors and a broken partition table. 2. gnome-abrt — https://bugzilla.redhat.com/show_bug.cgi?id=2357036 — NEW GNOME Abrt no longer translated The update to GTK4/libadwaita broke translations in gnome-abrt, so most of the app now shows text in English, even for users with translations like Portuguese. This seems to have happened because the translation template (POT file) hasn’t been updated since 2020, so new text can’t be translated until that’s fixed. We expect that the new gnome-abrt version will have updated translations (synced from Weblate), which should be released a month or two after the pot file update PR gets merged to give the translators enough time to update their translations. 3. gnome-shell — https://bugzilla.redhat.com/show_bug.cgi?id=2355033 — NEW Fedora 42 beta unable to shutdown despite "No inhibitors" On Fedora 42 Beta running in a virtual machine, sometimes the user can't shut down directly from the GNOME menu. Logging out first and then shutting down works, however the issue doesn’t always happen and would appear to be inconsistent. It seems to only happen in VMs. Other environments such as QEMU, Hyper-V or bare metal are reportedly unaffected. Proposed blockers ----------------- 1. distribution — https://bugzilla.redhat.com/show_bug.cgi?id=2352679 — ASSIGNED Fedora 42: Server boot aarch64 image exceeds maximum size Server exceeded the initial maximum blocking size of 1GB. A PR has been submitted and merged to increase the blocking size to 1.2GB. This seems to have resolved most of the issue, and some firmware trimming PRs from Fedora QA have also reduced the size. 2. fedora-release — https://bugzilla.redhat.com/show_bug.cgi?id=2357258 — POST Fedora KDE Plasma Desktop Edition is not correctly identified at /etc/os-release There's a requirement that says each Fedora Edition must clearly show its name in the installer and in the /etc/os-release file after it's installed, but the new KDE Plasma Desktop Edition did not do that yet. A PR has been submitted to fix https://src.fedoraproject.org/rpms/fedora-release/pull-request/374 3. fedora-release — https://bugzilla.redhat.com/show_bug.cgi?id=2357270 — NEW fedora-release package need to be rebuild to include a series of changes for final F42 release For final release (GA), all "Prerelease" messages from all variants should be removed. According to Fedora rules, there should be no pre-release warnings shown during install or in key parts of the system once it's officially released. Right now, pre-release notices still appear during installation because the package isn’t updated yet. This needs to be completed before Final. 4. gnome-abrt — https://bugzilla.redhat.com/show_bug.cgi?id=2356257 — NEW Can't open settings to adjust Bugzilla apikey In F42, the new gnome-abrt UI is missing a button to access settings. This means users can’t change their Bugzilla API key after entering it the first time. If the key becomes invalid (like due to a typo or expiration), bug reporting just fails with an error — there's no prompt to fix it or enter a new key. As a result, users can't report bugs anymore unless this is fixed. Apparently the preferences menu was never added to gnome-abrt in the new version, though it was linked in the old one. This is a step back in user experience, but the new version still offers significant improvements. The preferences were always part of "report-gtk", which opens when the user clicks "Create Report." Users can access the preferences menu while reporting a problem, from the top-left corner of the report window (e.g., if the API key is expired), or by reverting to the older version of gnome-abrt. 5. libdnf — https://bugzilla.redhat.com/show_bug.cgi?id=2354865 — NEW libdnf (DNF4) should read DNF5 repo overrides After modifying system repositories with DNF5, some users' changes appear to be no longer synced with PackageKit. This seems to be because DNF5 now stores changes in a separate override directory, while PackageKit still uses the older DNF4, which doesn't recognize these changes. A fix is likely not going to happen in time for F42 release, so it is suggested that GUI users continue to use the graphical interface for now. 6. libdnf — https://bugzilla.redhat.com/show_bug.cgi?id=2325906 — POST [live] Can't reuse existing RAID partitioning In the web UI, it's not possible to reuse an existing RAID partition (tested with Fedora 42 on top of RAID1 with Fedora 40). The partitioning fails with an error related to an invalid array name ("system2:pv00"). The issue seems to be with mdadm's naming policy, possibly due to changes in its latest release or the inclusion of the system hostname in the RAID array. This appears to be a regression issue and a potential fix has been filed https://github.com/md-raid-utilities/mdadm/pull/159 Please visit the blocker bugs app[4] for more details on each bug above. Kind regards, Aoife [1] https://calendar.fedoraproject.org/QA/2025/4/7/#m10995 [2] https://calendar.fedoraproject.org/Fedora%20release/2025/4/10/#m11013 [3] https://fedoraproject.org/wiki/Fedora_Release_Criteria [4] https://qa.fedoraproject.org/blockerbugs/milestone/42/beta/buglist -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
