Code: Select all
apt-get install network-manager
apt-get install network-manager-gnome
systemctl enable network-manager
systemctl stop wicd
systemctl disable wicd
By the way, I am using a wired, not wireless, connection.
Code: Select all
apt-get install network-manager
apt-get install network-manager-gnome
systemctl enable network-manager
systemctl stop wicd
systemctl disable wicd
Code: Select all
systemctl list-unit-files --no-pager | grep enabled
Yep. I have only wicd installed at this time.Head_on_a_Stick wrote:Can we please see the full output ofCode: Select all
systemctl list-unit-files --no-pager | grep enabled
Code: Select all
cups.path enabled
anacron.service enabled
autovt@.service enabled
avahi-daemon.service enabled
bluetooth.service enabled
console-setup.service enabled
cron.service enabled
cups-browsed.service enabled
cups.service enabled
dbus-org.bluez.service enabled
dbus-org.freedesktop.Avahi.service enabled
dbus-org.freedesktop.ModemManager1.service enabled
display-manager.service enabled
getty@.service enabled
irqbalance.service enabled
keyboard-setup.service enabled
kodi.service enabled
lightdm.service enabled
ModemManager.service enabled
networking.service enabled
pppd-dns.service enabled
rsync.service enabled
rsyslog.service enabled
rtkit-daemon.service enabled
syslog.service enabled
systemd-timesyncd.service enabled
avahi-daemon.socket enabled
cups.socket enabled
remote-fs.target enabled
anacron.timer enabled
apt-daily-upgrade.timer enabled
apt-daily.timer enabled
I've never used wicd so I don't know how it's supposed to work but you don't seem to have any unit files enabled for either that or NetworkManager.ticojohn wrote:I have only wicd installed at this time
Code: Select all
/lib/systemd/system/NetworkManager-dispatcher.service
/lib/systemd/system/NetworkManager-wait-online.service
/lib/systemd/system/NetworkManager.service
/lib/systemd/system/network-manager.service
Well, I tried to install as per the post and had to then uninstall wicd (some kind of conflict). But then I could not get network-manager to recognize my wired connection. HMMM! Anyway, I may go back through the process. Maybe I missed something the first time around. Going to not mess with it the rest of today. Want to watch American Football. Yes I like futbol as well. And Iḿ not going to offend you by saying who is my favorite team. Thanks for the inputs. Iĺl give it a go tomorrow and post results and the procedure I follow.Head_on_a_Stick wrote:I've never used wicd so I don't know how it's supposed to work but you don't seem to have any unit files enabled for either that or NetworkManager.ticojohn wrote:I have only wicd installed at this time
If you install NetworkManager does it enable the unit files itself?
Code: Select all
auto wlan0
iface wlan0 inet dhcp
wpa-ssid [my ssid]
wpa-psk [my Internet password]
You may be right. The biggest issue I have with wicd is that it can take up to 20 seconds to make a connection after I have logged in. Not that it is a real huge issue. Also read that it is no longer supported, although that may no longer be true. Also, I don't use wifi on the NUC. Just thought it would be nice having the same network manager on all my systems (Jessie 1386, Stretch i386, and Stretch amd64 on the desktop all using network-manager; Stretch amd64 on the NUC using wicd). Again, you may be correct and I might just be creating problems for myself. I might just step back and rethink the situation and invoke that old adage; if it ain't broke, don't fix it.Bulkley wrote:ticojohn, I wonder if you are asking for too much trouble. Desktops don't travel. I'm guessing that the Intel NUC won't travel.
Check the journal for any cluesticojohn wrote:The biggest issue I have with wicd is that it can take up to 20 seconds to make a connection
The NUC has both wired and wireless capabilities. The wifi connection appears to be available almost immediately, it is the wired connection that takes a long time. I'll look at the journal, even though I'll probably still be clueless. LOL! Thanks.Head_on_a_Stick wrote:Check the journal for any cluesticojohn wrote:The biggest issue I have with wicd is that it can take up to 20 seconds to make a connection
My guess would be that networking.service is causing a delay in wicd.service
Code: Select all
systemctl status networking
You must ensure that no other service that wants to configure the network is running; in fact, multiple networking services will conflict.dotlj wrote:wicd and network-manager can co-exist, but both will work better if they are the only network manager.
Yes, sorry I should have made that clearer.You must ensure that no other service that wants to configure the network is running; in fact, multiple networking services will conflict.