On Sun, Nov 27 2011, Dan Johansson wrote: > On Sunday 27 November 2011 02.02:54 Paul Hartman wrote: >> On Fri, Nov 25, 2011 at 4:58 PM, Allan Gottlieb <gottl...@nyu.edu> wrote: >> > In the last day or two wicd broke badly due to a net-tools upgrade. >> > >> > The recommended workarounds are to specify USE=old-output >> > for net-tools or to downgrade net-tools one version (I am ~amd64). >> > >> > Neither of these have helped me. Wicd cannot start either the >> > wired or wireless interface. >> >> I have no solution, but just a "me too" that wicd-based networking >> stopped working entirely after I emerged some updates a couple days >> ago. My short-term "solution" was just stop wicd and use the old-style >> net init script instead since I haven't had time to research any this >> weekend yet. > > I had the same issue after upgrading net-tools, wicd stoped working. > While googling for a solution I found a workaround: Use the "ioctl" backend > instead of the "external" backend. > For me this workaround works.
Thanks for the comments. I did the changes suggested in the bug report (downgrade net-tools or specify USE=old-output). This changed the behavior, but it was far from perfect. The next morning, however, after no hardware/software changes but after our thanksgiving guests (plus their laptops, phones, and ipads) left, wicd is working pretty well on both affected machines. I was nowhere near the 50 dhcp connection limit, but perhaps the extra radio transmissions were hurting. Anyway now one machine has the downgraded net-tools, the other USE=old-output and both seem to work. This was definitely not fun. Now for a really scary thought. I just let portage put gnome 3 on my "extra" laptop. That machine has a fresh fairly minimalistic desktop/gnome install. Light testing shows gnome-3 works as advertised. Do I dare put it on my real laptop? I am tempted to wait until intersession so as not to hinder preparing for my lectures; but I worry about letting a system go 1 month without updates. allan
