[SOLVED] Disable NetworkManager (under Gnome 3)

aexl · 2015-02-03 00:53:45

Since the last update I have a weird problem with my wireless connections. I use Gnome 3.14 (with gdm) on my Lenovo Yoga 2 Pro, but I don't use their official NetworkManager, I use netctl-auto instead. So the problem is, that since the last update, the Service NetworkManager.service starts automatically, and so it propably conflicts with netctl-auto. To get it to work again, I always need to the the following:

sudo systemctl stop NetworkManager.service
sudo systemctl restart netctl-auto@wlp1s0.service

I've already tried to disable NetworkManager with

sudo systemctl disable NetworkManager.service

but this didn't help, it seems as though it starts again after the next boot. Uninstalling NetworkManager doesn't seem to be possible neither, because tracker and telepathy-mission-control depends on it. Do you have any advice?

Last edited by aexl (2015-02-10 00:07:17)

benghaem · 2015-02-03 05:53:23

I have also experienced this problem and was similarly unable to disable the NetworkManager service. However, as I only had Gnome installed as an extra DE I proceeded to remove NetworkManager and the software that depended on it completely. I then recreated my resolv.conf because it had been reset. I am using a Lenovo T440s. I'm sorry if this was unhelpful, but I can confirm that removing NetworkManager solves the problem.

Head_on_a_Stick · 2015-02-03 11:07:27

I use GNOME 3 with dhcpcd.service controlling my networking and I have no problems with NetworkManager starting (it is installed but `disable`d).

empty@Arch ~ % systemctl status NetworkManager
● NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled; vendor preset: disabled)
   Active: inactive (dead)

What is the output of:

ls -l /etc/systemd/system/multi-user.target.wants

You could try:

# systemctl mask NetworkManager.service

But that should not be necessary.

aexl · 2015-02-04 08:09:04

Here is the output of "systemctl status NetworkManager.service" after the reboot:

● NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled; vendor preset: disabled)
   Active: active (running) since Mit 2015-02-04 08:45:51 CET; 31s ago
 Main PID: 372 (NetworkManager)
   CGroup: /system.slice/NetworkManager.service
           └─372 /usr/bin/NetworkManager --no-daemon

Feb 04 08:45:51 vitali NetworkManager[372]: <info>  (wlp1s0): using nl80211 for WiFi device control
Feb 04 08:45:51 vitali NetworkManager[372]: <info>  (wlp1s0): driver supports Access Point (AP) mode
Feb 04 08:45:51 vitali NetworkManager[372]: <info>  (wlp1s0): new 802.11 WiFi device (driver: 'iwlwifi' ifindex: 2)
Feb 04 08:45:51 vitali NetworkManager[372]: <info>  (wlp1s0): exported as /org/freedesktop/NetworkManager/Devices/1
Feb 04 08:45:51 vitali NetworkManager[372]: <info>  (wlp1s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Feb 04 08:45:51 vitali NetworkManager[372]: <info>  (wlp1s0): preparing device
Feb 04 08:45:51 vitali NetworkManager[372]: <info>  startup complete
Feb 04 08:45:51 vitali NetworkManager[372]: <info>  WiFi now disabled by radio killswitch
Feb 04 08:45:51 vitali NetworkManager[372]: <info>  use BlueZ version 5
Feb 04 08:45:53 vitali NetworkManager[372]: <info>  wpa_supplicant started

Isn't it strange that it gets started, even after disabling it with systemctl? This time I even had to disable Bluetooth in the Gnome Settings to get the Wifi running...

Here is the output of "ls -l /etc/systemd/system/multi-user.target.wants":

total 20
lrwxrwxrwx 1 root root 40 22. Dez 05:19 cpupower.service -> /usr/lib/systemd/system/cpupower.service
lrwxrwxrwx 1 root root 44 22. Dez 13:20 netctl-auto@wlp1s0.service -> /usr/lib/systemd/system/netctl-auto@.service
lrwxrwxrwx 1 root root 35 22. Dez 07:48 psd.service -> /usr/lib/systemd/system/psd.service
lrwxrwxrwx 1 root root 51 11. Dez 03:13 remote-fs.target -> ../../../../usr/lib/systemd/system/remote-fs.target
lrwxrwxrwx 1 root root 35 22. Dez 05:26 tlp.service -> /usr/lib/systemd/system/tlp.service

What does this "mask" command exaclty? Do you think this would solve my problem or is there a better solution?

Alad · 2015-02-04 09:08:50

Mask symlinks the service to /dev/null. You'll get a bunch of garbage in the journal, but good as a last measure otherwise.

aexl · 2015-02-10 00:06:18

Thanks, masking NetworkManager.service solved the problem. I just don't know, if it is the optimal solution...

Arch Linux

#1 2015-02-03 00:53:45

[SOLVED] Disable NetworkManager (under Gnome 3)

#2 2015-02-03 05:53:23

Re: [SOLVED] Disable NetworkManager (under Gnome 3)

#3 2015-02-03 11:07:27

Re: [SOLVED] Disable NetworkManager (under Gnome 3)

#4 2015-02-04 08:09:04

Re: [SOLVED] Disable NetworkManager (under Gnome 3)

#5 2015-02-04 09:08:50

Re: [SOLVED] Disable NetworkManager (under Gnome 3)

#6 2015-02-10 00:06:18

Re: [SOLVED] Disable NetworkManager (under Gnome 3)

Board footer