There is a serial-port interface, but I don’t think it would be suited for this kind of usage, and it doesn’t allow read access to /run/udev/data/+dmi:id
anyway.
If you edit chromium’s generated apparmor profile as suggested in that other bug to allow read access to /run/udev/data/+dmi:id
, does it fix the problem?