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] Issue in gazebo opening after running "make" #23809

Open
NaShoval opened this issue Oct 14, 2024 · 3 comments · May be fixed by #24164
Open

[Bug] Issue in gazebo opening after running "make" #23809

NaShoval opened this issue Oct 14, 2024 · 3 comments · May be fixed by #24164

Comments

@NaShoval
Copy link

Describe the bug

When I run "make" in the PX4's directory, my gazebo does not initialise automatically.
When I manually initialise it, and than closing the gazebo window - the first window (that I expected PX4 to open), suddenly appears.
I just update to ubuntu 24.04 and did not have this issue until now..

To Reproduce

No response

Expected behavior

No response

Screenshot / Media

No response

Flight Log

make px4_sitl gz_advanced_plane
[0/1] cd /home/hawk/GitDir/PX4-Autopilot/build/px4_sitl_default/src/modules/simulation/gz_br...4_SIM_MODEL=gz_advanced_plane /home/hawk/GitDir/PX4-Autopilot/build/px4_sitl_default/bin/px4

______  __   __    ___ 
| ___ \ \ \ / /   /   |
| |_/ /  \ V /   / /| |
|  __/   /   \  / /_| |
| |     / /^\ \ \___  |
\_|     \/   \/     |_/

px4 starting.

INFO  [px4] startup script: /bin/sh etc/init.d-posix/rcS 0
INFO  [init] found model autostart file as SYS_AUTOSTART=4008
INFO  [param] selected parameter default file parameters.bson
INFO  [param] importing from 'parameters.bson'
INFO  [parameters] BSON document size 460 bytes, decoded 460 bytes (INT32:18, FLOAT:5)
INFO  [param] selected parameter backup file parameters_backup.bson
INFO  [dataman] data manager file './dataman' size is 7872608 bytes
INFO  [init] Gazebo simulator
INFO  [init] starting gazebo with world: /home/hawk/GitDir/PX4-Autopilot/Tools/simulation/gz/worlds/default.sdf
WARN  [init] PX4_GZ_MODEL_POSE not set, spawning at origin.
INFO  [gz_bridge] world: default, model name: advanced_plane_0, simulation model: advanced_plane
INFO  [gz_bridge] Requested Model Position: 0,0,0,0,0,0
INFO  [gz_bridge] Model position z is less or equal 0.0, moving upwards
gz sim -g: symbol lookup error: /snap/core20/current/lib/x86_64-linux-gnu/libpthread.so.0: undefined symbol: __libc_pthread_init, version GLIBC_PRIVATE
ERROR [gz_bridge] Service call timed out. Check GZ_SIM_RESOURCE_PATH is set correctly.
WARN  [gz_bridge] Service call timed out as Gazebo has not been detected.
ERROR [gz_bridge] Service call timed out: /gui/follow
ERROR [gz_bridge] Service call timed out: /gui/follow/offset
INFO  [lockstep_scheduler] setting initial absolute time to 3280000 us
INFO  [commander] LED: open /dev/led0 failed (22)
WARN  [health_and_arming_checks] Preflight Fail: Airspeed selector module down
WARN  [health_and_arming_checks] Preflight Fail: ekf2 missing data
WARN  [health_and_arming_checks] Preflight Fail: No connection to the ground control station
INFO  [airspeed_selector] No airspeed sensor detected. Switch to non-airspeed mode.
INFO  [uxrce_dds_client] init UDP agent IP:127.0.0.1, port:8888
INFO  [tone_alarm] home set
INFO  [mavlink] mode: Normal, data rate: 4000000 B/s on udp port 18570 remote port 14550
INFO  [mavlink] partner IP: 127.0.0.1
INFO  [mavlink] mode: Onboard, data rate: 4000000 B/s on udp port 14580 remote port 14540
INFO  [mavlink] mode: Onboard, data rate: 4000 B/s on udp port 14280 remote port 14030
INFO  [mavlink] mode: Gimbal, data rate: 400000 B/s on udp port 13030 remote port 13280 

Software Version

Gazebo harmonic 8.6.0

Flight controller

No response

Vehicle type

Other

How are the different components wired up (including port information)

No response

Additional context

No response

@Wangzy321
Copy link

1
How should it be resolved?

@leechor
Copy link

leechor commented Jan 3, 2025

1 How should it be resolved?

have you solved it ?

@dakejahl dakejahl linked a pull request Jan 3, 2025 that will close this issue
@dakejahl
Copy link
Contributor

dakejahl commented Jan 3, 2025

@leechor try #24164

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants