[Ivy Zhou]

Hi

I am using Mac system and access to another linux machine via "ssh".
When I create the mesh and then type "paraFoam", I can open the paraview, however, in the terminal it was written
"Xlib: extension “NV-GLX” missing on display "****" "

How should I solved the problem ?

Thanks very much. I am currently doing my bachelor thesis, which is driving me a bit crazy since I often get stuck
Any help would be really appreciated

[wyldckat]

Hi Ivy,

As I said on your other thread http://www.cfd-online.com/Forums/par...ux-system.html - I'll answer to this issue here.

Last year I helped someone with a similar issue on a Mac: http://engits.eu/vanilla/index.php?p...ard-engrid./p1
The answer is this:

Originally Posted by preichl

Setting the environment variable via the command below worked for me.

export LIBGL_ALWAYS_INDIRECT=y

Best regards,
Bruno

[Ivy Zhou]

Hi Bruno~~~

Thanks soooo much ))
I think it works Yeah~~

Best Regards!!
Ivy

[chery1986]

Hi Bruno

I have similar problem to remotely use paraview on RHEL from win7
Xlib: extension "NV-GLX" missing on display "localhost:10.0".

Do you have any idea to fix the problem?

Originally Posted by wyldckat

Hi Ivy,

As I said on your other thread http://www.cfd-online.com/Forums/par...ux-system.html - I'll answer to this issue here.

Last year I helped someone with a similar issue on a Mac: http://engits.eu/vanilla/index.php?p...ard-engrid./p1
The answer is this:

Best regards,
Bruno

[wyldckat]

Greetings Chen Yu,

Originally Posted by chery1986

Do you have any idea to fix the problem?

Did you try to follow the instructions given in post #2? Namely the post you quoted?

Best regards,
Bruno

[chery1986]

I have tried
export LIBGL_ALWAYS_INDIRECT=y
in mobaXterm under win7, but doesn't help with this problem.

Originally Posted by wyldckat

Greetings Chen Yu,


Did you try to follow the instructions given in post #2? Namely the post you quoted?

Best regards,
Bruno

[wyldckat]

Hi Chen Yu,

I had a look into mobaXterm and I don't trust it. It's not open-source and I have some trouble trusting "free" software nowadays.

The best I can do is ask you for details on how are you setting up the interface, namely:

1. Are you logging in from Windows directly to a Linux machine in the same network?
   1. If not, are you logging in over the internet and/or are you using a 2 step logging in? For example: 1st you logging to a first Linux machine and then from that machine you logging to the other one.
2. Are the NVidia drivers properly installed in the Linux machine?
3. What settings are you using in mobaXterm? Are you certain that you turned on the X11 port tunnel?
4. Are you able to open any other application windows through the connection created with mobaXterm?
5. Which ParaView version are you using? It's possible that the version you're using does not support the option "LIBGL_ALWAYS_INDIRECT".

Best regards,
Bruno

[chery1986]

Answering your question

1. Yes, the win7 machine and RedHat linux machine are in the same network
2. I think the driver is installed properly, the monitor connected to the linux machine also works well
3&4. X11 port is open, gedit and other Xwindows work fine.
5. My paraview version is 3.12.0 64bit, how can I make sure whether it supports "LIBGL_ALWAYS_INDIRECT"?

Thank you

Originally Posted by wyldckat

Hi Chen Yu,

I had a look into mobaXterm and I don't trust it. It's not open-source and I have some trouble trusting "free" software nowadays.

The best I can do is ask you for details on how are you setting up the interface, namely:

1. Are you logging in from Windows directly to a Linux machine in the same network?
   1. If not, are you logging in over the internet and/or are you using a 2 step logging in? For example: 1st you logging to a first Linux machine and then from that machine you logging to the other one.
2. Are the NVidia drivers properly installed in the Linux machine?
3. What settings are you using in mobaXterm? Are you certain that you turned on the X11 port tunnel?
4. Are you able to open any other application windows through the connection created with mobaXterm?
5. Which ParaView version are you using? It's possible that the version you're using does not support the option "LIBGL_ALWAYS_INDIRECT".

Best regards,
Bruno

[wyldckat]

If gedit works, and the graphics are correctly installed in the RHEL machine, then the problem might be with how the flag is being set. ParaView 3.12.0 should work just fine with this flag.

Try this instead:

export LIBGL_ALWAYS_INDIRECT=1
paraview

If it still gives the same error, this post at Unix.StackExchange seems to give a hint: http://unix.stackexchange.com/a/60822 - it seems that this flag is meant to be used with Mesa 3D in the Linux machine, instead of the drivers provided with the graphics card.

And after a quick search, it seems that this errata might be related to the problem you're having: https://rhn.redhat.com/errata/RHBA-2013-0344.html - try following the instructions given there to fix the problem on the RHEL machine.