Ubuntu
oxide-qt package

Browser won't open from inside a snap

Bug #1639947 reported by Michael Terry
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
oxide-qt (Ubuntu)
New
Undecided
Unassigned

Bug Description

"""
[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.

Revision history for this message
Olivier Tilloy (osomon) wrote :

This is the same problem as discussed in bug #1599234, so I’ll mark this one as duplicate.

@Michael: out of curiosity, in which context are you embedding oxide inside a snap? Note that the plan of record is to have oxide be part of the Qt/UITK snap in the future.

Revision history for this message
Michael Terry (mterry) wrote :

This was testing the unity8 desktop snap with a built-in webbrowser-app deb package.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.