Comment 8 for bug 1097002

Actually, on Quantal, I even installed a Debian kernel, upstream looked at the result and said as soon as the kernel gets the authenticate signal it promptly connects. As you can see from the syslogs, once the NM gets around to issuing the "authentiate", the kernel goes right ahead and connects.

The problem is, the NM does not bother to send the "authenticate" to the kernel. No way the kernel can connect if NM doesn't ask it to.

Where in the NM scripts is it supposed to issue the authenticate and connect? Is it possible to patch the NM to put a tell tale syslog message in the NM scripts to say it is going to connect, or why it won't issue the connect?

I can try to apply a patch, but I'm not a developer so I don't know how to write a patch for NM to find out where it decides not to connect, or why NM stopped before issuing the authenticate.

Thank you for looking at this.

BTW, linuxmint14 based on Quantal has no such trouble. Use settings to set up hidden wireless and works every time thereafter. I don't know how to compare the mint14 nm scripts to the quantal nm scripts.