Today, when I came to work, I found that after booting up the system, the wifi connection did not automatically happen. At home, I use wired internet from a router. Previously, everything connected automatically.
I started looking at the logs.
sudo 66-inservice  wpa_supplicant
Name                  : wpa_supplicant
Version               : 0.2.0
In tree               : root
Status                : enabled, down (exitcode 255) 0 seconds, normally up, want up, ready 0 seconds
Type                  : classic
Description           : wpa_supplicant daemon
Source                : /usr/lib/66/service/wpa_supplicant
Live                  : /run/66/scandir/0/wpa_supplicant
Dependencies          : wpa_supplicant-log
External dependencies : None
Optional dependencies : None
Start script          :  execl-cmdline -s { wpa_supplicant ${cmd_args} } 
Stop script           : None
Environment source    : /etc/66/conf/wpa_supplicant/0.2.0
Environment file      : environment variables from: /etc/66/conf/wpa_supplicant/0.2.0/.wpa_supplicant
                        cmd_args=!-udW

Log name              : wpa_supplicant-log
Log destination       : /var/log/66/wpa_supplicant
Log file              : 
2022-04-22 14:49:30.199081959  wpa_supplicant v2.10
2022-04-22 14:49:30.200395109  dbus: Register D-Bus object '/fi/w1/wpa_supplicant1'
2022-04-22 14:49:30.200970772  dbus: Could not request service name: already registered
2022-04-22 14:49:30.200978423  Failed to initialize wpa_supplicant
2022-04-22 14:49:31.200252628  wpa_supplicant v2.10
2022-04-22 14:49:31.201695704  dbus: Register D-Bus object '/fi/w1/wpa_supplicant1'
2022-04-22 14:49:31.202116318  dbus: Could not request service name: already registered
2022-04-22 14:49:31.202136429  Failed to initialize wpa_supplicant
2022-04-22 14:49:32.201541347  wpa_supplicant v2.10
2022-04-22 14:49:32.203238385  dbus: Register D-Bus object '/fi/w1/wpa_supplicant1'
2022-04-22 14:49:32.203502791  dbus: Could not request service name: already registered
2022-04-22 14:49:32.203575953  Failed to initialize wpa_supplicant
2022-04-22 14:49:33.202649598  wpa_supplicant v2.10
2022-04-22 14:49:33.204393551  dbus: Register D-Bus object '/fi/w1/wpa_supplicant1'
2022-04-22 14:49:33.204781712  dbus: Could not request service name: already registered
2022-04-22 14:49:33.204838827  Failed to initialize wpa_supplicant
2022-04-22 14:49:34.203915140  wpa_supplicant v2.10
2022-04-22 14:49:34.205750231  dbus: Register D-Bus object '/fi/w1/wpa_supplicant1'
2022-04-22 14:49:34.206291159  dbus: Could not request service name: already registered
2022-04-22 14:49:34.206298969  Failed to initialize wpa_supplicant
wpa_supplicant is not working:
sudo 66-intree -zg
Name         : boot
Initialized  : yes
Enabled      : no
Starts after : None
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(228,Enabled,classic) tty-earlier@ tty12
               ├─(up,Enabled,oneshot) system-hostname
               ├─(up,Enabled,oneshot) mount-run
               ├─(up,Enabled,oneshot) populate-run
               ├─(up,Enabled,oneshot) mount-tmp
               ├─(up,Enabled,oneshot) populate-tmp
               ├─(up,Enabled,oneshot) mount-proc
               ├─(up,Enabled,oneshot) mount-sys
               ├─(up,Enabled,oneshot) populate-sys
               ├─(up,Enabled,oneshot) mount-dev
               ├─(up,Enabled,oneshot) mount-pts
               ├─(up,Enabled,oneshot) mount-shm
               ├─(up,Enabled,oneshot) populate-dev
               ├─(up,Enabled,oneshot) mount-cgroups
               ├─(up,Enabled,bundle) 00
               ├─(up,Enabled,oneshot) system-hwclock
               ├─(up,Enabled,oneshot) modules-kernel
               ├─(up,Enabled,oneshot) system-random
               ├─(up,Enabled,oneshot) modules-system
               ├─(up,Enabled,oneshot) system-sysctl
               ├─(275,Enabled,longrun) udevd-log
               ├─(443,Enabled,longrun) udevd
               ├─(up,Enabled,oneshot) udevadm
               ├─(up,Enabled,oneshot) system-fontnkey
               ├─(up,Enabled,bundle) all-Mount
               ├─(up,Enabled,oneshot) system-fsck
               ├─(up,Enabled,oneshot) mount-fstab
               ├─(up,Enabled,bundle) all-System
               ├─(up,Enabled,oneshot) mount-rw
               ├─(up,Enabled,oneshot) local-authfiles
               ├─(up,Enabled,oneshot) local-loop
               ├─(up,Enabled,oneshot) local-sethostname
               ├─(up,Enabled,oneshot) local-time
               ├─(up,Enabled,oneshot) local-tmpfiles
               ├─(up,Enabled,oneshot) local-dmesg
               ├─(up,Enabled,oneshot) mount-netfs
               ├─(up,Enabled,oneshot) mount-swap
               ├─(up,Enabled,bundle) all-Local
               ├─(up,Enabled,oneshot) all-Runtime
               ├─(up,Enabled,bundle) All
               ├─(875,Enabled,longrun) tty-rc@ tty1
               ├─(876,Enabled,longrun) tty-rc@ tty2
               └─(up,Enabled,module) boot@ system

Name         : root
Initialized  : yes
Enabled      : yes
Starts after : None
Current      : yes
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(709,Enabled,classic) wpa_supplicant-log
               ├─(0,Enabled,classic) wpa_supplicant
               ├─(713,Enabled,classic) bluetoothd-log
               ├─(881,Enabled,classic) bluetoothd
               ├─(715,Enabled,classic) openntpd-log
               ├─(716,Enabled,classic) openntpd
               ├─(736,Enabled,longrun) dbus-log
               ├─(748,Enabled,longrun) dbus
               ├─(743,Enabled,longrun) consolekit-log
               ├─(756,Enabled,longrun) consolekit
               ├─(741,Enabled,longrun) connmand-log
               └─(757,Enabled,longrun) connmand

Name         : boot-user
Initialized  : yes
Enabled      : yes
Starts after : root
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(up,Enabled,oneshot) setenv@ grandma
               ├─(805,Enabled,longrun) svscan@ grandma-log
               ├─(866,Enabled,longrun) svscan@ grandma
               ├─(up,Enabled,module) scandir@ grandma
               ├─(up,Enabled,oneshot) mount-run@ grandma
               ├─(up,Enabled,module) boot-user@ grandma
               ├─(up,Enabled,oneshot) setenv@ grandpa
               ├─(808,Enabled,longrun) svscan@ grandpa-log
               ├─(863,Enabled,longrun) svscan@ grandpa
               ├─(up,Enabled,module) scandir@ grandpa
               ├─(up,Enabled,oneshot) mount-run@ grandpa
               └─(up,Enabled,module) boot-user@ grandpa
I tried to run a console command - sudo wpa_cli 
wpa_cli v2.10
Copyright (c) 2004-2022, Jouni Malinen <j@ w1.fi> and contributors

This software may be distributed under the terms of the BSD license.
See README for more details.



Interactive mode

Could not connect to wpa_supplicant: (nil) - re-trying
I tried to create a /etc/wpa_supplicant/wpa_supplicant.conf according to [post]9090[/post]. This did not help.

Tried to stop and start again d-bus and wpa_supplicant , also no results.

Just in case - rfkill list output 
0: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
1: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: yes
2: asus-wlan: Wireless LAN
	Soft blocked: no
	Hard blocked: no
3: asus-bluetooth: Bluetooth
	Soft blocked: no
	Hard blocked: no
So how to defeat this problem?
Sound like same problem I was having here: https://forum.obarun.org/viewtopic.php?id=1523

I still have wpa_supplicant in root tree & connmand separated in boot-user tree for a lazy workaround,

but someone mentioned that wpa_supplicant can be started as module specifying the interface it should bring up;

for ex: wpa_supplicant@ wlp2s0 which would be one of mine and that may allow it to run in the same tree as connmand with no issues.
Wat-now wroteSound like same problem I was having here: https://forum.obarun.org/viewtopic.php?id=1523
I read this post.
Wat-now wrote

I still have wpa_supplicant in root tree & connmand separated in boot-user tree for a lazy workaround,

but someone mentioned that wpa_supplicant can be started as module specifying the interface it should bring up;
I can't see the connection between connmand and the wpa_supplicant dropping.
Well, connmand starts an unsupervised instance of wpa_supplicant, if the instance started by 66 has problems starting,hence the error: "dbus: Could not request service name: already registered"-- that is the connection.

It is already running before 66 tries to restart it, and you would see this thru some htop, etc. query.

edit: I also saw that rfkill showed your wifi card hard-blocked which may have a connection to this.

Did a user accidentally touch some sort of hard switch that toggles wifi antenna power or something?
Thank you very much,Wat-now.

The problem with the lack of wifi was solved in a strange way. The output of the rfkill command did not suit me either.
The card was hard-blocked. The hardware button disabled and enabled only bluetooth. Tried rebooting with the last kernel-I have the lts kernel loaded by default. The hardware button worked as it should and wi-fi is working fine again.

Powered by Obarun