Package Details: solaar 0.9.2-7

Git Clone URL: (read-only)
Package Base: solaar
Description: Device manager for Logitech's Unifying receiver peripherals
Upstream URL:
Licenses: GPL2
Conflicts: solaar
Provides: solaar
Submitter: None
Maintainer: atriix
Last Packager: atriix
Votes: 155
Popularity: 5.637195
First Submitted: 2013-02-02 23:27
Last Updated: 2017-05-20 20:47

Latest Comments

OldNuc commented on 2017-05-23 16:12

This issue exists with both old and new receivers.

solaar-cli -d show
Unifying Receiver [/dev/hidraw0:DBF096BA] with 1 devices
09:37:04,070 INFO logitech_receiver.receiver: <UnifyingReceiver(/dev/hidraw0,3)>: found new device 1 (4051)
1: Wireless Mouse M510 [M510:DBF096BA]
09:37:05,806 ERROR logitech_receiver.receiver: failed to read Nano wpid for device 2 of <UnifyingReceiver(/dev/hidraw0,3)>
09:37:05,806 ERROR logitech_receiver.receiver: register_new_device
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/logitech_receiver/", line 409, in register_new_device
dev = PairedDevice(self, number, notification)
File "/usr/lib/python3.6/site-packages/logitech_receiver/", line 103, in __init__
raise _base.NoSuchDevice(number=number, receiver=receiver, error="read Nano wpid")

atriix commented on 2017-05-20 20:52

Conflict with ltunify-git removed.

However you may want to look at solaar-git instead since there have been no releases drafted since Jul 24, 2013.

drws commented on 2017-04-23 14:28

Manpage for solaar-cli is missing!

Lekensteyn commented on 2016-11-03 20:18

@atriix Can you revert that change? I've adopted and updated ltunify-git yesterday by renaming the udev rules file so the packages can be co-installed.

atriix commented on 2016-11-03 19:30

@jamesan PKGBUILD has been updated to conflict with ltunify-git

jamesan commented on 2016-11-02 10:36

This package conflicts with ltunify-git as both packages install /usr/lib/udev/rules.d/42-logitech-unify-permissions.rules. At a glance, the file as specified in both packages define identical udev rules (except that Solaar includes an additional USB product ID, 0xc52e, for the MK220 classic Nano receiver).

Can either:
1. the file be renamed so both packages can be installed in a system; or
2. ltunify-git be added to the PKGBUILD conflicts variable to acknowledge that both packages cannot be installed at the same time as they are now?

I'm submitting a similar comment for the ltunify-git package as well, as only one PKGBUILD needs to change to resolve this issue.

kgizdov commented on 2016-05-06 12:20

@Lekensteyn, I guess this also explains why on Wayland there is no tray icon...

Lekensteyn commented on 2016-04-17 12:16

The tray icon issue happens because it uses the XEmbed protocol to create it. xembedsniproxy (used by KDE Plasma) is supposed to bridge that old protocol to the modern protocol uses by Plasma, but it does not seem to work well for all programs. There is no fix for it (yet), patches are welcome.

The warnings were fixed upstream with e1eee2e078ae986bb2e0947ce5a0ddca888a23ba.

dgaus commented on 2016-04-17 01:10

Hi, just installed 0.9.2-5, when I open solaar I get

/usr/lib/python3.5/site-packages/solaar/ PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk', '3.0') before import to ensure that the right version gets loaded.
/usr/lib/python3.5/site-packages/solaar/ui/ PyGIWarning: Notify was imported without specifying a version first. Use gi.require_version('Notify', '0.7') before import to ensure that the right version gets loaded.
from gi.repository import Notify

An icon appears, it recognizes the mouse that's plugged in and displays the battery level, but I cannot interact with it, left or right click, so I cannot pair new devices. Using kde/plasma. Any ideas? thanks

atriix commented on 2016-04-05 11:48

added python-six to 0.9.2-5, which in theory should make things work

clep commented on 2016-04-05 11:03


I can confirm that python-six is needed to get it working again.

Further there could be some permissions issues, the tool will not show all paired device and new pairing also not possible. To fix this kill solaar,remove the Unifying Receiver and re-insert it. Than start solaar again.



fyvfy commented on 2016-04-02 21:47

@Kubax fixed. thanks!

atriix commented on 2016-04-02 10:56

@fyvfy and @Kubax, I'll try to look into that.

Kubax commented on 2016-04-02 09:49

installing "python-six" seems to fix it. Python-pyudev relies on python-six but doesn't install it. Found it by opening python and typed "import pyudev;"

fyvfy commented on 2016-03-30 21:33

Solaar: missing required package 'python-pyudev' after upgrading python-pyudev (0.16.1-4 -> 0.19.0-1)

atriix commented on 2016-02-10 21:10

@r3pek fixed in 0.9.2-4

r3pek commented on 2016-02-08 14:41

You forgot to mksrcinfo before pushing into the repo. .SRCINFO has pkgrel=2 while PKGBUILD has pkgrel=3

(can't install with new pacaur)

whisperer commented on 2015-11-11 14:59

I was able to solve the problem by:
1) Uninstalling my installation of solaar
2) Downloading the latest tar.gz (v0.9.2) from the solaar website
3) Extracting the tar.gz
4) Installing pyudev (with pip2)
5) Creating a softlink for the solaar icon, e.g. like this:
$ sudo ln -s /home/username/programs/Solaar-0.9.2/share/solaar/icons/solaar.svg /usr/share/icons/hicolor/scalable/apps/solaar.svg

Now I can start solaar by running:
$ python2 /home/username/programs/Solaar-0.9.2/bin/solaar

I still get the "... imported without specifying a version first" warnings, but that's ok.

Hope this quick fix helps you guys!

atriix commented on 2015-11-03 22:34

Sorry about the delay, missed the flag.

- PyGTK dependency is no more
- udev rules moved to /usr/lib/udev/rules.d as per @justin8 suggestion

vorot93 commented on 2015-09-04 10:47

Solaar uses GI exclusively now. PyGTK dependency is not required anymore.

justin8 commented on 2015-08-20 12:14

btw, /etc/udev/rules.d is for local system specific rules. Package provided ones should be in /usr/lib/udev/rules.d, then users can override them using /etc if desired.

atriix commented on 2015-07-09 15:59

Since @RareCoinsGuy didn't move the package to aur4, I did so. This package also contains a patch which fixes the error mentioned.

If @RareCoinsGuy sill have interest in being a maintainer, please file such request.

tachy commented on 2015-04-09 21:17

Regarding: solaar: error: Argument 0 does not allow None as a value

I can't write Python, but I debugged it anyway (took a lot of time).
The error originates from lib/solaar/ui/ line 80:

Outcommenting that line "fixes" the error, and I haven't found any side effects, yet.

I have created a patch and update PKGBUILD here:


darose commented on 2015-03-25 14:54

Doesn't seem to work:

[darose@daroseneo solaar]$ solaar
solaar: error: Argument 0 does not allow None as a value

SammysHP commented on 2015-02-19 20:20

Sorry for the late response. I have not tested the git version, the PKGBUILD isn't maintained anymore. But I can try it when I have time.

Lekensteyn commented on 2015-01-29 16:53

@SammysHP Do you have the same problem with the solaar-git package?

SammysHP commented on 2015-01-29 14:06

This does not work anymore.

$ solaar
/usr/lib/python3.4/site-packages/gi/overrides/ RuntimeWarning: You have imported the Gtk 2.0 module. Because Gtk 2.0 was not designed for use with introspection some of the interfaces and API will fail. As such this is not supported by the pygobject development team and we encourage you to port your app to Gtk 3 or greater. PyGTK is the recomended python module to use with Gtk 2.0
warnings.warn(warn_msg, RuntimeWarning)
solaar: error: 'gi.repository.Gtk' object has no attribute 'get_major_version'

OldNuc commented on 2014-03-30 15:57

Killed Solaar and then restarted through terminal, no errors but no tray icon and no gui. If I repeat the start through terminal the gui comes up along with error: already running. If I close the gui then the tray icon shows up. I think all of this behavior is a Cinnamon issue.

Yamakaky commented on 2014-03-30 11:02

Package broken, needs to be rebuilt for python3.4

OldNuc commented on 2014-03-29 14:39

Just ran a reinstall and that seems to fix the no start issue. The tray icon went away with the last Cinnamon update but that is not a deal breaker. Will see what happens on the next reboot.

OldNuc commented on 2014-03-29 14:37

Lekensteyn commented on 2014-03-29 14:35

Hvae you tried rebuilding Solaar? I saw that error when Python was unable to find the solaar modules in /usr/lib/pythonX.Y/site-packages/ where X.Y the python version (3.4).

OldNuc commented on 2014-03-29 14:30

For the cli version:
Traceback (most recent call last):
File "/usr/bin/solaar-cli", line 41, in <module>
import solaar.cli
ImportError: No module named 'solaar'

For the graphic version:
Traceback (most recent call last):
File "/usr/bin/solaar", line 43, in <module>
import solaar.gtk
ImportError: No module named 'solaar'

That is the extent of the investigation so far.

Lekensteyn commented on 2014-03-29 10:37

@OldNuc what is broken for you (error messages)? It works for me, tested with git and the 0.9.2 tag.

OldNuc commented on 2014-03-29 03:29

The latest python update appears to have broken solaar

Diego commented on 2013-09-03 04:46

no, this is the vanilla asset

dumphblooz commented on 2013-08-31 11:41

Please, remove solaar from autostart. Remove /etc/xdg/autostart/solaar.desktop.

Anonymous comment on 2013-07-25 21:05

Updated to 0.9.2 and added libappindicator3 as optdepend.

phw commented on 2013-07-15 09:00

Thanks for the quick update. Maybe one last suggestion: The package could optdepend on libappindicator3 (also in aur), which alows better integration into Unity and also gnome 3 if using the appindicator gnome-shell extension.

Anonymous comment on 2013-07-15 05:06

Updated to 0.9.1 and also added the code to update the icon cache. Thanks phw.

The checksum error was caused by the fact that the package was downloading 0.9.tgz instead of 0.9.0.tgz. In such case Github aparently send the last version starting by 0.9 and here it was updated when 0.9.1 was release.

phw commented on 2013-07-13 09:14

You should also update the icon cache on post_install in solaar.install, otherwise there will be no icon until the commands are run manually (or by installing another package). Other packages use something like that:

post_install() {
xdg-icon-resource forceupdate --theme hicolor
update-desktop-database -q

phw commented on 2013-07-13 08:57

The checksum for the solaar archive is wrong. Correct checksum entry would be:


Diego commented on 2013-07-10 13:46

But now we have to speak with Mantainer of ltunify and ltunify-git to consider our choice

Diego commented on 2013-07-10 13:43

No, I've made a dynamic version: look

Lekensteyn commented on 2013-07-10 13:40

Just use a static version.


Diego commented on 2013-07-10 13:29

ok... in this way works but on git package i cannot use pkgver() function....

Lekensteyn commented on 2013-07-10 13:24

The idea is to use the following source URLs:

Not cloning the whole repo.

Diego commented on 2013-07-10 13:20

OK I now make a removal request on aur-general for my draft.
udev-logitech-unifying is the ultimate name. I create -git version of this

Diego commented on 2013-07-10 13:17

but if link directly on github sould be a -git package... is wrong

Lekensteyn commented on 2013-07-10 13:13

What about naming it "udev-logitech-unifying" instead? There are other Logitech products.

Yes, Solaars udev rule can also be used in ltunofy. I suggest to copy its rule and put it in the tarball, there is no need for downloading the whole source just for that single file... Alternatively, link directly to the raw file on github.

Diego commented on 2013-07-10 13:10

is possible to use solaar's udev rule in ltunify?

Diego commented on 2013-07-10 13:09
this is a draft, what do you think?
I will disown it and @arnaudt may take it

Anonymous comment on 2013-07-10 12:57

If both file are compatible, I would also suggest to make a new package.

Diego commented on 2013-07-10 12:57

@Lekensteyn i know... i'm cdprincipe on github :P
ok... now i make new PKGBUILD only for the udev rule

Lekensteyn commented on 2013-07-10 12:29

May I suggest to put the config file in a new package? There is no need to have both files. The udev rule in Solaar is the same as the one in ltunify except that it also adds a rule for certain Nano receivers (of which I could not confirm whether it is really needed/useful or not).

Diego commented on 2013-07-10 11:42

Please rename udev rule to enhance compatibility between solaar and ltunify
view PKGBUILD of solaar-git

Anonymous comment on 2013-07-09 20:56

Updated to stable 0.9 that now have the new UI and supports multiple Unifying receivers :)

Diego commented on 2013-07-07 15:33

Uhm... the git version have the new interface... impressive

Diego commented on 2013-07-07 15:32


Anonymous comment on 2013-07-07 15:31


Diego commented on 2013-07-07 15:21

Please update this package or disown it
In we have 0.8.99 here

Diego commented on 2013-07-07 15:14

Please update this package or disown it
In we have 0.8.99

Anonymous comment on 2013-05-21 05:09


As for the plugdev group it is created by the packet if not present on the system. I updated the Wiki.

Diego commented on 2013-05-20 21:50


Lekensteyn commented on 2013-04-27 14:34

Note: the udev rule assumes the "plugdev" group which does not exist on Arch.
I have noted it at, please edit if necessary.

Anonymous comment on 2013-02-03 18:57

Thanks for reporting!
This package was intended to run with Python3 but packaged with Python2 which caused the dependencies problem. I uploaded a fixed version.

Anonymous comment on 2013-02-03 08:02

Missing some dependencies: