Yeah we’re getting that error as well, unfortunately the guy in charge of that system (@rohbotics) is otherwise occupied at the moment and hasn’t been able to look into it yet. Same goes for all other packages on focal.
In the meantime you can always grab it on https://github.com/rohbotics/pifi and compile it locally (should be as simple as sudo pip3 install .), assuming you get all the dependencies in order.
If you install a desktop, you don’t need Pifi, and if you start with an ARM64 Focal server, you can enable WiFi via the CLI. If I remember once Ubuntu went to focal, they don’t use nmcli, and there is a different way to enable wifi.
I am trying to get pifi to work on ARM64, and I get this:
ubuntu@ubuntu:~/pifi$ pifi status
Traceback (most recent call last):
File “/usr/local/bin/pifi”, line 8, in
sys.exit(main())
File “/usr/local/lib/python3.8/dist-packages/pifi/pifi.py”, line 347, in main
commandsargs.command
File “/usr/local/lib/python3.8/dist-packages/pifi/pifi.py”, line 69, in status
for ApModeDevice in nm.managedAPCapableDevices():
File “/usr/local/lib/python3.8/dist-packages/pifi/nm_helper.py”, line 96, in managedAPCapableDevices
for device in managedWifiDevices(NetworkManager=NetworkManager):
File “/usr/local/lib/python3.8/dist-packages/pifi/nm_helper.py”, line 85, in managedWifiDevices
for device in NetworkManager.NetworkManager.GetDevices():
File “”, line 3, in GetDevices
File “/usr/local/lib/python3.8/dist-packages/NetworkManager.py”, line 261, in proxy
self._proxy = dbus.SystemBus().get_object(self.dbus_service, self.object_path, follow_name_owner_changes=True)
File “/usr/lib/python3/dist-packages/dbus/bus.py”, line 225, in get_object
self._require_main_loop() # we don’t get the signals otherwise
RuntimeError: To make asynchronous calls, receive signals or export objects, D-Bus connections must be attached to a main loop by passing mainloop=… to the constructor or calling dbus.set_default_main_loop(…)