1- send system logs to the MAC OS people... who knows if they can help...
2- Use you mac only for remote desktop, raspberry will do all the job ( I know it can )
3- Do more tests, and share information is this forum...
4- Once, I send some logs to KDE developpers ...
5- try to update Kstars to 3.1
Guillem, we are the KStars developers. Unless the problem is from some other KDE program, we are the ones to talk to. There is no 3.1 for Mac OS yet because I haven't built the 3.1 DMG yet because I had an issue last week with the build. The build issue is not with KStars but with Craft and QT. I sent a message to the KDE folks about the issue and I am waiting for a response. I would not recommend sending a message to Apple, because they don't send them to us. It really doesn't do anything to help. But yes, the best idea is to post whatever information you find on this forum so I can look into it.
I took a closer look at your lldb log. This prints A LOT:
File "<string>", line 1, in <module> NameError: name 'run_one_line' is not defined Traceback (most recent call last)
Mine definitely does not do that. I did a google search for this and everybody seems to say that this is a python error. I found this result, and they have a possible solution for that at the bottom:
You can try that solution and see if it works. Maybe it will just prevent that from printing in the log so much, but if that error is occurring that much, it could explain the speed problem
yes, I noticed that print too.
Went to the page you linked me to, did the first two steps of the troubleshooting.
I'm weary of going further forward, ad I see a sudo command and I know those can bypass MacOS safeties and do damage
Do you suggest I keep going?
after reading more carefully what you wrote, I jumped directly to the fix they propose at the bottom of the page you linked me to.
pip install six
Then restarted KStars via the terminal
The issue about that line printing a lot is now gone, but Kstars is still sluggish and the computer freezes as described in previous posts.
I've tried a simple sequence with the simulators and it did not crash, but I'm still very worried about it crashing on me with real equipment connected.
Logs are attached (unfortunately I've been stupid enough not to save the log relative to six installation...)
Let me know you r thoughts
I've also seen this issue with the Mac Version of EKOS v3. Various things see to set off.
What version of Kstars/EKOS is in StellarMate firmware v1.3.1?
Is there going to be a v3.1 version of the Mac version anytime soon, this could be my issue. The version on the StellarMate itself seems to remain running, but it has other issues right now too, like EQMOD mount control (issue raised in another thread)
I only have v1.3 and would like to get a copy of this if possible please as I found v2.9.8 on the Mac and StellarMate to be pretty reliable and I'd like move back to while there are still reliability issues with v3.x
your last post prompted me to try and use KStars 2.9.8, which I had zipped before installing 3.0.0.
Guess what? No sluggish behaviour whatsoever.
Therefore my guess something has been broken when making 3.0.0.
I don't remember why I switched to 2.9.8, but I reckon it was something to do with flat fields not being captured as flats in 2.9.8, but I wouldn't bet my eyes on it.
May this help?
That sounds good, KStars 2.9.8 does work very well on Macs. There could be something wrong with 3.0.0, at least for your machine. I am currently using 3.0.0 and the only problem I think I currently have is the strange qt resolution bug that you mentioned with the Star Profile Viewer. I hope to look into this in the near future, possibly this weekend to see if I can't get 3.1 to build. Hopefully if I can produce a new DMG it won't have the same issues for you. But for now, yes 2.9.8 should be fine. I used that one for months.