Closed kpietrzyk closed 1 month ago
I'm afraid we don't really have a Linux machine to test this ourselves, but I do have a few suggestions:
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.
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
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 https://github.com/electron/electron/issues/41066 for more details.
Is this an issue specifically with Appium Inspector?
Is there an existing issue for this?
Current Behavior
after downloading and changing chmod of appimage i get this error:
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
./appium-inspector --no-sandbox returns that:![Screenshot from 2024-07-23 18-57-20](https://github.com/user-attachments/assets/d98aad2f-e51d-4a5c-bf8c-8f7dd3cd0268)