-
Notifications
You must be signed in to change notification settings - Fork 486
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 Black screen and no world model #2457
Comments
Original comment by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina). Could you try running Gazebo by itself on verbose mode as follows and see if any error messages are printed?
The first time you run it, Gazebo may try to download some models from the internet, and this can take a while depending on your internet connection. |
Same thing on fedora 32 |
Echoing @bfsgr, the the gazebo fedora package has the same problem, as reported at https://bugzilla.redhat.com/show_bug.cgi?id=1871291 I've been trying to debug this in various ways, such as using a newer version of OGRE, updating from gazebo-10.1.0 to gazebo 11.1.0, using Intel and Nvidia graphics, without any luck. Running with
The GTK issue seems to be related to Qt. And For reference, my current test setup is:
The issue should be reproducable with the stock packages in fedora 32. A few patches are needed to build gazebo on Fedora, but none of them look to me to affect rendering (un-bundling skyx is the only thing that I think might be related - in my testing I disabled that patch and am using gazebo's built-in skyx). I can help debug and try things if needed. |
I let Gazebo run over night and model opened just the black scene. This was 1st reported in 2018 any ETA on a fix now that 11.1 is out? |
I am not sure if it can help, but you can find some info related to Ogre 1.12 also in #2700 . |
If you are able to build and run the Gazebo test suite, that probably could provide some useful information on what it is working and what is not. |
Fair enough. Running I think this test is trying to connect to a gzserver, so if the gzserver isn't responding, it makes sense that the test would never connect and hangs. It could also be why the client never renders anything. The full test output is:
While the test is running, before a timeout, I see the following topic list:
And trying to echo a topic gets me:
|
Reported as #2828 |
Surprisingly, if you set |
The symbol visibility flags are what's causing the problem for me. To be sure, I did a clean re-build (using |
Can you provide a link to the F32 package and the build how-to instructions? |
@richmattes this error message is suspicious to me, though it may be a symptom and not related to the cause. Does this message still appear once you've adjusted the visibility flags and things are working? |
That warning is coming from I was able to set a breakpoint on the destructor that the message is printed in. It trips four times during program startup, but since it warns based on time, and I'm slowing things down with the debugger, I'm unsure which one is printing the error. Backtraces (they all look the same):
|
Not sure if this is related but I have a
Here are some
backtrace of the running process:
|
Original report (archived issue) by Anonymous.
The original report had attachments: gaz.JPG
Installed ROS and Gazebo.
used
roscore &
rosrun gazebo_ros gazebo.
A GUI opened with a black screen.
The text was updated successfully, but these errors were encountered: