> Shouldn't this be something stronger, like "depends on"? I.e., for SRU purposes, the wpa fix is a per-requisite for this, no?
In my opinion, no. The networkmanager fix should be able to be applied without the wpa patch being present without causing any regressions, since the networkmanager patch is just an addition of a new signal handler - but the end-user behavior change just won't be noticeable if it isn't fired from anything else (like wpa). In this case, the wpa-side fix for Jammy and Noble is not as trivial to backport, and I haven't had chance to find out what else needs to be backported to those yet - but the only users who have brought this issue to our attention on Noble and prior are a partner who is already using a backported Questing version of wpa, which we can trivially apply this fix to - so it will still be easy for us to verify that the NetworkManager side fix works on older distros using a backported wpa. (and then, nm will be ready once we have more time to address the wpa backport.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2122458 Title: Password re-entry popup does not appear on incorrect password entry with WPA3 networks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2122458/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
