Nothing to do with udev, it just causes the initramfs to be rebuilt.
What happens is that apparently due to the recently uploaded base-files there is now a /run directory, which might get partially populated during runtime. Apparently during initramfs time, udev uses /dev/.udev, but then when then initramfs is done, udev gets stopped, and restarted in the "real" system again, at which point it uses /run/udev/. But the latter does not have any of the previously detected properties like ID_INPUT_*, and thus stuff fails all over the place.
As you already figured out, "sudo rm /run/*" will temporarily fix the problem again.
We need to make up our mind here if we want to complete the base-files upload for /run, and adjust initramfs-tools etc. accordingly, or revert it, to avoid having more people fall into this trap.
Nothing to do with udev, it just causes the initramfs to be rebuilt.
What happens is that apparently due to the recently uploaded base-files there is now a /run directory, which might get partially populated during runtime. Apparently during initramfs time, udev uses /dev/.udev, but then when then initramfs is done, udev gets stopped, and restarted in the "real" system again, at which point it uses /run/udev/. But the latter does not have any of the previously detected properties like ID_INPUT_*, and thus stuff fails all over the place.
As you already figured out, "sudo rm /run/*" will temporarily fix the problem again.
We need to make up our mind here if we want to complete the base-files upload for /run, and adjust initramfs-tools etc. accordingly, or revert it, to avoid having more people fall into this trap.