ok, please try again. It should work now. Sorry there have been multiple changes in the last couple of days that have been messing up my build script. First, there were some major craft changes. Then there was an issue with different versions of libraw. Then there was an issue with the qml directory getting changed. All of the changes will be good in the end, but temporarily, they caused some headaches.

Thanks,

Rob

OK, the crash logs were both different, I though Robert may have already deployed the changes. Guessing I am too eager. I will now try the newest.

Just installed 2.9.5. Tried to run it and it crashed. Log attached

edit - tried to open crash file, and it is corrupted. Re-attached as pdf

Yes, there were a couple of different issues. One issue is that the libraw version that craft is building is for some reason different than the libraw version that homebrew is building for INDI. So there was a version issue and one version was not getting included in the app bundle. I don't know why they want to build a different version with a different name, but it has caused a bit of a headache. The libraw issue would cause an error if you try to take a raw image with a camera. The other issue was that the qml files for the mountbox and the whats interesting window used to be included in the data directory, but now they are embedded in the app. This would cause an error when starting either INDI or the Whats interesting window. I am hoping that the dmg I posted a half hour ago addresses both of them.

Does this crash happen immediately on startup or do you do something first. This doesn't look like either of the issues I just addressed.

Same here. I completely removed KStars via App Cleaner, including the ~/Libary/Application Support/Kstars (or kstars I am not sure about the capital K) directory and reinstalled. Immediate crash. I have attached the crash log.

So the crash log isn't helping because it isn't obvious like the libraw error that was so clearly spelled out.. Can you run KStars from the command line in a terminal window and get the text that prints in the terminal or get a kstars log of the session?

Sure:

Installed 2.9.5 in my other machine (same work flow, scrub old program with appclean first).
console log shows same error as on my last post.

Any command line options you'd like me to add to increase the verbosity of the output?

ah, thank you, thats much better info.

no, I think I might have found a lead based on what you said via a google search.