I just did a diff between the old and the new kstarsrc and looked through the differences in settings.  Many of them would almost certainly not cause any crashes, such as the window size being different.  But one thing that stood out is that I had logging turned on in my kstarsrc that was causing a crash.  Specifically I had turned on Verbose logging with CCD checked.  I did some tests and that seems to cause a crash about 50% of the time, but without it being checked, it doesn't cause a crash, at least that I see with a couple of quick tests.  Can you check to see if you have that setting enabled when using the settings file that caused the crash?  Or maybe just try opening KStars, turning on CCD logging and see if that reliably crashes it for you?  If so, we may have found a major clue as to what causes my mysterious crash that was seemingly affecting just me.

Read More...

Hmm, Jean-Claude, you might be on to something.  I just tried your experiment, renaming my kstarsrc file and then tried starting an indiserver in KStars.  It crashed with the old one very easily, it didn't crash with the new one when I tried it a couple of times.  I'm not sure this was a well conducted experiment since I really need to do it many times in a more controlled way, but it's enough that I think you might have something here.  We should see if there is some setting that got saved in there that somehow affected it.  It's easy to check, it is literally a text file full of settings.

Read More...

So as in all the drivers, there is the "Options" tab where you can save, and load configurations in the INDI driver.  Is that what you are using to do the saving and loading?  I just tried it myself, though I don't have a weather device.  I was able to set the port, save the configuration, close the driver, then load it again. Now most drivers I have been familiar with in the past have automatically loaded the configuration. Is this one any different?

Read More...

Hi Peter,

I'm glad to hear it all worked out!  As for your two minor issues, I am not sure I can help with those right now.  I am surprised that the scope focal length and guide scope focal length do not save.  Did KStars crash before you restarted it?  Sometimes I note that if there is a crash and it doesn't get shut down properly, some preferences don't save.  But if that isn't the problem, I am not sure I know.  You might try posting in a new forum post.

For the second item, that is a new feature that I don't have any experience with.  I have had my head very deep in the building and packaging scripts and code and I haven't even gotten to play with any new features recently, (plus it is full moon).  You might want to ask Jasem or post in the general forum, since I think he is the one who might have worked on that.

Thanks,

Rob

Read More...

Scott Denning, very interesting.  Is this on INDIServer startup or on shutdown?  I remember there was a cross platform KStars crash that happened sometimes on indiserver shutdown, but I thought this new crash on startup that I started seeing just a few months ago was Mac only.  The. shutdown bug was addressed I believe.

Thanks,

Rob

Read More...

Hi JAMBBE,

Yes, with the first two betas that I posted there were packaging problems because of all the changes I had to make, my packaging script had some bugs.  The testers in this forum thread really helped me sort out the issues though with their testing, so I am most appreciative.  It should be good now, thanks for trying it out and reporting that it worked well.

There is a bug (I mentioned it earlier in the thread) that I see sometimes when starting an INDIServer where KStars sometimes but not always crashes and I don't know the cause.  This issue has existed for a few months and is not at all related to the INDI drivers issues that were reported with the betas above.  The INDIServer still starts successfully however, and if you restart kstars and reconnect to the INDIserver you already started everything works fine.  I wish I knew why this happens but I haven't figured it out yet.  It does seem that it might be dependent on Mac versions, since it happens on my Monterey Mac, but not on a Big Sur Mac that I tested it on the other day.  Now that a couple of more people can look into it with the work I did the last two weeks maybe we can investigate this further.

The other things you are mentioning with FITSViewer and and auto stretch are probably things that got changed in this version of KStars.  I am not familiar with any of the software changes this time around since I have been really focused on making all the changes so that we can get daily builds of KStars for Mac on the KDE Binary server.  They don't sound like Mac only issues, nor do they sound like anything I have been working on.  A good idea might be to post these questions/bugs in a new thread where more people might see it.  The only people who will look at this thread are those interested in the Mac beta build.

Please let me know if you notice any other issues and thank you for testing,

Rob
 

Read More...

John, the Scheduler is heavily dependent on dbus, so if dbus is not working, then that would make the scheduler not work properly.  So dbus was not working properly for you?  In this build, I am trying to use the default craft build of dbus instead of using the custom recipe that I made a few years ago.  So if dbus does not work, we may have to bring back my old recipe.

Read More...

David, the indi-3rdParty code should have been pulled today since my build script uses the most recent master of INDI and KStars as the default.

Read More...

David, maybe try restarting the computer?  Just a thought.  It looks like dbus got packaged up ok.

Read More...

Jean-Claude Excellent, please keep testing and see if there is anything else.

David - I will check and see why dbus might be causing an issue for you

Read More...

Ok thank you, please try this again:

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

This time there was a file with the same name that was getting copied into the dmg instead of the file I meant it to copy.  I think that should be fixed now.

As I said before, there were a LOT of changes and while it does work on my computer, I really need you guys :-). So thank you for testing.

Read More...

Thanks for testing again Jean-Claude.  This is definitely progress, but there still is an issue with ASI, but only in the packaged up version.  Thank you for bringing my attention to it.  I can replicate this issue since I just tested it, so it should be easier to diagnose.  I will upload another once I solve it.  It could be another issue in my script.

Read More...

Ok, second try, I think I fixed the issue.  Basically the drivers were all still linked to a folder on my computer because in my packaging script, I had made one small error.  Please check that it works now.

www.indilib.org/jdownloads/kstars/beta/kstars-3.5.7-beta2.dmg

Please check to see that the driver linking issue is fixed and please check for any other issues.

Read More...