On Fri, 2018-06-29 at 16:32 +0200, Thomas Haller wrote:
at the time when NM searches for a suitable profile to autoactivate, is the one with the higher available for autoconnect?
Yes it is. They both have "permissions" defined in the [connection] section to be only valid for the user who owns the machine. In my case, in both profiles: [connection] permissions=user:jgoguen:;
For example, as it is 802-1x, does it have the required secrets?
It turns out this is actually the problem. I was able to track down, but I have no idea why, that gnome-keyring is actually not unlocked (or more likely not responding to DBus, it's unlocked by PAM so it should be unlocked when the session starts) when NetworkManager attempts to load secrets for the 802.1X profile, but it is loaded just fine when I'm able to get a shell up to manually query it. Thank you, now I get to figure out how to make NM wait or make gnome- keyring come up earlier. -- Joel Goguen
Attachment:
signature.asc
Description: This is a digitally signed message part