Thank you Patrick! I will check that

Patrick, you might be on to something. I just looked at the previous DMG I made and all the links to libraries are relative links whereas somehow this current dmg has some absolute links which could very much cause a problem like this on somebody else's system but not mine since on mine the files exist. I don't think I changed anything in the build script that could cause this and I don't think INDI changed. So let me see if this is change in craft or if it has something to do with Ventura. I recently updated to Ventura.

This is why you guys are so important! Thanks!

Ok, I investigated the cause of the absolute links and it turns out it was due to a change I had made to the script between 3.6.1 and 3.6.2. I had added a couple of symbolic links in the script but I had made the links to the full path of the files by accident. So I just made a correction to it and built another dmg.

Please see if this one works. 3rd time is the charm I hope.

Thank you Patrick for the clue! Hopefully it was just the links and isn't something wrong with those two drivers.

www.indilib.org/jdownloads/kstars/beta/kstars-3.6.2-beta3.dmg

Thanks,

Rob

Rob - unfortunately I am getting the same result. I've attached log files for your review. Regrettably I don't have the technical chops to interpret the information.

I just downloaded and tried your lastest version Rob.
I also have the exact same problems I had earlier.

1. EKOS opens up fine, but it crashes to the desktop as soon as I try and connect the Moonlight Nitecrawler focuser/rotator, or AAG Cloudwatcher.
However, these devices load fine: Nexdome, ZWO EFW, ASI1600MM, SX CCD Lodestar, and iOptron CEM120. As long as I don't launch the Cloudwatcher or Nightcrawler it seems fine. But once I g back and try and load with of those two, KStars crashes to the desktop.

2. After crashing, NOTHING will load up until I reboot the Mac. If I skip rebooting, and just try to launch ANY device it will crash. But after a reboot, I can launch EKOS and load all those devices I listed above, except the Nitecrawler or Cloudwatcher. Those crash the whole system.

3. Version 3.6.2 beta (build 2022-10-28) works fine with all my devices.

Hi Peter,

In terms of your issue with rebooting: If you do get a crash while ekos is running, indiserver might still be running when it crashes KStars. a quick way to stop that would be to go to terminal and type "killall indiserver" and I would think that would have the same effect for you as the rebooting you described.

Based on the other part of what you said, it may be that there is some issue with the Moonlight driver and the AAG Cloudwatcher driver. I do have a moonlight, so I could probably run a test of that driver myself and see what happens.

Frederick, I will take a look at it and see if there are any other clues in your logs.

Sorry Rob. "killall indiserver" had no effect. After killing indiserver and relaunching KStars, it still crashes as soon as I try and connect to any device. I have to reboot to get it running again.

Ok based on your feedback, we are now thinking this must be an internal KStars or INDI bug. You pretty much ruled out it being a packaging issue. We are looking into it.

Thanks for the help. We will let you know when we have more info.

Hi Rob - I wanted to make sure you were aware that the KStars download site (edu.kde.org/kstars/) has the 3.6.2 version as the current release. I did try it and it still crashes when starting a profile. Perhaps consideration should be given for having the 3.6.1 release for Mac users posted on that site until 3.6.2 is able to run reliably.

I have run kstars-3.6.2-beta2.dmg on macOS 11.7.1.
It worked in a simulator profile.
It crashed repeatedly in my real profiles.
Another point : kstars-3.6.2-beta2 is not localised (es störrt mir aber nicht)
Thanks Rob

Yes definitely agree that we should not post the 3.6.2 version until we figure out what is going on with it. I will ask Jasem why it is posted.

Also, I did a bunch of testing last night with various devices and profiles and various pi’s. The only time I could get it to crash was when I tried to start a profile on a remote indiserver that was using an older indi. When kstars connected to it, it worked at first, but the minute I tried to take a picture it crashed. After experimenting to see why it crashed, I found that the image trains combo box was blank and was not editable. I am thinking that the cause of this is that there is some incompatibility between the older version of indi and image trains? The crash was caused for me because it tried to access a camera that did not exist in the image train.

So now I am wondering, for you guys that experienced crashes, did you get to the point where it connected and can you see if the image trains combo boxes in Ekos are blank?