I get the same repeated crash. My log file shows a problem with libASICamera2.so ?

2021-04-23T12:42:58.301 ADT DEBG ][ org.kde.kstars.indi] - INDI Server: "2021-04-23T15:42:58: Driver indi_asi_ccd: indi_asi_ccd: error while loading shared libraries: libASICamera2.so: cannot open shared object file: No such file or directory"
[2021-04-23T12:42:58.301 ADT DEBG ][ org.kde.kstars.indi] - INDI Server: "2021-04-23T15:42:58: Driver indi_asi_ccd: stdin EOF"
[2021-04-23T12:42:58.301 ADT DEBG ][ org.kde.kstars.indi] - INDI Server: "2021-04-23T15:42:58: Driver indi_asi_ccd: Terminated after #0 restarts."


Jerry Black replied to the topic 'Headless KStars' in the forum. 6 days ago

Yes getting the resolution to stick as full screen with matching resolution can be a bit of a user interface weirdness, but it can be done with the right sequence of icon clicks. I tend to choose a slightly less than full screen window size on my Mac’s local screen so I manage I windows there more easily. That is probably just a Mac versus Windows common mode of use. Anyway it can be done, and everything works great with that figured out, at least for me.


Jerry Black replied to the topic 'Headless KStars' in the forum. 7 days ago

This doesn't specifically answer your question, but I'm using NoMachine www.nomachine.com/ to connect to my Odroid-N2 Ubuntu KStars rather than VNC and don't have problems. The NoMachine server starts on the Odroid-N2 upon boot. Not sure about virtual machines, but I naively think it should work.



Just looking for feedback from anyone using the Starlight Xpress Adaptive Optics unit? I'm wondering if it is actually able to overcome poor seeing and how it integrates with the rest of the KStars environment.



It appears that the camera has it's pixel dimensions specified as taller than wide. I suspect they should be reversed.


I can't add useful information to this discussion except to note that issuing

sudo sh -c 'echo 256 > /sys/module/usbcore/parameters/usbfs_memory_mb'
fixes my connection problems with running the source code Build: 2021-03-19T15:18:51Z  for both my
ZWO ASI224MC guide camera and
Nikon Z7    (8256 x 5504) => 90.9 Mb fits files
the default usbfs_memory_mb on my ubuntu 20.0.4 was 16  (as noted elsewhere)
The stable version works for me (as one might expect).


Jerry Black replied to the topic 'Headless Ubuntu on Raspberry Pi' in the forum. 1 month ago

Another voice in praise of NoMachine. I can't really comment on its performance relative to other solutions, but it's working quite nicely for me on an Odroid-N2 and UbuntuMate 20.0.4. Just now trying to see if I can notice a difference with a solid colour background.


I can confirm that Bleeding edge nightly Build: 2021-03-17T15:03:52Z has solved my connection problems with the Nikon and Zwo ASI224MC camera :)


Jerry Black replied to the topic 'Current MacOS Build?' in the forum. 1 month ago

What is the current status with respect to running on Apple Silicon M1 chip based machines? Rosetta2 or native?


Just confirming that this page www.indilib.org/download.html contains the up-to-date instructions for switching to/from the bleeding edge version? e.g.

sudo apt-add-repository ppa:mutlaqja/indinightly
sudo apt-get update
sudo apt-get install indi-full kstars-bleeding gsc

As a result this is what UbuntuMate 20.0.4 shows when reverting to the stable branch
It's not clear to me how to ensure "make sure you're using the latest Indi when using the latest KStars" this is happening with this environment. It appears to be automatic (assuming I switch back to the nightlies).


With bleeding edge versions since about March 12th, I have been unable to see my cameras with KStars, while Phd2 can see the ZWO 224mc directly, Kstars issues the notification...

"kstars Unable to establish the following device Nikon DSLR Please ensure each device is connected and powered on."
lsusb shows both cameras as usb devices.

If I run Kstars with internal guiding it notifies that it can't see either camera.

Running the stable 2021-03-1 version works as expected.

I couldn't find an error in any log I inspected that provided more detail than the notification message.
Running on Odroid-N2 using Unbuntu 20.0.4

Perhaps unrelated, I have enabled the Terrain feature in the bleeding edge version and it is working.

Any suggestion on how to debug this?