1. Forum
  2. FidoNet
  3. ALT.OS.LINUX.MAGEIA

  • NaCl Helper error message on slrn

    From William Unruh@2:250/1 to All on Fri Jul 31 05:21:42 2020
    Running slrn on Mageia 7. When I click on a web link which opens a
    browser window, I keep getting the error message (plastered across my
    slrn display
    :ERROR:nacl_helper_linux.cc(308)] NaCl helper process running without a sandbox!
    Most likely you need to configure your SUID sandbox correctly

    No idea what this means or how I would "configure my SUID sandbox"
    correctly or incorrectly.

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From William Unruh@2:250/1 to All on Fri Jul 31 05:51:36 2020
    On 2020-07-31, William Unruh <unruh@invalid.ca> wrote:
    Running slrn on Mageia 7. When I click on a web link which opens a
    browser window, I keep getting the error message (plastered across my
    slrn display
    :ERROR:nacl_helper_linux.cc(308)] NaCl helper process running without a sandbox!
    Most likely you need to configure your SUID sandbox correctly

    No idea what this means or how I would "configure my SUID sandbox"
    correctly or incorrectly.

    Just realised I did not say what browser-- google-chrome-stable-83.0.4103.116-1


    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Fri Jul 31 06:23:42 2020
    On Fri, 31 Jul 2020 00:51:36 -0400, William Unruh <unruh@invalid.ca> wrote:

    On 2020-07-31, William Unruh <unruh@invalid.ca> wrote:
    Running slrn on Mageia 7. When I click on a web link which opens a
    browser window, I keep getting the error message (plastered across my
    slrn display
    :ERROR:nacl_helper_linux.cc(308)] NaCl helper process running without a sandbox!
    Most likely you need to configure your SUID sandbox correctly

    No idea what this means or how I would "configure my SUID sandbox"
    correctly or incorrectly.

    Just realised I did not say what browser--
    google-chrome-stable-83.0.4103.116-1

    With chromium-browser-stable from the Mageia 7 repos ...
    $ ll /usr/lib64/chromium-browser/chrome-sandbox
    -rwsr-xr-x 1 root root 26408 May 8 21:09 /usr/lib64/chromium-browser/chrome-sandbox*

    Look for the equivalent file for google-chrome, and check it's permission settings,
    especially the s (setuid) for the user part, which can be fixed using chmod u+s on
    that file.

    Regards, Dave Hodgins

    --
    Change dwhodgins@nomail.afraid.org to davidwhodgins@teksavvy.com for
    email replies.

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From William Unruh@2:250/1 to All on Fri Jul 31 17:43:14 2020
    On 2020-07-31, David W. Hodgins <dwhodgins@nomail.afraid.org> wrote:
    On Fri, 31 Jul 2020 00:51:36 -0400, William Unruh <unruh@invalid.ca> wrote:

    On 2020-07-31, William Unruh <unruh@invalid.ca> wrote:
    Running slrn on Mageia 7. When I click on a web link which opens a
    browser window, I keep getting the error message (plastered across my
    slrn display
    :ERROR:nacl_helper_linux.cc(308)] NaCl helper process running without a sandbox!
    Most likely you need to configure your SUID sandbox correctly

    No idea what this means or how I would "configure my SUID sandbox"
    correctly or incorrectly.

    Just realised I did not say what browser-- google-chrome-stable-83.0.4103.116-1

    With chromium-browser-stable from the Mageia 7 repos ...
    $ ll /usr/lib64/chromium-browser/chrome-sandbox
    -rwsr-xr-x 1 root root 26408 May 8 21:09
    /usr/lib64/chromium-browser/chrome-sandbox*

    Look for the equivalent file for google-chrome, and check it's permission
    settings,
    especially the s (setuid) for the user part, which can be fixed using chmod
    u+s on
    that file.

    >ls -l /opt/google/chrome/chrome-sandbox
    -rwsr-xr-x 1 root root 228736 Jun 19 13:12 /opt/google/chrome/chrome-sandbox

    So it certainly seems to be OK.

    There is also another chrome-sandbox in
    >ls -l /usr/share/skypeforlinux/chrome-sandbox
    -rwxr-xr-x 1 root root 5581136 May 12 11:27 /usr/share/skypeforlinux/chrome-sandbox

    but surely that is not the one that is used since that directory is
    not in my PATH (but of course neither is /opt/google/chrome in PATH)



    Regards, Dave Hodgins


    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From root@2:250/1 to All on Fri Jul 31 19:38:50 2020
    ["Followup-To:" header set to alt.os.linux.]
    William Unruh <unruh@invalid.ca> wrote:
    On 2020-07-31, David W. Hodgins <dwhodgins@nomail.afraid.org> wrote:
    On Fri, 31 Jul 2020 00:51:36 -0400, William Unruh <unruh@invalid.ca> wrote: >>
    On 2020-07-31, William Unruh <unruh@invalid.ca> wrote:
    Running slrn on Mageia 7. When I click on a web link which opens a
    browser window, I keep getting the error message (plastered across my
    slrn display
    :ERROR:nacl_helper_linux.cc(308)] NaCl helper process running without a sandbox!
    Most likely you need to configure your SUID sandbox correctly

    No idea what this means or how I would "configure my SUID sandbox"
    correctly or incorrectly.

    Just realised I did not say what browser-- google-chrome-stable-83.0.4103.116-1

    With chromium-browser-stable from the Mageia 7 repos ...
    $ ll /usr/lib64/chromium-browser/chrome-sandbox
    -rwsr-xr-x 1 root root 26408 May 8 21:09 /usr/lib64/chromium-browser/chrome-sandbox*

    Look for the equivalent file for google-chrome, and check it's permission settings,
    especially the s (setuid) for the user part, which can be fixed using chmod u+s on
    that file.

    ls -l /opt/google/chrome/chrome-sandbox
    -rwsr-xr-x 1 root root 228736 Jun 19 13:12 /opt/google/chrome/chrome-sandbox

    So it certainly seems to be OK.

    There is also another chrome-sandbox in
    ls -l /usr/share/skypeforlinux/chrome-sandbox
    -rwxr-xr-x 1 root root 5581136 May 12 11:27
    /usr/share/skypeforlinux/chrome-sandbox

    but surely that is not the one that is used since that directory is
    not in my PATH (but of course neither is /opt/google/chrome in PATH)

    /usr/bin/google-chrome-stable should be in your path.
    In that file I add --no-sandbox to the exec statement.
    That shows a warning at chrome startup but thereafter
    chrome runs fine.





    Regards, Dave Hodgins


    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: Linux Advocacy (2:250/1@fidonet)