On Thu, Dec 12 2013, wra...@privatdemail.net wrote: > On 13/12/13 09:47, Canek Peláez Valdés wrote: >> On Wed, Dec 11, 2013 at 4:52 PM, <gottl...@nyu.edu> wrote: >>> At home I use a wired connection so did notice the following problem >>> until I traveled and tried to connect wirelessly. The problem must have >>> started sometime within the past month. >>> >>> If I have wicd started by systemd, i.e. systemctl enable wicd The wired >>> network is started fine but not the wireless. Instead, I see in the >>> systemd journal >>> >>> wicd[290]: Failed to connect to non-global ctrl_ifname: wired error: No >>> such file or directory wicd[290]: Failed to connect to non-global >>> ctrl_ifname: wireless error: No such file or directory >>> >>> If I instead systemctl disable wicd, reboot, and then manually type >>> wpa_supplicant -i wireless -c /etc/wpa_supplicant/wpa_supplicant.conf -B >>> it works. >>> >>> Indeed after I have booted I can start wicd and cannot get the error >>> above, but the actual behavior is not consistent. >>> >>> My system is ~amd64, profile gnome/systemd >>> >>> My wireless driver is from the package broadcom-sta (wl) >> >> I have never used wicd, so I can't say exactly what it's the problem; but I >> was under the impression that wicd is basically dead. Its last release was >> more than a year and a half ago. >> >> Regards. >> > > I don't use wicd (or systemd) either, but you could have a look at what the > systemd unit is attempting to run (assuming it isn't one of it's "special" > type of units). Systemd units are just plain-text files. > > Default unit location is > /usr/lib/systemd/system > (or you could try > locate wicd.service > > and the parameter you're looking for is ExecStart.
thanks but I had done that and the command is simply /usr/sbin/wicd --no-daemon Perhaps relevant is Type=dbus Canek points out that wicd has had no new releases. Perhaps I should switch to networkmanager. I will try that tomorrow. Thank you both, allan
