Return to Level1Techs.com

Latest Linux Kernel Breaks G502 Mice - Arch - Issue Resolved

I was wondering why my extra buttons stopped working, and apparently there are now basic logitech drivers in the kernel which breaks the workaround (mix of generic mouse and keyboard polling) to get the extra buttons working.

https://bbs.archlinux.org/viewtopic.php?id=248898

edit:

Just an update to this post:

The problem was nailed down to NOT the linux kernel as was previously thought. The issue was systemd.

The latest systemd fixes the problem so just do a pacman -Syu and you get your buttons back!

6 Likes

Do you happen to know if this also affects the G402? That would be annoying :expressionless:

Unknown, I only have two g502 mice.

I was reading the bug reports and apparently it’s even broken in testing still.

I really don’t want to have to recompile my kernel every upgrade so hopefully this gets fixed quickly.

What a surprise, something broken on a bleeding edge distro :wink:

/s

But for real though, thanks for the PSA.

1 Like

Can you not just blacklist the new kernel driver and load the previous driver that worked?

Are you using libinput?

not sure if blacklisting is really an option. there have been a lot of logitech specific stuff added to the kernel in 5.2 that piggybacks on eachother so it might cause instability.

I’m not surprised. The maintainers of Arch have a bad habit, of trying to fix stuff that’s not broken, and then break it.

Arch is the main reason I refuse to use pre-made kernels. I got tired of their non-sense. For now just default back to the previous kernel and wait it out, or use one of the other kernels available in the AUR

i’m still salty about Arch deprecating the synaptic driver in favor of libinput, so leave me alone

Also side note for those who don’t already know, if you use Arch, you know damn well what you signed up for, keep a working kernel in your /boot folder. It will save your skin one of these days.

this is not because of Arch, this is the mainline Linux kernel changes.

This is part of the logitech revamp that is going on in 5.2

edit: also, I’m not complaining, was just letting folks know in case they use arch or an arch based distro as it was driving me nuts for a few hours until I figured out the problem

I know, i mean no harm, i’m Just being salty cause i’ve used Arch for 3 years and went through the headache of fixing things and get Vietnam flashbacks of the nightmares.

I still feel in my heart it’s an Arch problem though. To test this theory, try using The same kernel version but one available on the AUR and see if you have issues.

1 Like

it’s all good. I just want to be clear on it as it seems this will get fixed in future updates.

I figure the risk of stuff breaking is par for the course, and a sacrifice I’m willing to make so that others don’t have the problem in more stable versions. I can deal with the weird problems as it helps me learn more about my system everytime I have to do a workaround etc.

I’m just waiting for Linus to get wind of it so I can see his rant on kernel.org

:rofl:

1 Like

Mh so… which version is affected exactly? Cause I just got a notification on my Fedora install that 5.2.13 is available soooo… :thinking:

5.2.13 is still affected AFAIK

edit: to be clear, I haven’t updated to this version as of yet, only have other folks who have posted about it to go on

OK so which Kernel did you get it on first? Cause currently I’m on 5.2.11 and my G402 Keys are still working

/edit
actually just saw in the link you posted it says 5.2.11 was the issue… mh

Just an update to this post:

The problem was nailed down to NOT the linux kernel as was previously thought. The issue was systemd.

The latest systemd fixes the problem so just do a pacman -Syu and you get your buttons back!

3 Likes

Systemd-udev?

I can’t think of anything else in systemd that could cause this issue. :confused:

Not 100% sure. The 243 version of systemd fixed the problem for me.

1 Like

I’m gonna have to dig into the change log to see what caused it. It’s piqued my interest.

I can confirm in the updates the systemd-udev was updated so perhaps that was the root cause? I have a problem keeping track of all the changes as I clear my paccache often to rebuild a distro I’ve been maintaining so sometimes I miss things like this.

Let us know if you find any clues :wink: