okay, I've uploaded a very similar patch to what Roman has proposed to
intrepid. I tested the packages in a kvm instance, obviously without
wpasupplicant.

My current guess what's going wrong here:

The udev rules gets activated too early in the boot sequence, most
probably with S10udev, where udev gets started. This is before any fscks
have been done and also before the root filesystem has been remounted rw
in S20checkroot.sh. This is not really the best time to start things
like wpasupplicant.

Syncronizing the udev rule with S40networking is probably still not
exactly the right solution. However I still think it is correct for this
particular problem, because at that time, we are expect that the network
is able to come up. In fact it should be safe to do already right after
S20checkroot.sh. Waiting until S40networking isn't too bad as well,
however.

-- 
wpasupplicant doesn't start when the network start
https://bugs.launchpad.net/bugs/44194
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

Reply via email to