I'm glad that this solved the issue!
Please note that the next time the chromium snap is refreshed, the
apparmor profile will be re-generated, so you will lose this
modification, and will have to re-apply it. So that's not a good long-
term workaround.
I will work with the snapd team to have this included in the raw_usb
interface.
** Changed in: chromium-browser (Ubuntu)
Status: New => Triaged
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1890365
Title:
[snap] Web Serial fails to access local device
Status in chromium-browser package in Ubuntu:
Triaged
Bug description:
A javascript-based web page works fine when accessed through Chrome,
fails to recognize that any devices exist when accessed from Chromium
on the same Unubtu 20.04 platform.
The code includes the following snippet:
const requestOptions = {
filters: [{ usbVendorId: 0x1881 }]
};
port = await navigator.serial.requestPort(requestOptions);
await port.open({ baudrate: 9600 });
writer = port.writable.getWriter();
reader = port.readable.getReader();
Under Chrome 84.0.4147.105 (Official Build) (64-bit), ttyACM0 device
is listed in the pop-up, is selectable, and can communicate. Under
Chromium 84.0.4147.105 (Official Build) snap (64-bit), the pop-up
contains only "No compatible devices found" message.
Experimental Web Features flag is enabled in both browsers.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1890365/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
