Are the other policies still being applied?  If so, this would be a functional issue rather than a security bug per-se.

There are no other policies/policy files in use other than the one I have placed under /etc/opt/chrome/policies/managed.  I am using Openbox, running the browser from /home/<user>/.config/openbox/menu.xml:

-----------------------------------------------------

 <item label="Web browser">
    <action name="Execute"><execute>google-chrome --start-maximized --no-first-run</execute></action>
  </item>

-----------------------------------------------------

...and from /home/<user>/.config/openbox/autostart:

-----------------------------------------------------

google-chrome --start-maximized --no-first-run

-----------------------------------------------------

I have this configuration working on 21 other machines, Chrome installed from the same sources.  I have also verified the permissions on the file/path compared to the boxes that work.  I dunno if I'm doing something wrong, somewhere but at this point I'm stumped.  What other info can I provide?

Thanks for your help!

Marking as functional and removing restrictions.

is there a status on this by chance?

This is a known issue and should be fixed now. Please restart your chrome stable#60.0.3112.90/60.0.3112.101 browser to make it work. The respective server side change has been rolled back.

Thank you!

Well, this is still broken for non-Enterprise browser users like us. Is there a json policy syntax workaround?

This is till broken in linux after updating to 60.0.3112.113-1.  Per https://www.chromium.org/administrators/linux-quick-start I set up the most basic json policy file with the code:

{
  "HomepageLocation": "www.chromium.org"
}

The browser does not behave as expected.

This is till broken in linux after updating to 60.0.3112.113-1.  Per https://www.chromium.org/administrators/linux-quick-start I set up the most basic json policy file with the code:

{
  "HomepageLocation": "www.chromium.org"
}

The browser does not behave as expected.

This is a different bug from 755256 (the one was just about url blacklist/whitelists not working and the experiment is now disabled in m60)

Status check?

Status check?

Hey Thiemo, would you know anything about the .json policy files? I vaguely remember something about that.

Ivan, the link in the original report explains it. Do you have a specific question?

Status check?

Status check? We are rolling out more kiosk machines using Ubuntu 18.04LTS and would really like this fixed please.