Closed victorkirov closed 1 year ago
Update: I tried editing /usr/bin/solaar
first line to be #!/usr/bin/python3.9
but it complained that python3-gi
is not installed (guessing it only registers for my main python installation of 3.10?)
Python libraries are specific to the Python version. Installing Python libraries using your distribution's tools usually only installs the libraries for the system version of Python.
Yeah, I tried to install PyObject to python3.9 and forcing solaar to run from that, but it didn't help :sweat: Is there maybe a dependency that Solaar uses that is outdated and the used version is not python3.10 compatible?
I suspect that Python 3.10 is not completely installed. You may have to reboot your system to complete the installation. I have run Solaar in Python 3.10 for quite a while, and am now running in Python 3.11.
It also may be that you have a version of pyyaml that is not compatible with Python 3.10. See https://stackoverflow.com/questions/72659999/chatterbot-module-error-attributeerror-module-collections-has-no-attribute and https://github.com/yaml/pyyaml/issues/622.
In general, upgrading the main version of Python on your system can lead to some subtle errors. Even upgrading the version of Python that you are using can create errors. One thing that might work is installing Solaar using pip. That should pick up versions of the Python libraries that Solaar depends on for the version of Python that you are using.
If none of this works, please provide the complete output of solaar -ddd
and the contents of ~/.config/solaar/rules.yaml. Further debugging may require upgrading Solaar's error logging.
You are the best! Upgrading PyYaml worked perfectly. Thank you :tada:
Information
solaar --version
orgit describe --tags
if cloned from this repository):1.1.8uname -srmo
):Linux 6.1.11-76060111-generic x86_64 GNU/Linux
solaar show
:~/.config/solaar/config.yaml
(or~/.config/solaar/config.json
if~/.config/solaar/config.yaml
not present):Contents of ~/.config/solaar/config.yaml
Describe the bug Importing from collections directly was deprecated for Python 3.10. It appears a required module is still doing it when loading the rules.
To Reproduce Steps to reproduce the behavior:
-ddd
and notice that the rules haven't loaded and above error appears