Matthias, are you sure the absence of udevsettle was the origin of the problem? Did the committed (in casper 1.79) fix actually solve your issue?
It seems to me that udevtrigger doesn't really understand the -B and -I command line options (see man udevtrigger). And for this reason it returns an error, without actually doing nothing! So the udevsettle fix (which is needed anyway) is useless unless the udevtrigger line is fixed too (by removing the ' -Bpci -Iclass="0x02*" ' part, I think). Am I wrong? -- networking script does not wait for udev to settle https://launchpad.net/bugs/77438 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
