-
Notifications
You must be signed in to change notification settings - Fork 86
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
Comments
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. |
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 |
How is it picking up vtk-5.8 from this path: |
I'm pretty confused by that path -- a "buildd" folder doesn't show up
anywhere in my system.
I'm not sure what you mean by vtk system?
…On Fri, Apr 21, 2017 at 8:16 AM, Pat Marion ***@***.***> wrote:
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?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#503 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AC7LTz_7z_mHmfQzYJiPLrVBkbf9NtsFks5ryJ4FgaJpZM4NDhds>
.
|
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... |
I fixed this by setting the USE_SYSTEM_VTK=OFF option. |
There are two things to double check:
They need to be the same. |
@gizatt Is this problem solved? |
@QinZiwen IIRC this was a VTK version mismatch (system vs director-or-drake-source-installed) that I haven't had trouble with since |
@gizatt Sorry, I didn't understand what you meant |
Vtk no special requirements, like:
|
Right, but Director expects a certain vtk version (6 or 7, I think? see the
director homepage) while your system might have another version installed.
If you run director and it loads vtk dynamic libraries that are a different
version than it director was built with, this problem might come up.
…On Mar 11, 2018 20:48, "Ziwen Qin" ***@***.***> wrote:
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)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#503 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AC7LTzdlDfTju1t2yOFvbKyGtLOamp-jks5tdcXsgaJpZM4NDhds>
.
|
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
anddirectorPython testMainWindowApp.py
(and probably others) have stopped launching with error:This has persisted after a clean rebuild (of spartan) and a reboot.
While I search and try stuff, any ideas?
The text was updated successfully, but these errors were encountered: