Closed hierr closed 2 years ago
pfps
commented
2 years ago Run Solaar as solaar -ddd and provide output from startup to when main window appears. Provide contents of files in ~/.config/solaar. Also try removing ~/.config/solaar/config.yaml and then run Solaar as solaar -ddd and provide output as above.
hierr
commented
2 years ago Run Solaar as
solaar -dddand provide output from startup to when main window appears. Provide contents of files in ~/.config/solaar. Also try removing ~/.config/solaar/config.yaml and then run Solaar assolaar -dddand provide output as above.
I changed the issue because i was mistaken; the rules were there and i was able to add them, they just don't work (i think because the diversion rules disappeared).
I removed the ~/.config/solaar/config.yaml and here is the output of solaar -ddd:
pfps
commented
2 years ago Solaar now keeps track of settings that have caused problems and doesn't try them again. This is done to speed startup. It appears that at some recent run of Solaar there were problems and many settings were marked as non-operational. To fix modify ~/.config/solaar/config.yaml and remove the entries for the key _absent. Then run Solaar again with -ddd and see if the settings come back. If not, provide output from Solaar.
hierr
commented
2 years ago Solaar now keeps track of settings that have caused problems and doesn't try them again. This is done to speed startup. It appears that at some recent run of Solaar there were problems and many settings were marked as non-operational. To fix modify ~/.config/solaar/config.yaml and remove the entries for the key
_absent. Then run Solaar again with -ddd and see if the settings come back. If not, provide output from Solaar.
It did bring back the settings to the GUI but the rules still doesn't work even though the options are set to 'diverted'. Switching them back to regular makes it work in regular fashion. The _absent keys came back after starting Solaar.
pfps
commented
2 years ago I think the remaining problem is that you need to set permissions on /dev/uinput so that Solaar can use uinput to simulate input. Because using Xtest in Wayland is difficult Solaar only uses uinput under Wayland. See https://pwr-solaar.github.io/Solaar/rules for more information.
16:19:51,705 WARNING [MainThread] logitech_receiver.diversion: rules cannot access active process or modifier keys in Wayland
16:19:51,705 WARNING [MainThread] logitech_receiver.diversion: cannot create uinput device: "/dev/uinput" cannot be opened for writingI think the remaining problem is that you need to set permissions on /dev/uinput so that Solaar can use uinput to simulate input. Because using Xtest in Wayland is difficult Solaar only uses uinput under Wayland. See https://pwr-solaar.github.io/Solaar/rules for more information.
16:19:51,705 WARNING [MainThread] logitech_receiver.diversion: rules cannot access active process or modifier keys in Wayland 16:19:51,705 WARNING [MainThread] logitech_receiver.diversion: cannot create uinput device: "/dev/uinput" cannot be opened for writing
Yeah, that worked. Thanks!
Information
solaar --versionorgit describe --tagsif cloned from this repository): 1.1.3rc2uname -srmo):Linux 5.13.0-40-generic x86_64 GNU/Linuxsolaar show:Describe the bug After updating to version 1.1.3rc2 from 1.1.1 all my user defined rules of my Logitech MX Keys keyboard stopped working and the options to divert keys (which i think is the cause) disappeared from Solaar GUI. Also, all options that were available to my Logitech Master 3, like changing DPI, disappeared; only scroll wheel diversion remained.
To Reproduce Steps to reproduce the behavior:
Screenshots
