Auto-connecting the camera interface for the chromium snap


#1

This is a request to auto-connect the camera interface for the chromium snap.

It is a pretty common use-case to do video-conferencing or other webrtc-based applications within browsers these days, and without the camera interface the chromium snap will report that no webcam can be found, which will lead users to report bugs because they want this feature to work out of the box.

Besides, chromium prompts for permission to allow camera capture on a per-domain basis, so that’s an additional level of security for actual access to the hardware.


Auto-connecting the cups-control and password-manager-service interfaces for the chromium snap
#2

+1 for autoconnection. There is an immediate need, this is from a trusted publisher and the code in question (chromium) provides contextual prompting for camera access.


#3

Apologies for the delay. +1 from me too.


#4

Chromium has additional prompts regarding the camera being requested so that is a +1 from me. It would probably be sensible to auto-connect cups-control too, so that printing is seamlessly available.

What about network-manager? It has a Plug for network-manager but it requires manual connection.


#5

Chromium has a geolocation provider that uses the NetworkManager DBus interface to list the WiFi access points (https://cs.chromium.org/chromium/src/device/geolocation/wifi_data_provider_linux.cc).

It looks fine to me to not have that plug auto-connected, what do others think?


#6

Can you please also consider granting auto-connection for the following interfaces:

  • password-manager-service (without this chromium will store passwords in plain text, see bug #1755463)
  • cups-control

#7

3 votes for, 0 against for camera. This is now live.

@oSoMoN - since this topic is for camera and it was already voted on, can you create another topic for cups-control and password-manager-service?


#8

Done, thanks @jdstrand.