Created attachment 384054 [details] emerge --info solaar Solaar built and installed, but attempting to run it gives me this: ERROR:root:Could not find any typelib for Gtk Solaar: missing required package 'gir1.2-gtk-3.0' Missing (runtime?) dependency? The installation.md file suggests gtk3 is required for the GUI, which I guess should translate to a gtk3 use flag? ~amd64 with kde4-live from the gentoo/kde overlay as my DE. No gtk3 installed, gtk2 installed to support pan, firefox, claws-mail, etc. Gnome2 as such not installed. emerge --info solaar output attached. Running solaar-cli as user fails with permissions error on /dev/hidraw1, despite the user being in plugdev group. >ls -l /dev/hidraw* crw------- 1 root root 251, 0 Aug 31 14:38 /dev/hidraw0 crw------- 1 root root 251, 1 Aug 31 14:38 /dev/hidraw1 crw------- 1 root root 251, 2 Aug 31 14:38 /dev/hidraw2 crw------- 1 root root 251, 3 Aug 31 14:38 /dev/hidraw3 crw------- 1 root root 251, 4 Aug 31 14:38 /dev/hidraw4 crw------- 1 root root 251, 5 Aug 31 14:38 /dev/hidraw5 The 42-logitech-unify-permissions.rules file was installed, but the line changing the mode/group is commented out. So the elog message saying users need to be in the plugdev group appears to be invalid, root appears to be needed, with all the implications for running the GUI as root. =:^( Running solaar-cli as root does appear to work: $>>sudo solaar-cli show Unifying Receiver [/dev/hidraw1:6CD9946E] with 2 devices 1: Wireless Mouse M510 [M510:AC9B3CEE] offline 2: Wireless Keyboard K350 [K350:A607A8F9] Tho (upstream bug I guess) I can't say I'm comfortable running it yet as the included readme doesn't say much about running it and there's apparently no manpage. Which is why I would have liked to try the GUI. Presumably I'd get familiar with the concepts there and could then run the CLI with less trouble. BTW, the readme mentions docs/devices.md for a list of covered devices. The ebuild doesn't install that (except perhaps with USE=docs). Could it? I see the other docs in the tarball and agree USE=docs for them, but devices.md seems more generally useful to me. [It occurs to me that this might well be regarded as several separate bugs. If you'd rather deal with them that way, say so and I'll file separate bugs.]
Well, one of your questions can be answered with "here comes the Borg". As (sort of) explained in that rules file, those devices are meant to be handled by ACL markers. The catch is that those are sort of context specific - "uaccess" is for systemd, "udev-acl" for consolekit[acl]. As for the gui, that looks like gtk:3[introspection].
These various issues should all be fixed in 0.9.2-r3.
