@Nick We merged a slightly different fix for this same end-user behavior in Questing as sauce after upstream had not replied for several months. However, upstream ended up replying [0] a bit after we did that to mention that the approach currently in questing could theoretically cause the notification to appear under some other (unrelated) conditions.
I haven't actually observed myself any cases where this has happened, but if we want to completely unify Questing with Resolute with respect to this behavior, you could apply the changes in https://code.launchpad.net/~mitchellaugustin/ubuntu/+source/wpa/+git/wpa/+merge/496765 to Questing as well. The end-user behavior of my test case in this SRU template should be the same regardless, though (and the only difference would be that you'd see SaePasswordMismatch on dbus rather than PskMismatch). [0] https://lists.infradead.org/pipermail/hostap/2025-October/043804.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2125203 Title: wpa_supplicant does not specify disconnection reason, which prevents NetworkManager from displaying password re-entry prompt on auth failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/2125203/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
