I had just installed latest KStars and INDI. No crashes here, neither with manually connecting devices, nor with autoconnect. (Just ASI cam won't connect - see separate post)
System see signature...
Or does it depend on specific devices? That was 2 ZWo cameras (1600/290), EFW and EAF, plus the telescope simulator...
I have a system being investigated on for the crash issue (was either PPA or github with patch), and I also installed from scratch (Ubuntu Mate 20.04 LTS and KStars 3.4.3 & friends, from PPA) on an identical system (ODroid C4) that does not seem to have the issue. I haven't tested it with hardware yet though.
I can reproducer this error SIGABORT now with any combination of devices (no longer juts the ASI camera) - currently I am down to only mount and cam and still crashing...simulators I can run!!!!
And another variant of this same crash - this time controlled - unchecked auto connect and let EKOS come up then connected mount = OK....connected ZWO cam (I expected crashed here) = OK....so now connected QHY cam (whihc has always bee stable) = CRASH
SIGABORT is related to running out of memory from what I know so there seems to be a dynamic memory issue here since simulator can load but have no real load - I notices there is a new analyis icon/tab - could it be that that new feature is grabbing objects and eating the system?....can that utility be disabled by config so I can run a test of that theory?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
[New Thread 0xafb86090 (LWP 1487)]
[New Thread 0xaa2d7090 (LWP 1488)]
[New Thread 0xa9360090 (LWP 1489)]
[New Thread 0xa735f090 (LWP 1490)]
[New Thread 0xa51ff090 (LWP 1491)]
[New Thread 0xa23f4090 (LWP 1492)]
[New Thread 0xa17da090 (LWP 1493)]
[New Thread 0xa0dff090 (LWP 1494)]
[New Thread 0xa05fe090 (LWP 1495)]
[New Thread 0x9fdfd090 (LWP 1496)]
[New Thread 0x9f5fc090 (LWP 1497)]
[New Thread 0x9ecb7090 (LWP 1498)]
[New Thread 0x9ccb6090 (LWP 1499)]
[Thread 0x9ccb6090 (LWP 1499) exited]
[Thread 0xa17da090 (LWP 1493) exited]
[Thread 0x9fdfd090 (LWP 1496) exited]
[Thread 0xa0dff090 (LWP 1494) exited]
[New Thread 0xa0dff090 (LWP 1506)]
[New Thread 0x9fdfd090 (LWP 1508)]
[New Thread 0xa17da090 (LWP 1509)]
[New Thread 0x9ccb6090 (LWP 1513)]
[Thread 0x9fdfd090 (LWP 1508) exited]
[Thread 0xa17da090 (LWP 1509) exited]
[Thread 0xa0dff090 (LWP 1506) exited]
[New Thread 0xa0dff090 (LWP 1529)]
[New Thread 0xa17da090 (LWP 1553)]
[New Thread 0x9fdfd090 (LWP 1556)]
[New Thread 0x9a122090 (LWP 1562)]
Thread 1 "kstars" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0xb3aeb230 in __GI_abort () at abort.c:79
#2 0xb3d458d8 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
#3 0xb3d435b0 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
#4 0xb3d43624 in std::terminate() () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
#5 0xb3d43990 in __cxa_throw () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
#6 0xb3d6c234 in std::__throw_logic_error(char const*) () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
#7 0x00a44dc4 in INDI::BaseDevice::messageQueue[abi:cxx11](int) const ()
#8 0x006602b6 in INDI_D::updateMessageLog (this=0xa2f20150, idv=0xa2f20ed0, messageID=<optimized out>) at ./kstars/indi/indidevice.cpp:293
#9 0xb4b64c68 in QMetaCallEvent::placeMetaCall(QObject*) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#10 0xb4b68bec in QObject::event(QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#11 0xb54a09c4 in QWidget::event(QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5
#12 0xb545ddb4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5
#13 0xb54662a8 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5
Backtrace stopped: Cannot access memory at address 0x4317c6f8
Rendering Error in layout Message/Item: array_keys(): Argument #1 ($array) must be of type array, null given. Please enable debug mode for more information.
That would result in a deadlock. I now have a working solution that I'm just testing through all scenarios... just waiting for Gilles to confirm it's working well on his system.