Whalebird - fails to run due to sandbox issue

snap
1

I’ve been using Whalebird for my Mastodon access, and its great.

Sadly this week, it’s now falling over when it’s run. When I run it from bash I’m getting the error message below. I’m thinking there is a regression in (I’m assuming the lastest version) v2.7.2.

Is there a workaround that I can do that won’t compromise the sandboxing for the app, in the interim? Otherwise I’ll wait for the dev to fix it in due course.

[11218:0526/153620.060400: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/whalebird/56/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap (core dumped)

Permissions readout from ls -l:
-rwxr-xr-x 1 root root 5185424 May 20 15:22 chrome-sandbox

1 Like
2

Quick update. New release v2.7.3 (released today) works OK so far, and I’m back in business.

I did have a look at Whalebird’s GitHub page, and from I read from it that was an issue with Electron. It was a bit of learning experience in any case. Just happy its working. :slight_smile:

1 Like