Does anyone know how to get this to open in macOS Big Sur? It won't let me launch the app because it doesn't recognize the developer.

Does right-click and "Open" work?

Also, moving the LNM extracted folder out of Downloads might be the fix as far as I remember.

Right click and open fixes the problem but now the app becomes unresponsive after launch and I have to force quit it. I am running macOS Big Sur Beta 7.

I have moved both LNM and LNM Connect to my Applications folder.

Edited September 18, 20205 yr by captain420

I do not have BigSur around. I tested with a Catalina VM and on an old Sierra macbook.

Can you dig out the LNM log and send it to me? I'd like to see where LNM stops. The log file is a bit hidden and hard to find on macOS when LNM is not running.

Also: Try to rename or delete the folder "ABarthel" which has all the settings and databases. Just in case something is wrong there.

File locations are explained here:

https://www.littlenavmap.org/manuals/littlenavmap/release/2.6/en/FILES.html#files

Alex

You're right, it's very difficul to locate the log files. I have tried going into the /var/folders/ location and have seen weird folders, but they don't seem to have anything. Certain folders in there gave me a permission denied. Also tried deleting the ABarthel folder and it's still the same.

Edited September 20, 20205 yr by captain420

Open a terminal and try this to find the log file:

find /private/var/folders -name "abarthel-*.log" 2> /dev/null

Once found you can copy the path and open it in TextEdit.

Alex

tried that command and it returned no results. I did this while having LNM running.

Maybe a change in BigSur. No idea how to fix this. You have another computer to run this networked?

I have LNM 2.6.0 beta installed on my Windows machine and it runs fine. Just can't get it to run on my macbook.

I would like to use LNM on my macbook, since I use my Windows machine for MSFS in fullscreen mode. That way I can still use LNM while flying.

The same happens when I try to open Little Navconnect. However I was able to find the log file for that. Perhaps you can look at that and determine why LNM won't launch either.

I sent you a PM.

 

Edited September 25, 20205 yr by captain420

BTW: I remember a similar issue in Catalina where LNM was stored in a translocation folder and could not save files properly. I'm not sure but this apparently happens if you open the program from the download folder. Try to move it to another place like $HOME/Programs or such.

Also, try to clear the quarantine bit for "Little Navmap.app":

sudo xattr -r -d com.apple.quarantine *

This command is run as admin. Make sure to run it in the right folder inside "Little Navmap.app". X-Plane users have to use this to clear their plugins.

Alex

3 minutes ago, albar965 said:

BTW: I remember a similar issue in Catalina where LNM was stored in a translocation folder and could not save files properly. I'm not sure but this apparently happens if you open the program from the download folder. Try to move it to another place like $HOME/Programs or such.

Also, try to clear the quarantine bit for "Little Navmap.app":

sudo xattr -r -d com.apple.quarantine *

This command is run as admin. Make sure to run it in the right folder inside "Little Navmap.app". X-Plane users have to use this to clear their plugins.

Alex

My Little Navmap.app is in ~/Applications

and I tried running tha command inside of the Little Navmap.app/ folder and it still hangs when I launch the app. Still no log file for LNM. I only see a log file for Littlle navconnect.

 

Edited September 25, 20205 yr by captain420

I'm stupid. 😞 It's so easy to get a log.

Open a terminal and run below from the command line:

~/Programs/Little\ Navmap.app/Contents/MacOS/littlenavmap > ~/lnm.log 2>&1

Note the backslash after "Little" to escape the space.
">" redirects all output to the file lnm.log in your home folder.
"2>&1" sends error messages to this log too.
 

Alex

Edited September 25, 20205 yr by albar965

This is the contents of lnm.log

static void NavApp::initSplashScreen()

Edited September 25, 20205 yr by captain420

One line only?

Gimme some time. I'll check after the 2.6.1.beta. A bit overworked here ...

Alex, yes only that one line in the entire log file. No problem! Take your time.