-
Notifications
You must be signed in to change notification settings - Fork 426
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regression from 1.1.13: BoltReceiver is broken #2674
Comments
I am starting to look after the problem, but this is deep further to my knowledge |
That's a bug, indeed. |
Should be fixed by #2661 |
@rloutrel Can you try out #2661? To clone and use Solar from its GitHub repository
Run Solaar as bin/solaar from this directory. To run PR #2661, first clone Solaar if you have not already done so and cd to the clone directory. The first time you download the pull request, fetch it into a new branch and checkout that branch, as in:
To download a new version of the pull request, fetch it and then set your pull branch to the new fetch, as in:
|
The bug is fixed with these modifications |
@rloutrel Thanks for the report. |
Information
solaar --version
orgit describe --tags
if cloned from this repository): current master versionuname -srmo
): Linux 6.11.6-300.fc41.x86_64 x86_64 GNU/Linuxsolaar show
:Exception ignored in: <function Receiver.del at 0x7fb670593c40>
Traceback (most recent call last):
File "/home/user/PycharmProjects/Solaar/lib/logitech_receiver/receiver.py", line 146, in del
self.close()
File "/home/user/PycharmProjects/Solaar/lib/logitech_receiver/receiver.py", line 138, in close
handle, self.handle = self.handle, None
^^^^^^^^^^^
AttributeError: 'BoltReceiver' object has no attribute 'handle'
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behaviour:
** Screenshots (v 1.1.13 vs current master) **
V 1.1.13
V current Master
Additional context
When switching back to the tag 1.1.13, the boltreceiver ist working as expected
The text was updated successfully, but these errors were encountered: