|
Hello, It took me a while to repeat it again. Turns out it is probably a behavior of the nm applet not the nm. I am testing my python toolkit in a full Ubuntu desktop with the applet running. When I was testing the nm-applet picked up the bad key before my script and I quickly clicked cancel. When cancelling the applet key prompt the state goes from 60 to 30, I must have been quick enough every time for my script to miss the 60. (It sleeps 1 between checks) I guess this is by design as the applet tries to recover from the situation. If another connection exists the state goes back to 50 after a while (30,50,60,30,50....) (not sure what happens if you have a lot of connections with bad keys, but why would you) If you still want to see the log best regards, Jonas > Subject: Re: small potential exception when adding a wifi connection while device disconnected > From: dcbw redhat com > To: jonas_vikstrom hotmail com > CC: networkmanager-list gnome org > Date: Wed, 16 May 2012 17:49:07 -0500 > > On Tue, 2012-05-08 at 19:11 +0000, Jonas Vikstrom wrote: > > Hello, > > I have potentially found a small exception when adding a wifi > > connection while device disconnected. > > > > > > If I do: > > > > > > dev_iface.Disconnect() > > ... > > con_path = nm_settings_iface.AddConnection(config) > > activate_connection(get_con_uuid_by_path(con_path)) > > #activate in case it wa s previously disconneced > > > > > > but the config contains a faulty encryption key (psk) > > > > > > I then monitor the progress with a looping > > dev_prop_iface.Get("org.freedesktop.NetworkManager.Device", "State") > > > > > > it starts as expected with 50 for a while. Then it would normally give > > up and switch to 60. > > I will then catch this and prompt for a new password. > > > > > > BUT when we started with a disconnected wifi the state is switched > > back to 30 instead. > > Is this by design? I notice that there is no dev_iface.Connect().... > > > > > > Complete code here > > https://github.com/vikjon0/qfpynm > > (I have kind of worked around the problem but not sure if I will get > > sub seq issues) > > Can you grab some NM log output? Either run NM with --no-daemon or > grab /var/log/messages (or wherever syslog dumps the 'daemon' facility > in your distro). > > Dan > > |