Error message with Logitech G Pro X Lightspeed gaming headset #2797
Labels
Comments
|
It appears that this device works differently from other devices when the headset is turned off. What to do about this is undetermined at present. Output of |
|
Also post output of |
|
Sorry, I'm still new to the linux world. solaar show gives me an error about wayland and a missing gnome shell extension, that's why I omitted it. I've seen other reports missing this, so I thought it would be ok. I've since installed the shell extension, activated it and rebooted, but the message persists: solaar show output (same with headset on/off):solaar -ddd output:Not sure if this is usable, it runs really fast up until it reaches the point where I ^C, because it seems to be stuck there. lsusb output:Thanks, let me know if theres anything else I can do to help. |
Thorwan
changed the title
|
Changed the title and updated the description in the initial post, because I just encountered the error rebooting with the headset turned on. So my original assumption about the nature of this is probably wrong. |
|
The headset has worked with Solaar in the past. I want to be sure of what happens when you turn the headset off and on, so try running Also try |
solaar -ddd output (no audio playback, 30s after starting solaar -ddd, I turned the headset off, 10s later I turned it back on, 20s after that quit the application)solaar -ddd output (youtube audio playback on headset, 30s after starting solaar -ddd, I turned the headset off, 10s later I turned it back on, 20s after that quit the application)Edit to add: As I mentioned before, I pretty sure this started one or two versions ago. The headset was working with solaar before without issue. |
|
OK, so Solaar has to be able to set up the device when the headset is not turned on, because there is no Linux udev information when the headset is turned off or on. This makes things harder for Solaar. The logic Solaar uses has to be able to keep the device around even if Solaar can't even ping it. |
|
PR #2798 might fix the problem. Run it, and post whether the problem is fixes. If not, post output of To clone and use Solar from its GitHub repository Run Solaar as bin/solaar from this directory. To run PR #2798, 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: |
|
Just to make sure I've done this correctly: and started the application using The headset shows up in the application, even when turned off. Terminal output after starting the application with the headset turned off, then turn it on and off again: |
|
It's looking better but there is still some sort of error. Try running as |
|
Hope this helps. Headset on, starting bin/solaar -ddd, after 30s headset off, after 10s headset on |
|
No crash shows up, just some issues trying to push values to some settings. There is a different issue for that so I'm going to merge the PR, which will close this issue. |
|
Awesome, thanks a lot! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Information
solaar --versionorgit describe --tagsif cloned from this repository): 1.1.14uname -srmo): 6.12.11-200.fc41.x86_64solaar show:~/.config/solaar/config.yaml(or~/.config/solaar/config.jsonif~/.config/solaar/config.yamlnot present):There are two files:
File 1
File 2
Describe the bug
After booting an error message from the solaar application appears:
Cannot connect to device error
Found a Logitech device at /dev/hidraw2, but encountered an error connecting to it.
Try disconnecting the device and then reconnecting it or turning it off and then on.
This seems to be caused by my Logitech G Pro X Lightspeed gaming headset dongle being connected, but the headset turned off. Starting the PC with the headset turned on, the message does not appear.Update: This assumption seems not to be correct, just encountered this booting with the headset turned on.
To Reproduce
Boot PC with Lightspeed receiver connected but headset turned offJust seems to happen with the headset receiver connected while booting.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
I'm also using other Lightspeed products: G502 Lightspeed mouse and G915 TKL Lightspeed keyboard which work without issues.
The error message did not appear two versions ago.
The text was updated successfully, but these errors were encountered: