Closed FraYoshi closed 1 year ago
This is very likely:
The Linux HID++ driver modifies the Scroll Wheel Resolution setting 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", which is the default for new devices. The mouse has to be reset (e.g., by turning it off and on again) before this fix will take effect. [https://github.com/pwr-Solaar/Solaar#known-issues]
There have been changes to the driver that make this issue affect more devices.
You do appear to be encountering a bug related to your older receiver. Can you clone Solaar from this repository and run it as bin/solaar -ddd
and see whether you still get the AttributeError? Also run bin/solaar -ddd show
There have been changes to the driver that make this issue affect more devices.
Indeed, ignoring the setting for the bluetooth, fixed it.
and see whether you still get the AttributeError?
The attribute error changed from
AttributeError: 'Device' object has no attribute 'get_kind_from_index'
to
AttributeError: 'NoneType' object has no attribute 'handle'
Also run
bin/solaar -ddd show
:
Thanks. I'm going to change the title of this issue to something about the 27MHz receiver.
Solaar doesn't know about your keyboard. Can you provide a name for it (something like Wireless Keyboard SXXX)?
Also please provide the full output of bin/solaar -ddd
that shows the new error.
Solaar doesn't know about your keyboard. Can you provide a name for it (something like Wireless Keyboard SXXX)?
It's a 'Cordless Desktop EX110' , quite old! It was bundled with a mouse that I do no longer use.
Also please provide the full output of bin/solaar -ddd that shows the new error.
Unfortunately, I tried to reproduce the attribute error, but shows up only for the keyboard (no mouse connected) and now is the same as before: AttributeError: 'Device' object has no attribute 'get_kind_from_index'
Also, does not show up if I use show
but only with ./bin/solaar -ddd
The GUI and the CLI use different methods to find devices. Only the GUI has the problem.
Solaar is complaining about your rules.yaml file. Can you provide the contents of ~/.config/solaar/rules.yaml?
It looks as if the debug output does not come from the version of Solaar in this repository. Please clone Solaar from this repository, cd to the clone directory, and run bin/solaar -ddd
Solaar is complaining about your rules.yaml file.
My rules.yaml (yes, just that, but might be my fault, I was experimenting with It months ago):
%YAML 1.3
My Config:
It looks as if the debug output does not come from the version of Solaar in this repository.
I am pretty sure I run from the repository. Anyway, just to be on the safe side, I killed and unistalled the system version of Solaar.
Here the new output (now It gives permission errors):
So all is well now? The Solaar GUI should show your keyboard.
The error goes away normally, when using the mainstream Solaar, but when running via the git version, it continues to pop out.
This, just when connecting the bluetooth mouse.. otherwise, the error does not appear.
no mouse:
after mouse:
Solaar depends on extra permissions on devices, which is obtained using a udev rule. I expect that when you removed Solaar this rule was removed. If you clone Solaar you have to manually install the rule, as described in https://pwr-solaar.github.io/Solaar/installation.
Installing Solaar’s udev rule
Solaar needs to write to HID devices for receivers and devices. To be able to do this without running as root requires a udev rule that gives seated users write access to the HID devices for Logitech receiver and devices.
You can install this rule by copying, as root, rules.d/42-logitech-unify-permissions.rules from Solaar to /etc/udev/rules.d. You will probably also have to tell udev to reload its rule via sudo udevadm control --reload-rules.
For this rule to set up the correct permissions for your receivers and devices you will then need to either disconnect your receivers and any USB-connected or Bluetooth-connected devices and re-connect them or reboot your computer.
Are you setting the attribute error at all when running bin/solaar -ddd
?
Followed the instructions and started with the git version correctly. No attribute error shows up now. Just as completion, re-tried with the Arch repository's version, it pops up again. But is no longer an issue related to this project, I guess..
OK, so I'll close this issue.
Information
1.1.8
Arch Linux
Linux 6.2.9-arch1-1 x86_64 GNU/Linux
solaar show
:Config:
Describe the bug
After last upgrade of the system, bluetooth mouse does no longer scroll correctly. It skips steps and is very slow when it works. A
xinput test <n>
shows that the scroll happens only once every 4/5 movements. If the movement is continuos, it continues to receive inputs, but if stopped for halfish a second, it stops receiving. It happens ONLY with the scroll wheel and ONLY via bluetooth. UsingBluez 5.66-1
, and tried downgrading bluez and solaar to a previous working version and restarting the services, but the problem remains.To Reproduce
Steps to reproduce the behavior:
Screenshots
https://user-images.githubusercontent.com/14005514/229499519-bc715b37-977d-430a-b815-2e75069a6026.mp4
Additional context
Using a TP-Link UB500 Adapter, and it hs worked flawlessly for the last 4/5 months (didn't have it before)