I'm guessing this is caused by Chromium's use of udev for device enumeration. Gamepad API on Linux uses udev to enumerate devices in the joydev, evdev, and hidraw subsystems.
"Unfortunately we're mostly stuck like this for now, since Chromium expects to read devices from udev, which cannot be directly exposed into the sandbox due to having an unstable ABI."
As noted up-thread, there's a flatpak workaround that involves configuring the udev filesystem to be read-only.
I'd like to fix this by removing Chromium's dependency on udev. Is there an alternative that plays nicely with snap/flatpak sandboxing?
Hi, I found this bug while investigating the Chromium bug https:/ /crbug. com/1359677
I'm guessing this is caused by Chromium's use of udev for device enumeration. Gamepad API on Linux uses udev to enumerate devices in the joydev, evdev, and hidraw subsystems.
flatpak has a similar problem: https:/ /github. com/flathub/ org.chromium. Chromium/ issues/ 40
"Unfortunately we're mostly stuck like this for now, since Chromium expects to read devices from udev, which cannot be directly exposed into the sandbox due to having an unstable ABI."
As noted up-thread, there's a flatpak workaround that involves configuring the udev filesystem to be read-only.
I'd like to fix this by removing Chromium's dependency on udev. Is there an alternative that plays nicely with snap/flatpak sandboxing?