Hi guys, when Chromium starts, the first tab pops-up a warning:
Quote:
You are using an unsupported command-line flag: --no-sandbox. Stability and security will suffer.
None of my launchers has this flag set. Googling about for this warning gives some answers, most of them re. MSWin 7, including removing the flag from the command line of the launcher (none is set) and adjusting various options in about
:flags but none seem to be relevant.
However if I go to about
: in the address box, the following result shows up:
Code:
| Chromium |
24.0.1290.0 (Developer Build 160607) |
| OS |
Linux |
| WebKit |
537.13 (Unknown URL@0) |
| JavaScript |
V8 3.14.1.2 |
| Flash |
11.2 r202 |
| User Agent |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.13 (KHTML, like Gecko) Chrome/24.0.1290.0 Safari/537.13 SUSE/24.0.1290.0 |
| Command Line |
/usr/lib64/chromium/chromium --no-sandbox --password-store=kwallet --flag-switches-begin --enable-autologin --show-autofill-type-predictions --flag-switches-end |
| Executable Path |
/usr/lib64/chromium/chromium |
| Profile Path |
/home/stephen/.config/chromium/Default |
/usr/lib64/chromium/chromium
is a 'shared library' and I don't know to to change things within it.
In that directory /usr/lib64/chromium are two scripts, chromium-generic and chromium-kde, both of which mention this switch:
SUSE Paste SUSE Paste I don't know if these are relevant or even being used.
The above scripts have a line pointing to:
APPNAME=chromium
LIBDIR=/usr/lib64/chromium
GDB=/usr/bin/gdb
CHROME_SANDBOX=/usr/lib/chrome_sandbox
The is no such file/dir in /usr/lib/chrome_sandbox
And further down:
if [ ! -u $CHROME_SANDBOX ] ; then
SANDBOX="--no-sandbox"
fi
Should I create an empty file there? Or a directory?
Or should I boycott Google altogether as despite their 'don't be evil' motto they are are evading corporation tax in the UK.... ;)
No comments:
Post a Comment