Chromium Xubuntu 16.04 does not work.
[8953:8953:0825/175333:FATAL:browser_main_loop.cc(221)] Running without the SUID sandbox! See https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the sandbox on.
#0 0x563566fb5cae <unknown>
#1 0x563566fc82db <unknown>
#2 0x56356940f8ff <unknown>
#3 0x5635692446dd <unknown>
#4 0x563569244296 <unknown>
#5 0x563566f862da <unknown>
#6 0x563566f85040 <unknown>
#7 0x563566ba8798 <unknown>
#8 0x7fd849fa4830 __libc_start_main
#9 0x563566ba8669 <unknown>
Aborted (core dumped)
Side note. This forum made a mess of trying to past this terminal output the hashes and the numbers confused the hell out of it, bold and not bold and impossible to disable either.
[quote=“Andrew_NZ, post:1, topic:51, full:true”] This forum made a mess of trying to past this terminal output the hashes and the numbers confused the hell out of it, bold and not bold and impossible to disable either.
For code, please use the
</> button in the editor to format text as code, then it doesn’t do that.
I can reproduce the issue on Ubuntu 16.04 with Chromium-51.0.2684.0-x86_64.AppImage. In contrast, the earlier version Chromium-50.0.2644.0-x86_64.AppImage works.
--disable-setuid-sandbox as an argument when launching Chromium-51.0.2684.0-x86_64.AppImage is a workaround until a better solution is found.
Thanks for the work around, apologies forgot about the code button.
Can you please provide the output of
Do you have any known kernel modifications going on?
The sandbox shouldn’t be required on 16.04 since the sandboxing is done at the kernel level now.
Just looked more into this on my end and here is the info…
This check was patched to not be needed on supported systems. It landed in commit revision
399361. However, due to some lag in committing it didn’t land in time for V51 which was built at commit rev
382149. So you need to manually use
--disable-setuid-sandbox until the v52 app image lands which should have the proper fix for kernel sandbox support in it.
Do NOT use
--no-sandbox, that disables all security sandboxing which will leave you open to attack. Use
--disable-setuid-sandbox until v52 lands with the fix internally.
Thanks Garbee for the clarification!