retitle  581586 wicd: failed to set up network with parallel booting 
(CONCURRENCY=makefile)
reassign 581586 wicd
user     initscripts-ng-de...@lists.alioth.debian.org
usertag  581586 + incorrect-dependency
thanks

[Russ Allbery]
> This is a very preliminary and probably not very usable bug report,
> unfortunately, since I haven't had time to do much investigation; I
> just disabled it again and moved on since I'm in the middle of a
> bunch of other things.  But due to the upcoming default change I
> wanted to get the bug filed in case other people ran into something
> similar and so that people were aware of it.

Very good that you did this, and thank you for bringing it to our
attention.  It is though not very useful to file it against insserv,
as the problem is likely to be in some other package.  Usertagging it
to put it on the list of dependency based boot sequencing issues, and
reassign to wicd to get input from the wicd maintainer.

Can you provide the output from /usr/share/insserv/make-testsuite, the
content of /etc/network/interfaces and the version numbers for
dhclient, ifupdown and wicd?

> I tried enabling CONCURRENCY=makefile on my laptop, and after
> rebooting the system, everything appeared to work fine, except that
> I could not get a DHCP lease.  This is a very baffling problem, I
> realize, and I can't see any obvious connection either.  But
> unloading and reloading the wireless driver (ath9k) didn't help,
> killing dhclient and running ifdown/ifup didn't help, plugging in a
> physical network connection and bringing up eth0 didn't work, and
> wicd didn't succeed either.  Wireless authentication worked, I could
> see the DHCP queries go out, but I couldn't get a lease.

Could this be a variation of #508289?  wicd was involved there too.
Reassigning there to see if the maintainer of wicd have input.

Happy hacking,
-- 
Petter Reinholdtsen



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to