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 Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Fix Released
--
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
The above PR was merged and should be part of the snapd 2.48 release.
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
I submitted https://github.com/snapcore/snapd/pull/9627 to add this to
the raw_usb interface.
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
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
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,
The denial on /proc/tty/drivers looks relevant.
Can you try the following?
- close chromium
- edit (with sudo)
/var/lib/snapd/apparmor/profiles/snap.chromium.chromium, add the
following line to the profile:
@{PROC}/tty/drivers r,
- reload the apparmor profile with: "sudo
'''
$ 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
That's right, snaps run sandboxed, so what matters is not device access
on the host, but what the snapd sandbox allows. Strictly speaking this
is not an Ubuntu-specific bug, because snaps run on other linux
distributions. This is definitely a snap-specific issue, which won't
affect the version of
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
A relevant denial from comment #2 is:
AVC apparmor="DENIED" operation="open"
profile="snap.chromium.chromium" name="/run/udev/data/c166:0" pid=2802
requested_mask="r" denied_mask="r"
That should be allowed by connecting the raw-usb interface though.
Could you please ensure that said
Made no difference. Tried before or after launching the browser.
By the way, this bug is not there in edge. Only Chromium.
On 10/30/20 12:27 PM, Olivier Tilloy wrote:
> Does the following help?
>
> sudo snap connect chromium:raw-usb
>
> ** Changed in: chromium-browser (Ubuntu)
>
Does the following help?
sudo snap connect chromium:raw-usb
** Changed in: chromium-browser (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
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
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'
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]:
17 matches
Mail list logo
