Russ Allbery <r...@debian.org> writes: > Petter Reinholdtsen <p...@hungry.com> writes:
>> Could this be a variation of #508289? wicd was involved there too. >> Reassigning there to see if the maintainer of wicd have input. > Hm, maybe. It seems like a similar problem. I can try uninstalling > wicd and see if that makes the problem go away, assuming I can reproduce > it. Or maybe next weekend. Apologies for the delay in getting more information. I can confirm that this does appear to be related to wicd, although I'm not sure why. I've been experiencing some oddities with getting the wireless network to initialize properly on my laptop for a while and was writing them off to my old base station, but not only does stopping wicd solve the problem that I experienced here, it makes those other problems go away as well (or at least significantly reduces them). For some reason, concurrent boot exacerbates the problem. My best hypothesis is that wicd is somehow grabbing the wireless device and preventing dhclient from doing what it was supposed to do, but I'm not sure. I'm running the current versions of the relevant packages: wicd 1.7.0+ds1-2 dhcp3 3.1.3-2 I don't have access to that system right at the moment and can't easily provide the additional information you asked for, but I hopefully will be able to get that to you in the next week. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
