[Desktop-packages] [Bug 1890939] Re: [snap] The SUID sandbox helper binary was found, but is not configured correctly.

2020-08-25 Thread Olivier Tilloy
That's suspicious, can you please share the output of `ls -l
/snap/chromium/current/usr/lib/chromium-browser/chrome-sandbox` ?

Is the latest update (revision 1269) similarly affected?

** Changed in: chromium-browser (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1890939

Title:
  [snap] The SUID sandbox helper binary was found, but is not configured
  correctly.

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  The chromium snap version 1260 has the wrong mode for chrome-sandbox,
  as it happened also in bug #1854091:

  ```
  $ /snap/bin/chromium
  [4009:4009:0809/115259.781182:FATAL:setuid_sandbox_host.cc(158)] The SUID 
sandbox helper binary was found, but is not configured correctly. Rather than 
run without sandboxing I'm aborting now. You need to make sure that 
/snap/chromium/1260/usr/lib/chromium-browser/chrome-sandbox is owned by root 
and has mode 4755.
  Trace/breakpoint trap
  $ [4134:4134:0100/00.834554:ERROR:zygote_linux.cc(653)] write: Broken 
pipe (32)
  ```

  I have reverted it to the previous version (1244) and this one works
  (and has the right mode for chromium-sandbox).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1890939/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1890939] Re: [snap] The SUID sandbox helper binary was found, but is not configured correctly.

2020-08-30 Thread Alex Muntada
The current version (1284) works OK and the SUID bits are back:

```
$ ls -l /snap/chromium/current/usr/lib/chromium-browser/chrome-sandbox
-r-sr-xr-x 1 root root 333952 Aug 29 14:43 
/snap/chromium/current/usr/lib/chromium-browser/chrome-sandbox
$ snap info chromium
name:  chromium
summary:   Chromium web browser, open-source version of Chrome
publisher: Canonical✓
store-url: https://snapcraft.io/chromium
contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
license:   unset
description: |
  An open-source browser project that aims to build a safer, faster, and more 
stable way for all
  Internet users to experience the web.
commands:
  - chromium.chromedriver
  - chromium
snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
tracking: latest/stable
refresh-date: today at 09:06 CEST
channels:
  latest/stable:85.0.4183.83 2020-08-29 (1284) 169MB -
  latest/candidate: 85.0.4183.83 2020-08-29 (1284) 169MB -
  latest/beta:  85.0.4183.76 2020-08-24 (1271) 167MB -
  latest/edge:  86.0.4240.8  2020-08-27 (1278) 168MB -
installed:  85.0.4183.83(1284) 169MB -
```

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1890939

Title:
  [snap] The SUID sandbox helper binary was found, but is not configured
  correctly.

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  The chromium snap version 1260 has the wrong mode for chrome-sandbox,
  as it happened also in bug #1854091:

  ```
  $ /snap/bin/chromium
  [4009:4009:0809/115259.781182:FATAL:setuid_sandbox_host.cc(158)] The SUID 
sandbox helper binary was found, but is not configured correctly. Rather than 
run without sandboxing I'm aborting now. You need to make sure that 
/snap/chromium/1260/usr/lib/chromium-browser/chrome-sandbox is owned by root 
and has mode 4755.
  Trace/breakpoint trap
  $ [4134:4134:0100/00.834554:ERROR:zygote_linux.cc(653)] write: Broken 
pipe (32)
  ```

  I have reverted it to the previous version (1244) and this one works
  (and has the right mode for chromium-sandbox).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1890939/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1890939] Re: [snap] The SUID sandbox helper binary was found, but is not configured correctly.

2020-08-30 Thread Olivier Tilloy
Thanks for following up!

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1890939

Title:
  [snap] The SUID sandbox helper binary was found, but is not configured
  correctly.

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  The chromium snap version 1260 has the wrong mode for chrome-sandbox,
  as it happened also in bug #1854091:

  ```
  $ /snap/bin/chromium
  [4009:4009:0809/115259.781182:FATAL:setuid_sandbox_host.cc(158)] The SUID 
sandbox helper binary was found, but is not configured correctly. Rather than 
run without sandboxing I'm aborting now. You need to make sure that 
/snap/chromium/1260/usr/lib/chromium-browser/chrome-sandbox is owned by root 
and has mode 4755.
  Trace/breakpoint trap
  $ [4134:4134:0100/00.834554:ERROR:zygote_linux.cc(653)] write: Broken 
pipe (32)
  ```

  I have reverted it to the previous version (1244) and this one works
  (and has the right mode for chromium-sandbox).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1890939/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp