Thanks for the patch. I can give it a try and report if building kstars is not too involved for my machine.

Keep you posted ASAP.

Gilles

OK, after sorting through a package that had changed name in Ubuntu Mate 20.04 LTS (kio), and waiting over 3.5 hours for kstars to build on my ODroid C4 (doesn't like "make -j 8" or even "make -j 4" so I had to "make" -> SLOW) I started kstars and, unfortunately, the patch did not help, the problem persisted. Too bad as I was hopeful things would work. Anyway, I re-ran kstars from the EKOS debugger and have attached the debug zip file for examination.

Thanks again for all the help on this issue.

Gilles

Stupid question: How do I start Ekos with debugger activated and where are the logs?

You don't need to start Ekos the an activated debugger. 'ekosdebugger' takes care of that.

Once you install ekos-debugger, you can start it (ekosdebugger, no hyphen) and it will open a window with 2 tabs, one for kstars and the other for INDI where you select the setup you want to debug (mount, guide, observatory..., profile, etc...). You start kstars and the debugging process pressing the 'play' button (top left). kstars will start soon after that. You then do whatever is needed to reproduce the problem you want to debug and once kstars crashes, the log files will have been generated and can be saved by pressing the 'disk' button on the top right.

Great tool for someone like me, not used to debugging.

Hope this help.

is it possible to start kstars, indi and all the devices separately from the console? If so how to do it.
I'm looking for a temporarily workaround.

Please check your email.

Just start kstars as usual, but edit your profile and remove the hook at "Auto Connect". Then start INDI, and the INDI control window will show up. There you can connect devices one by one. That should work both for local and remote setups....

Is it also possible to connect the devices one by one thru a script manually?