-
Notifications
You must be signed in to change notification settings - Fork 193
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
Gazebo Not Responding on launch #24
Comments
Original comment by Brian Bingham (Bitbucket: brian_bingham). I can verify similar symptoms from my setup. Working backwards in the default branch, the issues seems to arise with this commit/merge (rev=186): https://osrf-migration.github.io/vrx-gh-pages/#!/osrf/vmrc/commits/3e6600a0c6ba6731087a34fa4fbbcad8f1d5f170 For me the default branch was operational prior to the commit, but not after. @kev-the-dev , @caguero - can you see if the most recent default branch works for you? |
Original comment by Kevin Allen (Bitbucket: kev-the-dev). Cannot replicate after doing a clean build. Perhaps it's some old stuff running. A few general steps to rule out other issues:
Do a complete rebuild:
Make sure no other gazebo instances are running
|
Original comment by Brian Bingham (Bitbucket: brian_bingham). For my setup, the issue seems to be with the sandisland/model.sdf file.
then things are back to a working state. Looking at the changes, not sure why adding simplified collision geometry would affect. Also, probably worth debugging why we are getting different results with different setups. I've verified - to the best of my knowledge - that having the system up to date, no other gazebo processes and clean workspace and fresh clone of the head of the default branch causes gazebo to hang. |
Original comment by Kevin Allen (Bitbucket: kev-the-dev). It's a long shot, but could one of you try running the sdf-warn branch in PR #23? Maybe the SDF version makes the box collisions invalid. |
Original comment by Brian Bingham (Bitbucket: brian_bingham). Will try it a bit later today. |
Original comment by Brian Bingham (Bitbucket: brian_bingham). Tried the sdf-warn branch without any luck - Gazebo still hangs. |
Original comment by Brian Bingham (Bitbucket: brian_bingham). Need to add instructions in setup tutorial to make sure and use the gazebo (not ros) Ubuntu packages. E.g., http://gazebosim.org/tutorials?tut=install_ubuntu This bug shows up when using Gazebo 7.0.0 from the ros package repo, but if you add the gazebo package repo, and update, you should have at least version 7.13.1. With this version the bug is fixed! Will close issue once we get docs up. |
Original comment by Kevin Allen (Bitbucket: kev-the-dev). |
Original comment by Brian Bingham (Bitbucket: brian_bingham).
Issue was making sure to use the gazebo package repository (instead of the ros repos) so that the gazebo7 install is upgraded from 7.0.0 to 7.13.1 |
Original comment by Raymond Andrade (Bitbucket: 808brick). Thank you for resolving the issue |
Original report (archived issue) by Raymond Andrade (Bitbucket: 808brick).
I think the latest release to main repository has a Gazebo related bug in it. After following all the setup instructions in the tutorial, I am unable to startup the simulation, as Gazebo just hangs on launch. The Gazebo window and GUI opens, but then the program just hangs and never shows the simulation.
The last thing printed in the terminal is:
[spawn_model-3] process has finished cleanly
log file: /home/raymond/.ros/log/a1ec64b8-8c8d-11e8-8535-1002b5c27c61/spawn_model-3*.log
I had a previous version of the simulation working, but I decided to reinstall the simulation as mine had not been updated since late May. I have tried restarting terminal, restarting computer, and recompiling with catkin_make.
Any help would be appreciated
The text was updated successfully, but these errors were encountered: