Linux devices manager for the Logitech Unifying Receiver
https://pwr-solaar.github.io/Solaar
Solaar will detect all devices paired with your Unifying Receiver, and
at the very least display some basic information about them.
For some devices, extra settings (usually not available through the
standard Linux system configuration) are supported. For a full list of
supported devices and their features, see docs/devices.md.
- Devel package for openSUSE:Factory
-
4
derived packages
- Links to openSUSE:Factory / solaar
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout hardware/solaar && cd $_ - Create Badge
Refresh
Refresh
Source Files (show unmerged sources)
| Filename | Size | Changed |
|---|---|---|
| Solaar-1.1.11.obscpio | 0004165132 3.97 MB | |
| Solaar.obsinfo | 0000000096 96 Bytes | |
| _service | 0000000681 681 Bytes | |
| _servicedata | 0000000234 234 Bytes | |
| solaar-fix-desktop-categories.patch | 0000000891 891 Bytes | |
| solaar.changes | 0000037355 36.5 KB | |
| solaar.spec | 0000005020 4.9 KB |
Latest Revision
buildservice-autocommit
accepted
request 1159772
from
Andreas Schneider (gladiac)
(revision 73)
Andreas Schneider (gladiac)
(revision 73)
baserev update by copy to link target
Comments 13
Hi! Version 1.1.1 was just released. (I can submit it).
Solaar 1.1.2 does not run for me on opensuse 15.3. I get:
Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/solaar/i18n.py", line 63, in <module> unicode # noqa: F821 NameError: name 'unicode' is not defined
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "/usr/bin/solaar", line 54, in <module> import solaar.gtk File "/usr/lib/python3.6/site-packages/solaar/gtk.py", line 29, in <module> import solaar.i18n as _i18n File "/usr/lib/python3.6/site-packages/solaar/i18n.py", line 69, in <module> pgettext = _gettext.pgettext AttributeError: module 'gettext' has no attribute 'pgettext'
Maybe it was fixed in pre 1.1.3 commit (misc: remove support for Python 2 unicode) https://github.com/pwr-Solaar/Solaar/commit/bb20631a27b5d6be3380e7d77c98d3abec0cf52e
BUT be aware of commit "dist: update required python version to 3.7" https://github.com/pwr-Solaar/Solaar/commit/0e1522aa62a9d035453592da7290af808a7bc985
opensuse 15.3 has python 3.6.15
Update: I fixed the error above locally, but other errors were raised. It seems solaar 1.1.2 does not run with python 3.6 anymore. So solaar for opensuse 15.3 should be downgraded to 1.1.1?
Thank you
OpensuseNutzer
If you're on openSUSE 15.3 you should not really use this package, but https://build.opensuse.org/package/show/openSUSE:Backports:SLE-15-SP3/solaar
To drop python-dataclasses again prevent sollar to start in Leap. The standard in Leap is python 3.6 And SUSE support python 3.6 in Leap. Solaar 1.1.3 runs under Leap. I will post an request again.
Here the Error under Leap:
(2/2) Installieren: solaar-1.1.3-lp153.52.1.noarch .............................................................................................................................[fertig] eric@client1:~> solaar solaar: error: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/solaar/gtk.py", line 158, in main import solaar.ui as ui File "/usr/lib/python3.6/site-packages/solaar/ui/init.py", line 101, in <module> from . import diversion_rules, notify, tray, window # isort:skip # noqa: E402 File "/usr/lib/python3.6/site-packages/solaar/ui/diversion_rules.py", line 24, in <module> from dataclasses import dataclass, field ModuleNotFoundError: No module named 'dataclasses'
Solaar 1.1.6 needs python >= 3.7. On openSUSE Leap 15.4 I got with Solaar: SyntaxError: future feature annotations is not defined. future feature annotations is in python >= 3.7.
solaar: error: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/solaar/gtk.py", line 163, in main import solaar.ui as ui File "/usr/lib/python3.6/site-packages/solaar/ui/init.py", line 28, in <module> from logitech_receiver.status import ALERT # NOQA: E402 # isort:skip File "/usr/lib/python3.6/site-packages/logitech_receiver/init.py", line 33, in <module> from . import listener, status # noqa: F401 File "/usr/lib/python3.6/site-packages/logitech_receiver/listener.py", line 25, in <module> from . import base as base File "/usr/lib/python3.6/site-packages/logitech_receiver/base.py", line 33, in <module> import hidapi as _hid File "/usr/lib/python3.6/site-packages/hidapi/init.py", line 20, in <module> from hidapi.udev import close # noqa: F401 File "/usr/lib/python3.6/site-packages/hidapi/udev.py", line 39, in <module> from hid_parser import ReportDescriptor as _ReportDescriptor File "/usr/lib/python3.6/site-packages/hid_parser/init.py", line 3 from __future_ import annotations # noqa:F407
Upstream stopped supporting python 3.6 already a while ago. I've disabled 15.4 and 15.3 now.
What's a while? Version 1.1.5 will build and run under Leap and python 3.6. Fist edition with python3.7 is version 1.1.6
With 1.1.6 they changed the requirement to >= 3.7
https://github.com/pwr-Solaar/Solaar/commit/049dfcecbc330b5762c14f9baae6690276659614
ecsos is right and thank you, gladiac.
Unfortunately I updated solaar on my 15.3 system to 1.1.6, that does not run anymore. Is there a chance to revert to the previous version 1.1.5? I mean, the build of this repository is disabled but it contains a not running version. Maybe it can be reverted to 1.1.5 for opensuse 15.3 and 15.4? Or is there a backup of the package files for manual download?
Thank you
Opensusenutzer
You are absolutely right solar >= 1.1.6 does not run on Leap due to red python 3.6 Haven't you noticed that lately people don't care if a package builds for Leap or not? Only Tumbleweed counts. Perhaps this is also due to the fact that Leap is being dropped anyway and is to be replaced by the unspeakable ALP. If you want solaar in version 1.1.5 for Leap, take my repo.
Thank you very much. I took the version from your repo and all is fine again.
An option is to submit 1.1.5 to devel:languages:python:backports. I also do backports to Leap and it is not really easy with python. They do not support versioned packages in site-packages like ruby. So python modules are broken most of the time.