Public bug reported:
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:
Disabling apparmor for chromium
$ sudo ln -s /etc/apparmor.d/usr.bin.chromium-browser /etc/apparmor.d/disable/
$ sudo apparmor_parser -R /etc/apparmor.d/disable/usr.bin.chromium-browser
had no effect.
Adding "/dev/tty* rw" right below the line for "/dev/null rw" in
The output is shown. Please note that no additional lines show up when
I load the page that has that javascript code, or on clicking the button
that causes the connect attempt. All of that output is already there.
$ journalctl -f | grep chromium
Aug 05 15:21:33 slon dbus-daemon[1410]:
Also: it is chroME that is installed as a snap package, chroMIUM is
installed through apt-get, and it works just fine:
$ journalctl -f | grep chrome
Aug 05 15:26:57 slon dbus-daemon[782]: [system] Activating via systemd: service
name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.80'
Adding
@{PROC}/tty/drivers r,
to /var/lib/snapd/apparmor/profiles/snap.chromium.chromium did the trick.
The file actually had rwk permissions set to TTY*, and ACM* (mine is one
of those), according to the comments in the file.
There was no output in journalctl.
This can be considered a fix,
browser (Ubuntu)
> Status: Expired => New
>
--
---------
Edward Sternin, Physics Department, Brock U, St.Catharines, Ontario, L2S 3A1
http://www.physics.brocku.ca/People/Faculty/Sternin/
voice: (905)688-5550x3414
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
'''
$ snap connections chromium | grep usb
raw-usb chromium:raw-usb :raw-usb manual
$ journalctl -f | grep chromium
Nov 05 18:41:42 XX audit[80101]: AVC apparmor="DENIED" operation="open"
profile="snap.chromium.chromium" name="/proc/tty/drivers" pid=80101
Confirm resolved, after a system update, under snapd 2.49.1, the default
acees is "rwk" and WebUSB device access works.
Thanks, Olivier!
--
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:
