Hi Saturne33,

please check your kern.log (ubuntu ==> /var/log/kern.log) and look for the message coming up

As you can see on my log i get a segfault out of libc-2.31.so.

out of /var/log/kern.log Jan 7 17:26:13 kv-XPS-15-9560 kernel: [34344.408379] indi_atik_wheel[25755]: segfault at 0 ip 00007f33b01bab82 sp 00007fff8d9582f8 error 4 in libc-2.31.so[7f33b0059000+178000]

It seems that there was a change in this library since Ubuntu 18.x to 20.x. Maybe a rebuild will help but could also may cause older versions to no longer work.

I would also be happy if someone could come up with a solution.

regards
Klaus

Hi Klaus,
Thanks for your message. I just checked the kern.log:
On my laptop:
Feb 21 15:21:35 didier-XPS-13-9343 kernel: [10250.013177] indi_atik_wheel[4610]: segfault at 0 ip 00007f231104cb82 sp 00007ffdc64eaef8 error 4 in libc-2.31.so[7f2310eeb000+178000]

On my tower PC:
No such 'segfault' message.

Hoping that it may speaks to some experts to trigger a fixing...
Best regards

I can reproduce this error exactly (on both 20.04 and 21.04, as well as on Fedora 33), and nothing provided by Atik seems to address the issue:

Apr 24 22:30:29 astrolaptop kernel: [ 382.645496] indi_atik_wheel[3117]: segfault at 0 ip 00007f32893eab82 sp 00007ffd7acaa318 error 4 in libc-2.31.so[7f3289289000+178000]
Apr 24 22:30:29 astrolaptop kernel: [ 382.645508] Code: ff ff e9 01 80 f3 ff 90 f3 0f 1e fa 89 f8 31 d2 c5 c5 ef ff 09 f0 25 ff 0f 00 00 3d 80 0f 00 00 0f 8f 52 03 00 00 c5 fe 6f 0f <c5> f5 74 06 c5 fd da c1 c5 fd 74 c7 c5 fd d7 c8 85 c9 74 7a f3 0f

Ok, so I have a partial workaround, but it's pretty clunky.

Idea 1: Run another instance of indiserver in docker with Ubuntu 18.04, and connect to EFW remotely
Problem: For reasons I only vaguely understand, docker doesn't sufficiently isolate the broken Atik library from the newer kernel, so the crash persists

Idea 2: From a modern OS like Ubuntu 20.04, download Gnome Boxes and set up an Ubuntu 18.04 virtual machine, enable access to the EFW USB device in "preferences", install indiserver, and connect to the EFW remotely
Problem: While this works within the VM, the driver on the client still crashes with a segfault even when connecting remotely. Is there a way in indi to connect to a remote driver without having the driver installed on a client?

Idea 3: Give up on automatic control of the EFW, and just run a parallel instance of kstars in the 18.04 VM to control it.
Problem: This obviously sucks, but at least it does work.

I've messaged Atik about this, but only time will tell if they're willing to rebuild their driver for a non-archaic kernel. In the meantime:

1. I might need to learn how to use wireshark to figure out how to talk to the EFW and write a proper open source driver. It's a pretty simple device after all...
2. Does anyone know of solutions to the remote driver crash? That would be a decent workaround if it could be made to work.

I have the same problem. It was working fine until I did an update of kstars.
Here's my kernel log

Apr 25 22:25:47 hp-elite kernel: [   86.634417] aufs au_opts_verify:1623:dockerd[2778]: dirperm1 breaks the protection by the permission bits on the lower branch
Apr 25 22:27:07 hp-elite kernel: [  166.683503] usb 3-2: new full-speed USB device number 4 using xhci_hcd
Apr 25 22:27:07 hp-elite kernel: [  166.838512] usb 3-2: New USB device found, idVendor=0403, idProduct=6015
Apr 25 22:27:07 hp-elite kernel: [  166.838516] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 25 22:27:07 hp-elite kernel: [  166.838518] usb 3-2: Product: FT230X Basic UART
Apr 25 22:27:07 hp-elite kernel: [  166.838520] usb 3-2: Manufacturer: FTDI
Apr 25 22:27:07 hp-elite kernel: [  166.838521] usb 3-2: SerialNumber: DN05ROJB
Apr 25 22:27:07 hp-elite kernel: [  166.841793] ftdi_sio 3-2:1.0: FTDI USB Serial Device converter detected
Apr 25 22:27:07 hp-elite kernel: [  166.841838] usb 3-2: Detected FT-X
Apr 25 22:27:07 hp-elite kernel: [  166.842245] usb 3-2: FTDI USB Serial Device converter now attached to ttyUSB1
Apr 25 22:27:07 hp-elite kernel: [  167.011484] usb 3-1.1: new high-speed USB device number 5 using xhci_hcd
Apr 25 22:27:07 hp-elite kernel: [  167.211601] usb 3-1.1: New USB device found, idVendor=20e7, idProduct=df31
Apr 25 22:27:07 hp-elite kernel: [  167.211605] usb 3-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Apr 25 22:27:07 hp-elite kernel: [  167.535505] usb 3-1.3: new full-speed USB device number 6 using xhci_hcd
Apr 25 22:27:08 hp-elite kernel: [  167.738476] usb 3-1.3: New USB device found, idVendor=04d8, idProduct=003f
Apr 25 22:27:08 hp-elite kernel: [  167.738480] usb 3-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Apr 25 22:27:08 hp-elite kernel: [  167.738482] usb 3-1.3: Product: Filter Wheel 2
Apr 25 22:27:08 hp-elite kernel: [  167.738484] usb 3-1.3: Manufacturer: Atik Instruments
Apr 25 22:27:08 hp-elite kernel: [  168.009718] hidraw: raw HID events driver (C) Jiri Kosina
Apr 25 22:27:08 hp-elite kernel: [  168.021838] usbcore: registered new interface driver usbhid
Apr 25 22:27:08 hp-elite kernel: [  168.021839] usbhid: USB HID core driver
Apr 25 22:27:08 hp-elite kernel: [  168.160085] hid-generic 0003:04D8:003F.0001: hiddev0,hidraw0: USB HID v1.11 Device [Atik Instruments Filter Wheel 2] on usb-0000:00:14.0-1.3/input0
Apr 25 22:52:07 hp-elite kernel: [ 1667.199610] kstars[1998]: segfault at 6c ip 0000560b009d1c7d sp 00007ffc274b4e40 error 4 in kstars[560b005de000+d23000]

Actually my issue could be something else. I also cannot connect to my SX CCD or my Atik 383L+ camera after updating.

I think that's actually a different issue - the segfault information is different, and the symptoms are somewhat different. As far as I can tell, the issue that I've been seeing is something specific to the binary Atik library when used on newer kernels, rather than something internal to kstars or indi.

I'm not sure what to suggest for your issue, but a general rebuild isn't a bad place to start. Perhaps check that any third party components were also updated in sync with kstars/indi.

Hi Everyone,

Because an astrophoto setup is a chain that don't works if a part fail ... I have been oblige to move under Windows, where all the Ascom drivers works.
At this occasion I discovered the open source software 'N.I.N.A' and honestly I have been impressed. And at least I can make pictures !
Nevertheless my wish is to stay as much as possible within linux (Mint 20.2 currently). Accordingly I'm regularly testing updates of Kstars/ Ekos/ Indi. That I did today, but only to find that the error remains (Kstars 3.5.5 stable and INDI drivers updates).
I unfortunately cannot improve the situation by myself, so I continue to hope that someone, someday, will identify the problem.
Clear sky to All,
Didier

I've re-opened my issue here: github.com/indilib/indi-3rdparty/issues/382

I've been using Boxes to change the filter wheel manually, but that's really annoying when I should be able to set up a whole night of imaging ahead of time.

I was able to get mine working on Ubuntu 20.04 - pulling from the latest on Github, when I installed the following system packages things worked right away:

libgcc1
lib64stdc++6

I Grant,
Pleased to read that the topic is progressing positively!
I'm using Mint 20.2 that is based upon Ubuntu 20.04 (Focal Fossa). 'libgcc1' was natively installed but not 'lib64stdc++6'. So I did it manually (Synaptic package) for the latest, and rebooted the machine, in case.
Unfortunately it doesn't solve the issue in my case. Is their any other action that I could test ?
Have a good day!
Didier

In the comment linked below, user paolostivanin identified the shared object files which are required by the libraries:

github.com/indilib/indi-3rdparty/issues/...suecomment-926911217

I didn't have my original (problematic) configuration set up, so I created a new 20.04 machine, followed the build/installation instructions, and then tried to install the packages which provide these files. These were the only two which didn't show up as installed on my system, but there were others - go through those files and do a search to see if there are any other ones which you might not have by default. Also, it may help to rebuild/reinstall kstars/indi/libatik/indi-atik after grabbing these prerequisites.