<div dir="ltr">No luck:<div>./x2goglx glxinfo|grep -i open<br>OpenGL vendor string: VMware, Inc.<br>OpenGL renderer string: llvmpipe (LLVM 10.0.0, 256 bits)<br>OpenGL version string: 3.0 Mesa 20.1.5<br>OpenGL shading language version string: 3.30<br>OpenGL context flags: (none)<br>OpenGL extensions:<br>[rkudyba@storm ~]$ ./x2goglx gazebo<br>AL lib: (WW) alcCloseDevice: Releasing context 0x561a7f165b50<br>AL lib: (WW) alcSetError: Error generated on device (nil), code 0xa002<br></div><div><br></div><div>FWIW this was an issue with Gazeo 9 and this comment <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1816487#c1">https://bugzilla.redhat.com/show_bug.cgi?id=1816487#c1</a> says:</div><div>"A workaround is to override the session with environment variable XDG_SESSION_TYPE<br><br>XDG_SESSION_TYPE=x11 gazebo"<br></div><div><br></div><div>Whilst this comment: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1815270#c3">https://bugzilla.redhat.com/show_bug.cgi?id=1815270#c3</a></div><div><br></div><div>"It looks like it's an OGRE/Wayland issue. I found a similar error report from rviz here:<br><a href="https://github.com/ros-visualization/rviz/issues/1442">https://github.com/ros-visualization/rviz/issues/1442</a><br><br>The work-around listed in the bug report works, and gazebo launches properly:<br>QT_QPA_PLATFORM=xcb gazebo<br><br>One way forward is to force gazebo to use xcb platform. I'll see if there's a way to do that in code so you don't have to use the environment variable."<br></div><div><br></div><div>None of those made a difference.</div><div><br></div><div>Here's some more debug upon starting gazebo with verbose option:</div><div>[Err] [RenderEngine.cc:743] Unable to create glx visual<br>[Wrn] [RenderEngine.cc:93] Unable to create X window. Rendering will be disabled<br>[Wrn] [RenderEngine.cc:293] Cannot initialize render engine since render path type is NONE. Ignore this warning ifrendering has been turned off on purpose.<br>[Err] [RenderEngine.cc:743] Unable to create glx visual<br>[Wrn] [RenderEngine.cc:93] Unable to create X window. Rendering will be disabled<br>[Wrn] [RenderEngine.cc:293] Cannot initialize render engine since render path type is NONE. Ignore this warning ifrendering has been turned off on purpose.<br>[Wrn] [GuiIface.cc:122] X server does not support XInput 2<br>[Wrn] [GuiIface.cc:122] QXcbConnection: XCB error: 1 (BadRequest), sequence: 168, resource id: 78, major code: 130 (Unknown), minor code: 47<br>[Err] [GLWidget.cc:178] GLWidget could not create a scene. This will likely result in a blank screen.<br>[Wrn] [Publisher.cc:142] Queue limit reached for topic /gazebo/default/physics/contacts, deleting message. This warning is printed only once.<br>[Wrn] [Event.cc:61] Warning: Deleting a connection right after creation. Make sure to save the ConnectionPtr from a Connect call<br>AL lib: (WW) alcCloseDevice: Releasing context 0x55b168a79810<br>AL lib: (WW) alcSetError: Error generated on device (nil), code 0xa002<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Aug 20, 2020 at 3:11 PM Ulrich Sibiller <<a href="mailto:uli42@gmx.de">uli42@gmx.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Thu, Aug 20, 2020 at 5:21 PM Robert Kudyba <<a href="mailto:rkudyba@fordham.edu" target="_blank">rkudyba@fordham.edu</a>> wrote:<br>
><br>
> Is there another step after running ninja? Still getting this error:<br>
<br>
Yes. After compilation you need to preload the resulting lib:<br>
<br>
The easiest way for that is this:<br>
1. copy build/src/gallium/targets/libgl-xlib dor some safe place<br>
2. write a small wrapper called "~/x2goglx" with this content:<br>
#!/bin/sh<br>
LD_LIBRARY_PATH=<your directory>/libgl-xlib:${LD_LIBRARY_PATH} exec "$@"<br>
<br>
(replace <your directory> with the path to where you copied the above<br>
directory to)<br>
<br>
Then<br>
$ chmod u+rx ~/x2goglx<br>
<br>
Then test with (should show OpenGL 1.4)<br>
$ ~/x2goglx glxinfo<br>
<br>
Then run gazebo:<br>
<br>
$ ~/x2goglx gazebo<br>
<br>
<br>
<br>
<br>
> gazebo<br>
> AL lib: (WW) alcCloseDevice: Releasing context 0x55b6657b6d20<br>
> AL lib: (WW) alcSetError: Error generated on device (nil), code 0xa002<br>
> segfault at 20 ip 00007fe4d7081cc6 sp 00007fff0d0c1280 error 4 in libOgreMain.so.1.9.0[7fe4d6e7d000+2f0000]<br>
> Aug 20 11:19:11 storm kernel: Code: 00 5b 5d 41 5c 41 5d 41 5e c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 55 48 89 e5 41 56 49 89 fe 41 55 41 54 53 48 83 ec 60 <48> 8b 7f 20 64 48 8b 04 25 28 00 00 00 48 89 45 d8 31 c0 48 85 ff<br>
><br>
> On Thu, Aug 20, 2020 at 11:17 AM Robert Kudyba <<a href="mailto:rkudyba@fordham.edu" target="_blank">rkudyba@fordham.edu</a>> wrote:<br>
>><br>
>> I never would've figured this out without your help! I take it these warnings are safe to ignore? Also, should I CC the dev list? Or did you intentionally remove it?<br>
>><br>
>> WARNING: Library target 'GLESv2' has 'name_prefix' set. Compilers may not find it from its '-lGLESv2' linker flag in the 'glesv2-uninstalled.pc' pkg-config file.<br>
>> Message: Configuration summary:<br>
>><br>
>> prefix: /usr/local<br>
>> libdir: lib64<br>
>> includedir: include<br>
>><br>
>> OpenGL: yes (ES1: yes ES2: yes)<br>
>> OSMesa: no<br>
>><br>
>> GLX: Xlib-based (Gallium)<br>
>><br>
>> EGL: no<br>
>> GBM: no<br>
>> EGL/Vulkan/VL platforms: x11<br>
>><br>
>> Vulkan drivers: no<br>
>><br>
>> llvm: yes<br>
>> llvm-version: 10.0.0<br>
>><br>
>> Gallium drivers: swrast<br>
>> Gallium st: mesa<br>
>> HUD lmsensors: no<br>
>><br>
>> Shared-glapi: yes<br>
>><br>
>> Build targets in project: 101<br>
>> WARNING: Project specifies a minimum meson_version '>= 0.46' but uses features which were added in newer versions:<br>
>> * 0.51.0: {'dep.get_variable'}<br>
>> * 0.52.0: {'version arg in find_program'}<br>
>><br>
>> Option buildtype is: release [default: debugoptimized]<br>
>> Found ninja-1.10.0 at /usr/bin/ninja<br>
>> WARNING: custom_target 'glcpp-parse.[ch]' has more than one output! Using the first one.<br>
>> WARNING: custom_target 'glsl_parser' has more than one output! Using the first one.<br>
>> WARNING: custom_target 'program_parse_tab.[ch]' has more than one output! Using the first one.<br>
>> (base) [root@storm build]# ninja<br>
>> [187/945] Compiling C object src/gallium/drivers/softpipe/libsoftpipe.a.p/sp_quad_blend.c.o<br>
>> ../src/gallium/drivers/softpipe/sp_quad_blend.c: In function ‘blend_fallback’:<br>
>> ../src/gallium/drivers/softpipe/sp_quad_blend.c:245:46: warning: ‘res[0][0]’ may be used uninitialized in this function [-Wmaybe-uninitialized]<br>
>><br>
>> ../src/gallium/auxiliary/gallivm/lp_bld_nir.h:242:27: warning: ‘result’ may be used uninitialized in this function [-Wmaybe-uninitialized]<br>
>> 242 | LLVMTypeRef arr_type = LLVMArrayType(LLVMTypeOf(values[0]), value_count);<br>
>> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
>> ../src/gallium/auxiliary/gallivm/lp_bld_nir.c:168:4: warning: ‘undef’ may be used uninitialized in this function [-Wmaybe-uninitialized]<br>
>> 168 | assign_ssa(bld_base, ssa->index, ssa->num_components == 1 ? vals[0] : lp_nir_array_build_gather_values(bld_base->base.gallivm->builder, vals, ssa->num_components));<br>
>> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
>> [945/945] Linking target src/gallium/targets/libgl-xlib/libGL.so.1.5.0<br>
>><br>
>><br>
>> On Thu, Aug 20, 2020 at 11:09 AM Ulrich Sibiller <<a href="mailto:uli42@gmx.de" target="_blank">uli42@gmx.de</a>> wrote:<br>
>>><br>
>>> Ahm, according to the meson source the error appears when it cannot<br>
>>> find "meson.build" in the parent directory. I have just downloaded the<br>
>>> mesa source (<a href="https://archive.mesa3d.org//mesa-20.1.6.tar.xz" rel="noreferrer" target="_blank">https://archive.mesa3d.org//mesa-20.1.6.tar.xz</a>) and it<br>
>>> contains the relevant file.<br>
>>><br>
>>> So in detail you need to:<br>
>>> 1. download the tarball<br>
>>> 2. extract it<br>
>>> 3. cd to the extracted dir: cd mesa-20.1.6<br>
>>> 4. mkdir build<br>
>>> 5. cd build<br>
>>> 6. meson ....<br>
>>> 7. ninja<br>
>>> ...<br>
>>><br>
>>> Uli<br>
>>><br>
>>> On Thu, Aug 20, 2020 at 5:00 PM Ulrich Sibiller <<a href="mailto:uli42@gmx.de" target="_blank">uli42@gmx.de</a>> wrote:<br>
>>> ><br>
>>> > On Thu, Aug 20, 2020 at 4:41 PM Robert Kudyba <<a href="mailto:rkudyba@fordham.edu" target="_blank">rkudyba@fordham.edu</a>> wrote:<br>
>>> > > So yes to have to compile, but no to the first question on uninstalling?<br>
>>> ><br>
>>> > exactly. But if the meson of fedora is incompatible to the mesa source<br>
>>> > you are out of luck for now.<br>
>>> ><br>
>>> > > Yes I am prompted by Fedora to run this when I ran the meson command. But I'm still not following. I see here <a href="https://docs.mesa3d.org/gallium/drivers/llvmpipe.html" rel="noreferrer" target="_blank">https://docs.mesa3d.org/gallium/drivers/llvmpipe.html</a><br>
>>> > ><br>
>>> > > scons: *** No SConstruct file found.<br>
>>> > > File "/usr/lib/python3.8/site-packages/SCons/Script/Main.py", line 940, in _main<br>
>>> > ><br>
>>> > > Then:<br>
>>> > > Alternatively, you can build it with meson with:<br>
>>> > > mkdir build<br>
>>> > > cd build<br>
>>> > > meson -D glx=gallium-xlib -D gallium-drivers=swrast<br>
>>> > > ninja<br>
>>> > ><br>
>>> > > So is this the meson command that I should replace with:<br>
>>> > > meson -D glx=gallium-xlib -D gallium-drivers=swrast -D platforms=x11 -D dri3=false -D dri-drivers="" -D vulkan-drivers="" -D buildtype=release -D optimization=3<br>
>>> ><br>
>>> > exactly.<br>
>>> ><br>
>>> > > I still get ERROR: Must specify at least one directory name.<br>
>>> ><br>
>>> > All the examples I have seen do NOT require a directory being<br>
>>> > specified so I do not know what's going on here. I also do not have a<br>
>>> > fedora to play with.<br>
>>> ><br>
>>> > Uli<br>
</blockquote></div>