VNL closes down directly when opening Viewer

[gellen]

hi, everyone.
I also have the problem which had been reported by ipsecog on February 8, 2010, 22:28 in this forum:

I can run VNL fine (it starts) and can open the Editor, Job, and the Analyzer icons, but none of the other tools, such as viewer, database,custom,builder.As soon as I click on these icons, the program just shuts down directly.
Then it reports:
./vnl: line 3:  1815 Segmentation fault      VNL_PATH=$EXEC_DIR/../.. PSEUDOPOTENTIALS_PATH=$EXEC_DIR/../../atkpython/share/pseudopotentials PYTHONHOME=$EXEC_DIR/.. PYTHONPATH= LD_LIBRARY_PATH=$EXEC_DIR/../lib $EXEC_DIR/vnl_exec $*

Tip:
here, the version of atk is atk-10.8.1,linux64.  The linux version is Redhat 5.3 Enterprise x86_64. and my ulimit is :
$ ulimit -a
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 106496
max locked memory       (kbytes, -l) 32
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) unlimited
cpu time               (seconds, -t) unlimited
max user processes              (-u) 106496
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited

Is there something wrong? and how can I deal with this error?
thankyou！

[Nordland]

Have you been able to run the ATK 2010.02 or ATK 2010.08 ?

[gellen]

I have never installed the ATK 2010.02 or 2010.08 in my cluster since I can't download these two versions now. But I had installed ATK-10.8.0 in my cluster and it works well. Now I want to update to the 10.8.1, then  I come to the problem reported above.

[medeepak]

@gellen

Hi have you solved your problem
if so please share here how have you done it

[Anders Blom]

Until we solve this problem in the code (which we are working on), the user can do two things:

1) A proper permanent solution is to install vendor graphics drivers instead of MESA. That usually solves all problems.
2) As a workaround, if you open the Help menu in VNL and click "About", then the problem disappears. It is of course a bit inconvenient that you have to do this each time you start VNL, but at least you can use the program