With luck, this is the last time I'll send this until Fedora 34 Beta!
The Go/No-Go is Thursday.
Action summary
====================
Accepted blockers
-----------------
1. sddm — login stuck when changing users repeatedly (log out, log in
a different one) — ASSIGNED
ACTION: QA to test FEDORA-2020-f5be904258
2. shim — Secure Boot fails to boot F33 Beta image — NEW
ACTION: (none. waiting for new shim to be signed)
Proposed blockers
-----------------
1. bluez — bluetooth mouse does not autoconnect after sleep — NEW
ACTION: bluez maintainers to diagnose and fix issue
Bug-by-bug detail
=============
Accepted blockers
-----------------
1. sddm —
https://bugzilla.redhat.com/show_bug.cgi?id=1861700 — ASSIGNED
login stuck when changing users repeatedly (log out, log in a different one)
Tricky bug that may need F34 to fix fully. Short term suggestion is to
provide service files of type=dbus. rdieter has implemented a
workaround to restart dbus.service after an 8-second wait. This is
update FEDORA-2020-f5be904258.
2. shim
https://bugzilla.redhat.com/show_bug.cgi?id=1883609 NEW
Secure Boot fails to boot F33 Beta image
It appears that Ubuntu has pushed a Secure Boot revocation list early,
so people who have previously installed Ubtunu will not be able to
boot Fedora. This is accepted as a FESCo blocker. A new shim was
intended for submission with an expectation of getting it signed in
"not more than a couple of days".
Proposed blockers
-----------------
1. bluez —
https://bugzilla.redhat.com/show_bug.cgi?id=1874082 — NEW
bluetooth mouse does not autoconnect after sleep
Some Bluetooth devices do not reconnect after resuming from sleep
without manual intervention. From the discussion on the test mailing
list, it's not universal, but it does not appear to be limited to a
few devices, either. Update FEDORA-2020-00bf5ac290 contained a
possible fix, but did not change the behavior.
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis