Network Manager 1.12 Random disconections?


Hi ,

On unstable repo I have updated today the network manger to version 1.12 and from that moment I have a lot of network problems.
For example when I am listening to the online radio with clementine it randomly stops and clementine either stops or proceeds with the next station.Also while watching an online video out of sudden it stops to reconnect again.

I hope is not my connection but everything was working fine until I did the updates…
Well hopefully it will be fixed soon


Did you reboot after the update? Did all Network Manager components get upgraded at the same time?


Is this with a wired or wireless connection.

Perhaps you could provide an output please.

inxi -Fxzc0


My connection is wired and I did reboot my pc.

I think in the past I have disable and masked the NetworkManager-wait-online.service dont know if that is the reason. :thinking:


I would not think that would cause this behaviour.


Are you using an r8168 NIC.

[WPC wolfyrion]# inxi -Fxzc0
System:    Host: WPC Kernel: 4.18.0-1-MANJARO x86_64 bits: 64 compiler: gcc v: 8.1.1 Desktop: KDE Plasma 5.13.2 
           tk: Qt 5.11.1 Distro: Manjaro Linux 17.1.10 Hakoila 
Machine:   Type: Desktop Mobo: ASRock model: X399 Professional Gaming serial: <filter> 
           UEFI [Legacy]: American Megatrends v: P2.00 date: 11/21/2017 
CPU:       Topology: 16-Core (2-Die) model: AMD Ryzen Threadripper 1950X bits: 64 type: MT MCP MCM arch: Zen 
           rev: 1 L2 cache: 8192 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 217294 
           Speed: 2196 MHz min/max: 2200/3600 MHz Core speeds (MHz): 1: 2325 2: 3480 3: 2184 4: 1975 5: 3082 
           6: 2259 7: 1799 8: 2058 9: 2176 10: 3361 11: 3479 12: 2046 13: 3319 14: 2485 15: 1988 16: 1829 
           17: 1977 18: 1996 19: 2159 20: 2183 21: 2189 22: 3252 23: 2161 24: 2025 25: 2018 26: 2191 27: 2339 
           28: 1818 29: 1752 30: 1842 31: 1887 32: 2134 
Graphics:  Card-1: NVIDIA GP102 [GeForce GTX 1080 Ti] driver: nvidia v: 396.24 bus ID: 42:00.0 
           Display: x11 server: X.Org 1.20.0 driver: nvidia 
           resolution: 2560x1440~60Hz, 1920x1080~60Hz, 3840x2160~30Hz, 1920x1080~60Hz 
           OpenGL: renderer: GeForce GTX 1080 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 396.24 direct render: Yes 
Audio:     Card-1: Advanced Micro Devices [AMD] Family 17h HD Audio driver: snd_hda_intel v: kernel 
           bus ID: 0a:00.3 
           Card-2: NVIDIA GP102 HDMI Audio driver: snd_hda_intel v: kernel bus ID: 42:00.1 
           Card-3: Focusrite-Novation Scarlett 18i8 2nd Gen type: USB driver: snd-usb-audio bus ID: 3:2 
           Sound Server: ALSA v: k4.18.0-1-MANJARO 
Network:   Card-1: Aquantia AQC107 NBase-T/IEEE 802.3bz Ethernet [AQtion] driver: atlantic v: 
           port: N/A bus ID: 03:00.0 
           IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Card-2: Intel I211 Gigabit Network Connection driver: igb v: 5.4.0-k port: 7000 bus ID: 04:00.0 
           IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Card-3: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi v: kernel bus ID: 05:00.0 
           IF: wlp5s0 state: down mac: <filter> 
           Card-4: Intel I211 Gigabit Network Connection driver: igb v: 5.4.0-k port: 6000 bus ID: 06:00.0 
           IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           IF-ID-1: enp6s0 state: down mac: <filter> 
Drives:    HDD Total Size: 17.07 TiB used: 8.90 TiB (52.1%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 PRO 512GB size: 476.94 GiB 
           ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 960 PRO 512GB size: 476.94 GiB 
           ID-3: /dev/sda vendor: Western Digital model: WD40EFRX-68WT0N0 size: 3.64 TiB 
           ID-4: /dev/sdb vendor: Samsung model: SSD 850 PRO 256GB size: 238.47 GiB 
           ID-5: /dev/sdc vendor: Western Digital model: WD40EFRX-68WT0N0 size: 3.64 TiB 
           ID-6: /dev/sdd vendor: Seagate model: ST10000DM0004-1ZC101 size: 9.10 TiB 
Partition: ID-1: / size: 476.93 GiB used: 185.32 GiB (38.9%) fs: f2fs dev: /dev/nvme0n1p1 
           ID-2: /boot size: 968.3 MiB used: 135.2 MiB (14.0%) fs: ext4 dev: /dev/sdc1 
           ID-3: /home size: 476.93 GiB used: 203.54 GiB (42.7%) fs: f2fs dev: /dev/nvme1n1p1 
Sensors:   System Temperatures: cpu: 51.2 C mobo: N/A gpu: nvidia temp: 50 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 32% 
Info:      Processes: 566 Uptime: 1h 01m Memory: 31.34 GiB used: 6.21 GiB (19.8%) Init: systemd Compilers: 
           gcc: 8.1.1 clang: 6.0.0 Shell: bash v: 4.4.23 inxi: 3.0.12 


First off I would downgrade to the 4.14 LTS kernel to test things out there. If no better test other kernels.

For some reason dual NIC mobo’s seem to have a fair bit of issues I’ve noticed. If your BIOS allows, try disabling one of your NIC’s and your wireless adapter as well. Just to see if there is any difference.


I am telling you is not a nic problem since everything was working fine before the update.
Only one nic atm is enabled and still random disconnections are happening.
Also is not a kernel problem and LTS is a very old kernel and NOT compatible with some of my devices.
I guess I can go back to 4.17 but I didnt have this problem with 4.8 before the updates.

Anyway I will speak with my provider as well or check other devices in my network if are experiencing random disconnections.


Did you connect all cards to the same network? Just recently I read somewhere, forget where thought, that that might be the cause for errors.
Either disconnect the cables of the cards you don’t use, or disconnect as @tbg already wrote, or connect them to different networks.


Testing out kernel 4.16 & 4,17 is very easy so I don’t know why you would make an issue out of that. Kernel regressions happen fairly regularly that can destabilize what were otherwise perfectly working network drivers.

If you’re that sure it is network manager why not downgrade it.


I guess you are not very familiar with the process of troubleshooting. The whole point is to eliminate variables, even if you may consider my process pointless, it is nevertheless the proper method.

If you do not want to listen to my suggestions that is fine, I’m sure someone else will be by to offer you assistance soon. However if you want to post a help request you should really follow any rational suggestions offered. Otherwise, why bother requesting help if you have no intention of following the advice given?

I had to request twice that you post your hardware specs, before you complied. Any help thread requires your specs. Even that was a bother for you. Sorry to have inconvenienced you with my pointless requests. BTW, the first thing you should have done was confirmed it was not your Internet provider causing your issues before posting a help request. You seem to expect the forum should just provide you with the magical answer without you actually having to do anything yourself. You will find that generally doesn’t work well.

Carry on bravely.


version 1.12 for Networking manager is not minor update


That made me giggle a bit …cough… lets say that my whole life has to do daily with troubleshooting :wink:

Anyway I went back to testing repo which uses network manager 1.10 and everything is normal again.
Btw Are you all on unstable repo ? I find it a bit weird that only me has this problem.
(well I would find it weirder if you are not on the unstable repo and do troubleshooting)

The weirder thing for me is that after installing kernel 4.17 on unstable repo the problem I had with the notifications in KDE are back again which they were fixed with today updates and using kernel 4.18.
post related

ps: atm I am having my ISP checking everything since I have noticed one disconnection within more than 1 hour of listening to radio (maybe that was normal)


Yes, I just picked up 1.12 on my machines (all running MATE, though) and haven’t noticed anything odd yet.


I have tested 1.12 with ALL 3 different network cards and different ip’s on each network card.
ALL network cards had the same problem, random disconnects every few seconds.

I am back to unstable but at the moment I have put network manager to my ignore list so as not to update that package since it gives me problems.

Maybe this is happening on desktop pcs with multiple network cards? :thinking:


Possibly. I assume you’ve checked for any pacnews that need merging?


My apologies but I dont know what do you mean…
What it means to check any pacnews that need merging?
What I have to do ?


If you haven’t seen any messages during the 1.10->1.12 update there probably aren’t any configuration file changes…


It may not have been network manager that was responsible for your connectivity issues. The recent systemd update may have been responsible. If you had used a methodical troubleshooting approach you would have been able to definitively identify the problematic upgrade.

See the following post that may be related to your issue:

[Résolu] Connexion internet très lente/échec après maj vers v17.1.11