I should probably file another bug for the connection loop...
When I filed this bug the softAP didn't exist yet, so that can't have been the cause.
We have two (related) problems here:
1) when you're in an area with many access points, many PropertiesChanged signals are fired and they slow down the device for 2-3 seconds
2) when NM gets stuck connecting to a network which doesn't exist, PropertiesChanged signals are fired in an endless loop (well, it pauses 2-3 secs every time before firing all signals again)
@awe I'm sorry if the two things are mixing up :(
I should probably file another bug for the connection loop...
When I filed this bug the softAP didn't exist yet, so that can't have been the cause.
We have two (related) problems here:
1) when you're in an area with many access points, many PropertiesChanged signals are fired and they slow down the device for 2-3 seconds
2) when NM gets stuck connecting to a network which doesn't exist, PropertiesChanged signals are fired in an endless loop (well, it pauses 2-3 secs every time before firing all signals again)