PDA

View Full Version : Avizo on Linux: error message related to DISPLAY environment variable


Kalidor
22nd September 2010, 06:39
Hello,

when starting Avizo on Ubuntu Linux, I get the following error message:


Executing /opt/Avizo/bin/start...
Using arch-LinuxAMD64-Optimize ...

ERROR: Cannot open display ':0.0'.


ERROR: Unable to query attribute VideoRam specified in query ':0.0[GPU:0]/VideoRam' (no Display connection).


ERROR: Cannot open display ':0.0'.


ERROR: Unable to query attribute NvidiaDriverVersion specified in query ':0.0[GPU:0]/NvidiaDriverVersion' (no Display
connection).


The error is not critical -- Avizo starts and works -- but I would like to know what is going on.

My $DISPLAY environment variable is actually set to ":4.0".
DISPLAY=:4.0 xclock
works,
DISPLAY=:0.0 xclock
does not.
DISPLAY=:4.0 avizo
is ignored by Avizo: it still tries ":0.0". It does not ignore something like
DISPLAY=localhost:4.0 avizo
(shot in the dark) but then it doesn't start at all.
Avizomain: cannot connect to X server localhost:4.0

Does anyone get similar messages and/or know what this is all about?

Regards,
Rainer

forum_admin
1st October 2010, 15:20
Avizo 6.2.1 maybe help. Abnormal graphics card queries were done in Avizo6.2.1 through latest OIV 8.1.
Could you give that a try?
Shawn on behalf of Jean-Luc at VSG Support Hotline

Kalidor
1st October 2010, 15:43
Avizo 6.2.1 maybe help. Abnormal graphics card queries were done in Avizo6.2.1 through latest OIV 8.1.
Could you give that a try?
Shawn on behalf of Jean-Luc at VSG Support Hotline


Sorry but I do not understand your reply. What is it that I should try?

I'm using v6.2.1 (build date 2010-07-21).

Regards,
Rainer

mmarsh
1st October 2010, 15:52
Hi Rainer,

I can't tell what shell you are using, but if you wish to set the DISPLAY variable as an environment variable, so that it is dereferenced correctly by the Avizo start script, you may need to use the export syntax when setting the variable.

e.g.
export DISPLAY=:4.0

Not sure if this is the issue, but it is easy to test quickly to see if the Avizo error message changes.

-Mike

Kalidor
1st October 2010, 16:44
Hi Mike,

I'm using zsh (and sometimes bash). Fact is that Avizo simply ignores the DISPLAY variable in that case (whereas xclock, e.g., does not, so I know that it's 'exported' correctly)...

Regards,
Rainer

Kalidor
1st October 2010, 17:07
By the way, even if I put

export DISPLAY=:4.0

inside the start-up script "start", it is being ignored by Avizo.