New issue
Advanced search Search tips

Issue 915865 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Jan 18
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Documentation misleading about policies (/etc/chromium-browser/policies)

Reported by marielin...@gmail.com, Dec 17

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.85 Safari/537.36 Vivaldi/2.2.1388.34

Steps to reproduce the problem:
On this page:
https://sites.google.com/a/chromium.org/dev/administrators/linux-quick-start?pli=1

It is mentionned that the policies should be stored in /etc/opt/chrome/policies/

while it should be in
/etc/chromium-browser/policies/

What is the expected behavior?

What went wrong?
With the described location, nothing is working :-)

Did this work before? N/A 

Chrome version: 71.0.3578.85  Channel: n/a
OS Version: 65
Flash Version: 

It should probably also be mentionned that on some distro, the folder is created by the packager (ubuntu, raspbian).

Thanks for completing this information...
 
Also same problem here: 
https://www.chromium.org/administrators/linux-quick-start

The specified location is /etc/opt/chrome/policies, which is also misleading...
Labels: Needs-Triage-M71
Cc: atwilson@chromium.org
Components: -Platform>DevTools Enterprise
Owner: dgozman@chromium.org
Status: Assigned (was: Unconfirmed)
Owner: ----
Status: Unconfirmed (was: Assigned)
Cc: -atwilson@chromium.org pastarmovj@chromium.org georgesak@chromium.org
Owner: privard@chromium.org
Assigning to chrome enterprise team to triage/figure out if some documentation update is reasonable - not sure if we can realistically document where every single linux chromium distribution pulls their policies from.
Putting a note saying that this folder is subject to change according to distribution should be a good hint :-)

Is there a way to get that information inside chromium? Preferences pages? starting it with a parameter (like --debug or something) ?
Status: Assigned (was: Unconfirmed)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.

Comment 9 by pastarmovj@chromium.org, Jan 18 (4 days ago)

Status: WontFix (was: Assigned)
This documentation although hosted in the chromium.org page (subject to change very soon) is specifically about the Chrome policy management and therefore talks about the location of policies for Google Chrome. Any other location is a custom decision of other Chromium clones. 

Sign in to add a comment