G733 Headset Missing LED Controls Until Start, Kill, Start Of Solaar App #2784
Comments
|
This looks like a bug, but it may be that it has been fixed. Please update to version 1.1.14 of Solaar. |
|
Using latest version via PipX gives the same result. Image:
|
|
OK. To find out more about what is happening run Solaar as |
|
I have G733. I dont fully understand your issue. But what I can provide in this context is:
Reproduce without even restarting your pc
Result: How to solve it:
Result: Now Solaar on boot sees that the headset exists, properly detects it and allows you to edit the RGB settings. Adding to that, now you can close your headset and open it again, and the RGB will work fine. As long as Solaar isnt restarted, it will be able to properly handle your headset to its full extent. In general, I suspect that because the headset is wireless, and can be turned on and off, manually or automatically to save battery but Solaar doesnt do some kind of subroutine, when new, previously undetected, devices are connected. Thus, when you start Solaar, with all the needed devices connected, Solaar detects them properly, stats all needed subroutines and no issues arise. I believe the issues roots from Solaar assuming that all connected devices, will be connected when the program starts, like it used to be true when all devices were wired. |
|
The issue is, I believe, that the headset works differently from most other devices that Solaar can support when the headset is turned off. Determining the difference is likely not possible without someone who both understands how Solaar works and how the device works. |
I'm waiting for this information. |
|
run-with-headset-powered-off.txt I am not the one who originally opened the issue. And I didnt want to take over the issue, in case the OP was experiencing a differnt issue. But since they are not replying with the logs, I will. Here are my logs attached. One file contains the logs of running solaar, while my headset was previously turned off, which causes the headset to not get the profile for rgb and thus have its rgb mistakenly turned on. While the other is the run of solaar while my headset was already on and connected to my pc, which caused the rbg to be turned of the moment solaar was booted. Note that in both cases, after seeing the results based of the rgb, I rebooted my headset for good measure. Nothing unexpected happened. I then killed solaar using the gui "Quit App" button. |
Information
solaar --versionorgit describe --tagsif cloned from this repository): solaar 1.1.13+dfsg-1uname -srmo):Linux 6.11.0-13-generic x86_64 GNU/Linuxsolaar show:~/.config/solaar/config.yaml(or~/.config/solaar/config.jsonif~/.config/solaar/config.yamlnot present):WARNING [MainThread] solaar.ui.icons: failed to detect iconsDescribe the bug
The first time I start Solaar(either via command, selecting from Ubuntu Start Menu, or adding to Startup Applications for Ubuntu), the window for Solaar shows that it found my G733 headset, it shows "LED Control = Solaar". But the next line is "Divert G and M Keys...", there is no shown options to change the LED settings.
However, if I click "Quit Solaar" in the bottom left and then relaunch Solaar (in any of the 3 previously mentioned ways), it will then show the two LED's to control under neat the "LED Control = Solaar" option/setting. Its then fine until I reboot the system, or until I logout and log back in.
To Reproduce
Steps to reproduce the behavior:
`I described the steps to reproduce in the 'Describe the bug' section above.
Screenshots
LED Control Options I'm talking about:
Additional context
bash -c "sleep 10 && solaar --window=hide"to add a 10 second delay before the launch. This did not seem to change anything.The text was updated successfully, but these errors were encountered: