On Tue, Dec 30, 2008 at 03:06:01AM -0000, Derek Kulinski wrote:
> Hello Alexander,
>
> > not really sure, but after resume and after things have settled and
> > then killing wpa_supplicant should make it trigger connection within a
> > few seconds.
>
> No, no... after doing that (killing wpa_supplicant) it pretty much
> always works. I just think that this shouldn't be necessary. For
> people who're just trying Linux for their first time, it might be
> extremely confusing.
Yes, its like i said. either NM has a race and doesnt properly send a
"Scan" to wpasupplicant after wake up (e.g. too early) ... or
wpasupplicant has a race and forgets about the scan because when it
receives it something isnt ready yet.
On Tue, Dec 30, 2008 at 03:06:01AM -0000, Derek Kulinski wrote:
> Hello Alexander,
>
> > not really sure, but after resume and after things have settled and
> > then killing wpa_supplicant should make it trigger connection within a
> > few seconds.
>
> No, no... after doing that (killing wpa_supplicant) it pretty much
> always works. I just think that this shouldn't be necessary. For
> people who're just trying Linux for their first time, it might be
> extremely confusing.
Yes, its like i said. either NM has a race and doesnt properly send a
"Scan" to wpasupplicant after wake up (e.g. too early) ... or
wpasupplicant has a race and forgets about the scan because when it
receives it something isnt ready yet.
Can you check out the network-manager for intrepid available in launchpad. net/~network- manager/ +archive? If that fixes it, it
http://
was definitly an NM issue :)
- Alexander