One aspect I feel it's slightly incorrect: The old `pam_authd.so` cannot be dlclosed once loaded, so any long-running process that already mapped the 0.6.1 module (the classic case being gnome-shell's unlock path) will get gRPC Unimplemented errors from the new daemon until it is restarted. GDM logins spawn a fresh gdm-session-worker per attempt and pick up the new module, so initial login is fine; the exposure is stale in-process modules
On unlock gnome-shell starts a new gdm-session-worker instance once the user hits enter (e.g. when you switch from the clock view to the authentication prompt view) and kills it on Escape or idle, so this should not be really an issue. That said, it's also important to note that the gnome-shell authd integration that was uploaded in resolute was mostly tested with authd 0.6.1 during its development, given that it was the one in the archive at the time. So, while e2e tests should ensure the compatibility with version 0.7.1, it's definitely something that should be highlighted in the SRU bug report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2173548 Title: SRU(Resolute): Update authd to 0.7.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/authd/+bug/2173548/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
