gzserver segmentation fault, gazebo won't start [closed]
For some reason gazebo just refuses to start.
Gazebo multi-robot simulator, version 9.14.0
Copyright (C) 2012 Open Source Robotics Foundation.
Released under the Apache 2 License.
http://gazebosim.org
[Msg] Waiting for master.
Gazebo multi-robot simulator, version 9.14.0
Copyright (C) 2012 Open Source Robotics Foundation.
Released under the Apache 2 License.
http://gazebosim.org
[Msg] Waiting for master.
[Msg] Connected to gazebo master @ http://127.0.0.1:11345
[Msg] Publicized address: 172.25.127.110
When I run gzserver on its own,
[1] 19471 segmentation fault gzserver
I have tried both reinstalling ROS and installing Gazebo separately, but nothing changed.
I using Ros Melodic on Ubuntu 18.04, runnning on WSL2.
EDIT:
Valgrind shows this:
==1511== Process terminating with default action of signal 11 (SIGSEGV)
==1511== Access not within mapped region at address 0x4
==1511== at 0x40E86496: ??? (in /usr/lib/x86_64-linux-gnu/OGRE-1.9.0/RenderSystem_GL.so.1.9.0)
==1511== by 0x40E8AEDF: ??? (in /usr/lib/x86_64-linux-gnu/OGRE-1.9.0/RenderSystem_GL.so.1.9.0)
==1511== by 0x40EAF932: Ogre::GLRenderSystem::GLRenderSystem() (in /usr/lib/x86_64-linux-gnu/OGRE-1.9.0/RenderSystem_GL.so.1.9.0)
==1511== by 0x40EAA6E3: ??? (in /usr/lib/x86_64-linux-gnu/OGRE-1.9.0/RenderSystem_GL.so.1.9.0)
==1511== by 0x53B6A25: Ogre::Root::installPlugin(Ogre::Plugin*) (in /usr/lib/x86_64-linux-gnu/libOgreMain.so.1.9.0)
==1511== by 0x40E93799: dllStartPlugin (in /usr/lib/x86_64-linux-gnu/OGRE-1.9.0/RenderSystem_GL.so.1.9.0)
==1511== by 0x53B6C60: Ogre::Root::loadPlugin(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) (in /usr/lib/x86_64-linux-gnu/libOgreMain.so.1.9.0)
==1511== by 0x6D8ECA3: gazebo::rendering::RenderEngine::LoadPlugins() (in /usr/lib/x86_64-linux-gnu/libgazebo_rendering.so.9.14.0)
==1511== by 0x6D92BBB: gazebo::rendering::RenderEngine::Load() (in /usr/lib/x86_64-linux-gnu/libgazebo_rendering.so.9.14.0)
==1511== by 0x6D96184: gazebo::rendering::load() (in /usr/lib/x86_64-linux-gnu/libgazebo_rendering.so.9.14.0)
==1511== by 0x4E76594: gazebo::setupServer(int, char**) (in /usr/lib/x86_64-linux-gnu/libgazebo.so.9.14.0)
==1511== by 0x4E5DBA9: gazebo::Server::ParseArgs(int, char**) (in /usr/lib/x86_64-linux-gnu/libgazebo.so.9.14.0)
==1511== If you believe this happened as a result of a stack
==1511== overflow in your program's main thread (unlikely but
==1511== possible), you can try to increase the size of the
==1511== main thread stack using the --main-stacksize= flag.
==1511== The main thread stack size used in this run was 8388608.
Afaik, WSL2 does not come with an X-server.
Gazebo is a UI application.
Even
gzserverrequires a working graphics infrastructure (or it used to, I don't know whether this has changed recently), as it uses GPU acceleration for some tasks.Seeing
OGREbeing mentioned in the backtrace you show makes me suspect that something on the graphics side isn't working there.Finally: seeing as you can't even start Gazebo itself (and ROS is not even involved yet), I would recommend you post on Gazebo Answers instead of here.
I am running VcXsrv for my GUI things, which did work for my other GUI applications, and I do know of people who could run it this way on WSL (though he managed to run it straight out of the box...).
Thanks for the reply though! And yeah, I probably should move this question over there.
Seems you posted this over at Gazebo Answers: Gzserver segmentation fault on start, running on WSL2.
A comment here with a link so we keep things connected would've been appreciated.