Meeting minutes and logs:
https://meetbot-raw.fedoraproject.org//blocker-review_matrix_fedoraproject-org/2025-10-06/

Here is an AI-generated summary of a Blocker review meeting [1] from
October 6, 2025.
Please be aware that the summary is intended for a quick convenient
recapitulation of the meeting, but might contain factual errors. Read the
full meeting log for all the details.

## Proposed Final blockers

(2401623) fedora ISOs will not boot in qemu-kvm using UEFI [2]

The issue is that Fedora ISOs fail to boot in QEMU/KVM with UEFI enabled,
which appears to be related to older host firmwares. Adam Williamson noted
that the problem doesn't seem to meet the criterion of virtualization being
"entirely broken". Kamil Páral questioned how host firmware could affect a
virtual guest and suggested it might be a bug in VT-d. The group discussed
that the issue seems to be triggered by a specific combination of hardware
properties, such as the lack of support for 1G page tables. To better
understand the scope and impact, they decided to delay the decision.

Resolution: Punted. The team agreed to ask Gerd Hoffmann for the exact
combination of properties necessary to trigger the bug to assess how common
the issue is likely to be.

(2400488) libdnf context is not reading and enforcing protected packages,
causing PackageKit to not honor protected packages settings [3]

This bug report states that `libdnf` does not enforce protected packages,
which could allow a user to remove critical system components via graphical
tools like GNOME Software, which uses PackageKit. Initially, Brandon
Nielsen had trouble reproducing the issue. The discussion then focused on
whether the existing release criterion, which explicitly covers graphical
package managers, was sufficient. Kamil Páral, who originally proposed the
criterion, confirmed it was aimed at graphical tools but agreed it should
be updated. Brandon was eventually able to reproduce the bug by searching
for a protected font package (which isn't shown in the main "Installed
Software" list) and removing it, which broke the system. The group decided
to accept the bug as a blocker, on the condition that the associated
criterion is formally amended to cover such cases.

Resolution: Accepted as a Final blocker. This decision is provisional on
amending the Final release criterion as proposed by Kamil. The bug will
then be considered a violation of the newly amended criterion.

(2363937) Version upgrade from Fedora 41 to 42 disables postfix.service [4]

During a system upgrade, the `postfix.service` is being disabled. Adam
Williamson mentioned the issue seems serious but its cause is not yet
understood, and it might not be specific to upgrades. Since other services
like `nftables` are also reportedly affected, there was speculation that
the root cause could be in `systemd` or `rpm` rather than the `postfix`
package itself. As more investigation is needed to determine if it violates
any criteria, the decision was postponed.

Resolution: Punted. The team decided to look into the issue more before
making a final decision, as it does not clearly violate the criteria at
this time.

## Proposed Final freeze exceptions

(2388961) glycin backend saving jpg format with alpha channel does not work
at all [5]

This bug involves the `gdk-pixbuf2` library where the glycin backend fails
when saving JPG files that have an alpha channel. While the GNOME team
expressed interest in getting it tested, a clear justification for a Freeze
Exception was not provided during the meeting. Matthias Clasen from the
GNOME team joined and noted that failing to save a file constitutes
potential data loss, but also mentioned he believed the bug was already
fixed. Without a strong rationale, the team decided against accepting it as
a Freeze Exception for now.

Resolution: Rejected as a Final freeze exception. There was no clear
rationale provided for why this bug justifies a freeze exception. The team
is open to reconsidering if a justification is presented.

(2400488) libdnf context is not reading and enforcing protected packages,
causing PackageKit to not honor protected packages settings [3]

This bug was discussed earlier and provisionally accepted as a blocker.
Adam Williamson proposed to also accept it as a Freeze Exception as a
fallback in case the blocker status is later revoked. The group agreed,
acknowledging that the issue is significant enough that it should be fixed
for the release, especially since a user could encounter it on a fresh
installation.

Resolution: Accepted as a Final freeze exception. This was accepted as a
fallback in case the blocker status falls through. The problem is
considered important enough to be fixed for the Final release.

## Accepted Final blockers

(2387466) Fedora 43: Server boot aarch64 image exceeds maximum size [6]

A fix for this issue is available in a Bodhi update. The team is asking for
help with testing and adding karma to the update so it can be pushed to the
stable repositories.

(2394213) default hostonly-mode "sloppy" results in significant increase in
initramfs size [7]

Progress on this issue is stalled. A backported fix was applied to Fedora
42 but has not yet been applied to Fedora 43. It is still unclear if that
change is sufficient to resolve the problem. The team is waiting for a new
`dracut` build and further testing.

(2397086) Drop-down menus not working over RDP in Anaconda [8]

There has been no progress on this bug since the last meeting. The team is
waiting for developer input or debugging suggestions and has asked the
Workstation working group for assistance.

(2396309) Radxa Rock Pi 4 and Pine64 RockPro64 boards fail to boot with
Kiwi-produced images, probably all RockChip models [9]

Peter Boy confirmed that the issue persists with the latest builds,
affecting both minimal and workstation images. He will connect a serial
console to the affected devices this week to gather more detailed boot
failure information.

(2394561) SELinux is preventing systemd from 'open' accesses on the file
/tmp/webui-cockpit-ws.env. [10]

The fix for this SELinux issue has been verified. The update just needs to
be pushed to the stable repository.

## Open floor

No other topics were discussed.

[1] https://fedoraproject.org/wiki/QA/Meetings
[2] https://bugzilla.redhat.com/show_bug.cgi?id=2401623
[3] https://bugzilla.redhat.com/show_bug.cgi?id=2400488
[4] https://bugzilla.redhat.com/show_bug.cgi?id=2363937
[5] https://bugzilla.redhat.com/show_bug.cgi?id=2388961
[6] https://bugzilla.redhat.com/show_bug.cgi?id=2387466
[7] https://bugzilla.redhat.com/show_bug.cgi?id=2394213
[8] https://bugzilla.redhat.com/show_bug.cgi?id=2397086
[9] https://bugzilla.redhat.com/show_bug.cgi?id=2396309
[10] https://bugzilla.redhat.com/show_bug.cgi?id=2394561
-- 
_______________________________________________
test mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to