If Wavebox fails to launch on Linux and running from the terminal produces an error similar to the following...

FATAL:zygote_host_impl_linux.cc(116)] No usable sandbox! Update your kernel

...this indicates that you're using a Kernel that doesn't support some sandboxing features that Wavebox 10 turns on by default. This is normally on Linux Kernels older than 3.5. If you migrated from Wavebox Classic, this may be a new issue with Wavebox 10 as it has hardened security features over Wavebox 4, user-space sandboxing being one of those.

The recommended advice is to update to a newer Kernel, but if you're unable to do this, there are some alternative solutions you can use.

Run Wavebox with sandboxing disabled

You can run Wavebox with the --no-sandbox flag.

  1. To run on a one-off basis, run /opt/wavebox.io/wavebox/wavebox-launcher --no-sandbox
  2. To always run with sandboxing disabled, edit the Wavebox desktop file in /usr/share/applications/wavebox.desktop by adding the --no-sandbox flag to the exec command...
- Exec=/opt/wavebox.io/wavebox/wavebox-launcher %U
+ Exec=/opt/wavebox.io/wavebox/wavebox-launcher --no-sandbox %U

Enable user namespaces on your Kernel

The sandboxing that Wavebox uses, requires the user namespaces features in the Kernel. Some Kernels have this feature compiled in, but don't enable it by default. (Debian Stretch for example). You can enable this across your system by using the following commands...

echo 'kernel.unprivileged_userns_clone=1' > /etc/sysctl.d/00-local-userns.conf
service procps restart