Closed umeiko closed 1 month ago
you should test if this happens on #1269, because i will not try to fix the old backend that i consider deprecated, the only reason that i haven't changed it it's because i'm giving people on buster some extra time to update.
I have tried your new branch, It seems good, but rescan function seems not working good, It takes very long time to scan, and drop some erros
024-03-20 11:41:25,266 [screen.py:attach_panel()] - Current panel hierarchy: splash_screen > > network
2024-03-20 11:41:28,595 [functions.py:logging_exception_handler()] - Uncaught exception <class 'sdbus_block.networkmanager.exceptions.NmDeviceNotAllowedError'>: Scanning not allowed immediately following previous scan
File "/home/umeko/KlipperScreen/panels/network.py", line 309, in reload_networks
self.sdbus_nm.rescan()
File "/home/umeko/KlipperScreen/ks_includes/sdbus_nm.py", line 227, in rescan
return self.wlan_device.request_scan({})
File "/home/umeko/.KlipperScreen-env/lib/python3.8/site-packages/sdbus/dbus_proxy_sync_method.py", line 98, in __call__
return self._call_dbus_sync(*rebuilt_args)
File "/home/umeko/.KlipperScreen-env/lib/python3.8/site-packages/sdbus/dbus_proxy_sync_method.py", line 82, in _call_dbus_sync
reply_message = self.interface._attached_bus.call(
NoneType: None
some time this, with very very long time scaning:
2024-03-20 11:49:48,779 [screen.py:show_panel()] - Reinitializing panel
2024-03-20 11:49:48,850 [network.py:__init__()] - Network interfaces: ['lo', 'ipa_lan0', 'rmnet_ipa0', 'wlan0']
2024-03-20 11:49:48,866 [network.py:__init__()] - Wireless interfaces: ['wlan0']
2024-03-20 11:49:48,876 [network.py:__init__()] - Primary interface: wlan0
2024-03-20 11:49:48,907 [screen.py:attach_panel()] - Current panel hierarchy: splash_screen > > network
2024-03-20 11:49:52,035 [functions.py:logging_exception_handler()] - Uncaught exception <class 'sdbus.dbus_exceptions.DbusUnknownMethodError'>: No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/NetworkManager/AccessPoint/18
File "/home/umeko/KlipperScreen/panels/network.py", line 75, in load_networks
self.add_network(net['BSSID'])
File "/home/umeko/KlipperScreen/panels/network.py", line 86, in add_network
net = next(net for net in self.sdbus_nm.get_networks() if bssid == net['BSSID'])
File "/home/umeko/KlipperScreen/ks_includes/sdbus_nm.py", line 149, in get_networks
networks.extend(
File "/home/umeko/KlipperScreen/ks_includes/sdbus_nm.py", line 161, in <genexpr>
if ap.ssid
File "/home/umeko/.KlipperScreen-env/lib/python3.8/site-packages/sdbus/dbus_proxy_sync_property.py", line 89, in __get__
reply_message = obj._attached_bus. \
NoneType: None
Since you switched to the branch manually you need to install the additional requirements
source ~/.KlipperScreen-env/bin/activate
pip -r ~/KlipperScreen/scripts/KlipperScreen-requirements.txt
sudo service KlipperScreen restart
deactivate
this is covered in the docs in the manual update section
normally the update-manager takes care of this step
These logs are not including import error. These logs afterwards I have done requirements installation on klipperscreen venv.
i did some changes to the new backend branch that should resolve theses issues, except the slowness to scan, that may be tied to the hw, but it should not let you request another scan if the previous did not finish which seems to be the main error.
new backend merged
What happened?
I can't found my ssid on the KilpperScreen's Wifi pannel, but when i use
nmcli dev wifi
command, I can see my ssid.What did you expect to happen instead?
This is
nmcli dev wifi
shows:But KlipperScreen's pannel shows under, I can't found my ssid
218-3
:How to reproduce this bug?
The ssid with the strongest signal will not be displayed.
Additional information:
Ubuntu20.04
ath10k
Log output