Hi Jo,

yes, the link was what I was (trying to) point out. The executable is linked to libASICamera2.so, but this usually is a link to the actual (versioned) library. I was just not sure where they actually end up on your systems, as I don't have debian based installations around....
In my case it's likeand I had suspected that something wasn't updated properly in the package, and maybe leftovers from the 1.17 install had survived.

I would completely remove libasi, re-install it, and check where the links are pointing, and that they match the above pattern...

KStars 3.5.4 Beta (Build 2021-04-26To1:15:59Z) on Ubuntu 20.04.2 LTS still giving me the "INDI Driver indi_asi_ccd crashed. Restart it?" dialog loop.

Noticed the link in /usr/lib/ are incorrect:

What's the best way to remove/reinstall the libasi?  Then I'll verify/correct the links.

Seems you are missing a link libASICamera2.so.1 -> libASICamera2.so.1.16
In doubt you can create that yourself (ln -s libASICamera2.so.1.16 /usr/lib/libASICamera2.so.1).

I just compiled the latest version here on my computer (Tumbleweed). No issues, indi_asi_ccd doesn't crash, and drives the camera.

Just follow Jerry's instructions above and adapt to your installation, i.e. the subfolder where the lib would be placed. That differs from installation to installation. It eliminated the crash on my system.

ls -l /usr/lib/aarch64-linux-gnu/libASI*
lrwxrwxrwx 1 root root 18 Apr 21 16:06 /usr/lib/aarch64-linux-gnu/libASICamera2.so -> libASICamera2.so.1
-rw-r--r-- 1 root root 1887712 Apr 21 16:06 /usr/lib/aarch64-linux-gnu/libASICamera2.so.1.16

cd /usr/lib/aarch64-linux-gnu
sudo rm libASICamera2.so
sudo ln -s libASICamera2.so.1.16 libASICamera2.so

Thanks - very familiar how to set the links up, but was more looking for how to "completely remove libasi, re-install it" as Peter suggests above. I did straighten out the libASICamera2.so link to point to the existing libASICamera2.so.1.16 library and I no longer get the indi_asi_ccd crash dialog. Will verify the driver talks to the actual camera later.

What's the ultimate cause of this broken link? Bad apt-get upgrade? Bad install?
(Coincidently, after I fixed the libASI link, I did a update/upgrade and the link reverted to the identical broken state.  Looking at it closer, it almost looks like a character limit or typo - the link target is "libASICamera2.so.1" and should be "libASICamera2.so.16")

 

But now my EAF doesn't show in Ekos. Similar problem?

That still seems to be a recurring problem.  Check with Brian (starman365) on how to fix this.  I for my part just reverted back to the Indi version of March 10.  That continues to work for me.

I can't find anything on missing EAF or anything related from "starman365" or "Brian". Anyone else have a suggestion?
I tried reverting to the 3.5.3 Stable, but now that won't connect to my ASI equipment at all.

This is independent of the kstars version, it is an INDI problem (of libasi, to be exact). So that are the packages to up/downgrade.

What does 'ls -l /usr/lib/libEAFFocuser*' tell? And if you run 'indi_asi_focuser'?

check out

indilib.org/forum/ekos/9346-asi-eaf-not-...n-nightly.html#69722

That’s Brian’s post.

The library links look fine:

Executing the indi_asi_focuser via command-line does nothing.

I followed the "Building INDI from Source" section only and that took care of it. Didn't have to build the third-party stuff or KStars or anything else. EAF appeared in Ekos and connected. Thanks!