New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"missing required system package python3-gobject" despite it being installed. #2141
Comments
Python packages are specific to the version of python. I expect that you have two versions of python - one used by the system and one used by you when running Solaar. |
@pfps, so what should I do, if anything? |
You have to either align your version of python with the system version or install the python libraries for your version of python. But first, you have to determine whether you are indeed using different version of python than the system version. This all depends on your distribution so I can't help there. I expect that there are questions on Stack Exchange that are related so you might try to search there. |
@pfps, I can probably do what you're asking, I just don't really understand the terminology you use, such as alignment, in this context. I'll see what I can do. |
There are multiple versions of Python, each with its own set of libraries. If you are using, for example, Python 3.10 but the system uses Python 3.11, then you are out of alignment with the system Python. |
@pfps, what do you mean by me and "the system" using a different version of python? Doesn't each package define the version of python it depends upon? If I have multiple versions installed, if that's what you mean, I can't imagine that being problematic. zypper search -s <# https://superuser.com/a/793450/904401 #> -i <# https://www.cyberciti.biz/faq/list-all-installed-packages-on-opensuse-suse-linux/ #> python3
are the |
The problem is that different versions of python use different libraries. Using the system to install a python library may only install the library for the version of python that the system uses. It may be that the Suse distribution of Solaar assumes that Solaar is being run with the same version of python that the system uses. |
Yeah, @pfps, I'll attempt to ascertain whether this is an upstream issue: https://build.opensuse.org/package/show/openSUSE%3AFactory/solaar#comment-1825377 |
Works on my desktop, just not my laptop. I'll reinstall the OS on the laptop to verify. |
Had similar issue on Tumbleweed when using solaar. Seems that installing |
Is there anything that needs to be done here? |
@pfps, if @Nidhhogg's comment #2141 (comment) is correct, the aforementioned package must be added as a package dependency for openSUSE. |
Package dependencies are the responsibility of the packager so I suggest contacting whoever is packaging Solaar for openSUSE. I'll add a note to the installation documentation. |
Information
Solaar version (
solaar --version
orgit describe --tags
if cloned from this repository): 1.1.9Distribution: opensuse:tumbleweed:20230917
Kernel version (ex.
uname -srmo
):6.5.3-1
Output of
solaar show
:Contents of
$HOME/.config/solaar/config.yaml
(or$HOME/.config/solaar/config.json
if$HOME/.config/solaar/config.yaml
not present):Errors or warnings from Solaar:
Describe the bug
appears after invoking
solaar
.To Reproduce
Steps to reproduce the behavior:
outputs
outputs
outputs
Screenshots
Additional context
I am using https://download.opensuse.org/repositories/openSUSE:/Factory/standard/noarch/solaar-1.1.9-1.2.noarch.rpm
The text was updated successfully, but these errors were encountered: