search

libratbag / libratbag

A DBus daemon to configure input devices, mainly high-end and gaming mice
MIT License
2.12k stars 258 forks source link

Logitech G502 X Plus - No devices available #1655

Open zackmagic42 opened 3 weeks ago

zackmagic42 commented 3 weeks ago

Information

Device info (if applicable): Logitech G502 X Plus

$ ratbagctl singing-gundi info Unable to find device singing-gundi


**Describe the bug**
Cannot get the mouse to appear as an available device. Added following device file:
[Device]
Name=Logitech G502 X PLUS Wireless
DeviceMatch=usb:046d:c095;usb:046d:c547
DeviceType=mouse
Driver=hidpp20

[Driver/hidpp20]
DeviceIndex=1

**To Reproduce**
Steps to reproduce the behavior:
1. Added g502-x-plus-wireless device file to /usr/share/libratbag/(above contents)
2. Restart ratbagd/reboot
3. Run ratbagctl
4. "No devices available."

**Logs**
Please start the daemon with verbosity and reproduce the issue.

First make sure it isn't running already.

$ ratbagd --verbose=raw ratbag error: Profile layout not supported: 0x05. ratbag error: Logitech USB Receiver: error opening hidraw node (Operation not supported)


systemctl status ratbagd
ratbagd.service - Daemon to introspect and modify configurable mice
     Loaded: loaded (/usr/lib/systemd/system/ratbagd.service; disabled; preset: disabled)
     Active: inactive (dead)

Oct 22 17:23:39 PC systemd[1]: Started Daemon to introspect and modify configurable mice.
Oct 22 17:23:40 PC ratbagd[3572]: ratbag error: Profile layout not supported: 0x05.
Oct 22 17:23:40 PC ratbagd[3572]: ratbag error: Logitech USB Receiver: error opening hidraw node (Operation not supported)
Oct 22 17:23:41 PC ratbagd[3572]: ratbag error: Profile layout not supported: 0x05.
Oct 22 17:23:41 PC ratbagd[3572]: ratbag error: Logitech USB Receiver: error opening hidraw node (Operation not supported)
Oct 22 17:23:41 PC ratbagd[3572]: ratbag error: Profile layout not supported: 0x05.
Oct 22 17:23:41 PC ratbagd[3572]: ratbag error: Logitech USB Receiver: error opening hidraw node (Operation not supported)
Oct 22 17:35:46 PC systemd[1]: Stopping Daemon to introspect and modify configurable mice...
Oct 22 17:35:46 PC systemd[1]: ratbagd.service: Deactivated successfully.
Oct 22 17:35:46 PC systemd[1]: Stopped Daemon to introspect and modify configurable mice.
Nytem commented 2 weeks ago

Same issue here with my G502 X Plus. Kinda sucks that this one mouse just doesn't work with it...

Nytem commented 2 weeks ago

I'm not sure if this effects anything, still kind of new to Linux and can be pretty dumb. I've always noticed that OpenRGB was detecting a "Logitech G915" Mechanical keyboard, but I built my own keyboard using the Keychron Q1 Pro.

Looking into it just now, I noticed that the OpenRGB udev rules shows this for that keyboard: Screenshot from 2024-10-25 17-50-56 Full rules file here.

It's the only device in OpenRGB's udev rules that uses 046d and c547, which happens to be the same for the G502 X Plus.

Again, I'm pretty stupid and new to Linux still, I just thought I'd bring this up in case maybe the OpenRGB udev rules are messing with it in some way?

zackmagic42 commented 2 weeks ago

That’s actually a good point, I didn’t think to check it. I installed OpenRGB through the arch repo which automatically adds the udev rules if I remember correctly so I totally forgot about that. When I’m in front of my PC again I’ll try disabling it in OpenRGB devices and if that doesn’t work I’ll try removing it from the udev rules file and see if either works. I’ll report back when I know one way or the other.

moxSedai commented 2 weeks ago

Will this mouse ever get support? I saw a 2 year-old issue that is still open about it.

Keksianer commented 2 weeks ago

I have another theorie. I have an similiar issue, not with G502 (i have spectrum edition), but with G5 (yes only G5, it is very old, but working), M570 and Keyboard G413. I have Garuda-Linux, it is based up on Arch Linux and..... only G502 are listed. Maybe it is a specific Arch-Linux problem? zackmagic is using Arch-Linux. What distros are you using? On reddit, here and other sites have people more often problems with piper/ratbag if there are using Arch-Linux distros. Well, it is just a feeling, could be wrong, but for most people it is just working.

moxSedai commented 2 weeks ago

I'm on Kubuntu 24.04

Nytem commented 2 weeks ago

I'm on PopOS 22.04, forgot to mention that in my original comment.

zackmagic42 commented 2 weeks ago

I wanted to post an update now that I was able to test. I modified the installed udev rules applied for openrgb. After disabling the device in software there were no changes. I then commented out the one line referencing the matching device ID, reloaded rules, and no change at all. I still see "No devices available." It seems like this is not an issue with openrgb or conflicting udev rules.

Nytem commented 2 weeks ago

rip. Wonder if they'll ever add proper support for the mouse, cause yeah there's still that open post from 2 years ago.

Keksianer commented 2 weeks ago

Well.... this is freeware.... the people who worked on this are doing this in there free time. It is hard to find a bug, if they don't know where it comes from and yes for you it is frustrating. I think the focus is more on support more mouses/keyboards, than to find a bug where only some people have. I wish that my mouses will be find by ratbag, there are also supported in device list....

In my opinion: Logitech does not have any Linux software, that the real frustating fact Don't be angry to the people here, there worked in their free time for software to use it for free. Be angry to Logitech, that their ignore Linux users. If i buy a new hardware, it will be definitly not a Logitech anymore and i bought Logitech for over 20 years.

I do some research. Sometimes this could work, i have to test it, too:

Sometimes ratbag have priveleg problems to communicate between PC and Mouse, that is not the fault of Linux oder ratbag, it is fault from Logitech Software (security maybe?).

If i have more ideas or find for me some solution, i will report. I don't know if the programmers/maintainers of radbag are reading actually this reports. They are human and have maybe important self-problems (thickness, work, family, etc.) and don't have time and that is okay, even it is for bad for us, because we want to have a good useable software.

At this Point: Thank you for your work porgrammers!

Nytem commented 2 weeks ago

Sorry, I didn't mean for my comment to come off as me being annoyed with anyone here that the mouse doesn't work, I 100% know that's Logitechs fault, and I'm thankful for the work the devs do here as ratbag allows many users to use their mice and it works with other mice I have. (the G502 X Plus just happens to be my favorite)

It was very likely bad wording on my end looking back, what I meant by my comment was more like "I wonder if it'll ever work or if it's a bug that's just really hard to squash". A lot of people in the previous post were working to try and find the problem, thankful for every one of them. I had 0 intention of ever being upset at the devs here.

As for the possible solution you posted, I'll give it a go when I can. The mouse works just fine and can swap profiles and all, it's just tedious as I've been booting up my laptop with windows next to my desktop to use G-Hub and edit the on-board profiles. I haven't had any luck with other solutions to at least get the mouse to show up in the terminal using ratbagctl.

So yeah, I'll give the possible solution a go when I can, maybe it just needs a factory reset to at least show up in ratbagctl (along with the other stuff from the other issue post). And I apologize again for my poor wording and my comment coming off the wrong way.

zackmagic42 commented 2 weeks ago

Ok, I have another update. I think the issue is still with accessing the HIDRAW device. I added a udev rule for the mouse: _SUBSYSTEMS=="usb|hidraw", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c547", TAG+="uaccess", TAG+="Logitech_G502_XWireless", GROUP="input", MODE="660" I also added my user to the input group and rebooted. Still receive "No devices available." when running ratbagctl. When starting ratbagd I still receive "ratbag error: Logitech USB Receiver: error opening hidraw node (Operation not supported)." At this point I'm out of ideas but if anyone has any suggestions I'll gladly try and report back.

moxSedai commented 2 weeks ago

Well.... this is freeware.... the people who worked on this are doing this in there free time. It is hard to find a bug, if they don't know where it comes from and yes for you it is frustrating. I think the focus is more on support more mouses/keyboards, than to find a bug where only some people have. I wish that my mouses will be find by ratbag, there are also supported in device list....

In my opinion: Logitech does not have any Linux software, that the real frustating fact Don't be angry to the people here, there worked in their free time for software to use it for free. Be angry to Logitech, that their ignore Linux users. If i buy a new hardware, it will be definitly not a Logitech anymore and i bought Logitech for over 20 years.

I do some research. Sometimes this could work, i have to test it, too:

* Start a PC or VM with Windows and Logitech Software

* if using VM: Be sure that Logitech GHub known your Mouse, in my case VM does not work.

* Make a factory reset to the mouse and/or edit some profiles.

* Save it to the Mouse, that's the importent point, don't save locally, save to Mouse!

* Try again with your Linux OS/PC.

Sometimes ratbag have priveleg problems to communicate between PC and Mouse, that is not the fault of Linux oder ratbag, it is fault from Logitech Software (security maybe?).

If i have more ideas or find for me some solution, i will report. I don't know if the programmers/maintainers of radbag are reading actually this reports. They are human and have maybe important self-problems (thickness, work, family, etc.) and don't have time and that is okay, even it is for bad for us, because we want to have a good useable software.

At this Point: Thank you for your work porgrammers!

I mean, it's not that there's a bug, the program entirely lacks support for the mouse.

moxSedai commented 2 weeks ago

To clarify, I have no issue with the devs here, I just would like for this issue to be acknowledged at the least.

The post from 2 years ago included a partial fix, which got ratbagd and piper to recognize that my mouse exists, but it has the incorrect number of inputs, changing the DPI doesn't work, and trying to use the additional inputs does not work.

Keksianer commented 2 weeks ago

To clarify, I have no issue with the devs here, I just would like for this issue to be acknowledged at the least.

The post from 2 years ago included a partial fix, which got ratbagd and piper to recognize that my mouse exists, but it has the incorrect number of inputs, changing the DPI doesn't work, and trying to use the additional inputs does not work.

have you ever tested with Solaar?

zackmagic42 commented 1 week ago

I have tested with Solaar and cannot get the mouse to appear there either.