UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/56.0.2924.76 Chrome/56.0.2924.76 Safari/537.36

Steps to reproduce the problem:
Run Chromium as root today with following flags
CHROMIUM_FLAGS=--kiosk chromium-browser --kiosk --disable-pinch --app=http://localhost/kiosk --user-data-dir=/var/lib/ephone/.config/chromium --remote-debugging-port=9222 --kiosk --start-maximized --no-first-run --no-default-browser-check

What is the expected behavior?
show me the browser

What went wrong?
got message in popup instead "Please start Chromium as a normal user. If you need to run as root for development, re-run with the --no-sandbox flag"

Did this work before? Yes same version    56.0.2924.76

Does this work in other browsers? N/A

Chrome version: 56.0.2924.76  Channel: n/a
OS Version: 4.4.0-64
Flash Version: 

We make kiosks, and yes we run the browser as root. We have hundreds of installations and up until today they were all working fine.

Today we got a call from a customer complaining about this message. I restarted with new option and that fixed it. I then when to two other machines which were working and restarted chromium. Both now required this new switch. I don't know what is going on. The behaviour of a program should not be a function of the date, but it looks like this program simply decided that after today it wanted a new command line option to keep working. This is a disaster for me as there are hundreds of sites using this, and they are not even all accessible over the Internet. The next power failure will brickify them. Can some one please tell me what is going on here?

 

Deleted: Screenshot from 2017-03-03 10-53-27.png 37.8 KB

	Screenshot from 2017-03-03 10-53-27.png 37.8 KB View Download