Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tar.gz release requires --no-sandbox to run #588

Open
CaviaPorcellus opened this issue May 27, 2024 · 2 comments
Open

Tar.gz release requires --no-sandbox to run #588

CaviaPorcellus opened this issue May 27, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@CaviaPorcellus
Copy link

CaviaPorcellus commented May 27, 2024

Describe the bug
The program does not run without adding the --no-sandbox flag.

To Reproduce
Steps to reproduce the behavior:

  1. Attempt to start the program.
  2. Nothing happens.

Expected behavior
The program should run without the --no-sandbox flag.

Desktop (please complete the following information):

  • Program version: 2.5.0
  • Asset Pack version: v2
  • OS: Kubuntu 24.04

Additional context
The program used to run fine as-is (i.e., without the --no-sandbox flag). I recently upgraded from Kubuntu 23.10 (where it worked fine) to Kubuntu 24.04, so I assume something changed. With the flag it runs as normal.

Without the --no-sandbox flag, I receive this error when running it in a terminal:
./unofficial-homestuck-collection [7687:0527/135327.956679:FATAL:setuid_sandbox_host.cc(158)] 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 /blahblahblah/oldunofficial-homestuck-collection-2.0.7/chrome-sandbox is owned by root and has mode 4755. Trace/breakpoint trap (core dumped)

@CaviaPorcellus CaviaPorcellus added the bug Something isn't working label May 27, 2024
@BurningButter
Copy link

I'm experiencing the same issue

@PoroCYon
Copy link

PoroCYon commented Oct 18, 2024

Same here (2.5.6, Void Linux, swaywm). Before exiting (without supplying the --no-sandbox flag), these lines are printed:

[35994:1018/230914.217156:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye.
Trace/breakpoint trap

(A few warnings show up as well, but those also appear when supplying --no-sandbox so are probably not causing anything bad.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants