Hi Joachim, thanks for looking into this and proposing a fix. I have been waiting for this for over 6 months now (sorry, I reported it too late).
Anyway, I vote for applying this patch as a temporary solution to the problem. A better fix will be to make ifup to fail if wpasupplicant fail. That way one would not relay on the write-ability of a particular file system, which may change over the time, and reintroduce the problem. Also, such an approach will never expose the machine to another network (if this happens because of some other problem in wpasupplicant). Thanks again for the detailed explanation of the problem, and the proposed fix. Cheers -- wpa_supplicant does not start on boot https://bugs.launchpad.net/bugs/192278 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
