-
-
Notifications
You must be signed in to change notification settings - Fork 488
Open
@AndKe
Description
Describe the problem
./arduino-ide_2.3.2_Linux_64bit.AppImage
[49662:0505/163801.040968: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_arduinl1RTCc/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap (core dumped)
To reproduce
Start Arduino IDE on a Ubuntu 24.04 machine.
Expected behavior
Work as normal.
Arduino IDE version
2.3.2
Operating system
Linux
Operating system version
Ubuntu 24.04
Additional context
The fault occurs with both the AppImage and ZIP packages of Arduino IDE.
Additional reports
- AppImage executable won't launch eclipse-theia/theia-ide#363 (comment)
- https://forum.arduino.cc/t/linux-install-issues/880034
- https://forum.arduino.cc/t/install-arduino-2-0/952428/4
- https://forum.arduino.cc/t/impossible-dinstaller-arduino-ide-v2-sur-debian-buster/1159541
- https://forum.arduino.cc/t/chrome-sandbox-error-in-ide-2-3-in-ubuntu-24-04/1247330/1
- https://forum.arduino.cc/t/chrome-sandbox-error-in-ide-2-3-in-ubuntu-24-04/1247330/2
- https://forum.arduino.cc/t/unable-to-install-2-3-2-on-kubuntu-24-04/1268893/1
- https://forum.arduino.cc/t/unable-to-install-2-3-2-on-kubuntu-24-04/1268893/4
- https://forum.arduino.cc/t/ide-under-ubuntu/1295528
- https://forum.arduino.cc/t/ide-launch-fails-sandbox-helper-binary-was-found-but-is-not-configured-correctly/1303643
- https://forum.arduino.cc/t/no-additional-boards-manager-urls-preference/1303646/3
- https://forum.arduino.cc/t/cant-install-2-3-3-on-ubuntu-24-04/1322047
- https://forum.arduino.cc/t/ide-2-x-dont-work-on-ubuntu-24-04lts/1335638
- https://forum.arduino.cc/t/sandbox-on-ubuntu-linux/1339925
- https://forum.arduino.cc/t/upgraded-linux-to-24-04-1-lts-how-to-restore-desktop-link/1351553
- https://forum.arduino.cc/t/ide-2-3-6-wont-run-on-xubuntu-4-18-linux-24-04-3-lts/1402679/3
Related
Issue checklist
- I searched for previous reports in the issue tracker
- I verified the problem still occurs when using the latest nightly build
- My report contains all necessary details