Public bug reported: Description: Ubuntu 20.04.4 LTS Release: 20.04
chromium 99.0.4844.51 1926 latest/stable canonical✓ I think with Chrome 99 manged policies in a json file are broken, they no longer seem to be picked up (used to work for me which a script I wrote). When one follows Chrome's documentation to use policies, it does not work: https://www.chromium.org/administrators/linux-quick-start/ If snap mutates various path's and changes various things, I hope this layer of obfuscation is documented somewhere? I could not find it. Similar to this issue but none of the paths in this issue work for me anymore: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1714244 I have tried many combos of dirs/permissions from stackoverflow and bug reports but they don't seem to work. I don't know what snap is doing to Chromium behind the scenes, and perhaps it seems undocumented? Apologies if it is documentented (but can't find it). ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- 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/1965188 Title: Policies not being picked up anymore Status in chromium-browser package in Ubuntu: New Bug description: Description: Ubuntu 20.04.4 LTS Release: 20.04 chromium 99.0.4844.51 1926 latest/stable canonical✓ I think with Chrome 99 manged policies in a json file are broken, they no longer seem to be picked up (used to work for me which a script I wrote). When one follows Chrome's documentation to use policies, it does not work: https://www.chromium.org/administrators/linux-quick- start/ If snap mutates various path's and changes various things, I hope this layer of obfuscation is documented somewhere? I could not find it. Similar to this issue but none of the paths in this issue work for me anymore: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1714244 I have tried many combos of dirs/permissions from stackoverflow and bug reports but they don't seem to work. I don't know what snap is doing to Chromium behind the scenes, and perhaps it seems undocumented? Apologies if it is documentented (but can't find it). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1965188/+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
