Preliminary tests (not thorough but connects/disconnects, GOTOs, few shutdown and restart INDI/EKOS/KStars) and I haven't had a crash. I will try to test as much as I can and provide more feedback.

This is looking very good. Thanks for all the efforts.

Everything still working fine after system shutdown/reboot.

I would love to go test under the stars tonight but, like when getting new astronomical equipment, debugging astronomical software seems to bring the clouds! LOL but

If you all want another tester, hit me up, I can easily reproduce locally. I am running on an x64 Ubuntu 18.04 system.

Cloudy here as well, so not doing much but preparing for a clear night.

Same here - I can test and blow stuff up if I have a fairly easy way to install - running SM OS on PI4 with no dev environment - so basic install from PPA

PPA builds are now running and StellarMate update is coming as well in 1-2 hours.

Great - I'll hammer at it as soon as it loads

Works now, thank you. I rebuilt from source, ran from the build directory, all worked fine. I could create a new configuration, configure all devices and save the changes. I could then relaunch that app, and it still worked (with changes). I rebooted the laptop where it runs, reconnected the devices and they all came up like they should.

I also did a "clean" and "install" and that worked as well.

Thanks, it doesn't look like a really easy fix, the nuance of the Blocking vs. Non-Blocking couldn't have been an easy one to figure out.

Installed with:

sudo apt-get install indi-full kstars-bleeding resulting in Kstars 3.5.0 beta.

Tried several start/stops and no more crashes.

Thanx all especially Jasem for the effort put into it.

update on buster does not get me anything new so still crashing - attemped to add the indi nightly PPA but not able on stellarmate os:

stellarmate@stellarmate:~ $ sudo apt-get indi-full kstars-bleeding
E: Invalid operation indi-full
stellarmate@stellarmate:~ $ sudo apt-get install indi-full kstars-bleeding
Reading package lists... Done
Building dependency tree
Reading state information... Done
kstars-bleeding is already the newest version (6:3.5.0-nightly~202008280113).
indi-full is already the newest version (1.8.6-stable~202007211053).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
stellarmate@stellarmate:~ $ sudo apt-add-repository ppa:mutlaqja/indinightly
Traceback (most recent call last):
File "/usr/bin/apt-add-repository", line 95, in <module>
sp = SoftwareProperties(options=options)
File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 109, in __init__
self.reload_sourceslist()
File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 599, in reload_sourceslist
self.distro.get_sources(self.sourceslist)
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 93, in get_sources
(self.id, self.codename))
aptsources.distro.NoDistroTemplateException: Error: could not find a distribution template for Raspbian/buster

what is the magic on buster to getting indi nightly?....add ing the PPA on my other Ubuntu box works but Buster will not add the PPA

Hi,
if you're using Stellarmate OS and stellarmate APP, you can switch to beta update to have it.
Regards

Yeah...SM app and direct on the PI4 at console both telling me I am up to date - the Kstars is 3.5.0 beta and appears to pull from the kstars nightly, but indi is saying stable - somehow I need to change that I assume

So...it looks like things updated after a few attempts via the SM app - I was able to connect and run via the app....then switched to local and am now up and stable - Build: 2020-08-28T01:13:29Z....can someone confirm if that is the expected timestamp - thanks