OpenCPN Beta 5.5.1109 (RC1) Released

[hreuver]

The above post reads better with the attached pictures.
Faulty icon in the plugin dialog and a missing horizontal bar...

[hreuver]

Now the crash also works under Ubuntu 21.04 with Flatpak.


The error I see:
$ opencpn
Gtk-Message: 13:54:49.449: Failed to load module "appmenu-gtk-module"
Gtk-Message: 13:54:49.450: Failed to load module "canberra-gtk-module"
SENC: nCPU: 8 m_max_jobs :7
opencpn: ../../src/cairo-arc.c:189: _cairo_arc_in_direction: Assertion `angle_max >= angle_min' failed.


Here the GTK-message upto SENC:nCPU: 8 is shown at every boot.
The cairo message follows the crash.


Last rules from the log:
13:58:56.145 MESSAGE chartdb.cpp:1148 Creating new chart
13:58:56.145 MESSAGE chartdb.cpp:1265 Initializing Chart /home/hja/Charts/oesENC/sgl001CF71B-BE_DE_NL-2021-38/OC-49-E30ON3.oesenc
13:59:48.554 MESSAGE chart1.cpp:7374 LOGBOOK: 2021-11-14 12:59:48 UTC DR Lat 53.19860 Lon 5.14440
14:00:49.662 MESSAGE chart1.cpp:7374 LOGBOOK: 2021-11-14 13:00:49 UTC DR Lat 53.19860 Lon 5.14440
14:01:29.879 MESSAGE chcanv.cpp:2369 Metrics: m_display_size_mm: 1000 g_Platform->getDisplaySize(): 1920:1080
14:01:29.879 MESSAGE chcanv.cpp:2374 wxDisplaySize(): 1920 1080
14:01:29.879 MESSAGE oesenc_pi.cpp:1006 oesenc_pi: Calculated pix/mm = 1.92
14:01:29.919 MESSAGE glChartCanvas.cpp:732 BuildFBO 3
14:01:29.919 MESSAGE glChartCanvas.cpp:1217 OpenGL Framebuffer OK, size = 1918
14:01:29.961 MESSAGE glChartCanvas.cpp:732 BuildFBO 3
14:01:29.961 MESSAGE glChartCanvas.cpp:1217 OpenGL Framebuffer OK, size = 1918
14:01:29.971 MESSAGE glChartCanvas.cpp:732 BuildFBO 3
14:01:29.972 MESSAGE glChartCanvas.cpp:1217 OpenGL Framebuffer OK, size = 1918
14:01:29.987 MESSAGE glChartCanvas.cpp:732 BuildFBO 3
14:01:29.987 MESSAGE glChartCanvas.cpp:1217 OpenGL Framebuffer OK, size = 1918

[bdbcat]

Leigh...
re:
"OpenCPN doesn't start now."


Can you give more information on this?
Thanks
Dave

[bdbcat]

hreuver...


Will you please re-state your problem with tides?
Thanks
Dave

[hreuver]

First I had a problem with tidal information on an earlier beta release (laptop, Linux, Ubuntu 21.04).

OpenCPN-version something like 5.5.9xx.y.
With the upgrade to 5.5.1109.x I still had the problem.
Since Ubuntu 21.04 is not an LTS version I did not think this problem critical since the OS will probably be replaced/upgraded before the next sailing season.

To get a better evaluation of a system for navigation I therefore switched to Flatpak. On the first run I had no problems.

After documenting the oesenc-problem I ran into problems with the tidal screen again.
The steps I recall:
- remove the oesenc-plugin-4.3.0.0
- reinstall the oesenc-plugin-4.2.20.0
- upgrade to oesenc 4.3.0.0
Somehow I must have triggered an issue there, since next:
- select a tidal bar with right mouse-click => crash!
(earlier a popup screen appeared with the tidal information in OpenCPN, now I got a commandline on the screen instead of Tidal information and OpenCPN was instantly killed).
- message was the message:


$ flatpak run org.opencpn.OpenCPN
tk-Message: 17:25:36.284: Failed to load module "appmenu-gtk-module"
Gtk-Message: 17:25:36.284: Failed to load module "canberra-gtk-module"
SENC: nCPU: 8 m_max_jobs :7
opencpn: ../../src/cairo-arc.c:189: _cairo_arc_in_direction: Assertion `angle_max >= angle_min' failed.


Since this should be mainstream Linux I reported the problem.
But basically it seems some (trivial?) error checking is missing on opening the dialog.

System as mentioned: x86/64, i5, Ubuntu 21.04.
Freedesktop 21.08 on Flatpak version 1.10.2.
Harmonics used: ./harmonix 10/HARMONIX.idx (some French source)
Charts used: BE-NL-DE o-charts with USB dongle (same problem w/o dongle present).

[bdbcat]

hreuver...
re:
"Harmonics used: ./harmonix 10/HARMONIX.idx (some French source)"


Can you send me a copy (or link) to this harmonics set?


Also, let us confirm that this is an interaction with the oeSENC charts.
Please remove the oeSENC charts (temporarily), and try the same tidal station right click.



Thanks
Dave

[hreuver]

Harmonix file: see attachment. I added ".pdf" to the zip file.


When removing the o-charts flatpak still crashes on the tidal dialog.
(I disabled the plugin and removed the directories in the charts section.)

[verkerkbr]

it is working here in the flatpak version on my AMD64.

[spiv]

Originally Posted by bdbcat

spiv:

1. Please refresh your OpenCPN Beta PPA repo. The latest version of OCPN available there for Ubuntu 20.04 is:

opencpn_5.5.1109+6643+02c862e35~ubuntu20.04.1_amd6 4.deb

Thanks
Dave

Dave,
I tried my best to make the change you suggested, Googled and asked the Kubuntu community, but I cannot do that.
All edit that I can do is to this window:
.

Other thing I could do is to delete that PPA and add a new one, but must be in the same format: http://ppa......etc etc

[bdbcat]

spiv....


Time has overtaken us.
The current version on the repo is now 5.5.1115. This should be fine for you.


Good Luck
Dave

[houlejm]

Originally Posted by spiv

Dave,
I tried my best to make the change you suggested, Googled and asked the Kubuntu community, but I cannot do that.
All edit that I can do is to this window:
Attachment 248394.

Other thing I could do is to delete that PPA and add a new one, but must be in the same format: http://ppa......etc etc

Spiv


There are two PPA for opencpn one is for stable releases and the other for debugging beta releases.
Normally I leave the beta ppa disabled except when i want to test future versions like now.
See attached pictures.


Jean-Marie

[Atria]

OK looks like with the version 5.5.1116 I'm able to install the version 4.3.0.0 of oeSENC_PI which appeared in the updated catalog master. On the version 5.5.1109, the oeSENC plug in didn't show up although the catalog master was updated. When the oeSENC plugin was installed the assertion issue disappeared. BTW, when trying to install the oeSENC plugin manually with the command $ sudo apt install oesen_pi, the version 4.0 was installed. Since this version was known to be buggy, this is when the assersion issue started. Looks like all is fine now and I can use my oeSENC charts again.