Lock file incorrect permissions issue

[pinguino]

Lately whenever I build opencpn I encounter this error message when starting the opencpn executable. It happens on x86 and Rpi platforms. Does anyone know what's going on?

[coupdemistral]

same problem here. Brand new Dell XPS running Ubuntu 18. Cloned the opencpn.git repo , compiled and installed it without problems. Then getting the permission message every time I launch it

[cagney]

When downloading the source/cloning which branch are you using?
The "master" is in development and not suited for general consumption.
Don't expect support if that is what you are using.
The branch to use is "v5.0.x".

Thomas

[rastam4n]

Originally Posted by cagney

When downloading the source/cloning which branch are you using?
The "master" is in development and not suited for general consumption.
Don't expect support if that is what you are using.
The branch to use is "v5.0.x".

Thomas

Hello Thomas
I following these instructions https://opencpn.org/wiki/dokuwiki/do...ad_source_code

Is this the incorrect branch? I am experiencing the same challenges as the others above.
Kind regards
Peter

[AmericadelSur]

Hi, I have the same problem here. I am using the 5.0.522 version.

I did build the Debian version (I am using ChromeOS with the linux container), fixed some dependencies that were not there when compiling, and then I see this exact same error.

Did any of you find a solution? I tried doing chmod 777 to the folder, but I don't think thats the issue.

Thanks!

[cagney]

I think I found a way around this, thanks to starting an old Linux box......
OpenCPN does indeed create a lock-file in your home directory called "OpenCPN"

If you already have a file/folder called "OpenCPN" in your home directory, you get this message. At least on Linux, just click OK and go on, as nothing stops you from running multiple instances of O. Windows is a different story.

So the workaround is to rename your file/folder, called OpenCPN, to something else.

It is a bit strange to use a lock-file called "OpenCPN" in the users $HOME. I'll try to make sure this goes away to the next release, somehow...

Thomas

[AmericadelSur]

Thomas, thank you very much. As you said, I do have the OpenCPN directory, which has the OpenCPN build.

I renamed the folder and everything is working smoothly now. THANK YOU!

[transmitterdan]

It is fixed for the next release.

[brice3010]

Originally Posted by cagney

I think I found a way around this, thanks to starting an old Linux box......
OpenCPN does indeed create a lock-file in your home directory called "OpenCPN"

If you already have a file/folder called "OpenCPN" in your home directory, you get this message. At least on Linux, just click OK and go on, as nothing stops you from running multiple instances of O. Windows is a different story.

So the workaround is to rename your file/folder, called OpenCPN, to something else.

It is a bit strange to use a lock-file called "OpenCPN" in the users $HOME. I'll try to make sure this goes away to the next release, somehow...

Thomas

Confirmed: I had the same issue starting out of nowhere on OpenCPN 5.2.4. Solution; go to /home/pi/.opencpn/ and change the name of _OpenCPN_SILock to _OpenCPN_SILock_old