Author |
Message |
ZaneZimer
Joined: 2016-06-19 21:33:37 Posts: 342 Location: Columbus area, OH, USA
|
I'm on a Linux rig, running Fedora 22 (32 bit/PAE/nvidia) and when I launch Cool VL Viewer a stack trace is generated and I fail to get web content. I do not know if this is because of my particular set up or perhaps a missing dependency. Searching for bits of the trace output, Google reveals that others are fixing this error in Chromium by passing a command line argument to disable the sandbox (--no-sandbox). Given that the CEF plugin is a lib, I suspect this will not work. My version information is below. Any thoughts?
|
2016-06-19 21:46:10 |
|
|
Henri Beauchamp
Joined: 2009-03-17 18:42:51 Posts: 5550
|
Not sure why the sandbox fails on your particular system (missing system-wide certificates or libraries ?): remember to check your system libraries dependencies with (from a terminal opened in the installation directory of the viewer): If it's not a missing library issue, you may disable the sandbox altogether by editing the cool_vl_viewer script around line 140 and change the: lines for: You might also want to try and build the viewer from sources (which should prove quite easy under Linux, see the doc/LinuxBuildHowto.txt file in the sources tree) and see if it solves that issue.
|
2016-06-19 22:08:49 |
|
|
ZaneZimer
Joined: 2016-06-19 21:33:37 Posts: 342 Location: Columbus area, OH, USA
|
Ensuring that the env variable is blank in the start up script allows the viewer to start up properly. I'll give the source a look and see about building locally because I'm curious why it might be failing for me.
Thanks, ZZ
|
2016-06-19 22:51:33 |
|
|
ZaneZimer
Joined: 2016-06-19 21:33:37 Posts: 342 Location: Columbus area, OH, USA
|
I have tried to build the project, but alas, it fails to build the chrome_sandbox with various errors like: I did some more digging and it may not even be required based on: https://bugs.chromium.org/p/chromium/issues/detail?id=598454For now, I'll just run with a modified start up script as that seems to allow me to run properly. ZZ
|
2016-06-20 15:50:10 |
|
|
Henri Beauchamp
Joined: 2009-03-17 18:42:51 Posts: 5550
|
Please, do read the doc/LinuxBuildHowto.txt file: the viewer shall be built with gcc, not with llvm/clang... Yes, that sandbox stuff is pretty silly anyway... It could be useful when the viewer is ran as root, but in that case the sandbox doesn't work either...
|
2016-06-20 16:58:53 |
|
|
ZaneZimer
Joined: 2016-06-19 21:33:37 Posts: 342 Location: Columbus area, OH, USA
|
And of course in my testing, I thought the change to the launcher script worked. It does not. I had set the viewer to use webkit at one point and obviously forgot. So even with the script alteration, I get the stack trace, CEF still doesn't work and there is a new error: Heh, and I misunderstood. You meant build Cool VL Viewer. I had been trying to build just CEF. ZZ
|
2016-06-20 17:45:17 |
|
|
Henri Beauchamp
Joined: 2009-03-17 18:42:51 Posts: 5550
|
I'm afraid we will have to wait for that sandbox stuff to be deprecated then... In the mean time, you should be able to run the viewer with CEF3 from a root session... As for rebuilding CEF3 yourself... Well... Good luck. The instructions are here. Not sure it would accept to build without a sandbox either... EDIT: does your distro's kernel use SELinux extensions ? If yes, it could explain it refuses to escalate the privileges of the plugin via the sandbox...
|
2016-06-20 18:18:17 |
|
|
ZaneZimer
Joined: 2016-06-19 21:33:37 Posts: 342 Location: Columbus area, OH, USA
|
Well even if I successfuly built CEF, I am thinking I couldn't just drop it in Cool VL Viewer anyway. Now that I think a bit more, I a guessing you build it against a specific release of CEF.
Fedora does use SELinux which I have set to permissive. I do not get any warnings of violations when I run the viewer. That was one of my first thoughts. I may be missing something else though.
|
2016-06-20 18:49:30 |
|
|
Henri Beauchamp
Joined: 2009-03-17 18:42:51 Posts: 5550
|
Yes, the one quoted in the "recipe" file. You'll also have to rebuild the llceflib library, using your new CEF3 build, and the plugin itself, using the newly built llceflib library... The SELinux stuff might be worth investigating (not using any such kernel myself, so I won't be able to help you on that). Did you try a Chromium browser of the same version as the CEF3 plugin ?... I would guess it's sandboxed too, and should show the same issue (or have a workaround for it)...
|
2016-06-20 19:15:04 |
|
|
Henri Beauchamp
Joined: 2009-03-17 18:42:51 Posts: 5550
|
Please, verify that the "chrome-sandbox" binary (in bin/llplugin/) is set UUID root ('chmod +s chrome-sandbox', from a root terminal): the SUUID bit might have been reset at installation time, if you didn't install the viewer as root...
Also, in today's releases, I used a patched CEF3 plugin version that does allow to disable the sandbox for the non-root users (with the same 'export CHROME_DEVEL_SANDBOX=""' trick in the wrapper script as the one you already tried: this time however, it should work).
|
2016-07-09 12:40:06 |
|
|