QuantumATK Forum

QuantumATK => General Questions and Answers => Topic started by: yasheng on March 1, 2017, 11:47

Title: VNL 2016.3 stopped working - initializing shaders ....
Post by: yasheng on March 1, 2017, 11:47

Dear All,

I was working with VNL on my desktop yesterday when the Linux system of our institute crashed. When I came back this morning to use VNL, it is not opening.

It stopped at the point 'Initializing shaders .....'. 

I re-installed the VNL desktop, but I got the same problem.

Do you have any idea how to fix this problem? please reply.

Thank you
Yasheng

 

Title: Re: VNL 2016.3 stopped working - initializing shaders ....
Post by: yasheng on March 1, 2017, 13:30

I appreciate if anyone reply. This is very strange problem with VNL. I need it fixed very urgently.

Title: Re: VNL 2016.3 stopped working - initializing shaders ....
Post by: yasheng on March 1, 2017, 15:47

The following message appeared when I started the vnl from terminal.


setNativeLocks failed: Resource temporarily unavailable
setNativeLocks failed: Resource temporarily unavailable
setNativeLocks failed: Resource temporarily unavailable
setNativeLocks failed: Resource temporarily unavailable
setNativeLocks failed: Resource temporarily unavailable
setNativeLocks failed: Resource temporarily unavailable
setNativeLocks failed: Resource temporarily unavailable
setNativeLocks failed: Resource temporarily unavailable
setNativeLocks failed: Resource temporarily unavailable
setNativeLocks failed: Resource temporarily unavailable
setNativeLocks failed: Resource temporarily unavailable
setNativeLocks failed: Resource temporarily unavailable
setNativeLocks failed: Resource temporarily unavailable
setNativeLocks failed: Resource temporarily unavailable
setNativeLocks failed: Resource temporarily unavailable
setNativeLocks failed: Resource temporarily unavailable
.........
.........



HELP !

Title: Re: VNL 2016.3 stopped working - initializing shaders ....
Post by: Petr Khomyakov on March 2, 2017, 10:00

You may try first unistalling VNL and deleting all the VNL hidden files, and then install it again from scratch. But it is more likely a local problem with drivers on your Linux machine after the system crash you have mentioned, not with the VNL as such.