12/15/2023 0 Comments Hangouts extension not workingIn essence, the extension allows " /*" with access to do the following: All "enable_hangout_services_extension=true" does is include this code in Chromium. The code for the Hangout Services component extension lives in chrome/browser/resources/hangout_services/. > *isn't* a reason that outweighs that, then please enable this extension. > reason that outweighs that, it needs to be documented. > in a way they won't easily discover and can't easily fix". > it important to break people's ability to do screen sharing by default > At the very least, this needs an explanation commensurate with "why is *isn't* a reason that outweighs that, then please enable this extension. Reason that outweighs that, it needs to be documented. In a way they won't easily discover and can't easily fix". It important to break people's ability to do screen sharing by default But that's not the question at hand.Īt the very least, this needs an explanation commensurate with "why is That functionality indeed, there are more standard WebRTC features thatĬould work instead. I'm not suggesting that this extension is the ideal method to enable Having this enabled causes.what problem, precisely? Having this disabled breaks the ability to do screen sharing in Hangouts Rebuilding the Chromium package is not a viable path for most people,Įspecially since the package gets updated regularly. See debian bug #886358 for more information. > disabled, please edit debian/rules to enable it and rebuild the package > If you would like to use one of the upstream built-ins that are currently > directly in the browser and the two-factor authentication extension. > There are two exceptions, the pdfium extension for viewing pdf files This includes things like Google Hangouts, etc. > since users have stated concern about enabled features that they have not > The debian package disables most built-in upstream extensions by default Quoting the relevant section in its entirety: The new text in README.Debian does not answer any of these questions. > able to use the screen sharing extension with my colleges. > After re-compiling chromium with that extension enabled I was finally > * or is there some other technical reason to disable it in Debian? > * Does it make the package non-free/contrib > search nor looking in the Debian source package found any hint: > Can you at least clarify *why* that feature is disabled? Neither my web > Debian disables the shreen sharing extention in its build of chromium. > Sorry for re-opeing this bug, but it cost me some time to find that > export CHROMIUM_FLAGS="$CHROMIUM_FLAGS -enable-remote-extensions" > chromium, which will bypass this restriction. > * You can also use the -enable-remote-extensions command line argument to > package for an example of how to do this. > line option passed into CHROMIUM_FLAGS. > extensions that are explicitly specified with the -load-extension command > * External extensions are now disabled by default. > chromium-browser (.75-4) unstable urgency=medium * or is there some other technical reason to disable it in Debian?Īfter re-compiling chromium with that extension enabled I was finallyĪble to use the screen sharing extension with my colleges.Īlso (a different issue): NEW still contains this text: * Does it make the package non-free/contrib Search nor looking in the Debian source package found any hint: > it enabled in their version, the suggested patch is correct.Ĭan you at least clarify *why* that feature is disabled? Neither my web > This is the intended default configuration. Sorry for re-opeing this bug, but it cost me some time to find thatĭebian disables the shreen sharing extention in its build of chromium.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |