"Sorry,the existing instance may be too busy to respond , please close any open dialogs and retry "

[Md Mahabul Islam]

I had opened a big size CHGCAR ( VASP charge density file) using VESTA after that whenever I am launching VESTA it is showing the following dialog "the existing instance may be too busy to respond , please close any open dialogs and retry " I removed the existing version of vesta and reinstalled it but it is showing the same error. How to delete that instance permanently in my Ubuntu 18.04, please help.

Thanks in advance.

[K K Sram]

i am not sure, there might be a locked file in your home directory. By the way, VESTA can be installed separately on your desktop system. May be you try individual installation, if that is not the case with you currently. 

On Wed, Aug 1, 2018 at 5:42 PM, Md Mahabul Islam <mhbl...@gmail.com> wrote:

I had opened a big size CHGCAR ( VASP charge density file) using VESTA after that whenever I am launching VESTA it is showing the following dialog "the existing instance may be too busy to respond , please close any open dialogs and retry " I removed the existing version of vesta and reinstalled it but it is showing the same error. How to delete that instance permanently in my Ubuntu 18.04, please help.

Thanks in advance.

--

---
You received this message because you are subscribed to the Google Groups "VESTA users' list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vesta-discuss+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Cippo Lippo]

Saw the same error for the first time yesterday.

Terrible workaround is to run "sudo VESTA"

[Md Mahabul Islam]

May be you need to restart your system . For my case I deleted the soft link of VESTA in $Home/bin/ and reinstalled it freshly , created the soft link again at the same location. Then I restarted my computer and launched VESTA from terminal , it popped up a message saying 'deleted lock-file' and it is running fine now. I am posting this so that it may help someone.

[Colin Daniels]

For anyone else struggling with this, this error was resolved for me by manually finding and deleting the 'lock-file' myself which was located in my home directory and named '.VESTA3-user:0.pid ' where 'user' was my username. For whatever reason, VESTA (version 3.4.8) did not delete it on its own, and reinstalling/restarting did not work.