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

Bug: AppImage Linux Ubuntu 24.04 LTS dosn't work #1567

Closed
2 tasks done
kpietrzyk opened this issue Jul 23, 2024 · 6 comments
Closed
2 tasks done

Bug: AppImage Linux Ubuntu 24.04 LTS dosn't work #1567

kpietrzyk opened this issue Jul 23, 2024 · 6 comments
Labels
bug Something isn't working

Comments

@kpietrzyk
Copy link

kpietrzyk commented Jul 23, 2024

Is this an issue specifically with Appium Inspector?

  • I have verified that my issue does not occur with Appium, and should be investigated as an Appium Inspector issue

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

after downloading and changing chmod of appimage i get this error:

[19889:0723/183728.430148: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 /tmp/.mount_Appium5UZNUQ/chrome-sandbox is owned by root and has mode 4755.

There is no chrome-sandbox in that location so there is no way to change it's owner.

Same error after extracting tar files and changing chrome-sandbox ownership and mode.

Expected Behavior

Run Appium Inspector from command line AppImage

Operating System

Linux

Appium Inspector Version

2024.6.1

Appium Version

2.11.2

Further Information

[19889:0723/183728.430148: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 /tmp/.mount_Appium5UZNUQ/chrome-sandbox is owned by root and has mode 4755.

./appium-inspector --no-sandbox returns that:
Screenshot from 2024-07-23 18-57-20

@kpietrzyk kpietrzyk added the bug Something isn't working label Jul 23, 2024
@eglitise
Copy link
Collaborator

I'm afraid we don't really have a Linux machine to test this ourselves, but I do have a few suggestions:

  • Are you using the version that matches your computer architecture? (x64 or arm64)
  • Does this error still appear on previous app versions? Note that if you're using arm64, support for it was only added in version 2024.3.4.

@mykola-mokhnach
Copy link
Contributor

@Samueru-sama
Copy link

This is because Ubuntu restricted access to userns with apparmor

Linux mint rolled back that change

While solus dropped apparmor and snap support

@kpietrzyk
Copy link
Author

Nice. Right after the fresh install, they made this kind of change :D Thank you for your support

I'm afraid we don't have a Linux machine to test this ourselves, but I do have a few suggestions:

* Are you using the version that matches your computer architecture? (x64 or arm64)

* Does this error still appear on previous app versions? Note that if you're using arm64, support was only added in version 2024.3.4.
  1. Yes. I'm running x64 app on AMD Ryzen 5 3600X CPU
  2. Yes. I tried to run previous version and the problem still occurred.

@Samueru-sama
Copy link

btw just in case there is no solution, if --no-sandbox doesn't work you will have to disable the restriction that ubuntu put in place.

sudo sysctl -w kernel.apparmor_restrict_unprivileged_unconfined=0
sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0

@eglitise
Copy link
Collaborator

Thanks for the info @Samueru-sama!
Closing this issue as it appears to affect all Electron apps and is not specific to the Inspector. Refer to electron/electron#41066 for more details.

@eglitise eglitise closed this as not planned Won't fix, can't repro, duplicate, stale Jul 26, 2024
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

4 participants