vercel / vercel/hyper

couldn't start Hyper 3.4.1: `FATAL:setuid_sandbox_host.cc`

Open
#8,097 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
44.7k
Forks
3.6k
Avg merge
21m
Merged PRs (30d)
1

Description

  • I am on the latest Hyper.app version
  • I have searched the issues of this repo and believe that this is not a duplicate

Issue

couldn't start Hyper-3.4.1.AppImage from terminal, got error:

[4348:0521/211822.779171: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-lWQyci/chrome-sandbox is owned by root and has mode 4755.
fish: Job 1, './Hyper-3.4.1.AppImage' terminated by signal SIGTRAP (Trace or breakpoint trap)

It has been working fine for a while and suddenly I couldn't start it. Can someone help me out of this?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing Hyper-3.4.1.AppImage on Ubuntu 24.04.2 and inspect the chrome-sandbox path and permissions shown in the fatal error. Review the AppImage startup and packaging configuration, using the linked hyper.json as context. Done means the packaged app starts without the setuid sandbox failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.