Question : Running without the SUID sandbox! - Chromium v52.0.2743.76

[Eric Zaluzec]

Hello, I have a quick question on where to look first with debugging the following problem :

I have built the chromium v52 (v52.0.2743.76) web browser to run on an embedded linux freescale imx7 with x11.

*Summarized - "When running chromium with --no-sandbox and --disable-setuid-sandbox, the chrome://settings page and all other pages return the, "Aw Snap! Something went wrong while displaying this webpage." How can I resolve this and get to a webpage just to do some quick html5 benchmark testing of hardware?

* Explanation -
Executing the /usr/bin/chromium/chrome binary outputs the message :

imx7dsabresd:/usr/bin/chromium$ ./chrome --args --allow-running-insecure-content --allow-insecure-localhost --window-size=800,480 --window-position=0,0 --incognito

[496:496:1219/072325:FATAL:browser_main_loop.cc(228)] Running without the SUID sandbox! See https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_dev  elopment.md for more information on developing with the sandbox on.
#0 0x0000551c2842 <unknown>
#1 0x0000551d1248 <unknown>
#2 0x0000570116ee <unknown>
#3 0x000056e9c5aa <unknown>
#4 0x000056e9c344 <unknown>
#5 0x0000551a4258 <unknown>
#6 0x0000551a2f06 <unknown>
#7 0x000054ee91ec ChromeMain
#8 0x00007610846a __libc_start_main
Aborted

-------------------------------------------
I changed permissions of sandbox and exported the following while running not as root:

chown root:root /usr/sbin/chrome-devel-sandbox

chmod 4755 /usr/sbin/chrome-devel-sandbox
export GOOGLE_API_KEY="no"
export GOOGLE_DEFAULT_CLIENT_ID="no"
export GOOGLE_DEFAULT_CLIENT_SECRET="no"
export CHROME_DEVEL_SANDBOX=/usr/sbin/chrome-devel-sandbox

-------------------------------------------
Adding the following chromium arguments does not change the error:

--allow-sandbox-debugging
--enable-sandbox


-------------------------------------------
When I add the following arguments, I get the chromium web browser to start-up, however, every page throws the "Aw, Snap! Something went wrong while displaying this webpage." Message. Even chrome://settings and chrome://gpu display this page.

--no-sandbox
--disable-setuid-sandbox

 ./chrome --args --allow-running-insecure-content --allow-insecure-localhost --window-size=800,480 --window-position=0,0 --disable-setuid-san
dbox --incognito
[624:624:1219/075256:ERROR:browser_main_loop.cc(231)] Running without the SUID sandbox! See https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_dev  elopment.md for more information on developing with the sandbox on.
[650:650:1219/075256:ERROR:gl_surface_glx.cc(381)] glxQueryVersion failed
[650:650:1219/075256:ERROR:gl_surface_x11.cc(252)] GLSurfaceGLX::InitializeOneOff failed.
[650:650:1219/075256:ERROR:gpu_child_thread.cc(369)] Exiting GPU process due to errors during initialization
[624:639:1219/075256:ERROR:browser_gpu_channel_host_factory.cc(119)] Failed to launch GPU process.
Received signal 4 <unknown> 000057fbac04
#0 0x000055264842 <unknown>
#1 0x000055264b04 <unknown>
#2 0x0000760ba020 <unknown>
#3 0x000057fbac04 <unknown>
#4 0x000055b68006 <unknown>
#5 0x000055b688f0 <unknown>
#6 0x000055b64e4a <unknown>
#7 0x000055b6526a <unknown>
#8 0x000056029e86 <unknown>
#9 0x000056022188 <unknown>
#10 0x00005602296c <unknown>
#11 0x000057543882 <unknown>
#12 0x000057544fa2 <unknown>
#13 0x00005753a680 <unknown>
#14 0x00005834be90 <unknown>
#15 0x00005594bc12 <unknown>
#16 0x0000552a8020 <unknown>
#17 0x0000583a61e8 <unknown>
#18 0x0000583a65cc <unknown>
#19 0x0000583a4d32 <unknown>
#20 0x0000552a8020 <unknown>
#21 0x0000552777ba <unknown>
#22 0x000055277e68 <unknown>
#23 0x000055278002 <unknown>
#24 0x000055278e20 <unknown>
#25 0x00005528767e <unknown>
#26 0x000055276e74 <unknown>
#27 0x0000575517e4 <unknown>
#28 0x000055245e72 <unknown>
#29 0x000055246258 <unknown>
#30 0x000055244f06 <unknown>
#31 0x000054f8b1ec ChromeMain
#32 0x0000760ab46a __libc_start_main
[end of stack trace]
[624:639:1219/075257:ERROR:browser_gpu_channel_host_factory.cc(119)] Failed to launch GPU process.
[624:639:1219/075257:ERROR:browser_gpu_channel_host_factory.cc(119)] Failed to launch GPU process.


-------------------------------------------
My next build cycle will add in the libgles & egl files to resolve the GPU errors, but how do I begin to debug the root cause of chrome not starting? Does it need to run with SUID sandbox? Is there a way that I confirm this is the root problem?

I am fine without running SUID sandbox, but I would like to visit a few web pages just to test the html5 performance of the hardware. Any tips on how to run with --disable-setuid-sandbox & -no-sandbox, but to resolve the 'Aw, Snap! Something went wrong while displaying this webpage' error? (even on the chrome://settings page).


Thanks for any help, tips, pointers or feedback anyone can provide.
-Eric Zaluzec

[Lei Zhang]

Hi Eric,

The error message you referred to in Chromium 52 no longer exists in
present day Chromium source code.

You did bypass the SUID sandbox issue. If you look closely at your
stack traces, you can see the second stack trace actually failed for a
different reason. Your chrome process received a signal 4 (SIGLL). As
to why that happened, you need to symbolize the stack trace somehow.

> --
> --
> Chromium Developers mailing list: chromi...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-dev