www.dl2rum.de

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 ...

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

Thanks Tom,
reboot solved the problem!

73 de Arnd DJ9PZ/AB2QP

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 ...

Hello Tom,

thanks for your reply!

How is the QSO data passed from WSJT-X to RUMlogNG instead? Where does the problem regarding the incorrect mapping of the fields happen between WSJT-X and RUMlogNG?

73 Arnd DJ9PZ/AB2QP

Hello, I'm running RUMlogNG (Version 5.16 (643)) and WSJT-X (v2.7.1-devel 20240202 improved PLUS) on macOS Sonoma 14.5 (MacMini M1 and MacBook Air M1). I've specified user defined logging fields in RUMlogNG (OPERATOR, STATION_CALLSIGN, MY_GRIDSQUARE, TIME_ON) and enabled "Save QSOs to logbook" and ...