https://fedoraproject.org/wiki/Changes/Migrate_to_lastlog2
Users that did not switch to authselect prior updating to F43 ends up
with failing PAM configuration and gdm crashing.
This can be fixed by running "authselect select local --force".
If users are using authselect (which should be the majority of users),
the configuration updates automatically and this is the kind of issues
taht authselect effectively prevents. In Fedora 36, users configuration
should have been automatically switched to authselect. But it looks like
the RPM scriptlet did not work for at least some users.
This especially applies for Silverblue users, where the RPM scriptlet
was not running before for obvious ostree reasons. But I see at least
one user with Workstation as well.
I am not sure if we can handle it somehow during the update process...
but maybe we can make a loud statement in the update guide? I am open to
suggestions.
Can we add checks of the configuration as part of 'dnf system-upgrade'?
This would not solve Silverblue, but at least non-ostree distros.
Or should we override user's non-authselect configuration forcefully
with authselect onece again (but this would normally require a change
page process and still likely fail for Silverblue users; and I do not
know why the user's configuration was not changed the first time)?
Or perhaps do the change in pam scriptlet? But again, this would not
solve Silverblue.
https://bugzilla.redhat.com/show_bug.cgi?id=2406225
https://bugzilla.redhat.com/show_bug.cgi?id=2396016
--
_______________________________________________
devel 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
