gz-harmonic gui app is stuck at "[Gui.cc:343] GUI requesting list of world names. The server may be busy downloading resources" #2285
Assignees
Labels
bug
Something isn't working
Comments
|
With the server running ( You should see: If not, there might be something wrong in your network setup. |
|
Chiming in to say that I have the same exact error when trying to get started with Gazebo. Working on Apple M2 Pro running Ventura 13.6.1. @azeey when I try your instructions above, I get |
|
I don't have much experience with network configuration on macOS, but if you can do it safely, a quick thing to try would be to disable the firewall and see if the issue goes away. In general, UDP multicast has been the main issue of these types of problems, so I recommend following my suggestion here |
Hey, gentlemen, I'm running these commands and receiving "data: "shapes", as mentioned in a quoted comment. I'm struggling to find anything while googling. @matt-mueller-ptc did you manage to solve the problem? I appreciate any help. Here's the whole stack: |
|
I have the same message but I using Ubuntu 22.04 only Gazebo11 classic GUI is working neither ignition nor Hurmonic I have deleted everything related to the classic version to see if it is the problem but nothing happend the GUI of the harmonic appear which you can choose whic sdf file you want and when I hit run it fails and print the GUI is not responding and if I run it from the terminal it stays a little bit printing that kind of message wait message then it prints also the GUI is not responding ....... I found someone talking about the firewall and locale setting but nothing , also adding that line to the .bashrc -> export GAZEBO_RESOURCE_PATH=/usr/share/gazebo-harmonic when I run the comand too: gz service -s /gazebo/worlds --reqtype gz.msgs.Empty --reptype gz.msgs.StringMsg_V -r 'unused: true' --timeout 2000 it prints out service time out |
|
Hi I am also seeing this same issue for Harmonic built from source. |
|
Hi @rreddy80 I found the solution to this problem as discussed here https://gazebosim.org/docs/latest/troubleshooting/ The following commands should resolve this problem. I tested it in Gazebo Harmonic source built in Ubuntu 22.04 sudo ufw allow in proto udp to 224.0.0.0/4
sudo ufw allow in proto udp from 224.0.0.0/4
gz sim -v 4 empty.sdf |
|
Hey @Mechazo11 That works for me as well, thanks! (Gazebo Ionic on Ubuntu 24.04) So to me it looks like a problem caused by the firewall configs on one's local host, rather than an incompatibility among the versions or the OS or drivers etc.. Recommend to try this if any others ran into the same problem. |
|
I'll go ahead and close this since this is most likely a network configurations issue which has now been documented in https://gazebosim.org/docs/latest/troubleshooting/#network-configuration-issue |
This solved my problem! Thanks! |
|
Hi @IsraaAbdelghany9 did you found a solution ? I've tried @Mechazo11 solution but it did not work. |
|
Hi @hfcaio which Gazebo are you using and have you tried source building it? |
|
Hi @Mechazo11. I am using gazebo harmonic, and I tried both binary and source building. Like a said before, I'm running ros in a docker container, the base image is from ardupilot.
|
|
@hfcaio can you post what you get when you echo export GZ_VERSION=harmonic
export GZ_SIM_RESOURCE_PATH=$GZ_SIM_RESOURCE_PATH:~/dev_ws/install/<project>_gz/share/<project>_gz/worlds |
|
Hi @Mechazo11, sorry for the delay.
And I am still having the same problem. |
|
Hi @hfcaio this is what I would do
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment
harmonic [brew install gz-harmonic]
Rendering plugin: [ogre | ogre2].
EGL headless mode:
Generally, mention all circumstances that might affect rendering capabilities:
Rendering system info:
dxdiagand report the GPU-related information.system_profiler SPDisplaysDataType. Copy the output here.Graphics/Displays:
Please, attach the ogre.log or ogre2.log file from
~/.gz/rendering: n/aDescription
Steps to reproduce
Terminal1 Output
Terminal2 Output
The text was updated successfully, but these errors were encountered: