Hey BTW, I suspect this 'error' is due to upstream commit 97afc0351a96e0daa83964df33937967c75c644f which changed udevadm's behavior; previously it silently ignored errors writing to /sys/devices/*/uevent files, but now it logs error and returns error code. So this is likely not *actually* a new failure, it's just now being reported as failure by udevadm.
There is a similar 'failure' in bug 1845319 where (only on ppc64el) it gets ENODEV when writing to /sys/devices/vio/uevent, but I checked older releases and the vio device has been returning ENODEV for a long time; udevadm was just ignoring that before now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1845314 Title: udisks2 fails to install in a container with systemd 243 Status in systemd package in Ubuntu: Confirmed Bug description: santa_ | rbalint: hey while systemd 243 was available in eoan I still got one of "my" issues (udisks2 fails to install in a container) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1845314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
