Running Fedora 31. After installing an update this morning telescope driver crashed. Running on a different system and using all simulators also encountered a crash.
Attached log is from the system running simulators.

Upgraded:
cinnamon-settings-daemon-4.4.0-2.fc31.x86_64 geolite2-city-20191217-1.fc31.noarch
geolite2-country-20191217-1.fc31.noarch ibus-typing-booster-2.7.4-1.fc31.noarch
rpm-ostree-libs-2019.7-1.fc31.x86_64 compat-cfitsio3370-3.370-6.20.x86_64
indi-aagcloudwatcher-bleeding-1.8.1-2.22.x86_64 indi-apogee-bleeding-1.8.1-2.22.x86_64
indi-asi-bleeding-1.8.1-2.22.x86_64 indi-atik-2:1.26-3.21.x86_64
indi-dsi-bleeding-1.8.1-2.22.x86_64 indi-eqmod-bleeding-1.8.1-2.22.x86_64
indi-ffmv-bleeding-1.8.1-2.22.x86_64 indi-fishcamp-bleeding-1.8.1-2.22.x86_64
indi-fli-bleeding-1.8.1-2.22.x86_64 indi-gphoto-bleeding-1.8.1-2.22.x86_64
indi-maxdomeii-bleeding-1.8.1-2.22.x86_64 indi-mi-bleeding-1.8.1-2.22.x86_64
indi-nexstarevo-bleeding-1.8.1-2.22.x86_64 indi-qhy-bleeding-1.8.1-2.22.x86_64
indi-qsi-bleeding-1.8.1-2.22.x86_64 indi-sbig-bleeding-1.8.1-2.22.x86_64
indi-spectracyber-bleeding-1.8.1-2.22.x86_64 indi-sx-bleeding-1.8.1-2.22.x86_64
kstars-bleeding-3.3.9-5.2.x86_64 libASICamera-common-0.7.0503-1.21.noarch
libapogee-3.2-48.22.x86_64 libfishcamp-1.1-47.22.x86_64
libindi-bleeding-1.8.1-1.23.x86_64 libnova014-0.14.0-2.20.x86_64
libqhy-1:6.0.1-2.22.x86_64 libqsi-7.6.1-155.22.x86_64
libsbigudrv-2.1.3-156.22.x86_64 lupinix-indi-bleeding-1.0-218.20.noarch
qhy-firmware-1:6.0.1-2.22.noarch sbig-firmware-2.1.3-156.22.noarch

I have un-installed KStars and INDI, along with removing any references to the package/repo. Deleted the .indi and KStars directories to remove any configuration files and databases that I am aware of. Re-ininstalled following the directions in indilib.org/download/fedora.html for Fedora 31.
Everything left at default settings except for geographical location. Defined a local simulator profile with just indi_simulator_telescope and indi_simulator_cdd.

I still get the same result KStars log attached. Both the telescope and ccd simulator drivers fail just depends which one fails first.

Running indiserver directly does not provide more information.
tg@tcup ~]$ indiserver -vv -r 1 indi_simulator_telescope
2020-01-06T22:22:14: startup: indiserver -vv -r 1 indi_simulator_telescope
2020-01-06T22:22:14: Driver indi_simulator_telescope: pid=220415 rfd=3 wfd=6 efd=7
2020-01-06T22:22:14: listening to port 7624 on fd 4
2020-01-06T22:22:14: Driver indi_simulator_telescope: sending <getProperties version='1.7'/>

2020-01-06T22:22:14: Driver indi_simulator_telescope: read <getProperties device='GPS Simulator' name='GEOGRAPHIC_COORD'>
2020-01-06T22:22:14: Driver indi_simulator_telescope: snooping on GPS Simulator.GEOGRAPHIC_COORD
2020-01-06T22:22:14: Driver indi_simulator_telescope: read <getProperties device='GPS Simulator' name='TIME_UTC'>
2020-01-06T22:22:14: Driver indi_simulator_telescope: snooping on GPS Simulator.TIME_UTC
2020-01-06T22:22:14: Driver indi_simulator_telescope: read <getProperties device='Dome Simulator' name='DOME_PARK'>
2020-01-06T22:22:14: Driver indi_simulator_telescope: snooping on Dome Simulator.DOME_PARK
2020-01-06T22:22:14: Driver indi_simulator_telescope: read <getProperties device='Dome Simulator' name='DOME_SHUTTER'>
2020-01-06T22:22:14: Driver indi_simulator_telescope: snooping on Dome Simulator.DOME_SHUTTER
Child process 220415 died
2020-01-06T22:22:14: Driver indi_simulator_telescope: stderr EOF
2020-01-06T22:22:14: Driver indi_simulator_telescope: restart #1

I tried usig gdb variations but will spare you the details since none were successful.

I had previously (Dec 30) fetched the sources to try and debug why the scope did not always park when the roof closed. If I rebuild just the telescope and ccd simulator driver executables using those sources then they work with the rest of the install.

Looking at the original executable compared to the locally built one with debug info things look normal.

[tg@tcup 2020-01-06]$ file /bin/indi_simulator_ccd.bu
/bin/indi_simulator_ccd.bu: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=a8244b5d1afae751610c09cbdd3ca067be4ad103, for GNU/Linux 3.2.0, stripped

tg@tcup 2020-01-06]$ file /bin/indi_simulator_ccd
/bin/indi_simulator_ccd: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=49a57ab6e0a268a30dd865c6135e8294b2b6de4c, for GNU/Linux 3.2.0, with debug_info, not stripped

I am hoping an update will show up that fixes this issue. Otherwise I will remove indi kstars from the update cycle and do local builds to get going again.

To narrow it down a bit more.

Running the original install software using the rebuilt indi_simulator_ccd and indi_simulator_telescope, can now get the Ekos panel and indi tab displays. Added some additional simulator drivers from the original install and most of them are able to start.

dome, focuser, weather, astrometry, filter, gps.

The following ones fail
ccd, telescope, guide, GPhoto

It seems that I am getting mixed up attempting to do a local build from git clone github.com/indilib/indi.git when
subsequent package update installs depend on a different version of libindidriver than the local build used. The linking of the libindidriver appears to get confused. After changing the link below away from that used in the Dec 30 build, indiserver can now start the drivers.

-rw-r--r--. 1 root root 15969684 Dec 30 14:59 /usr/lib64/libindidriver.a
lrwxrwxrwx. 1 root root 18 Nov 8 2018 /usr/lib64/libindidriver.so -> libindidriver.so.1
lrwxrwxrwx. 1 root root 22 Jan 8 10:49 /usr/lib64/libindidriver.so.1 -> libindidriver.so.1.8.2
-rwxr-xr-x. 1 root root 1179792 Jan 7 00:08 /usr/lib64/libindidriver.so.1.8.1
-rwxr-xr-x. 1 root root 6799192 Dec 30 14:58 /usr/lib64/libindidriver.so.1.8.2


-rw-r--r--. 1 root root 15969684 Dec 30 14:59 /usr/lib64/libindidriver.a
lrwxrwxrwx. 1 root root 18 Nov 8 2018 /usr/lib64/libindidriver.so -> libindidriver.so.1
lrwxrwxrwx. 1 root root 33 Jan 8 13:24 /usr/lib64/libindidriver.so.1 -> /usr/lib64/libindidriver.so.1.8.1
-rwxr-xr-x. 1 root root 1179792 Jan 7 00:08 /usr/lib64/libindidriver.so.1.8.1
-rwxr-xr-x. 1 root root 6799192 Dec 30 14:58 /usr/lib64/libindidriver.so.1.8.2

Note that it is insufficient to correct the links in this manner, the next update even one that does not include a new library will change the link back to the older library (but higher version) created from the build procedure. Also there are other libraries that are impacted in the same manner. Correcting the links and also removing the debug image is the approach I am trying. Will need to find an approach to avoid a debug session crossing a release boundary if that is what is behind this.