FYI I had the same issue and fix on Armbian 5.67 running on Radxa RockPi4
Found the fix: in case anyone else sees this behavior, apt-install the following dependencies
I have kstars and INDI compiled from source running on Armbian. I have got it mostly working, except that the application crashes when I connect to any telescope INDI driver (I have tested both my EQMOD mount and the telescope simulator. Both have the same behavior where Ekos will briefly show the green ‘connected’ status in the driver window - but then the whole application crashes.
I’ve attached a screen shot of the relevant terminal output when kstars is launched via terminal. A lot of fuss about missing QT components and then the line “segmentation fault”. Any ideas how I can fix this?
Other than this issue, I’ve got everything else up and working properly I think
I'm not sure if I'm running gdb correctly. The output above I launched kstars manually, then ran gdb, made kstars crash, and copy/pasted the output.
If I try and let gdb launch kstars using
gdb --ex run --args kstars
In case it is related, I should also mention that the buttons inside Ekos have no icons. See the attached screen shot.
Thank you Jasem. This is what I have from gdb
linaro@linaro-alip:~$ gdb --ex run --args kstars GNU gdb (Debian 7.12-6) 126.96.36.19961007-git Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "arm-linux-gnueabihf". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from kstars...done. Starting program: /usr/bin/kstars [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1". QXcbConnection: Could not connect to display Program received signal SIGABRT, Aborted. 0xf503d6f6 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6 (gdb) bt #0 0xf503d6f6 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6 #1 0xf504b3cc in raise () from /lib/arm-linux-gnueabihf/libc.so.6 #2 0xf504c0ba in abort () from /lib/arm-linux-gnueabihf/libc.so.6 #3 0xf5c02550 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5 #4 0xf13f9fd2 in QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, char const*) () from /usr/lib/arm-linux-gnueabihf/libQt5XcbQpa.so.5 #5 0xf13fc486 in QXcbIntegration::QXcbIntegration(QStringList const&, int&, char**) () from /usr/lib/arm-linux-gnueabihf/libQt5XcbQpa.so.5 #6 0xf77b3e90 in ?? () from /usr/lib/arm-linux-gnueabihf/qt5/plugins/platforms/libqxcb.so Backtrace stopped: previous frame identical to this frame (corrupt stack?) (gdb)
Hello, so after
Getting Ekos set up properly on my Rock Pi 4
I’ve got another issue going on.
I have not installed any 3rd party drivers yet to INDI, I am just trying to test the setup with the CCD, Telescope and Focuser simulators. When I connect kstars to the INDI server, the whole application crashes. I know this is not a lot of information to troubleshoot on - is there a log file located somewhere that I could post?
I have verified that INDI is working properly (I think) because when I launch the INDI web manager, the simulators connect to the INDI server just fine. I can even connect to the Rock Pi with a INDI client on my laptop and it’s talking to all the gear just fine. Appears to be an issue with my installation of kstars/Ekos - which is maybe not so surprising since I built from source myself.
Anyways, any input appreciated !
Thanks Jasem!! You are spot on - after re-running cmake for Indi then rebuilding kstars, it seems to be corrected!
Thanks Jason, you are correct. This is the (partial) output from cmake for kstars:
-- The following RUNTIME packages have not been found: * AstrometryNet , Astrometrics Library , <http://www.astrometry.net> Support for plate solving in KStars. -- The following OPTIONAL packages have not been found: * INDI (required version >= 1.7.1) , Astronomical instrumentation control , <http://www.indilib.org> Support for controlling astronomical devices on Linux with KStars. * Qt5DataVisualization * OpenGL , Open Graphics Library , <http://www.opengl.org> Support for hardware rendering in KStars. -- Configuring done -- Generating done CMake Warning: Manually-specified variables were not used by the project: CMAKE_INSTALL_PEFIX
Just to add, because it's probably obvious that I've never compiled a program from source before...
I think building from source is my only option here. My first choice obviously would have been to run Ubuntu and instalI from the repository. I did try to install one of the available Ubuntu builds floating around the internet for the RK3399 boards, but I couldn't get any of them to boot on the Rock Pi 4.
I picked up a Rock Pi 4Rock Pi 4 to run Ekos. The only desktop linux distribution available is Debian, so I'm trying to build indilib and kstars from source to get it up and running.
I've got kstars built and installed but my issue is that 'Ekos' and 'Device' are not appearing in the 'Tools' menu. Also, the INDI toolbar is empty. My issue sounds very similar to the one reported by Robert in this thread. . However, I"m not able to see what the ultimate solution in that case was.
I believe I have followed the directions appropriately. It's a fresh install of Debian with libindi and kstars installed to ~/Projects as per the directions from Jasem found here. .
After having this issue on the Rock Pi, I installed a Debian 9.6 VM on my laptop to see if I could get Ekos working properly on an x86/amd64 system. However, that process had the same outcome -- kstars installed and loaded but without Ekos or Device in the Tools menu and an empty INDI toolbar.
Any help would be greatly appreciated!! Let me know if more information is needed to figure out what I did wrong