I discovered I was affected by #219 , also reported on Discourse.
There is a udev rule in this file (/usr/lib/udev/rules.d/99-thinkpad-thresholds-udev.rules) that tries to chmod 0666 some files that don't exist on my machine (Framework 13, not Thinkpad).
These were my logs:
Jun 01 19:14:11 rnkftw (udev-worker)[499587]: BAT1: Process '/bin/chmod 666 /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:41/PNP0C0A:00/power_supply/BAT1/charge_control_start_threshold' failed with exit code 1.
Jun 01 19:14:11 rnkftw (udev-worker)[499587]: BAT1: Process '/bin/chmod 666 /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:41/PNP0C0A:00/power_supply/BAT1/charge_start_threshold' failed with exit code 1.
Jun 01 19:14:11 rnkftw (udev-worker)[499587]: BAT1: Process '/bin/chmod 666 /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:41/PNP0C0A:00/power_supply/BAT1/charge_stop_threshold' failed with exit code 1.
I have a framework 13. I resolved by issue by replacing the file with a /dev/null symlink and reloading (this seems needlessly convoluted, I blame Claude):
sudo ln -s /dev/null /etc/udev/rules.d/99-thinkpad-thresholds-udev.rules
Then I ran sudo udevadm control --reload, and my system stopped overheating in my lap from this tight loop chmod.
Issue #219 was closed as stale, but it seems it's still present, so I refiled it. Maybe something changed on my system and now BAT1 exists and this started to manifest, hard to say.
I discovered I was affected by #219 , also reported on Discourse.
There is a udev rule in this file (
/usr/lib/udev/rules.d/99-thinkpad-thresholds-udev.rules) that tries to chmod 0666 some files that don't exist on my machine (Framework 13, not Thinkpad).These were my logs:
I have a framework 13. I resolved by issue by replacing the file with a /dev/null symlink and reloading (this seems needlessly convoluted, I blame Claude):
sudo ln -s /dev/null /etc/udev/rules.d/99-thinkpad-thresholds-udev.rulesThen I ran
sudo udevadm control --reload, and my system stopped overheating in my lap from this tight loop chmod.Issue #219 was closed as stale, but it seems it's still present, so I refiled it. Maybe something changed on my system and now BAT1 exists and this started to manifest, hard to say.