Logitech wireless во linux


Linux Device Manager for Logitech Unifying Receivers and Devices.

Solaar is a Linux manager for many Logitech keyboards, mice, and trackpads that connect wirelessly to a USB Unifying, Bolt, Lightspeed, or Nano receiver; connect directly via a USB cable; or connect via Bluetooth. Solaar does not work with peripherals from other companies.

Documentation here is for the current version of Solaar. Some Linux distributions distribute old versions of Solaar. If you are using an old version and something described here does not work you should upgrade using one of the methods described below.

Solaar runs as a regular user process, albeit with direct access to the Linux interface that lets it directly communicate with the Logitech devices it manages using special Logitech-proprietary (HID++) commands. Each Logitech device implements a different subset of these commands. Solaar is thus only able to make the changes to devices that devices implement.

Solaar is not a device driver and does not process normal input from devices. It is thus unable to fix problems that arise from incorrect handling of mouse movements or keycodes by Linux drivers or other software.

Solaar can be used as a GUI application, the usual case, or via its command-line interface. The Solaar GUI is meant to run continuously in the background, monitoring devices, making changes to them, and responding to some messages they emit. To this end, it is useful to have Solaar start at user login so that changes made to devices by Solaar are applied at login and through out the user’s session.

Both Solaar interfaces are able to list the connected devices and show information about each device, often including battery status. Solaar is able to pair and unpair devices with receivers as supported by the device and receiver. Solaar can also control some changeable settings of devices, such as scroll wheel direction and function key behavior. Solaar keeps track of most of these settings on a per-computer basis, because devices forget most settings when powered down, and the GUI application restores them whenever a device connects. For more information on how to use Solaar see the usage page, and for more information on its capabilities see the capabilities page.

Solaar’s GUI normally uses an icon in the system tray and starts with its main window visible. This aspect of Solaar depends on having an active system tray, which is not the default situation for recent versions of Gnome. For information on to set up a system tray under Gnome see the capabilities page.

Solaar’s GUI can be started in several ways

  • —window=show (the default) starts with its main window visible,
  • —window=hide starts with its main window hidden,
  • —window=only does not use the system tray, and starts with main window visible.

For more information on Solaar’s command-line interface use the help option, as in solaar —help .

Solaar has progressed past version 1.1. Problems with earlier versions should not be reported as bugs. Instead, upgrade to a recent version or manually install the current version from GitHub. Some capabilities of Solaar have been developed by observing the behavior of Logitech receivers and devices and generalizing from these observations. If your Logitech receiver or device behaves strangely this may be caused by an incorrect behavior generalization. Please report such experiences by creating an issue in the Solaar repository.

Supported Devices

Solaar will detect all devices paired with supported Unifying, Bolt, Lightspeed, or Nano receivers, and at the very least display some basic information about them. Solaar will detect some Logitech devices that connect via a USB cable or Bluetooth.

Solaar can pair and unpair a Logitech device showing the Unifying logo (Solaar’s version of the logo) with any Unifying receiver, and pair and unpair a Logitech device showing the Bolt logo with any Bolt receiver, and can pair and unpair Lightspeed devices with Lightspeed receivers for the same model. Solaar can pair some Logitech devices with Logitech Nano receivers but not all Logitech devices can be paired with Nano receivers. Logitech devices without a Unifying or Bolt logo generally cannot be paired with Unifying or Bolt receivers.

Читайте также:  Как развернуть бэкап joomla

Solaar does not handle connecting or disconnecting via Bluetooth, which is done using the usual Bluetooth mechanisms.

For a partial list of supported devices and their features, see the devices page.

Prebuilt packages

Up-to-date prebuilt packages are available for some Linux distros (e.g., Fedora 33+) in their standard repositories. If a recent version of Solaar is not available from the standard repositories for your distribution you can try one of these packages.

  • Arch solaar package in the community repository
  • Ubuntu/Kubuntu 16.04+: use the solaar package from universe repository
  • Ubuntu/Kubuntu stable packages: use the Solaar stable ppa, courtesy of gogo
  • Ubuntu/Kubuntu git build packages: use the Solaar git ppa, courtesy of gogo
  • a Gentoo package, courtesy of Carlos Silva and Tim Harder
  • a Mageia package, courtesy of David Geiger

Solaar uses a standard system tray implementation; solaar-gnome3 is no longer required for gnome or unity integration.

Manual installation

See the installation page for the step-by-step procedure for manual installation.

Known Issues

If the Python hid-parser package is not available Solaar will not recognize some devices. Use pip to install hid-parser.

If some icons appear broken in the application, make sure you’ve properly configured the Gtk theme and icon theme in your control panel.

Solaar normally uses icon names for its icons, which in some system tray implementatations results in missing or wrong-sized icons. The —tray-icon-size option forces Solaar to use icon files of appropriate size for tray icons instead, which produces better results in some system tray implementatations. To use icon files close to 32 pixels in size use —tray-icon-size=32 .

The icon in the system tray can show up as ‘black on black’ in dark themes or as non-symbolic when the theme uses symbolic icons. This is due to problems in some system tray implementations. Changing to a different theme may help. The —battery-icons=symbolic option can be used to force symbolic icons.

The Linux HID++ driver modifies the setting Scroll Wheel Resolution to implement smooth scrolling. If Solaar later changes this setting scrolling can be either very fast or very slow. To fix this problem click on the icon at the right edge of the setting to set it to “Ignore this setting”. The mouse has to be reset (e.g., by turning it off and on again) before this fix will take effect.

The driver also sets the scrolling direction to its normal setting when implementing smooth scrolling. This can interfere with the Scroll Wheel Direction setting, requiring flipping this setting back and forth to restore reversed scrolling.

The driver sends messages to devices that do not conform with the Logitech HID++ specification resulting in reponses being sent back that look like other messages. For some devices this causes Solaar to report incorrect battery levels.

Many gaming mice and keyboards have the ONBOARD PROFILES feature. This feature can override other features, including polling rate and key lighting. To make the Polling Rate and M-Key LEDs settings effective the Onboard Profiles setting has to be disabled. This may have other effects, such as turning off backlighting.

Solaar will try to use uinput to simulate input from rules under Wayland or if Xtest is not available but this needs write permission on /dev/uinput. For more information see the rules page.

Diverted keys remain diverted and so do not have their normal behaviour when Solaar terminates or a device disconnects from a host that is running Solaar. If necessary, their normal behaviour can be reestablished by turning the device off and on again. This is most important to restore the host switching behaviour of a host switch key that was diverted, for example to switch away from a host that crashed or was turned off.

When a receiver-connected device changes hosts Solaar remembers which diverted keys were down on it. When the device changes back the first time any of these diverted keys is depressed Solaar will not realize that the key was newly depressed. For this reason Solaar rules that can change hosts should trigger on key releasing.

Contributing to Solaar

Conributions to Solaaar are very welcome.

Solaar has complete or partial translations of its GUI strings in several languages. If you want to update a translation or add a new one see the translation page for more information.

If you find a bug, please check first if it has already been reported. If yes, please add additional information you may have to the existing issue. If not, please open a new bug report issue. If you can provide a fix for it, please also open a GitHub pull request. Label your commits using the naming conventions in recent commits to Solaar.

Читайте также:  Картридж canon 303 аналоги

If you want to add a new feature to Solaar, feel free to open a feature request issue to discuss your proposal. There are also usually several open issues for enhancements that have already been requested.


This software is distributed under the terms of the GNU Public License, v2.


This project began as a third-hand clone of Noah K. Tilton’s logitech-solar-k750 project on GitHub (no longer available). It was developed further thanks to the diggings in Logitech’s HID++ protocol done by many other people:

Also, thanks to Douglas Wagner, Julien Gascard, and Peter Wu for helping with application testing and supporting new devices.


Logitech Unifying Receiver и Linux

Кратко: Logitech Unifying Receiver приёмник у беспроводных устройств Logitech к одному которому можно слинковать до 6 устройст. При этом устройство, с которым вместе идёт приёмник уже заранее слинковано с ним и работает из коробки.

Проблема в том, что бы добавить новое устройство. Для этого нужен софт, и софт этот есть был только под Windows и под Mac OS X. Хорошо, что слинковав устройства на одном компе можно было использовать их на остальных без проблем. Но, согласитесь, не удобно.

Не волновал бы меня этот факт если бы не стал обладателем манипулятора Logitech M510 и в ожидании прихода с amazon.com Logitech K800 (заказывал с амазона только с одной целью: получить клавиатуру с «американской» раскладкой, т.е. с широким левым shift и узким enter, отсутствие русских букв не смущает: на нетбуке, с которым уже не первый год, их тоже отродясь не было).

Поэтому начался поиск. Первый результат официального форума Logitech неутешительный: линкуйте устройства в Win/Mac пользуйтесь везде.

Но дальше была просто сказка: почти сразу находится английская статья, описывающая утилиту Solaar (раз,два), далее ссылка на Арчвики из которой узнаётся о ещё двух (правда чисто консольных) утилитах: ltunify и pairingtool

Опробовал только Solaar, хоть она и написана на Python (личное предвзятое отношение), но зато имеет и GUI и CLI версию.

Для владельцев Debian & Ubunu установка не станет проблемой: добавляете репозиторий, делаете atp-get update , а дальше pt-get install solaar . На официальном сайте есть так же пакеты для OpenSuSE, для ArchLinux есть пакет в AUR. Последний и использовал.

Надо заметить, что при установке не говорится о таких полезных вещах, как:

  • для работы нужно пользователя добавить в группу plugdev, делаем сами:
    И перелогиниваемся, что бы изменения вступили в силу.
  • после установки нужно или перегрузить машину или заставить udev перечитать правила:
    и переподключить ресивер.

Но у меня Solaar и после этого отказался видеть приёмник. Как оказалось, проблема была в моём LTS ядре 3.0.x (обновление сегодня утром принесло LTS ядро 3.10, так что проблем больше не будет), т.к. полноценная поддержка ресиверов появилась только в ядрах 3.2.

После обновления и перезагрузки с новым ядром устройство моментально увиделось. Как оказалось, помимо линковки устройств, программа так же позволяет менять некоторые настройки самих устройств, отображать некоторые статусы и отлинковывать их (даже если устройство не подключено и находится в недосягаемости, к примеру, потеряли). Для моей M510 настроек/статусов получилось немного:

  • уровень заряда батареи
  • включение/выключение плавной прокрутки

Поддерживаемые (гарантированно) устройства и фичи перечислены в табличке на официальном сайте: pwr.github.io/Solaar/devices.html, но даже если вашего устройства там нет, есть вероятность, что оно заработает. По крайней мере слинковать его можно будет. Думаю, в таком случае, следует связаться с автором и рассказать, что за устройство и как работает, для пополнения коллекции.

На этом всё. Придёт K800 посмотрю как с ней подружится.


Logitech Unifying Receiver

The Logitech Unifying Receiver [dead link 2022-09-21 ⓘ] is a wireless receiver using 2.4 GHz band radio communication that can connect up to six compatible wireless mice and keyboards to your computer. The input device that comes with the receiver is already paired with it and should work out of the box through plug and play. Logitech officially supports pairing of additional devices just through their Windows and macOS software.

Pairing and unpairing on Linux is supported by a number of tools, listed thereafter:

ltunify is a command-line C program that can perform pairing, unpairing and listing of devices. Solaar is a graphical Python program that integrates in your system tray and allows you to configure additional features of your input device such as swapping the functionality of Fn keys. libratbag is a configurable mice daemon that allows you to configure your devices, it has a GTK based graphical frontend app, piper.



Several solutions are available:

The following packages use the plugdev user group, create it if it does not exist, and add users to this group to avoid the need of running these as root:

Читайте также:  Open vmdk file in linux

Do not forget to relogin to apply user’s group membership. After installation, run

and then replug reciever. After that you will not need root permissions.


pairingtool can only be used for pairing and does not provide feedback, it also needs to know the device name for pairing. ltunify, Solaar and libratbag can detect the receiver automatically.


Examples on unpairing a device, pairing a new device and showing a list of all devices:


Solaar has a GUI and CLI. Example CLI pairing session:

To disable autostart of Solaar, remove /etc/xdg/autostart/solaar.desktop .


Currently, piper is not able to pair/manage devices for unifying receivers but libratbag does include a lur-command command line tool that is able to do this.


To find the device that the receiver has, therefore take a look at the outputs of

This will show the names of your receiver, for example hidraw0 .

Now switch off the device that you want to pair (if it was on) and execute your compiled program with the appropriate device as argument:

Now switch on the device you want to pair. After a few seconds your new device should work properly.

Known Problems

Wrong device (pairing tool only)

On some systems there is more than one device that has the same name. In that case you will receive the following error message when the wrong device is choosen:

Keyboard layout via xorg.conf

With kernel 3.2 the Unifying Receiver got its own kernel module hid_logitech_dj which does not work flawlessly together with keyboard layout setting set via xorg.conf. A temporary workaround is to use xorg-setxkbmap and set the layout manually. For example for a German layout with no deadkeys one has to execute:

To automate this process one could add this line to xinitrc or the according autostart file of your windows manager respectively desktop environment.

Logitech touchpad keyboard K400r with unifying receiver M325

The Logitech keyboard K400r with integrated touchpad comes with Logitech unifying receiver M325 so the above mentioned about the keyboard layout will apply here too.

Also the integrated touchpad is recognized as ‘pointer’ instead of ‘touchpad’ so you cannot use the Touchpad Synaptics drivers. Two finger horizontal scrolling and tapclick will work but in order to have a middle mouse button emulated you will have to add

to your evdev.conf. Now third button is emulated by pressing both buttons simultaneously.

Solaar ‘Permission denied’

Is it possible to have the error:

In this case, you can physically remove the Unifying Receiver and re-insert it, and re-run the command (as described in the second point of installation part on the official site [1]).

Wireless Keyboard does not work while booting (cannot enter luks passphrase)

While booting it is impossible to input anything with a Logitech wireless Keyboard (e. g. Logitech MK700). The cause of the problem is the own hid module for Logitech devices since Kernel 3.2.

A workaround is adding hid-logitech-hidpp to MODULES in /etc/mkinitcpio.conf :

and recreate the initrd for the kernel:

MouseJack Vulnerability

Several security vulnerabilities of the system have been reported and you may be in particular affected by the MouseJack Vulnerability if your firmware has not been updated recently.

It is possible to display the current firmware’s version by running:

RQR12 firmware with version earlier than 012.008.00030 and RQR24 firmware versions earlier than 024.006.00030 are affected by this vulnerability and should be updated.

The firmware can be updated using fwupd like so:

If everything looks good, apply the update:

Keyboard or mouse does not wake pc from sleep

Lag of the wireless device

Because the receiver uses the 2.4 GHz frequency band also used by Bluetooth and Wi-Fi 802.11, it is possible in some circumstances of heavy Wi-Fi usage close to the receiver to experience lag or disturbances in communication with the devices. This is unlikely because the receiver confines its communication to channels unused by the majority of 802.11 solutions and it is able to quickly change channel within the band if it detects any interference from another device. However, some users have experienced interferences.

Switching on/off the device will force the search for a «quiet» channel and may solve the issue.

This problem can also manifest if there is electrical noise from USB3 sockets on the motherboard, and it is located close to or in one. Moving the receiver to a USB hub or the end of an extension cable may fix this.

See also

Logiops — Logitech Options alternative for configuring supported mice and keyboards


Поделиться с друзьями