I do not understand your comment, perhaps because I do not understand snap.
/etc/udev/rules.d for this device configure it to be 666, and it works fine under other browsers, so you are not talking about actual device access, you are talking about the mapping of this real device onto some virtual "raw-usb" device of the snap's sandbox ? I did what you suggested, tried from the command line before and after launching chromium. I had previously also turned off apparmor for chromium altogether (comment #4). None of these affected the outcome. So, please explain how I "ensure that said interface is connected" for the purposes of the snap sandbox. I can use chromium successfully for accessing the device under RedHat, so this is specifically a Ubuntu/Chromium bug/misfeature. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890365 Title: [snap] Web Serial fails to access local device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1890365/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
