-
Notifications
You must be signed in to change notification settings - Fork 51
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
libEGL warning failed to create dri screen #587
Comments
Does this happen on native? The community post you link to referred to the problem happening in VMWare. Is this just a warning or the app crashes? Given how recent your GPUs are, it should work on native. It sounds like there is a driver misconfiguration somewhere, specially since it should be using DRI3 not DRI2.
Is this the full contents of running If so there is a driver problem, because NVIDIA drivers would only be offering OpenGL ES but not OpenGL (which your card definitely supports). |
Its just a warning, app doesn't crash.
|
I kept thinking about this. I couldn't reply sooner because I was ill. So everything works just fine, it's just that there is a warning that causes unnecessary concern. I suspect this could be caused by Switchable support allows Ignition to switch between Ogre-Next needs to initialize both backends, and It's quite possible the warning is coming from one of these devices which doesn't end up being used. There can be many devices in a system, because it's not just your NVIDIA + Intel GPUs (2 devices). Sometimes drivers expose more variations (i.e. Compute-only, no graphics) of the same physical HW, or SW emulation devices. If this theory is correct, it's not easy to fix. Communicating to Ogre-Next from Ignition that it doesn't plan to use Headless needs to happen extremely early and many things haven't been initialized yet. One way to test this theory could be to compile Ignition from scratch including Ogre-Next 2.2 from source but force disabling |
I also see this message native without specifying to run headless. I think it could be harmless as I'm able to continue using ign-rendering / gazebo. I see these msgs in my ogre2.log that look relevant (these are printed without specifying to use EGL): ogre2.log exceptions
|
That's what I said: Ogre doesn't know yet if ignition will use headless but it needs to present information to ignition in case it wants to, thus Ogre goes ahead and queries all devices (some of which may fail), regardless of ignition's intentions. |
Sorry it took me time to get to this, but I tried your suggestion @darksylinc and you're right. Also thanks a lot @iche033 for helping out! |
Environment
Description
Getting this warning message on a dual GPU machine as well as in Docker.
See this related community thread: forcing ignition to use ogre1 removes that warning message.
Could be ignored but helpful if its removed to avoid confusion.
Steps to reproduce
Launch the simulator
ign gazebo
The text was updated successfully, but these errors were encountered: