Tested with the Numworks calculator v0100, Ubuntu 19.10.

$ dpkg -l chromium-browser
...
ii  chromium-browser 77.0.3865.120-0ubuntu1.19.10.1 amd64        Transitional 
package - chromium-browser -> chromium snap
$ snap changes
ID   Status  Spawn               Ready               Summary
36   Done    today at 10:20 CET  today at 10:20 CET  Refresh "chromium" snap 
from "candidate/raw-usb-test" channel
$ snap interface raw-usb
name:    raw-usb
summary: allows raw access to all USB devices
slots:
  - core
$ sudo snap connect chromium:raw-usb
error: snap "chromium" has no plug named "raw-usb"

And without this connect, chrome://device-log/ says 'operation not permitted',
as designed.

At this point, the workaround of using chromium without a snap wrapper
seems no longer available.  The snap system knows something about raw-
usb, but the chromium snap from the raw-usb-test channel does not want
to connect to it.

Let me know when you want further testing.

-- 
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/1780678

Title:
  [snap] Chromium cannot use WebUSB

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  We're running into a weird bug on Ubuntu : WebUSB works on Chrome but
  doesn't on Chromium!

  Here's our udev rule:

  https://workshop.numworks.com/files/drivers/linux/50-numworks-
  calculator.rules

  It uses the uaccess tag which adds an ACL to the created file in /dev/
  so that the current logged-in user has RW access to the corresponding
  /dev/bus/usb/** device. Apparently that's the way to go, since relying
  on groups is fragile (not all distros use the "plugdev" group for
  example).

  That udev rules works just fine. When using a command-line utility
  such as "dfu-tool", the USB device is seen and can be read from and
  written to. It also works just fine on Chrome. But Chromium gives us
  an "access denied" error. It lists the device, we do get the pop-up,
  but we cannot communicate. On Chromium, chrome://device-log says :

  Failed to open /dev/bus/usb/001/011: Operation not permitted (1)

  Here are the infos on said file:

  user@virtualbox:~$ ls -l /dev/bus/usb/001/011
  crw-rw-r--+ 1 root root 189, 10 Jul  3 11:35 /dev/bus/usb/001/011

  As you can see, the file is owned root/root, but has an ACL (as shown
  by the "+" symbol)

  user@virtualbox:~$ getfacl /dev/bus/usb/001/011
  getfacl: Removing leading '/' from absolute path names
  # file: dev/bus/usb/001/011
  # owner: root
  # group: root
  user::rw-
  user:user:rw-
  group::rw-
  mask::rw-
  other::r--

  Here the ACL supposedely gives RW access to "user" who is indeed the
  current logged-in user, and the user running Chromium and Chrome.

  For reference :
   - Latest stable Ubuntu (18.04)
   - Using the Chromium that ships with Ubuntu (from the Ubuntu Software app. 
attached chrome://version page)
   - And using latest stable Chrome from google.com (attached chrome://version 
page)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1780678/+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

Reply via email to