Crashes on Ubuntu 24.04 due to permissions on /opt/Hyper/chrome-sandbox

• Ubuntu 24.04
• 3.4.1 and 4.0.0 canary 5 from deb
• https://gist.github.com/laidbackware/b4cefe9b20a1ef4cccea5a0cc1b82d71
• N/A
• **Open **

Issue

After upgrading from from Ubuntu 23.10 to 24.04 Hyper 3.4.1 started crashing on open with SIGTRAP in dlsym_doit(). I upgraded to 4.0.0 canary 5 and still the same problem.

Running in verbose mode from another terminal results a file permissions error, but .

➜ hyper -v
[28388:0428/111718.055728: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 /opt/Hyper/chrome-sandbox is owned by root and has mode 4755.

~/Downloads 
➜ ll /opt/Hyper/chrome-sandbox
-rwxr-xr-x 1 root root 52808 Jul 13  2023 /opt/Hyper/chrome-sandbox

This can be fixed by running the following chmod command to enable the setuid bit, which changes the user executable mode to s.

➜ sudo chmod 4755 /opt/Hyper/chrome-sandbox

➜ ll /opt/Hyper/chrome-sandbox
-rwsr-xr-x 1 root root 52536 Jan  7  2023 /opt/Hyper/chrome-sandbox

Removing and re-installing or upgrading the deb sets the permissions back to default which results in crashing again.

I'm not sure whether it's related, but sudo apt install ./<file>.deb generates the following error.

N: Download is performed unsandboxed as root, as file '/home/matt/Downloads/hyper_3.4.1_amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)

Issue also impacts the appimage.

➜ ./Hyper-4.0.0-canary.5-x86_64.AppImage 
[32189:0428/115238.921357: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 /tmp/.mount_Hyper-D928zV/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap (core dumped)

Reproduce the crash with the Debian package and AppImage, then inspect how /opt/Hyper/chrome-sandbox is installed and how its permissions are set. Done means a fresh install or upgrade preserves root ownership and mode 4755, allowing Hyper to start without the sandbox error.