Page 1 of 1

RUMlogNG unable to load logbook on Sequoia 15.0

Posted: Sun 22. Sep 2024, 17:18
by DJ9PZ
Hello,

after upgrading MacOS to Sequoia 15.0, RUMlogNG is unable to load any logbook: "The file couldn't be opened.".
It doesn't matter, where the file is located (local, iCloud).

Running RUMlogNG from shell yields among other messages:

2024-09-22 19:02:10.182 RUMlogNG[61746:2199285] ResolvingBookmarkData Error while loading: The file couldn’t be opened.
2024-09-22 19:02:10.182 RUMlogNG[61746:2199285] Failed to open log: Nix da
2024-09-22 19:02:10.182 RUMlogNG[61746:2199285] Failed to open log: Nix da
2024-09-22 19:02:10.182 RUMlogNG[61746:2199285] Failed to open log: Nix da
2024-09-22 19:02:10.182 RUMlogNG[61746:2199285] Failed to open log: Nix da


Creating a new logbook succeeds, but adding a QSO shows an error pop up on save:

Database Error.
Error while saving the QSO


It seems something is not yet working correctly on Sequoia.

Thanks in advance!

73 de Arnd DJ9PZ/AB2QP

Re: RUMlogNG unable to load logbook on Sequoia 15.0

Posted: Sun 22. Sep 2024, 17:34
by DL2RUM
Reboot your Mac.

Re: RUMlogNG unable to load logbook on Sequoia 15.0

Posted: Sun 22. Sep 2024, 17:41
by DJ9PZ
Thanks Tom,
reboot solved the problem!

73 de Arnd DJ9PZ/AB2QP

Re: RUMlogNG unable to load logbook on Sequoia 15.0

Posted: Thu 26. Sep 2024, 20:22
by DJ9PZ
Hello Tom,

unfortunately, the problem reoccurs after some time (next day?) or after a couple of invocations. I haven't been able to determine any correlation. A reboot solves the problem for some time, but I'm not really used to rebooting my Mac regularily.

Vy 73, Arnd DJ9PZ/AB2QP

Re: RUMlogNG unable to load logbook on Sequoia 15.0

Posted: Wed 2. Oct 2024, 22:20
by DJ9PZ
Hello Tom,

unfortunately, trying to start RUMlogNG on Sequoia 15.0 has a 50:50 chance of requiring a MacOS reboot (both on my Mac mini M1 as well as my MacBook Air M1). Any chance that there will be a solution coming in one of the next updates? I would be glad to provide further information or logs if this would help to solve this annoying problem.

Vy 73, Arnd DJ9PZ/AB2QP