-
Notifications
You must be signed in to change notification settings - Fork 331
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
buttercup-desktop AppImage complains about sandbox issue on lubuntu 24.04 LTS #1355
Comments
I am on Ubuntu 24.04 aswell. Buttercup can be started and seems to be fully operational by starting it with the --no-sandbox parameter. |
cool, this indeed works. But now I run into the next problem which is specified in an issue from somebody else last week titled something like ".... Authentification for Google drive fails" In the original thread is no solution yet. Should I post a message there? thx, P.S.: Buttercup is awesome!!!! |
@Samueru-sama Do you know if there's any action for us to take or is this something that the OS maintainers have to handle? |
@aikiks Best to take that to a proper issue, I believe there's one floating around. Logs will be required for debugging to be possible. |
One option is to add This is something that ubuntu has to fix, maybe you could put instructions on how to disable the restriction, or maybe something using pkexec and zenity that will disable the restriction when agreed by the user, it is really bad that projects are being put on this position to fix ubuntu's issues. |
Hi,
when I try to start buttercup from the Appimage I get the following error message.
~/Downloads/AppImages$ ./Buttercup-linux-x86_64.AppImage
[60849:0717/111256.607000: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_ButterrbXRkS/chrome-sandbox is owned by root and has mode 4755.
Trace/Breakpoint ausgelöst (Speicherabzug geschrieben)
How can I solve this issue?
Thanks,
Karl
The text was updated successfully, but these errors were encountered: