Applying udev rules fails - "Cannot allocate memory"

samteezy

I noticed an issue this week regarding an update of a third party package (Google Earth) after which udev rules no longer can apply.
I rebooted, and I'm still seeing the issue. Running sudo udevadm control --reload results in:

 [✓] Reloading udev rules                                               success
 [✗] Applying udev rules                                                 failed

A copy of the command output follows:

input33: Failed to write 'change' to '/sys/devices/virtual/input/input33/uevent': Cannot allocate memory

Not sure where to go next to see what could be causing this issue. I'm up to date on Budgie as of the most recent sync. sudo eopkg check shows no broken packages. Uninstalling the google-earth package didn't fix the issue either.

neofetch output:
OS: Solus x86_64
Kernel: 5.15.32-213.current
Uptime: 7 mins
Packages: 1206 (eopkg), 38 (flatpak)
Shell: bash 5.1.16
Resolution: 1920x1080, 1080x1920
DE: Budgie 10.6.1
WM: Mutter(Budgie)
Theme: Plata [GTK2/3]
Icons: Papirus [GTK2/3]
Terminal: gnome-terminal
CPU: AMD Ryzen 5 5600G with Radeon Graphics (12) @ 3.900GHz
GPU: AMD ATI 07:00.0 Cezanne
Memory: 2986MiB / 23410MiB

samteezy

Still trying to troubleshoot - I ran Memtest86 this morning and no errors shown after multiple passes, so it doesn't appear to be a RAM hardware issue.

Here's what I found when running journalctl:

Apr 28 10:41:09 tributo systemd-udevd[763]: /usr/lib64/udev/rules.d/11-dm-lvm.rules:40 Invalid value for OPTIONS key, ignoring: 'event_timeout=180'
Apr 28 10:41:09 tributo systemd-udevd[763]: /usr/lib64/udev/rules.d/11-dm-lvm.rules:40 The line takes no effect, ignoring.
Apr 28 10:41:09 tributo kernel: synth uevent: /devices/virtual/input/input33: failed to send uevent
Apr 28 10:41:09 tributo kernel: input input33: uevent: failed to send synthetic uevent

Output from udevadm info --query=all --path=/devices/virtual/input/input33:

P: /devices/virtual/input/input33
L: 0
E: DEVPATH=/devices/virtual/input/input33
E: SUBSYSTEM=input

samteezy

I'm seeing others report this on Reddit.
I've also opened an issue in Dev Tracker on it: https://dev.getsol.us/T10245

nolan

did you try using usysconf run -f?

samteezy

nolan Yes, and it doesn't fix anything.

@ma-renaud output of that command is py-evdev-uinput for me. sounds like I'll have to try to look at my package install history and start removing anything I've newly added... I'm hoping it wasn't a package update that broke anything, though.

ma-renaud

I had the same problem.
Using the following command should give you a clue of where it's coming from.
cat /sys/devices/virtual/input/input33/name

In my case it was python-evdev that was causing it and removing it solve the problem, but I had to also uninstall piper, solaar and lutris.

algent

samteezy output of that command is py-evdev-uinput for me

That looks like python-evdev package, and it has been recently updated.
Could you try to reinstall python-evdev with:

sudo eopkg it --reinstall python-evdev

If that doesn't help, then you can try to install the older version of python-evdev with:

sudo eopkg it https://packages.getsol.us/shannon/p/python-evdev/python-evdev-1.4.0-8-1-x86_64.eopkg

samteezy

algent I think solaar is somehow the issue here, at least in part.

If I uninstall it and then run usysconf run -f I don't get any errors any longer, even without touching python-evdev. Downgrading python-evdev without removing solaar still presents the error.

Stupid question perhaps - how does one find the direct package URL like you did for python-evdev? I want to try downgrading to the prior version of solaar.

algent

samteezy Stupid question perhaps - how does one find the direct package URL like you did for python-evdev? I want to try downgrading to the prior version of solaar.

You can find it at:

https://packages.getsol.us/

For example, solaar in shannon repo navigate
"Shannon" -> "s" -> "solaar"
There right click on preferred package release and copy the link address for example the previous release nr. 15.

https://packages.getsol.us/shannon/s/solaar/solaar-1.1.1-15-1-x86_64.eopkg

Skip the delta packages.

For packages we keep only last three releases. In the case of solaar we have release 14, 15 and 16.

samteezy

algent Thank you!

Yep, the older version of solaar combined with the newest python-evdev isn't presenting the errors, even after reboot, so I think it's an issue with solaar instead.

algent

Yep, the older version of solaar combined with the newest python-evdev isn't presenting the errors, even after reboot, so I think it's an issue with solaar instead.

I could try to rebuild again solaar v.1.1.2 on build server, but I need your help to check if it fixes the issue.

samteezy

algent Let me know how I can help. I'm about to start work for the day so my ability to respond/test is going to be sporadic, but worst case scenario I can test it Saturday morning.

algent

Ah, never mind. Looks like solaar doesn't have python-evdev in build dependences.

algent

samteezy Luckily there is a new release of solaar v.1.1.3 we can try that.
https://github.com/pwr-Solaar/Solaar/releases/tag/1.1.3

samteezy

algent Interesting about your prior comment of python-evdev not listed as dependency, as the release notes for 1.1.2 do list that specifically.
https://github.com/pwr-Solaar/Solaar/releases/tag/1.1.2

algent

python-evdev is runtime dependency, not build dependency. These are two different things.

You can check our script here : https://dev.getsol.us/source/solaar/browse/master/package.yml

samteezy

algent Ah, thanks for clarifying. This is where a little knowledge, but not a lot, can be dangerous 🙂

algent

@samteezy I am digging a little more.
Can you try to uninstall solaar, then run sudo usysconf run -f
then restart your session by doing log off/in.
After that install again solaar.

davidjharder

Newest solar has fixed this for me. Required a reboot. It will likely be a while before this lands in the Stable repository.

Great work @samteezy spotting the culprit

algent

@samteezy Can you test solaar v.1.1.3 please:

sudo eopkg it https://packages.getsol.us/unstable/s/solaar/solaar-1.1.3-17-1-x86_64.eopkg

I may require a reboot.

samteezy

algent Seems to work! Both after initial install, and then rebooting and running usysconf run -f, there are no errors.