Re: F36 Beta blocker status summary

2022-03-18 Thread Ben Cotton
Action summary


Accepted blockers
-
1. anaconda — When running anaconda on Wayland with two keyboard
layouts configured, hitting any modifier key with the second layout
selected switches to the first layout — ON_QA
ACTION: QA to verify FEDORA-2022-840ea87072


Proposed blockers
-

1. gnome-software — Fedora 34 cannot be upgraded to Fedora 36 with
Gnome Software — VERIFIED
ACTION: none

Bug-by-bug detail
=

Accepted blockers
-
1.  anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2016613 — ON_QA
When running anaconda on Wayland with two keyboard layouts configured,
hitting any modifier key with the second layout selected switches to
the first layout

adamwill's research shows that this bug has existed since F25, but
became more visible after KDE switched to Wayland by default. This bug
was deferred to F36 Beta under the "too hard to fix" exception. Update
FEDORA-2022-840ea87072 contains a candidate fix.


Proposed blockers
-

1. gnome-software —
https://bugzilla.redhat.com/show_bug.cgi?id=2064623 — VERIFIED
Fedora 34 cannot be upgraded to Fedora 36 with Gnome Software

Under some conditions, setting show-upgrade-prerelease does not result
in Software showing an available update. Reproducing has been spotty,
and there's an emerging consensus that if this is a bug, it's better
suited as a Final blocker.

-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: F36 Beta blocker status summary

2022-03-11 Thread Ben Cotton
Action summary


Accepted blockers
-
1. anaconda — When running anaconda on Wayland with two keyboard
layouts configured, hitting any modifier key with the second layout
selected switches to the first layout — POST
ACTION: Maintainers to package upstream PR #3912

2. fedora-release — fedora-release-identity-cloud says "Cloud
Edition", Cloud has not been an edition for years — ASSIGNED
ACTION: none

3. mutter — GNOME doesn't accept input from wireless keyboard if
there's not another "keyboard" input available — ON_QA
ACTION: QA to verify FEDORA-2022-21d81706cd

4. firefox — f36 composes still have firefox 96, f34 f35 have firefox 97 — ON_QA
ACTION: QA to verify FEDORA-2022-42ea499a7d


Proposed blockers
-

1. mutter — Workstation Live is frozen in a VM with QXL video driver
(Virtio works OK) — NEW
ACTION: Maintainers to diagnose and fix issue

2. selinux-policy — SELinux preventing systemd-network-generator from
creating files in /run/systemd/network/ — ASSIGNED
ACTION: Maintainers to update policy to fix issue


Bug-by-bug detail
=

Accepted blockers
-
1.  anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2016613 — POST
When running anaconda on Wayland with two keyboard layouts configured,
hitting any modifier key with the second layout selected switches to
the first layout

adamwill's research shows that this bug has existed since F25, but
became more viisble after KDE switched to Wayland by default. This bug
was deferred to F36 Beta under the "too hard to fix" exception.
jkonecny is working on  a fix to disconnect keyboard control between
Anaconda and the live environment. Upstream PR
https://github.com/rhinstaller/anaconda/pull/3912 has a candidate fix.

2. fedora-release —
https://bugzilla.redhat.com/show_bug.cgi?id=2018271 — ASSIGNED
fedora-release-identity-cloud says "Cloud Edition", Cloud has not been
an edition for years

Waived from F35 final under the "late blocker exception." Cloud WG is
working on a proposal to re-promote Cloud to Edition status, but that
will not happen for F36 release cycle. Council voted to waive this. An
update to the release criterion is pending that explicitly grants
Council the ability to do that.

3. mutter — https://bugzilla.redhat.com/show_bug.cgi?id=2017043 — ON_QA
GNOME doesn't accept input from wireless keyboard if there's not
another "keyboard" input available

On some hardware, devices with multiple capabilities that include
keyboard do not get registered as a keyboard. Thus they only work if
another keyboard is connected. FEDORA-2022-21d81706cd (GNOME 42
megaupdate) includes a candidate fix.

4. firefox — https://bugzilla.redhat.com/show_bug.cgi?id=2057193 — ON_QA
f36 composes still have firefox 96, f34 f35 have firefox 97

Builds of Firefox 97, which contains security fixes, are failing on
F36 and Rawhide due to a GCC 12 internal error. FEDORA-2022-42ea499a7d
provides a successful build of Firefox 97.


Proposed blockers
-

1. mutter — https://bugzilla.redhat.com/show_bug.cgi?id=2063156 — NEW
Workstation Live is frozen in a VM with QXL video driver (Virtio works OK)

Recent composes of Workstation with the default video driver freeze on
the welcome screen. Using virtio initially (including switching to qxl
post-install) does not have this behavior.

2. selinux-policy —
https://bugzilla.redhat.com/show_bug.cgi?id=2037047 — ASSIGNED
SELinux preventing systemd-network-generator from creating files in
/run/systemd/network/.

Passing network kernel arguments (e.g. to set the nameserver) at boot
causes a failure in systemd-network-generator due to an SELinux
denial.

-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: F36 Beta blocker status summary

2022-03-04 Thread Ben Cotton
The Go/No-Go meeting for the Early target date (2022-03-15) is
Thursday, which means we want to have a release candidate by Tuesday.

Action summary


Accepted blockers
-
1. anaconda — When running anaconda on Wayland with two keyboard
layouts configured, hitting any modifier key with the second layout
selected switches to the first layout — ASSIGNED
ACTION: Maintainers to fix issue

2. anaconda — Some variants are missing /etc/resolv.conf symlink (use
systemd-resolved) — POST
ACTION: QA to verify FEDORA-2022-cf175d0e19

3. fedora-release — fedora-release-identity-cloud says "Cloud
Edition", Cloud has not been an edition for years — ASSIGNED
ACTION: none

4. mlocate — F35 with mlocate installed cannot be upgraded to F36 due
to conflict with plocate — ASSIGNED
ACTION: Maintainers to update packages to correctly handle obsoletes

5. mutter — GNOME doesn't accept input from wireless keyboard if
there's not another "keyboard" input available — ASSIGNED
ACTION: Upstream to fix mutter to support multiple capabilities on a device

6. plasma-discover — Discover does not display applications correctly.
— VERIFIED
ACTION: none

7. firefox — f36 composes still have firefox 96, f34 f35 have firefox 97 — NEW
ACTION: Maintainers to resolve build issues

8. oz — Initial Setup startup failed due to invalid kickstart file — ON_QA
ACTION: QA to verify FEDORA-2022-c263b25459

Proposed blockers
-

1. NetworkManager-openvpn — After upgrade gnome-control-center to
42~beta-1.fc37 unable to configure VPN connection — NEW
ACTION: Upstream to update plugins for GTK4

2. dnfdragora — On Fedora 36 KDE, dnfdragora does not start. — NEW
ACTION: Maintainers to fix issue


Bug-by-bug detail
=

Accepted blockers
-
1.  anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2016613 — ASSIGNED
When running anaconda on Wayland with two keyboard layouts configured,
hitting any modifier key with the second layout selected switches to
the first layout

adamwill's research shows that this bug has existed since F25, but
became more viisble after KDE switched to Wayland by default. This bug
was deferred to F36 Beta under the "too hard to fix" exception.
jkonecny is working on  a fix to disconnect keyboard control between
Anaconda and the live environment.

2. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2032085 — ON_QA
Some variants are missing /etc/resolv.conf symlink (use systemd-resolved)

Some variants are not using systemd-resolved as intended. With some
recently-merged changes to Anaconda, this appears to be working
correctly now, at least for ostree variants. FEDORA-2022-cf175d0e19
contains a candidate fix.

3. fedora-release —
https://bugzilla.redhat.com/show_bug.cgi?id=2018271 — ASSIGNED
fedora-release-identity-cloud says "Cloud Edition", Cloud has not been
an edition for years

Waived from F35 final under the "late blocker exception." Cloud WG is
working on a proposal to re-promote Cloud to Edition status, but that
will not happen for F36 release cycle. Council is poised to waive
this: https://pagure.io/Fedora-Council/tickets/issue/389

4. mlocate — https://bugzilla.redhat.com/show_bug.cgi?id=2052433 — ASSIGNED
F35 with mlocate installed cannot be upgraded to F36 due to conflict
with plocate

The original change proposal planned for mlocate and plocate to be
parallel available in F36. However, this turns out to be more
challenging than expected. We have a path forward that will correctly
handle upgrades will allowing users to opt into keeping mlocate, it
just needs to be implemented.

5. mutter — https://bugzilla.redhat.com/show_bug.cgi?id=2017043 — NEW
GNOME doesn't accept input from wireless keyboard if there's not
another "keyboard" input available

On some hardware, devices with multiple capabilities that include
keyboard do not get registered as a keyboard. Thus they only work if
another keyboard is connected. It seems to mostly (or exclusively)
affect some ARM hardware. This appears to be a design flaw in mutter
and is reported upstream as
https://gitlab.gnome.org/GNOME/mutter/-/issues/2154

6. plasma-discover — https://bugzilla.redhat.com/show_bug.cgi?id=2057531 — NEW
Discover does not display applications correctly.

Discover was only showing Flatpaks, not RPMs. Refreshing appstream
partially helped. In recent composes, the behavior no longer appears.

7. firefox — https://bugzilla.redhat.com/show_bug.cgi?id=2057193 — NEW
f36 composes still have firefox 96, f34 f35 have firefox 97

Builds of Firefox 97, which contains security fixes, are failing on
F36 and Rawhide due to a GCC 12 internal error.
FEDORA-2022-e056239611 contains a fix for those issues, but is
apparently incomplete.

8. oz — https://bugzilla.redhat.com/show_bug.cgi?id=2057600 — ON_QA
Initial Setup startup failed due to invalid kickstart file

A previous fix for the "initial-setup doesn't require creating an
admin user" (RHBZ 2015490) assumes a kickstart file will be available,

Re: F36 Beta blocker status summary

2022-02-25 Thread Ben Cotton
Action summary


Accepted blockers
-
1. anaconda — When running anaconda on Wayland with two keyboard
layouts configured, hitting any modifier key with the second layout
selected switches to the first layout — ASSIGNED
ACTION: Maintainers to fix issue

2. anaconda — Some variants are missing /etc/resolv.conf symlink (use
systemd-resolved) — POST
ACTION: Maintainers to package upstream PR 3884

3. fedora-release — fedora-release-identity-cloud says "Cloud
Edition", Cloud has not been an edition for years — ASSIGNED
ACTION: Maintainers to update fedora-release-identity-cloud or
group-with-such-authority to waive this.

4. mlocate — F35 with mlocate installed cannot be upgraded to F36 due
to conflict with plocate — ASSIGNED
ACTION: FESCo to vote on #2765

5. mutter — GNOME doesn't accept input from wireless keyboard if
there's not another "keyboard" input available — ASSIGNED
ACTION: Upstream to fix mutter to support multiple capabilities on a device

6. plasma-discover — Discover does not display applications correctly. — ON_QA
ACTION: QA to check if the behavior reappears

7. sddm — SDDM crashes upon log out from the KDE session. — NEW
ACTION: Maintainers to diagnose and fix issue

Proposed blockers
-

1. firefox — f36 composes still have firefox 96, f34 f35 have firefox 97 — NEW
ACTION: Maintainers to resolve build issues

2. gnome-control-center — After upgrade gnome-control-center to
42~beta-1.fc37 unable to configure VPN connection — NEW
ACTION: Reporter to confirm the behavior exists on F36

3. initial-setup — dnf system-upgrade 35 to 36 fails with various
pipewire wireplumber conflicts — NEW
ACTION: Maintainers to package upstream PR 297 (or find a better fix)


Bug-by-bug detail
=

Accepted blockers
-
1.  anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2016613 — ASSIGNED
When running anaconda on Wayland with two keyboard layouts configured,
hitting any modifier key with the second layout selected switches to
the first layout

adamwill's research shows that this bug has existed since F25, but
became more viisble after KDE switched to Wayland by default. This bug
was deferred to F36 Beta under the "too hard to fix" exception.
There's ongoing discussion trying to come up with a potential fix,
however we still seem to be a long way from that point.

2. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2032085 — POST
Some variants are missing /etc/resolv.conf symlink (use systemd-resolved)

Some variants are not using systemd-resolved as intended. With some
recently-merged changes to Anaconda, this appears to be working
correctly now, at least for ostree variants. Upstream PR has a fix for
F36: https://github.com/rhinstaller/anaconda/pull/3884

3. fedora-release —
https://bugzilla.redhat.com/show_bug.cgi?id=2018271 — ASSIGNED
fedora-release-identity-cloud says "Cloud Edition", Cloud has not been
an edition for years

Waived from F35 final under the "late blocker exception." Cloud WG is
working on a proposal to re-promote Cloud to Edition status, but that
will not happen for F36 release cycle. A ticket is pending with the
Fedora Council, although Cloud could proceed with removing the word
"Edition" for now: https://pagure.io/Fedora-Council/tickets/issue/389

4. mlocate — https://bugzilla.redhat.com/show_bug.cgi?id=2052433 — ASSIGNED
F35 with mlocate installed cannot be upgraded to F36 due to conflict
with plocate

The original change proposal planned for mlocate and plocate to be
parallel available in F36. However, this turns out to be more
challenging than expected. FESCo #2765 requests approval to have
plocate replace mlocate on upgrade.

5. libinput — https://bugzilla.redhat.com/show_bug.cgi?id=2017043 — NEW
GNOME doesn't accept input from wireless keyboard if there's not
another "keyboard" input available

On some hardware, devices with multiple capabilities that include
keyboard do not get registered as a keyboard. Thus they only work if
another keyboard is connected. It seems to mostly (or exclusively)
affect some ARM hardware. This appears to be a design flaw in mutter
and is reported upstream as
https://gitlab.gnome.org/GNOME/mutter/-/issues/2154

6. plasma-discover — https://bugzilla.redhat.com/show_bug.cgi?id=2057531 — NEW
Discover does not display applications correctly.

Discover was only showing Flatpaks, not RPMs. Refreshing appstream
partially helped. In recent composes, the behavior no longer appears.
We'll keep this bug open to keep checking if the bad cache returns.

7. sddm — https://bugzilla.redhat.com/show_bug.cgi?id=2057419 — NEW
SDDM crashes upon log out from the KDE session.

When logging out of a Plasma session, SDDM does not restart, leaving
the user at a terminal. A reboot is required to fix. This may be
specific to Wayland.

Proposed blockers
-

1. firefox — https://bugzilla.redhat.com/show_bug.cgi?id=2057193 — NEW
f36 composes still have firefox 96, f34 f35 have firefox 

Re: F36 Beta blocker status summary

2022-02-17 Thread Stephen Gallagher
On Thu, Feb 10, 2022 at 3:27 PM Ben Cotton  wrote:

> Now that we've reached the branch point, it's time to start doing
> weekly blocker summaries again! Beta freeze begins on 22 February and
> the current target Beta release date is 15 March.
>
> Action summary
> 
>
> Accepted blockers
> -
>
...

> 3. fedora-release — fedora-release-identity-cloud says "Cloud
> Edition", Cloud has not been an edition for years — NEW
> ACTION: Maintainers to update fedora-release-identity-cloud or
> group-with-such-authority to waive this.
>
...

I offer https://src.fedoraproject.org/rpms/fedora-release/pull-request/215
as a potential solution here. (Rawhide version at
https://src.fedoraproject.org/rpms/fedora-release/pull-request/214)
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: F36 Beta blocker status summary

2022-02-17 Thread Ben Cotton
As a reminder: Beta freeze begins on 22 February and the current
target Beta release date is 15 March.


Action summary


Accepted blockers
-
1. anaconda — When running anaconda on Wayland with two keyboard
layouts configured, hitting any modifier key with the second layout
selected switches to the first layout — ASSIGNED
ACTION: Maintainers to diagnose issue

2. distribution — Fedora 36 backgrounds not present on
release-blocking desktops (GNOME, KDE) — ASSIGNED
ACTION: KDE Maintainers to update background packages (BZ 2055437)

3. fedora-release — fedora-release-identity-cloud says "Cloud
Edition", Cloud has not been an edition for years — NEW
ACTION: Maintainers to update fedora-release-identity-cloud or
group-with-such-authority to waive this.

4. kwin — openQA clicks in anaconda on KDE stop working shortly after
it starts — NEW
ACTION: Maintainers to diagnose issue

5. libinput — GNOME doesn't accept input from wireless keyboard if
there's not another "keyboard" input available — NEW
ACTION: Maintainers to diagnose issue

6. dnf — exclude_from_weak_autodetect=true effectively renders rich
weak dependencies useless — NEW
ACTION: QA and maintainers to test upstream PR

Proposed blockers
-

1. distribution — Some variants are missing /etc/resolv.conf symlink
(use systemd-resolved) — POST
ACTION: QA to verify issue is resolved

2. gnome-shell — Updating gnome-shell to 42~beta-1.fc37 or mutter to
42~beta-1.fc37 version breaks the login screen. — ON_QA
ACTION: QA to verify a compose with gjs-1.71.1

3. pipewire — dnf system-upgrade 35 to 36 fails with various pipewire
wireplumber conflicts — NEW
ACTION: Maintainers to diagnose and fix issue


Bug-by-bug detail
=

Accepted blockers
-
1.  anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2016613 — ASSIGNED
When running anaconda on Wayland with two keyboard layouts configured,
hitting any modifier key with the second layout selected switches to
the first layout

adamwill's research shows that this bug has existed since F25, but
became more viisble after KDE switched to Wayland by default. This bug
was deferred to F36 Beta under the "too hard to fix" exception.
There's ongoing discussion trying to come up with a potential fix,
however we still seem to be a long way from that point.

2. distribution — https://bugzilla.redhat.com/show_bug.cgi?id=2052654 — NEW
Fedora 36 backgrounds not present on release-blocking desktops (GNOME, KDE)

Update FEDORA-2022-08d5acc11b adds the F36 backgrounds. KDE Plasma
needs an update to pick up the new backgrounds (BZ 2055437)

3. fedora-release — https://bugzilla.redhat.com/show_bug.cgi?id=2018271 — NEW
fedora-release-identity-cloud says "Cloud Edition", Cloud has not been
an edition for years

Waived from F35 final under the "late blocker exception." Cloud WG is
working on a proposal to re-promote Cloud to Edition status, but that
will not happen for F36 release cycle.

4. kwin — https://bugzilla.redhat.com/show_bug.cgi?id=2047503 — NEW
openQA clicks in anaconda on KDE stop working shortly after it starts

Shortly after the installer starts, mouse clicks in openQA stop
working. Using 'development mode' which allows for manual interaction
still works. This bug only affects KDE, and appears to have been
introduced in the KDE Plasma 5.24 pre-release on 2022-01-19. This bug
is accepted under the "hinders execution of required Beta test plans"
criterion.

5. libinput — https://bugzilla.redhat.com/show_bug.cgi?id=2017043 — NEW
GNOME doesn't accept input from wireless keyboard if there's not
another "keyboard" input available

On some hardware, devices with multiple capabilities that include
keyboard do not get registered as a keyboard. Thus they only work if
another keyboard is connected. It seems to mostly (or exclusively)
affect some ARM hardware.

6. dnf — https://bugzilla.redhat.com/show_bug.cgi?id=2033130 — ASSIGNED
exclude_from_weak_autodetect=true effectively renders rich weak
dependencies useless

Behavior introduced by the "Enable exclude_from_weak_autodetect by
default in LIBDNF" System-Wide Change appear to have undesired effects
in some use cases, particularly with language packs. Upstream pull
request 1439 (https://github.com/rpm-software-management/libdnf/pull/1439)
contains an improvement for autodetection.


Proposed blockers
-

1. distribution — https://bugzilla.redhat.com/show_bug.cgi?id=2032085 — POST
Some variants are missing /etc/resolv.conf symlink (use systemd-resolved)

Some variants are not using systemd-resolved as intended. With some
recently-merged changes to Anaconda, this appears to be working
correctly now, at least for ostree variants.

2. gnome-shell — https://bugzilla.redhat.com/show_bug.cgi?id=2054761 — ON_QA
Updating gnome-shell to 42~beta-1.fc37 or mutter to 42~beta-1.fc37
version breaks the login screen.

A crash message is displayed instead of the login screen. This is
fixed in gjs 1.71.1.

3. 

F36 Beta blocker status summary

2022-02-10 Thread Ben Cotton
Now that we've reached the branch point, it's time to start doing
weekly blocker summaries again! Beta freeze begins on 22 February and
the current target Beta release date is 15 March.

Action summary


Accepted blockers
-
1. anaconda — When running anaconda on Wayland with two keyboard
layouts configured, hitting any modifier key with the second layout
selected switches to the first layout — ASSIGNED
ACTION: Maintainers to diagnose issue

2. distribution — Fedora 36 backgrounds not present on
release-blocking desktops (GNOME, KDE) — NEW
ACTION: Maintainers to update background packages

3. fedora-release — fedora-release-identity-cloud says "Cloud
Edition", Cloud has not been an edition for years — NEW
ACTION: Maintainers to update fedora-release-identity-cloud or
group-with-such-authority to waive this.

4. kwin — openQA clicks in anaconda on KDE stop working shortly after
it starts — NEW
ACTION: Maintainers to diagnose issue

5. libinput — GNOME doesn't accept input from wireless keyboard if
there's not another "keyboard" input available — NEW
ACTION: Maintainers to diagnose issue

6. linux-firmware — Fedora 36: Server boot x86_64 image exceeds
maximum size — ASSIGNED
ACTION: None

Proposed blockers
-

1. distribution — Some variants are missing /etc/resolv.conf symlink
(use systemd-resolved) — POST
ACTION: QA to verify issue is resolved

2. dnf — exclude_from_weak_autodetect=true effectively renders rich
weak dependencies useless — NEW
ACTION: dnf maintainers to decide on approach for "instally only newly
recommended packages" proposal

Bug-by-bug detail
=

Accepted blockers
-
1.  anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2016613 — ASSIGNED
When running anaconda on Wayland with two keyboard layouts configured,
hitting any modifier key with the second layout selected switches to
the first layout

adamwill's research shows that this bug has existed since F25, but
became more viisble after KDE switched to Wayland by default. This bug
was deferred to F36 Beta under the "too hard to fix" exception.
There's ongoing discussion trying to come up with a potential fix,
however we still seem to be a long way from that point.

2. distribution — https://bugzilla.redhat.com/show_bug.cgi?id=2052654 — NEW
Fedora 36 backgrounds not present on release-blocking desktops (GNOME, KDE)

The usual desktop background blocker.

3. fedora-release — https://bugzilla.redhat.com/show_bug.cgi?id=2018271 — NEW
fedora-release-identity-cloud says "Cloud Edition", Cloud has not been
an edition for years

Waived from F35 final under the "late blocker exception." Cloud WG is
working on a proposal to re-promote Cloud to Edition status, but that
will not happen for F36 release cycle.

4. kwin — https://bugzilla.redhat.com/show_bug.cgi?id=2047503 — NEW
openQA clicks in anaconda on KDE stop working shortly after it starts

Shortly after the installer starts, mouse clicks in openQA stop
working. Using 'development mode' which allows for manual interaction
still works. This bug only affects KDE, and appears to have been
introduced in the KDE Plasma 5.24 pre-release on 2022-01-19. This bug
is accepted under the "hinders execution of required Beta test plans"
criterion.

5. libinput — https://bugzilla.redhat.com/show_bug.cgi?id=2017043 — NEW
GNOME doesn't accept input from wireless keyboard if there's not
another "keyboard" input available

On some hardware, devices with multiple capabilities that include
keyboard do not get registered as a keyboard. Thus they only work if
another keyboard is connected. It seems to mostly (or exclusively)
affect some ARM hardware.

6. linux-firmware —
https://bugzilla.redhat.com/show_bug.cgi?id=2031214 — ASSIGNED
Fedora 36: Server boot x86_64 image exceeds maximum size

Fedora-Server-netinst-x86_64-36-20220210.n.0.iso is 731906048 bytes,
which is below the maximum size of 734003200. This bug can probably be
closed until the image exceeds the limit again.

Proposed blockers
-

1. distribution — https://bugzilla.redhat.com/show_bug.cgi?id=2032085 — POST
Some variants are missing /etc/resolv.conf symlink (use systemd-resolved)

Some variants are not using systemd-resolved as intended. With some
recently-merged changes to Anaconda, this appears to be working
correctly now.

2. dnf — https://bugzilla.redhat.com/show_bug.cgi?id=2033130 — NEW
exclude_from_weak_autodetect=true effectively renders rich weak
dependencies useless

Behavior introduced by the "Enable exclude_from_weak_autodetect by
default in LIBDNF" System-Wide Change appear to have undesired effects
in some use cases, particularly with language packs. It appears that a
robust fix is technically difficult, and the Change owners are
discussing reverting this Change for F36 (see BZ 2013327).

-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
devel mailing list