Code :: Blocks tells you to start another instance, even if it is not.

Question

When I try to run Code :: Blocks, I get the following error message:

Another instance of the program is already running. Code :: Blocks is currently configured for only one instance to run.

You can access this setting in the menu item "Environment".

I had a similar problem before, for example, with. Google Chrome, when I did not close it correctly, but for Chrome I managed to find the lock file, delete it and solve this problem.

For Code :: Blocks, I looked around and tried several suggested solutions, but none of them worked:

• find the process ( ps -A | grep 'codeblocks' ) and kill the process

  I found that this process was unsuccessful, but it did not help to kill him.

• allow multiple instances of Settings in the Environment menu

  I can not start any instance in the first place, so I can not access the menu.

  I tried to run Code :: Blocks from the terminal using codeblocks --multiple-instances , but this parameter should have been left a while ago, as it is no longer recognized.

• I looked at some kind of lock file to try to delete it

  Unfortunately, I did not find anything like a lock file :(

Answer 1

Awful, it seems like I have this annoying habit of finding a solution within minutes of complaining about a problem, instead, in my phase of "looking for a solution."

I found a lock file to remove and fix the problem: removing /tmp/Code::Blocks-username fixes the problem.

Some additional solutions are outlined in the official Code :: Blocks forum , including how to change the settings from "allow single instance" to "allow multiple instances" without actually launching Code :: Blocks.

Answer 2

Follow these steps

• Go to Settings → Environment → General settings
• Uncheck Allow only one running instance ...
• Tick Use an already running instance ...
• Check Bring it on top afterwards