Fedora Linux 34 Final blocker status update #2
by Ben Cotton
I'm on PTO tomorrow, so you get this a day early. Lucky you!
Action summary
====================
Accepted blockers
-----------------
1. sddm — logout after switch returns the user to console instead of sddm — NEW
ACTION: sddm maintainers to diagnose and fix issue
2. shim — include new bootloaders on Fedora 34 install media so UEFI
Secure Boot enabled systems can boot from them — ASSIGNED
ACTION: shim maintainers to provide shim signed with new key
Proposed blockers
-----------------
1. abrt — Abrt does not catch a simulated segfault — NEW
ACTION: QA to gather more data and have other testers confirm
2. LiveCD - KDE — KDE live image shows update notifications — MODIFIED
ACTION: QA to verify KDE live images
3. gdm — Login using password failed after upgrade to Fedora 34 — NEW
ACTION: gdm maintainers to diagnose and fix issue
4. mesa — External monitor doesn't work on Lenovo P50 after upgrading
to F34 — NEW
ACTION: mesa maintainers to submit F34 update for mesa-21.0.1-2
5. mutter — gnome-shell crashes when display blanking is activated — POST
ACTION: mutter maintainers to submit F34 update for mutter-40.0-2
Bug-by-bug detail
=============
Accepted blockers
-----------------
1. sddm — https://bugzilla.redhat.com/show_bug.cgi?id=1929643 — NEW
logout after switch returns the user to console instead of sddm
Using the "Switch User" functionality in sddm results in dropping to a
console: either to tty2 with a working text login prompt, or to tty1
where only a blinking cursor appears (no login prompt).
2. shim — https://bugzilla.redhat.com/show_bug.cgi?id=1938630 — ASSIGNED
include new bootloaders on Fedora 34 install media so UEFI Secure Boot
enabled systems can boot from them
The current shim was signed in 2018 and its signing key was revoked
last year due to the Boothole vulnerability. We need a new shim to
make sure F34 images will boot on machines with Secure Boot enabled.
Proposed blockers
-----------------
1. abrt — https://bugzilla.redhat.com/show_bug.cgi?id=1937783 — NEW
Abrt does not catch a simulated segfault
abrt is not catching simulated segfaults when SELinux is enabled.
However it is not universally-reproducible, so further testing is
needed.
2. LiveCD - KDE — https://bugzilla.redhat.com/show_bug.cgi?id=1939751 — NEW
KDE live image shows update notifications
Discover shows that updates are available, which live images are not
supposed to do. A fix to the kickstarts was merged, so now we just
need to verify a new compose.
3. gdm — https://bugzilla.redhat.com/show_bug.cgi?id=1942443 — NEW
Login using password failed after upgrade to Fedora 34
When a device has a fingerprint reader, but no fingerprints are
enrolled, login fails on the default terminal. Switching to a
different virtual console allows login. Removing fprintd-pam resolves
the problem, but is probably not the solution we want.
4. mesa — https://bugzilla.redhat.com/show_bug.cgi?id=1942175 — NEW
External monitor doesn't work on Lenovo P50 after upgrading to F34
If the display offloading GPU doesn't support OpenGL, we get two
OpenGL contexts for each GPU. Disabling zink, as in mesa-21.0.1-2
fixes the issue.
5. mutter — https://bugzilla.redhat.com/show_bug.cgi?id=1941971 — POST
gnome-shell crashes when display blanking is activated
With hybrid GPUs, when the screen is set to blank after a period of
inactivity, the blanking crashes gnome-shell and returns the user to
the gdm greeting screen. This is fixed in mutter-40.0-2.
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
3 years, 1 month
Fedora Accounts Migration & Production Rollout Update: Day 1.5/2 +1
by Aoife Moloney
Hi Everyone,
The title means that we are 1.5 days into our original planned disruption
period but some of the configurations were more complex and has resulted in
our team falling behind on completion.
We are still actively working on the production deployment of the new
Fedora Accounts System, but we believe you will be experiencing disruptions
for a minimum further 24 hours. Newest disruption time ending should be
around 1800 UTC on Friday 26th March.
We do apologise for the disruptions and loss of access you may be
experiencing in services you are trying to login to.
Currently the following services should be unaffected:
bodhi.fedoraproject.org
teams.fedoraproject.org
ask.fedoraproject.org
bugzilla.redhat.com (using SAML)
secondary.fpo
fedora wiki
We are also using https://status.fedoraproject.org/ for updates but the
going is slow so please bear with us.
If you cannot login to any service for Fedora, we recommend clearing
cookies/cache, waiting for up to one hour and retrying your login then. If
the issue persists, please open a ticket on
https://pagure.io/fedora-infrastructure/issues and our team will get to it
over the coming days.
Our team is working in IRC channel #fedora-aaa but we would ask you to file
tickets rather than report them there please.
Any and all help on this migration is most welcome and we would again like
to offer our sincerest thanks to the people from all over the world and
across multiple communities, not just Fedora, who have been helping our
team with this deployment and migration.
We hope to complete the most critical pieces of work by Friday 1800 UTC -
the end is in sight so thank you for your patience through this time!
Kindest regards,
Aoife & the Fedora Accounts Team
--
Aoife Moloney
Product Owner
Community Platform Engineering Team
Red Hat EMEA <https://www.redhat.com>
Communications House
Cork Road
Waterford
<https://www.redhat.com>
3 years, 1 month
gcompris-qt license change
by Andrea Musuruane
gcompris-qt changed license from GPLv3+ to AGPLv3 in version 1.1 because
they used a library for analog electricity activity under AGPLv3 causing
the whole software to be licensed under it.
Regards,
Andrea
3 years, 1 month
Fedora Accounts Migration & Production Rollout Update: Day 1/2
by Aoife Moloney
Hi Everyone,
Just wanted to share a quick update on the New Fedora Accounts deployment
to production and migration.
The team are working around the clock to configure all systems to
authenticate with the new service and you are likely to
experience inaccessibility to some services over the next 24 - 48 hours. If
you try to login to some services and recieve an 'Unknown User' or 'OpenID
request Cancelled' or similar, please try clearing cookies and try to
re-log in. If this still doesn't work, the accounts team are likely working
on this service at that moment. Please wait a few hours and re-try. If you
have any serious issues logging into services. please file a ticket in
https://pagure.io/fedora-infrastructure and our team will look into them as
soon as the production rollout has been completed. We are still expecting
this to be completed by Friday 26th March.
Over the next 24 - 48 hours, we are asking you all to please be patient
with us while we operationalize the new service and sincerely thank you for
your understanding during this outage period.
Our team is working in channel freenode #fedora-aaa and we would like to
also offer our sincerest gratitude and thanks to those of you across the
Fedora and CentOS communities who are helping us roll the new system out.
We will send another status report tomorrow on the progress we have made
and you can also use https://status.fedoraproject.org/ to check on service
downtime.
On behalf of the Fedora Accounts team, thank you all again for bearing with
us while we complete this project!
Kindest regards,
Aoife & The Fedora Account Team
--
Aoife Moloney
Product Owner
Community Platform Engineering Team
Red Hat EMEA <https://www.redhat.com>
Communications House
Cork Road
Waterford
<https://www.redhat.com>
3 years, 2 months
