Big Sur Update Broke RumlogNG for me

[W2CLM]

Tom - I deleted the program and associated files from my machine and reloaded from the App Store. aside from losing all of my settings, The program now executes. Very strange.

Thank you for looking into this. Your support is second to none.

73 - Chris

[DL2RUM]

Reinstallation of the app should not fix a problem. Deleting the Preferences and other associated files could have solved it.
When it crashes again, please remember your last changes.

[DL2RUM]

Hoop, did you read that?

[W2CLM]

Tom -

I think I found what *may* have been causing it. After opening several windows to replicate my last setup, I found that opening "solar activity monitor" causes it to crash. If I reopen the program all works fine until adding that module. Hope this helps.

[DL2RUM]

This window works fine here, I have to investigate further.

[W2CLM]

Thank you, Tom.

[K9QJS]

Tom,

I completely uninstalled WSJT-X and RumLogNG, including all settings files. I used the Uninstaller from CleanMyMac which appears to have done a thorough job.

The problem continues, RumLogNG crashes while I was running WSJT-X and when transmitting from WSJT-X, intermittently.

Crash Log attached.

73
Hoop

[K9QJS]

After some troubleshooting, here is a new observation which may, or may not, be insightful.

1. I did five FT8 contacts in a row, all successful, and the screen focus never shifted away from WSJT-X.
2. I did one more FT8 contact, and this time, I used mouse cursor to highlight the "Name" field from RumLogNG to copy it into the WSJTX record that would be saved; I like to include "Name" in my QSOs and I use QRZ.com to pull the name from their database. So for these moments, the screen focus is RumLogNG. I do this most all the time, highlight and copy a name into the WSJTX record before saving.
While I was doing this highlighting, WSJTX continued along its semi-automated path, transmitting a receive report. And at that time, once again, RumLogNG crashed. Crash log attached.

Again, I know that this may, or may not be, significant.

73, Hoop

[DL2RUM]

You can stop posting crash reports, it's always the same. Unfortunately it points me in one direction without any relationship to your observations.
It seems only few users are affected.
Do you use a 'normal', file based logbook or the iCloud synced logbook?

[K9QJS]

Tom

Thanks for reviewing. I really appreciate your help. Yes, I do have my Logbook in the "cloud" ... it is on Dropbox. So that is something else for me to try. There is likely something unique in my configuration and use.

73
Hoop