[Solved]fix network.target critical-chain timeout, and nm applet

mablue · 2021-06-25 06:30:14

hi.
I used to install arch and gnome desktop and want to add wifi icon to my taskbar and enable it(driver is detected automaticly but no icon of nm-applet or etc shown on each desktop env bars)and after installing bunch of network-managers and etc apps on gnome and xfce4 my boot time was much increased
I find this command to detect the problem

$ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @1min 32.175s
└─gdm.service @1min 31.977s +196ms
  └─systemd-user-sessions.service @1min 31.684s +292ms
    └─network.target @1min 31.682s

but I dont know how fix the problem I cant still connect normally to networks I use usb thetering or wifi with "dhcpcd" or "wifi-menu -o" commands
but its not true way I want a graphical auto connect to my connections.
please help me to fix this slow boot and network manager problem tnx

Last edited by mablue (2021-06-26 21:12:23)

seth · 2021-06-25 06:47:03

installing bunch of network-managers

Yeah, no.
See the big fat note in https://wiki.archlinux.org/title/Networ … k_managers - then post your complete system journal so we can see what's going on (sudo journalctl -b)

V1del · 2021-06-25 06:49:33

Welcome to the boards

You truncated the relevant part which will be the service delaying the boot before the network.target , also markdown doesn't work here, use

[code]code tags[/code]

That said you only need to have one networkmanager enabled for the applet and the service in question is called NetworkManager. Disable any dhcpcd, netctl or wpa_supplicant services you might have enabled.

mablue · 2021-06-25 08:10:48

seth wrote:

installing bunch of network-managers
Yeah, no.
See the big fat note in https://wiki.archlinux.org/title/Networ … k_managers - then post your complete system journal so we can see what's going on (sudo journalctl -b)

ops! I fixed the nm applet and auto connecting problem in first try with networkmanager intro
I think I didn't installed it befoure maybe! thankksss
maybe usefull for somebody:

$ sudo pacman -S networkmanager
$ systemctl start NetworkManager.service
$ systemctl enable NetworkManager.service

but still the boot takes long time and I seen a timeout error for just a moment that cant read it.maybe its in journal:

$ sudo journalctl -b |& curl -F 'f:1=<-' ix.io 
http://ix.io/3r3Z

V1del wrote:

Welcome to the boards
You truncated the relevant part which will be the service delaying the boot before the network.target , also markdown doesn't work here, use
[code]code tags[/code]
That said you only need to have one networkmanager enabled for the applet and the service in question is called NetworkManager. Disable any dhcpcd, netctl or wpa_supplicant services you might have enabled.

thank you Im happy too much
yes I think I enabled bunch of things but now network works good I fare about disable the dhcpcd but I will try maybe it fix my boot problem!thank you

Last edited by mablue (2021-06-25 08:14:43)

V1del · 2021-06-25 08:16:24

Jun 25 12:26:23 mab systemd[1]: Dependency failed for A basic dhcp ethernet connection.
Jun 25 12:26:23 mab systemd[1]: netctl@costume\x2ddhcp\x2dprofile.service: Job netctl@costume\x2ddhcp\x2dprofile.service/start failed with result 'dependency'.
Jun 25 12:26:23 mab systemd[1]: sys-subsystem-net-devices-enp0s20f0u5.device: Job sys-subsystem-net-devices-enp0s20f0u5.device/start failed with result 'timeout'.

You need to disable this stray netctl service. Should be

systemctl disable netctl@costume-dhcp-profile

mablue · 2021-06-25 08:25:58

V1del wrote:

Jun 25 12:26:23 mab systemd[1]: Dependency failed for A basic dhcp ethernet connection.
Jun 25 12:26:23 mab systemd[1]: netctl@costume\x2ddhcp\x2dprofile.service: Job netctl@costume\x2ddhcp\x2dprofile.service/start failed with result 'dependency'.
Jun 25 12:26:23 mab systemd[1]: sys-subsystem-net-devices-enp0s20f0u5.device: Job sys-subsystem-net-devices-enp0s20f0u5.device/start failed with result 'timeout'.

You need to disable this stray netctl service. Should be

systemctl disable netctl@costume-dhcp-profile

I run this cammand you said and yes something changed but still I wait long time to boot arch!

$ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @1min 32.303s
└─gdm.service @1min 32.211s +91ms
  └─systemd-user-sessions.service @1min 31.931s +278ms
    └─network.target @1min 31.929s
      └─wpa_supplicant.service @9.712s +89ms
        └─dbus.service @7.531s
          └─basic.target @7.530s
            └─sockets.target @7.530s
              └─dbus.socket @7.530s
                └─sysinit.target @7.530s
                  └─systemd-update-utmp.service @7.496s +33ms
                    └─systemd-tmpfiles-setup.service @7.274s +220ms
                      └─local-fs.target @7.272s
                        └─efi.mount @7.175s +96ms
                          └─systemd-fsck@dev-disk-by\x2duuid-F222\x2d9E76.servi>
                            └─local-fs-pre.target @6.477s
                              └─lvm2-monitor.service @1.765s +4.711s
                                └─systemd-journald.socket @1.749s
                                  └─-.mount @1.639s
                                    └─-.slice @1.639s

$ sudo journalctl -b |& curl -F 'f:1=<-' ix.io 
http://ix.io/3r45

Last edited by mablue (2021-06-25 08:27:57)

V1del · 2021-06-25 08:49:22

it's still active. in doubt just do a

sudo rm /etc/systemd/system/multi-user.target.wants/netctl*

mablue · 2021-06-26 19:29:38

V1del wrote:

it's still active. in doubt just do a
sudo rm /etc/systemd/system/multi-user.target.wants/netctl*

thanks its solved after running this command!

$ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @9.530s
└─gdm.service @9.355s +173ms
  └─systemd-user-sessions.service @9.326s +28ms
    └─network.target @9.325s
      └─NetworkManager.service @8.375s +949ms
        └─dbus.service @8.373s
          └─basic.target @8.371s
            └─sockets.target @8.371s
              └─dbus.socket @8.371s
                └─sysinit.target @8.371s
                  └─systemd-update-utmp.service @8.344s +26ms
                    └─systemd-tmpfiles-setup.service @8.218s +124ms
                      └─local-fs.target @8.216s
                        └─home.mount @8.129s +86ms
                          └─systemd-fsck@dev-disk-by\x2duuid-2dd08636\x2d2be6\x>
                            └─local-fs-pre.target @6.715s
                              └─lvm2-monitor.service @1.814s +4.900s
                                └─systemd-journald.socket @1.799s
                                  └─-.mount @1.722s
                                    └─-.slice @1.722s

Last edited by mablue (2021-06-26 19:30:48)

Arch Linux

#1 2021-06-25 06:30:14

[Solved]fix network.target critical-chain timeout, and nm applet

#2 2021-06-25 06:47:03

Re: [Solved]fix network.target critical-chain timeout, and nm applet

#3 2021-06-25 06:49:33

Re: [Solved]fix network.target critical-chain timeout, and nm applet

#4 2021-06-25 08:10:48

Re: [Solved]fix network.target critical-chain timeout, and nm applet

#5 2021-06-25 08:16:24

Re: [Solved]fix network.target critical-chain timeout, and nm applet

#6 2021-06-25 08:25:58

Re: [Solved]fix network.target critical-chain timeout, and nm applet

#7 2021-06-25 08:49:22

Re: [Solved]fix network.target critical-chain timeout, and nm applet

#8 2021-06-26 19:29:38

Re: [Solved]fix network.target critical-chain timeout, and nm applet

Board footer