Network monitor behaviour

why is nm-applet important?
NM will connect at boot to the network without nm-applet.

To manage/configure quick and easyly different connections of course, wireless, wired, vpn, etc.

a good reason but if you use always same networks (home, office, university, etc) the configurations are stored in /etc/NetworkManager (or so) i guess NM will connect to the available network.
i would try it without nm-applet, remove it and if it doesn’t work, you can find the plasma-nm in var/cache/pacman/pkg

edit:
our plasma-pa package is hopeless outdated, arch linux are using plasma-nm 5.18.2-1 and our plasma-nm 5.17.3-1
my suggestion is: report it as outdated on our bug tracker

edit conflict

such a censored!
so i can’t remove typo or add additional information.
the software annoys me more and more

I believe the problem is actually the plasma-nm. I uninstalled it, and things looks to go better, but now I cannot access my vpn anymore.

I would try the up-to-date version of applet-nm, I got the arch one but it didn’t compile on my system.

So I installed the nm-applet, from gnome i think, and it works good but it is not possible to connect to vpn’s even if it sees the two I configured on plasma-nm.

– UPDATE –
It is the same thing, only the nm-applet seems to be more stable than plasma-nm, but, every time, for example restoring from a suspension, it creates another connection with a standard configuration, that is not my configuration, ad connects to it.

Hope it to be solved soon, because it is very annoying and it is getting to be not usable, sigh.
Regards,

opened ISSUE #334
Reported as outdated, DONE !

1 Like

i suppose it is useless for you
Then, some other, old problems remain. Wireless deactivated/activated stuff on login.

I can confirm the issue here.
I have it on 3 pc, two with wired and one with wireless connection.
The wired ones never left the network, so it is definitely not a configuration issue.

I already thought our router was defunct…

The issue is very annoying, since it does make steam crash.

Link please, so we all can see the progress.

plasma-nm

Current version in our repositories

core/plasma-nm 5.17.3-1

New version available upstream

plasma-nm 5.18.3-1 https://www.archlinux.org/packages/extra/x86_64/plasma-nm/


Issue 334

Ok, thanks.
I can definitely confirm that uninstalling plasma-nm fixes the issue for me.

The whole Plasma group seems not to be update in chakra, so there is a good chance it is fixed in upstream…

Ok. How to manage VPN connection, that I need for work, without plasma-nm?

Actually, seems like I spoke to soon. Today I got the issues again… :expressionless:
Can anybody recommend some logs, in which to look for errors?

Please someone solve this issue, I am very nervous with it, because Chakra is no more usable to me.

Assuming you use openvpn you should use the commandline:

openvpn –config path/to/client.ovpn
example client.ovpn:

client
dev tun 
proto udp 
remote **youradress.tld** 1194 
resolv-retry infinite 
nobind 
persist-key 
persist-tun 
ca ca.crt 
cert **clientname.crt** 
key **clientname.key** 
ns-cert-type server 
comp-lzo 
verb 3

Stuff get worse, 100% CPU-Load on NetworkManager… :face_with_raised_eyebrow:

From Arch Wiki: NetworkManager

We should watch the journal with journalctl -f for errors. In my case I get a LOT of these within seconds, all the while Internet is still running…

...
Mär 24 19:32:37 cray NetworkManager[5208]: <error> [1585074757.9904] connectivity: connectivity check failed: 2
Mär 24 19:32:37 cray NetworkManager[5208]: <error> [1585074757.9904] connectivity: connectivity check failed: 2
Mär 24 19:32:37 cray NetworkManager[5208]: <error> [1585074757.9905] connectivity: connectivity check failed: 2
Mär 24 19:32:37 cray NetworkManager[5208]: <error> [1585074757.9905] connectivity: connectivity check failed: 2
Mär 24 19:32:37 cray NetworkManager[5208]: <error> [1585074757.9905] connectivity: connectivity check failed: 2
Mär 24 19:32:37 cray NetworkManager[5208]: <error> [1585074757.9905] connectivity: connectivity check failed: 2
Mär 24 19:32:37 cray NetworkManager[5208]: <error> [1585074757.9905] connectivity: connectivity check failed: 2
Mär 24 19:32:37 cray NetworkManager[5208]: <error> [1585074757.9906] connectivity: connectivity check failed: 2
Mär 24 19:32:37 cray NetworkManager[5208]: <error> [1585074757.9906] connectivity: connectivity check failed: 2
Mär 24 19:32:37 cray NetworkManager[5208]: <error> [1585074757.9906] connectivity: connectivity check failed: 2
...

and then it crashes and restarts:

Mär 24 19:34:14 cray NetworkManager[5208]: <info>  [1585074854.7985] manager: NetworkManager state is now CONNECTED_LOCAL
Mär 24 19:34:14 cray dbus-daemon[514]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.1019' (uid=0 pid=5208 comm="/usr/bin/NetworkManager --no-daemon ")
Mär 24 19:34:14 cray systemd[1]: Starting Network Manager Script Dispatcher Service...
Mär 24 19:34:14 cray dbus-daemon[514]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Mär 24 19:34:14 cray systemd[1]: Started Network Manager Script Dispatcher Service.
Mär 24 19:34:14 cray nm-dispatcher[8598]: req:1 'connectivity-change': new request (1 scripts)
Mär 24 19:34:14 cray nm-dispatcher[8598]: req:1 'connectivity-change': start running ordered scripts...
Mär 24 19:34:17 cray audit[5208]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 pid=5208 comm="NetworkManager" exe="/usr/bin/NetworkManager" sig=11 res=1
Mär 24 19:34:17 cray kernel: NetworkManager[5208]: segfault at 84 ip 00007f3f6a5d3ffc sp 00007ffd6ed34520 error 4 in libcurl.so.4.6.0[7f3f6a5aa000+59000]
Mär 24 19:34:17 cray kernel: Code: ff ff 4c 89 f7 67 e8 53 c0 ff ff 48 85 c0 74 44 66 0f 1f 44 00 00 48 8b 78 18 48 8b 47 10 48 85 c0 74 17 48 8b 90 f0 03 00 00 <f6> 82 84 00 00 00 08 75 07 44 89 a8 00 07 00 00 31 f6 ba 07 00 00
Mär 24 19:34:17 cray kernel: audit: type=1701 audit(1585074857.786:78): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=5208 comm="NetworkManager" exe="/usr/bin/NetworkManager" sig=11 res=1
Mär 24 19:34:17 cray systemd[1]: Started Process Core Dump (PID 8602/UID 0).
Mär 24 19:34:17 cray systemd-coredump[8603]: Removed old coredump core.NetworkManager.0.e8499e7a474a4239b4ab1cdb3be4718e.5077.1585073721000000.lz4.
Mär 24 19:34:17 cray systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=11/SEGV
Mär 24 19:34:17 cray systemd[1]: NetworkManager.service: Failed with result 'core-dump'.
Mär 24 19:34:18 cray systemd-coredump[8603]: Process 5208 (NetworkManager) of user 0 dumped core.
                                              
                                              Stack trace of thread 5208:
                                              #0  0x00007f3f6a5d3ffc n/a (libcurl.so.4)
                                              #1  0x00007f3f6a5d4254 curl_multi_socket_action (libcurl.so.4)
                                              #2  0x0000559d96cdd8eb n/a (NetworkManager)
                                              #3  0x0000559d96cddb62 n/a (NetworkManager)
                                              #4  0x00007f3f6a962960 g_main_context_dispatch (libglib-2.0.so.0)
                                              #5  0x00007f3f6a964608 n/a (libglib-2.0.so.0)
                                              #6  0x00007f3f6a965562 g_main_loop_run (libglib-2.0.so.0)
                                              #7  0x0000559d96b8c7c7 n/a (NetworkManager)
                                              #8  0x00007f3f6a3cee93 __libc_start_main (libc.so.6)
                                              #9  0x0000559d96b8cdfa n/a (NetworkManager)
                                              
                                              Stack trace of thread 5209:
                                              #0  0x00007f3f6a49aeb1 __poll (libc.so.6)
                                              #1  0x00007f3f6a96457e n/a (libglib-2.0.so.0)
                                              #2  0x00007f3f6a96464c g_main_context_iteration (libglib-2.0.so.0)
                                              #3  0x00007f3f6a964691 n/a (libglib-2.0.so.0)
                                              #4  0x00007f3f6a92e745 n/a (libglib-2.0.so.0)
                                              #5  0x00007f3f6a579580 start_thread (libpthread.so.0)
                                              #6  0x00007f3f6a4a5a83 __clone (libc.so.6)
                                              
                                              Stack trace of thread 5211:
                                              #0  0x00007f3f6a49aeb1 __poll (libc.so.6)
                                              #1  0x00007f3f6a96457e n/a (libglib-2.0.so.0)
                                              #2  0x00007f3f6a965562 g_main_loop_run (libglib-2.0.so.0)
                                              #3  0x00007f3f6b0d49a6 n/a (libgio-2.0.so.0)
                                              #4  0x00007f3f6a92e745 n/a (libglib-2.0.so.0)
                                              #5  0x00007f3f6a579580 start_thread (libpthread.so.0)
                                              #6  0x00007f3f6a4a5a83 __clone (libc.so.6)
Mär 24 19:34:18 cray systemd[1]: systemd-coredump@72-8602-0.service: Succeeded.
Mär 24 19:34:18 cray systemd[1]: NetworkManager.service: Service RestartSec=100ms expired, scheduling restart.
Mär 24 19:34:18 cray systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 59.
Mär 24 19:34:18 cray systemd[1]: Stopped Network Manager.
Mär 24 19:34:18 cray systemd[1]: Starting Network Manager...
Mär 24 19:34:18 cray NetworkManager[8612]: <info>  [1585074858.2984] NetworkManager (version 1.12.0-1) is starting... (after a restart)
Mär 24 19:34:18 cray NetworkManager[8612]: <info>  [1585074858.2985] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf)
Mär 24 19:34:18 cray NetworkManager[8612]: <info>  [1585074858.3126] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"

Exactly the same issue here. From time to time the NetworkManager runs crazy like yours.

@tomaggio
I think this is clearly a NetworkManager issue. Also the chakra version is quite outdated (build date 2018). Can you open a ticket for a new version?

btw I tried disablying connectivity checking in /etc/NetworkManager/NetworkManager.conf:

[connectivity]
.set.enabled=false

But that didn’t help…

mmh i my Chakra Version is:

$ cat /etc/lsb-release 
LSB_VERSION=1.4
DISTRIB_ID="Chakra"
DISTRIB_RELEASE="2019.03"
DISTRIB_CODENAME="Hawking"
DISTRIB_DESCRIPTION="Chakra"

The @team knows about this and is working on it. But i have no idea how long it will take.
Greets

I occasionally see network manager using excessive CPU time too. Restarting it seems to alleviate it.

sudo systemctl restart NetworkManager

1 Like