-
Notifications
You must be signed in to change notification settings - Fork 1
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
Symlink error when running simulation example #49
Comments
@rdlynx19 After a quick look, it might be because the Check if it is writable with this: ls -ld /tmp You should see something like this: If not, fix it with: sudo chmod 1777 /tmp Also, check for leftover PX4 lock files in ls -l /tmp/px4_lock-* If any exist, remove them (ensure no other PX4 instances are running): sudo rm /tmp/px4_lock-* It’s recommended not to run PX4 SITL with make px4_sitl gz_x500 If the issue persists, clean and rebuild the project: make clean
make px4_sitl_default
make px4_sitl gz_x500 Finally, ensure your user has proper ownership of the PX4 directory: sudo chown -R $USER:$USER /home/ros/PX4-Autopilot Let me know if this resolves your issue! |
Hi @edouardrolland
and it returns me an output similar to the one you mentioned. Running I am unable to clean the project, on running
Lastly, trying to change the ownership does not return anything
I think bash gets stuck in some way. |
Hello,
I followed the instructions on the README to setup the docker container in VS Code. After building and opening the container in VS Code, when I run the test commands:
I get the following error in the VS Code terminal:
I tried running the command as
sudo
but it still does not work.I would appreciate your help in solving this issue.
The text was updated successfully, but these errors were encountered: