[snap] Chromium USB enumeration fails when usbmon module is loaded
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Version:
chromium 87.0.4280.66 1411
Steps to reproduce:
1. Have Chromium snap, with raw-usb plug connected.
2. sudo modprobe usbmon.
3. Open Chromium and try to use a webpage that has webusb.
Result:
Chromium cannot see any USB devices on the system, regardless of whether it has raw-usb or not.
The following errors are printed on dmesg:
```
[3701471.283584] audit: type=1400 audit(160610184
[3701471.283636] audit: type=1400 audit(160610184
[3701471.283700] audit: type=1400 audit(160610184
[3701471.283786] audit: type=1400 audit(160610184
[3701471.283869] audit: type=1400 audit(160610184
[3701471.283982] audit: type=1400 audit(160610184
```
Chromium will then print this on stderr:
```
[3121487:
```
Why this happens:
Chromium enumerates USB devices by querying udev. Specifically by using udev_enumerate_
Impact:
There is no way for the user to know this error has occurred unless they happen to be watching dmesg or the stderr of Chromium (which requires they ran it from a terminal). Unless they check both of these places and realize that the error messages are connected, Chromium will just appear to behave as if there are no USB devices connected to the system at all. If the user does realize that usbmon is causing a problem, they must restart Chromium after unloading it, because it will not retry if enumeration ever fails.
description: | updated |
summary: |
- [snap] Chromium USB enumeration fails with usbmon module is loaded + [snap] Chromium USB enumeration fails when usbmon module is loaded |
tags: | added: snap |
Changed in chromium-browser (Ubuntu): | |
importance: | Undecided → Critical |
importance: | Critical → Medium |
This problem has got somewhat worse: now all webcam raw-usb udev nodes are owned by root. That means chromium raw-usb won't work if you have a webcam.
I think this is really a bug in chromium tbh.