[snap] No voice typing at google docs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
The voice typing feature of google docs is a online speech-to-text converter. It can be found on any google docs document under Toosl>Voice Typing and it only runs with Chrome or Chromium.
However while I can use this feature using the google chromium.deb build. I cdoesn't work on the chromium snap. Instead the browser constantly opens and closes the access to the microphone, resulting in a flickering microphone icon in the top right of the screen.
The fact that this works with the .deb but not with the snap make me think it is a snap related issue.
$ lsb_release -rd
Description: Ubuntu 20.04.1 LTS
Release: 20.04
$ apt-cache policy chromium-browser
chromium-browser:
Installed: (none)
Candidate: 1:85.0.
Version table:
1:
500 http://
80.
500 http://
$ apt-cache policy google-
google-
Installed: 85.0.4183.102-1
Candidate: 85.0.4183.102-1
Version table:
*** 85.0.4183.102-1 100
100 /var/lib/
summary: |
- No voice typing with chromium snap at google docs + [snap] No voice typing at google docs |
affects: | chromium (Ubuntu) → chromium-browser (Ubuntu) |
I can confirm the exact same behavior.
Google docs "Voice typing" constantly opens and closes the access to the microphone while other websites (like `https:/ /www.onlinemict est.com/`) work normally.
When looking at the sound settings while activating voice typing, I can see that the entry which flickr is called "Chromium input".
Note that activating the mic on `onlinemictest.com` create *two* consistent entries: "Chromium" and "Chromium input".
The major difference I've with OP is that I'm having the problem with both:
* Chromium 84.0.4147.135 built on Ubuntu focal/20.04, running on Ubuntu focal/20.04
from ungoogled-chromium (opensuse.org)
* Chromium 86.0.4240.75 snap
directly from Google using Ubuntu apt trust-proxy.
So I'd say snap is not at cause here ([r]which does not take anything to the fact that misusing snap concept to provide Google's opaque-binaries instead of a deb built from sourcecode is still insane[/r])