Posts: 62
Threads: 0
Joined: Jan 2020
Reputation:
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).
Posts: 341
Threads: 0
Joined: Apr 2016
Reputation:
23
@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.
Posts: 2,784
Threads: 59
Joined: Mar 2016
Reputation:
256
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.
Posts: 62
Threads: 0
Joined: Jan 2020
Reputation:
2
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.
Posts: 2,784
Threads: 59
Joined: Mar 2016
Reputation:
256
I did a quick test with no errors, thanks!
Posts: 62
Threads: 0
Joined: Jan 2020
Reputation:
2
Could you also check the OpenCPN flatpak issue?