This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
AvNav in OpenPlotter 3
#1
Exclamation 
@wellenvogel

There are some problems with AvNav in OpenPlotter 3 alpha.

- OpenCPN flatpak does not run when the o-charts plugin of AvNav is running: https://forum.openmarine.net/showthread....6#pid22906

- AvNav kills signal k server: https://forum.openmarine.net/showthread....6#pid22606

any idea?
Reply
#2
I guess it mainly goes to @e-sailing...
I already discussed a bit with him. We found the last version of avnav-installer to be broken (all the user pi stuff).
Killing the signalK server is nothing AvNav really can do - so again only the installer could....

For the OpenCPN flatpack issue:
I have no idea.
Do we have more info beside the one post ?
Currently I most probably do not really have a chance to test this (traveling for a while). What I could imagine :
(1) some LD_LIBRARY_PATH issues
(2) some clashes in display settings (avnav-ocharts uses Xvfb - this should normally not interfere - but you never know).
Reply
#3
@Sailoog
Yes.
The problem with signalk is caused by openplotter-avnav when using another user than pi. Fix in work.
There are some other fixes which should be changed in 3.0.5 already.
Reply
#4
OK, thanks.
Latest Raspberry OS versions include tools to change the default user pi at first start, so I guess we will no longer see the user pi around.
Reply
#5
We found the issue for OpenCPN flatpack to being able to run with avnav-ocharts plugin running...
Seems to be a bit similar to https://github.com/flatpak/flatpak/issues/3357.
So I will change the avnav-ocharts-provider to use a Xvfb display number different from 99 (the default). Most probably I will make this configurable to be prepared.
On the other hand it's a bit unclear what flatpak is doing there...
Reply
#6
Ok, now the installer 3.0.6 is available that should fix the user issues.
Additionally a new version of the AvNav ocharts-plugin (20220605) is available that should fix the OpenCPN flatpak issue.
Reply
#7
I did a quick test with no errors, thanks!
Reply
#8
Could you also check the OpenCPN flatpak issue?
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)