Skip to content
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

Cannot create GLX Context #503

Open
gizatt opened this issue Apr 20, 2017 · 12 comments
Open

Cannot create GLX Context #503

gizatt opened this issue Apr 20, 2017 · 12 comments

Comments

@gizatt
Copy link
Contributor

gizatt commented Apr 20, 2017

I'm exploring the many instances of this problem reported online (it originates in VTK), but for documentation's sake:

After no modifications I'm aware of (no reboot, no apt-get upgrade, no rebuild), drake-visualizer and directorPython testMainWindowApp.py (and probably others) have stopped launching with error:

ERROR: In /build/buildd/vtk-5.8.0/Rendering/vtkXOpenGLRenderWindow.cxx, line 404
vtkXOpenGLRenderWindow (0x263af40): Could not find a decent visual


ERROR: In /build/buildd/vtk-5.8.0/Rendering/vtkXOpenGLRenderWindow.cxx, line 404
vtkXOpenGLRenderWindow (0x263af40): Could not find a decent visual


ERROR: In /build/buildd/vtk-5.8.0/Rendering/vtkXOpenGLRenderWindow.cxx, line 631
vtkXOpenGLRenderWindow (0x263af40): Cannot create GLX context.  Aborting.

Aborted (core dumped)

This has persisted after a clean rebuild (of spartan) and a reboot.

While I search and try stuff, any ideas?

@patmarion
Copy link
Member

Can you run glxgears? Can you post output of glxinfo?

I have only seen this after modifying the video driver, and it resolves after a reboot.

@gizatt
Copy link
Contributor Author

gizatt commented Apr 20, 2017

glxgears works without warnings, glxinfo is at https://pastebin.com/izg6L2BR

Just reinstalled my video driver and rebooted and the problem is persisting; then purged out vtk 5.8, reinstalled, and rebuilt director (make -B) and it's persisting

@patmarion
Copy link
Member

patmarion commented Apr 21, 2017

How is it picking up vtk-5.8 from this path: /build/buildd/vtk-5.8.0/Rendering/vtkXOpenGLRenderWindow.cxx? Is that what you expect? Do you also have vtk system installed?

@gizatt
Copy link
Contributor Author

gizatt commented Apr 21, 2017 via email

@gizatt
Copy link
Contributor Author

gizatt commented Apr 21, 2017

I can't reproduce this in standalone drake-building-director; only in Spartan. I'm guessing it could be that the Spartan Director build is pulling in a conflicting version of a library...

@manuelli
Copy link
Collaborator

I fixed this by setting the USE_SYSTEM_VTK=OFF option.

@patmarion
Copy link
Member

There are two things to double check:

  1. which version you compiled and linked with
  2. which version of vtk gets loaded at runtime when you import vtk

They need to be the same.

@QinZiwen
Copy link

@gizatt Is this problem solved?

@gizatt
Copy link
Contributor Author

gizatt commented Mar 11, 2018

@QinZiwen IIRC this was a VTK version mismatch (system vs director-or-drake-source-installed) that I haven't had trouble with since

@QinZiwen
Copy link

@gizatt Sorry, I didn't understand what you meant

@QinZiwen
Copy link

QinZiwen commented Mar 12, 2018

Vtk no special requirements, like:

In general VTK tries to be as portable as possible; the specific configurations below are known to work and tested.

VTK supports the following C++11 compilers:


Microsoft Visual Studio 2013 or newer
gcc 4.8.3 or newer
Clang 3.3 or newer
Apple Clang 5.0 (from Xcode 5.0) or newer
Intel 14.0 or newer


VTK supports the following operating systems:


Windows Vista or newer
Mac OS X 10.7 or newer
Linux (ex: Ubuntu 12.04 or newer, Debian 4 or newer)

https://gitlab.kitware.com/vtk/vtk

@gizatt
Copy link
Contributor Author

gizatt commented Mar 12, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants