Public bug reported:
"""
[1107/151029:FATAL:setuid_sandbox_host.cc(157)] 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/unity8-session/x13/usr/lib/x86_64-linux-gnu/oxide-qt/chrome-sandbox is
owned by root and has mode 4755.
"""
$ ls -l
/snap/unity8-session/x13/usr/lib/x86_64-linux-gnu/oxide-qt/chrome-sandbox
-rwxr-xr-x 1 root root 18664 Nov 3 15:43
/snap/unity8-session/x13/usr/lib/x86_64-linux-gnu/oxide-qt/chrome-sandbox
So seems like either Snappy needs to allow 4755 or oxide needs to relax
its requirements.
** Affects: oxide-qt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639947
Title:
Browser won't open from inside a snap
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/oxide-qt/+bug/1639947/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
