Hello,

I think the two biggest items that make or break an automated session are GPSD and CCD. When both go down, ouch. I opened this in AstroBerry Raspbian. I am not finding the source of this error. Reinstalling indi_gpsd and indi_qhy does not resolve this error. EKOS claims that the GPS is powered off. I have reviewed every GPSD config file for any misinformation. GPSMON works. CGPS works. Indi_gpsd produces this error.

2020-08-17T00:49:37: Driver indi_gpsd: indi_gpsd: symbol lookup error: indi_gpsd: undefined symbol: _ZN4INDI13DefaultDeviceD2Ev

This looks like dead code being accessed. This error does not show up in the AstroRoot folder. What could produce this error?

Hello,

I used this command.

c++filt _ZN4INDI13DefaultDeviceD2Ev

It yeilded this output.

INDI::DefaultDevice::~DefaultDevice()

Now, to find the file this is in.

Hello,

Using Device within KSTARS, I have captured the output here. One question is with indi_gpsd. Where does indi_gpsd get its device information?

This looks like the gps InDI driver is reading an empty file. A search for indi_gpsd.service does not show a configuration file. EOF looks like an empty file.

I removed 127.0.0.1 for gpsd. Yet, I see it listed here. It must be reading a config file.

2020-08-21T15:28:27: startup: /usr/bin/indiserver -v -p 7624 -m 300 -r 0 -f /tmp/indififo98dfd71f
2020-08-21T15:28:27: listening to port 7624 on fd 3
FIFO: start indi_gpsd -n "GPSD"
With name: GPSD
FIFO: Starting driver indi_gpsd
2020-08-21T15:28:27: Driver indi_gpsd: pid=1676 rfd=4 wfd=7 efd=8
2020-08-21T15:28:27: Client 5: new arrival from 127.0.0.1:41912 - welcome!
2020-08-21T15:28:27: Driver indi_gpsd: indi_gpsd: symbol lookup error: indi_gpsd: undefined symbol: _ZN4INDI13DefaultDeviceD2Ev
2020-08-21T15:28:27: Driver indi_gpsd: stderr EOF
2020-08-21T15:28:27: Driver indi_gpsd: Terminated after #0 restarts.
Child process 1676 died
2020-08-21T15:28:30: Client 4: new arrival from 127.0.0.1:41920 - welcome!
FIFO: stop indi_gpsd -n "GPSD"
With name: GPSD
dp->name: indi_gpsd - tDriver: indi_gpsd
FIFO: start indi_gpsd -n "GPSD"
With name: GPSD
FIFO: Starting driver indi_gpsd
2020-08-21T15:28:31: Driver indi_gpsd: pid=1684 rfd=6 wfd=9 efd=10
2020-08-21T15:28:31: Driver indi_gpsd: indi_gpsd: symbol lookup error: indi_gpsd: undefined symbol: _ZN4INDI13DefaultDeviceD2Ev
2020-08-21T15:28:31: Driver indi_gpsd: stderr EOF
2020-08-21T15:28:31: Driver indi_gpsd: Terminated after #0 restarts.
Child process 1684 died

This kind of error is usually caused by a 3rd-party driver being compiled against different core INDI-library than is currently in the system and recompiling the driver should help. This is due to the way C++ compilers handle class inheritance and any change in the base class (in this case DefaultDevice) may cause symbols to change and not match what the driver expects anymore so they should always be kept in sync.

Hello Jpaana,

Thank you for the pointer. This doesn’t look like a fixable issue. Is that what I read?

What are some options? Download and recompile?

Hello,

Recompiling did not fix the GPSD error. QHYCCD error did not get fixed. This almost looks like it needs a config file.

If recompilation didn't help then it's probably an older duplicate copy of the library or driver that is conflicting. If you run "ldd /full/path/to/your/indi_gpsd" or "ldd /full/path/to/your/indi_qhy_ccd", it should give a list of libraries it's loading for that particular binary and also if it can't find a symbol. Something like:
linux-vdso.so.1 (0x00007ffcaa30a000)
libindidriver.so.1 => /usr/lib/x86_64-linux-gnu/libindidriver.so.1 (0x00007f33a4ee1000)
libgps.so.26 => /usr/lib/x86_64-linux-gnu/libgps.so.26 (0x00007f33a4ebc000)
and so on, a lot of lines. This is from an x64 machine, but the principle the same for ARM too. The line to pay attention here is that libinidriver.so.1 which is where the missing symbol should be. If it points to an unexpected place and not the system library (for example /usr/local/lib/) then that's the problem. There should only be one copy of the library and driver in the system and preferably compiled from same source to avoid mixing versions up.

Also command "which indi_gpsd" shows where it's trying to load the driver from so that's worth checking if there is an extra copy.

Hello jpaana,

Thank you for the pointers. I appreciate the commands. I was reviewing the .h files for missing libraries. I found a few, GTK3 was one. I added then recompiled. When I get back home, I will see what ldd has to say.

Hello,

astroberry@astroberry:~ $ ldd /usr/bin/indi_gpsd
linux-vdso.so.1 (0xbefd0000)
/usr/lib/arm-linux-gnueabihf/libarmmem-${PLATFORM}.so => /usr/lib/arm-linux-gnueabihf/libarmmem-v7l.so (0xb6f7e000)
libindidriver.so.1 => /usr/lib/arm-linux-gnueabihf/libindidriver.so.1 (0xb6dec000)
libindiAlignmentDriver.so.1 => /usr/lib/arm-linux-gnueabihf/libindiAlignmentDriver.so.1 (0xb6dc4000)
libgps.so.23 => /usr/lib/arm-linux-gnueabihf/libgps.so.23 (0xb6d9a000)
libnova-0.16.so.0 => /usr/lib/arm-linux-gnueabihf/libnova-0.16.so.0 (0xb6a13000)
librt.so.1 => /lib/arm-linux-gnueabihf/librt.so.1 (0xb69fc000)
libstdc++.so.6 => /usr/lib/arm-linux-gnueabihf/libstdc++.so.6 (0xb68b5000)
libm.so.6 => /lib/arm-linux-gnueabihf/libm.so.6 (0xb6833000)
libgcc_s.so.1 => /lib/arm-linux-gnueabihf/libgcc_s.so.1 (0xb6806000)
libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0xb66b8000)
/lib/ld-linux-armhf.so.3 (0xb6fa9000)
libusb-1.0.so.0 => /lib/arm-linux-gnueabihf/libusb-1.0.so.0 (0xb6693000)
libpthread.so.0 => /lib/arm-linux-gnueabihf/libpthread.so.0 (0xb6669000)
libcfitsio.so.7 => /usr/lib/arm-linux-gnueabihf/libcfitsio.so.7 (0xb63da000)
libz.so.1 => /lib/arm-linux-gnueabihf/libz.so.1 (0xb63af000)
libjpeg.so.62 => /usr/lib/arm-linux-gnueabihf/libjpeg.so.62 (0xb636a000)
libfftw3.so.3 => /usr/lib/arm-linux-gnueabihf/libfftw3.so.3 (0xb626c000)
libdl.so.2 => /lib/arm-linux-gnueabihf/libdl.so.2 (0xb6259000)
libgsl.so.23 => /usr/lib/arm-linux-gnueabihf/libgsl.so.23 (0xb604e000)
libgslcblas.so.0 => /usr/lib/arm-linux-gnueabihf/libgslcblas.so.0 (0xb600d000)
libdbus-1.so.3 => /lib/arm-linux-gnueabihf/libdbus-1.so.3 (0xb5fbc000)
libbluetooth.so.3 => /usr/lib/arm-linux-gnueabihf/libbluetooth.so.3 (0xb5f8c000)
libudev.so.1 => /lib/arm-linux-gnueabihf/libudev.so.1 (0xb5f5c000)
libcurl-gnutls.so.4 => /usr/lib/arm-linux-gnueabihf/libcurl-gnutls.so.4 (0xb5eda000)
libbz2.so.1.0 => /lib/arm-linux-gnueabihf/libbz2.so.1.0 (0xb5eba000)
libsystemd.so.0 => /lib/arm-linux-gnueabihf/libsystemd.so.0 (0xb5e1d000)
libnghttp2.so.14 => /usr/lib/arm-linux-gnueabihf/libnghttp2.so.14 (0xb5dee000)
libidn2.so.0 => /usr/lib/arm-linux-gnueabihf/libidn2.so.0 (0xb5dc2000)
librtmp.so.1 => /usr/lib/arm-linux-gnueabihf/librtmp.so.1 (0xb5d99000)
libssh2.so.1 => /usr/lib/arm-linux-gnueabihf/libssh2.so.1 (0xb5d63000)
libpsl.so.5 => /usr/lib/arm-linux-gnueabihf/libpsl.so.5 (0xb5d43000)
libnettle.so.6 => /usr/lib/arm-linux-gnueabihf/libnettle.so.6 (0xb5cff000)
libgnutls.so.30 => /usr/lib/arm-linux-gnueabihf/libgnutls.so.30 (0xb5b5c000)
libgssapi_krb5.so.2 => /usr/lib/arm-linux-gnueabihf/libgssapi_krb5.so.2 (0xb5b12000)
libkrb5.so.3 => /usr/lib/arm-linux-gnueabihf/libkrb5.so.3 (0xb5a57000)
libk5crypto.so.3 => /usr/lib/arm-linux-gnueabihf/libk5crypto.so.3 (0xb5a17000)
libcom_err.so.2 => /lib/arm-linux-gnueabihf/libcom_err.so.2 (0xb5a04000)
libldap_r-2.4.so.2 => /usr/lib/arm-linux-gnueabihf/libldap_r-2.4.so.2 (0xb59af000)
liblber-2.4.so.2 => /usr/lib/arm-linux-gnueabihf/liblber-2.4.so.2 (0xb5993000)
liblzma.so.5 => /lib/arm-linux-gnueabihf/liblzma.so.5 (0xb5962000)
liblz4.so.1 => /usr/lib/arm-linux-gnueabihf/liblz4.so.1 (0xb5936000)
libgcrypt.so.20 => /lib/arm-linux-gnueabihf/libgcrypt.so.20 (0xb585c000)
libunistring.so.2 => /usr/lib/arm-linux-gnueabihf/libunistring.so.2 (0xb56e0000)
libhogweed.so.4 => /usr/lib/arm-linux-gnueabihf/libhogweed.so.4 (0xb56a1000)
libgmp.so.10 => /usr/lib/arm-linux-gnueabihf/libgmp.so.10 (0xb5628000)
libp11-kit.so.0 => /usr/lib/arm-linux-gnueabihf/libp11-kit.so.0 (0xb5523000)
libtasn1.so.6 => /usr/lib/arm-linux-gnueabihf/libtasn1.so.6 (0xb5503000)
libkrb5support.so.0 => /usr/lib/arm-linux-gnueabihf/libkrb5support.so.0 (0xb54e9000)
libkeyutils.so.1 => /lib/arm-linux-gnueabihf/libkeyutils.so.1 (0xb54d5000)
libresolv.so.2 => /lib/arm-linux-gnueabihf/libresolv.so.2 (0xb54b1000)
libsasl2.so.2 => /usr/lib/arm-linux-gnueabihf/libsasl2.so.2 (0xb548a000)
libgpg-error.so.0 => /lib/arm-linux-gnueabihf/libgpg-error.so.0 (0xb5460000)
libffi.so.6 => /usr/lib/arm-linux-gnueabihf/libffi.so.6 (0xb5448000)

astroberry@astroberry:~ $ ldd /usr/bin/indi_qhy_ccd
linux-vdso.so.1 (0xbec90000)
/usr/lib/arm-linux-gnueabihf/libarmmem-${PLATFORM}.so => /usr/lib/arm-linux-gnueabihf/libarmmem-v7l.so (0xb6f4f000)
libindidriver.so.1 => /usr/lib/arm-linux-gnueabihf/libindidriver.so.1 (0xb6dbd000)
libindiAlignmentDriver.so.1 => /usr/lib/arm-linux-gnueabihf/libindiAlignmentDriver.so.1 (0xb6d95000)
libcfitsio.so.7 => /usr/lib/arm-linux-gnueabihf/libcfitsio.so.7 (0xb6b06000)
libqhyccd.so.20 => /usr/lib/arm-linux-gnueabihf/libqhyccd.so.20 (0xb68e7000)
libusb-1.0.so.0 => /lib/arm-linux-gnueabihf/libusb-1.0.so.0 (0xb68c2000)
libpthread.so.0 => /lib/arm-linux-gnueabihf/libpthread.so.0 (0xb6898000)
librt.so.1 => /lib/arm-linux-gnueabihf/librt.so.1 (0xb6881000)
libstdc++.so.6 => /usr/lib/arm-linux-gnueabihf/libstdc++.so.6 (0xb673a000)
libm.so.6 => /lib/arm-linux-gnueabihf/libm.so.6 (0xb66b8000)
libgcc_s.so.1 => /lib/arm-linux-gnueabihf/libgcc_s.so.1 (0xb668b000)
libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0xb653d000)
/lib/ld-linux-armhf.so.3 (0xb6f87000)
libnova-0.16.so.0 => /usr/lib/arm-linux-gnueabihf/libnova-0.16.so.0 (0xb61b6000)
libz.so.1 => /lib/arm-linux-gnueabihf/libz.so.1 (0xb618b000)
libjpeg.so.62 => /usr/lib/arm-linux-gnueabihf/libjpeg.so.62 (0xb6146000)
libfftw3.so.3 => /usr/lib/arm-linux-gnueabihf/libfftw3.so.3 (0xb6048000)
libdl.so.2 => /lib/arm-linux-gnueabihf/libdl.so.2 (0xb6035000)
libgsl.so.23 => /usr/lib/arm-linux-gnueabihf/libgsl.so.23 (0xb5e2a000)
libgslcblas.so.0 => /usr/lib/arm-linux-gnueabihf/libgslcblas.so.0 (0xb5de9000)
libcurl-gnutls.so.4 => /usr/lib/arm-linux-gnueabihf/libcurl-gnutls.so.4 (0xb5d67000)
libbz2.so.1.0 => /lib/arm-linux-gnueabihf/libbz2.so.1.0 (0xb5d47000)
libudev.so.1 => /lib/arm-linux-gnueabihf/libudev.so.1 (0xb5d17000)
libnghttp2.so.14 => /usr/lib/arm-linux-gnueabihf/libnghttp2.so.14 (0xb5ce8000)
libidn2.so.0 => /usr/lib/arm-linux-gnueabihf/libidn2.so.0 (0xb5cbc000)
librtmp.so.1 => /usr/lib/arm-linux-gnueabihf/librtmp.so.1 (0xb5c93000)
libssh2.so.1 => /usr/lib/arm-linux-gnueabihf/libssh2.so.1 (0xb5c5d000)
libpsl.so.5 => /usr/lib/arm-linux-gnueabihf/libpsl.so.5 (0xb5c3d000)
libnettle.so.6 => /usr/lib/arm-linux-gnueabihf/libnettle.so.6 (0xb5bf9000)
libgnutls.so.30 => /usr/lib/arm-linux-gnueabihf/libgnutls.so.30 (0xb5a56000)
libgssapi_krb5.so.2 => /usr/lib/arm-linux-gnueabihf/libgssapi_krb5.so.2 (0xb5a0c000)
libkrb5.so.3 => /usr/lib/arm-linux-gnueabihf/libkrb5.so.3 (0xb5951000)
libk5crypto.so.3 => /usr/lib/arm-linux-gnueabihf/libk5crypto.so.3 (0xb5911000)
libcom_err.so.2 => /lib/arm-linux-gnueabihf/libcom_err.so.2 (0xb58fe000)
libldap_r-2.4.so.2 => /usr/lib/arm-linux-gnueabihf/libldap_r-2.4.so.2 (0xb58a9000)
liblber-2.4.so.2 => /usr/lib/arm-linux-gnueabihf/liblber-2.4.so.2 (0xb588d000)
libunistring.so.2 => /usr/lib/arm-linux-gnueabihf/libunistring.so.2 (0xb5711000)
libhogweed.so.4 => /usr/lib/arm-linux-gnueabihf/libhogweed.so.4 (0xb56d2000)
libgmp.so.10 => /usr/lib/arm-linux-gnueabihf/libgmp.so.10 (0xb5659000)
libgcrypt.so.20 => /lib/arm-linux-gnueabihf/libgcrypt.so.20 (0xb557f000)
libp11-kit.so.0 => /usr/lib/arm-linux-gnueabihf/libp11-kit.so.0 (0xb547a000)
libtasn1.so.6 => /usr/lib/arm-linux-gnueabihf/libtasn1.so.6 (0xb545a000)
libkrb5support.so.0 => /usr/lib/arm-linux-gnueabihf/libkrb5support.so.0 (0xb5440000)
libkeyutils.so.1 => /lib/arm-linux-gnueabihf/libkeyutils.so.1 (0xb542c000)
libresolv.so.2 => /lib/arm-linux-gnueabihf/libresolv.so.2 (0xb5408000)
libsasl2.so.2 => /usr/lib/arm-linux-gnueabihf/libsasl2.so.2 (0xb53e1000)
libgpg-error.so.0 => /lib/arm-linux-gnueabihf/libgpg-error.so.0 (0xb53b7000)
libffi.so.6 => /usr/lib/arm-linux-gnueabihf/libffi.so.6 (0xb539f000)

Ok. I will be checking each directory to see if a Linked support driver was missed. As it stands, I think I will have to wait for an update. I am including the working ASI driver.

root@astroberry:/home/astroberry# ldd /usr/bin/indi_asi_ccd
linux-vdso.so.1 (0xbeaf6000)
/usr/lib/arm-linux-gnueabihf/libarmmem-${PLATFORM}.so => /usr/lib/arm-linux-gnueabihf/libarmmem-v7l.so (0xb6f99000)
libindidriver.so.1 => /usr/lib/arm-linux-gnueabihf/libindidriver.so.1 (0xb6e07000)
libindiAlignmentDriver.so.1 => /usr/lib/arm-linux-gnueabihf/libindiAlignmentDriver.so.1 (0xb6ddf000)
libcfitsio.so.7 => /usr/lib/arm-linux-gnueabihf/libcfitsio.so.7 (0xb6b50000)
libASICamera2.so => /usr/lib/arm-linux-gnueabihf/libASICamera2.so (0xb6999000)
libEFWFilter.so => /usr/lib/arm-linux-gnueabihf/libEFWFilter.so (0xb694e000)
libUSB2ST4Conv.so => /usr/lib/arm-linux-gnueabihf/libUSB2ST4Conv.so (0xb6932000)
libEAFFocuser.so => /usr/lib/arm-linux-gnueabihf/libEAFFocuser.so (0xb68e6000)
libusb-1.0.so.0 => /lib/arm-linux-gnueabihf/libusb-1.0.so.0 (0xb68c1000)
libz.so.1 => /lib/arm-linux-gnueabihf/libz.so.1 (0xb6896000)
libpthread.so.0 => /lib/arm-linux-gnueabihf/libpthread.so.0 (0xb686c000)
librt.so.1 => /lib/arm-linux-gnueabihf/librt.so.1 (0xb6855000)
libstdc++.so.6 => /usr/lib/arm-linux-gnueabihf/libstdc++.so.6 (0xb670e000)
libm.so.6 => /lib/arm-linux-gnueabihf/libm.so.6 (0xb668c000)
libgcc_s.so.1 => /lib/arm-linux-gnueabihf/libgcc_s.so.1 (0xb665f000)
libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0xb6511000)
/lib/ld-linux-armhf.so.3 (0xb6fce000)
libnova-0.16.so.0 => /usr/lib/arm-linux-gnueabihf/libnova-0.16.so.0 (0xb618a000)
libjpeg.so.62 => /usr/lib/arm-linux-gnueabihf/libjpeg.so.62 (0xb6145000)
libfftw3.so.3 => /usr/lib/arm-linux-gnueabihf/libfftw3.so.3 (0xb6047000)
libdl.so.2 => /lib/arm-linux-gnueabihf/libdl.so.2 (0xb6034000)
libgsl.so.23 => /usr/lib/arm-linux-gnueabihf/libgsl.so.23 (0xb5e29000)
libgslcblas.so.0 => /usr/lib/arm-linux-gnueabihf/libgslcblas.so.0 (0xb5de8000)
libcurl-gnutls.so.4 => /usr/lib/arm-linux-gnueabihf/libcurl-gnutls.so.4 (0xb5d66000)
libbz2.so.1.0 => /lib/arm-linux-gnueabihf/libbz2.so.1.0 (0xb5d46000)
libudev.so.1 => /lib/arm-linux-gnueabihf/libudev.so.1 (0xb5d16000)
libnghttp2.so.14 => /usr/lib/arm-linux-gnueabihf/libnghttp2.so.14 (0xb5ce7000)
libidn2.so.0 => /usr/lib/arm-linux-gnueabihf/libidn2.so.0 (0xb5cbb000)
librtmp.so.1 => /usr/lib/arm-linux-gnueabihf/librtmp.so.1 (0xb5c92000)
libssh2.so.1 => /usr/lib/arm-linux-gnueabihf/libssh2.so.1 (0xb5c5c000)
libpsl.so.5 => /usr/lib/arm-linux-gnueabihf/libpsl.so.5 (0xb5c3c000)
libnettle.so.6 => /usr/lib/arm-linux-gnueabihf/libnettle.so.6 (0xb5bf8000)
libgnutls.so.30 => /usr/lib/arm-linux-gnueabihf/libgnutls.so.30 (0xb5a55000)
libgssapi_krb5.so.2 => /usr/lib/arm-linux-gnueabihf/libgssapi_krb5.so.2 (0xb5a0b000)
libkrb5.so.3 => /usr/lib/arm-linux-gnueabihf/libkrb5.so.3 (0xb5950000)
libk5crypto.so.3 => /usr/lib/arm-linux-gnueabihf/libk5crypto.so.3 (0xb5910000)
libcom_err.so.2 => /lib/arm-linux-gnueabihf/libcom_err.so.2 (0xb58fd000)
libldap_r-2.4.so.2 => /usr/lib/arm-linux-gnueabihf/libldap_r-2.4.so.2 (0xb58a8000)
liblber-2.4.so.2 => /usr/lib/arm-linux-gnueabihf/liblber-2.4.so.2 (0xb588c000)
libunistring.so.2 => /usr/lib/arm-linux-gnueabihf/libunistring.so.2 (0xb5710000)
libhogweed.so.4 => /usr/lib/arm-linux-gnueabihf/libhogweed.so.4 (0xb56d1000)
libgmp.so.10 => /usr/lib/arm-linux-gnueabihf/libgmp.so.10 (0xb5658000)
libgcrypt.so.20 => /lib/arm-linux-gnueabihf/libgcrypt.so.20 (0xb557e000)
libp11-kit.so.0 => /usr/lib/arm-linux-gnueabihf/libp11-kit.so.0 (0xb5479000)
libtasn1.so.6 => /usr/lib/arm-linux-gnueabihf/libtasn1.so.6 (0xb5459000)
libkrb5support.so.0 => /usr/lib/arm-linux-gnueabihf/libkrb5support.so.0 (0xb543f000)
libkeyutils.so.1 => /lib/arm-linux-gnueabihf/libkeyutils.so.1 (0xb542b000)
libresolv.so.2 => /lib/arm-linux-gnueabihf/libresolv.so.2 (0xb5407000)
libsasl2.so.2 => /usr/lib/arm-linux-gnueabihf/libsasl2.so.2 (0xb53e0000)
libgpg-error.so.0 => /lib/arm-linux-gnueabihf/libgpg-error.so.0 (0xb53b6000)
libffi.so.6 => /usr/lib/arm-linux-gnueabihf/libffi.so.6 (0xb539e000)

Hello,

After normalizing the data, this is what I found. The library arm-linux-gnueabihf is missing libGPSD.so and libQHYcamera.so. This sticks out like a sore thumb.

Looking at /usr/lib/arm-linux-gnueabihf, I see libgps.so and libqhyccd.so. The files are there but do not seem to be included in the LDD list. This looks like a miss in the .h files. This must be the reason for the error messages. Now, to look at the build process of both drivers.

Hello,

This looks like another shift in thinking. Recently, /lib/udev/rules.d are where all driver rules are located. The installmanifest.txt has all udev rules pointing to /etc/udev/rules.d. Limited rules are in /etc/udev/rules. Bummer, another design shift with where the rules location are in. Looks like all CCD rules are in /etc/udev/rules.d.

Here is another issue. The manifest calls out libqhyccd.so.20.3.21. What is in /usr/lib/arm-linux-gnueabihf/ is libqhyccd.so.20.7.26. This is a mismatch. This confirms the missing QHYCCD symbols. I wonder if I change the install_manifest.txt? Nope. No other occurance of libqhyccd.so occur other than in the install_manifest.txt. Looks like many MAKE and CMAKE files are missing for QHYCCD. Hmm... This looks bigger than a breadbox. To me, this further confirms the missing QHYCCD symbols.

As for GPS, I am still researching why INDI cannot see the GPSD.

Hello,

I figured it out for both of these issues. The driver /usr/lib/arm-linux-gnueabihf/libindidriver.so.1.8.6 does not contain the symbol for _ZN4INDI13DefaultDeviceD2V. Nor does this driver contain the symbol for _ZN4INDI7CCDChip8setFrameEiiii. Looks like both 3rdParty drivers, indi-gpsd and indi-qhyccd, are not having a good day with libindidriver.so.1.8.6. Well, that error message mystery is solved. Looks like libindidriver needs to be updated.

Used: nm /usr/lib/arm-linux-gnueabihf/libindidriver.so.1.8.6

This gave all of the symbols in the driver. I looked up each one and did not find the symbol in the list. This is the EOF message.

I am adding where these messages occur, KSTARS device manager and EKOS profile start and connect. This points to the dance between KSTARS and INDI. Peripherals and a application have to have a heartbeat. A heartbeat provides assurance that an expect device has not been removed when called for use.

The symbols provided are generic. Nothing is specific as to vendor. KSTARS has libindidriver.xml as its resource for all the drivers INDI has to offer. When a profile is created, this list is consulted. Then the dance begins with Who are you, What type are you, and Are you powered?

These symbols identify a point to What are you? Now to look at KSTARS. LDD will tell me its communication methods with INDI. Then the source of these symbols will be found.