×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

[SOLVED] kstars crashing after starting Indi

  • Posts: 50
  • Thank you received: 11
Client:
I am running latest kstars 2.6.0
KDE Frameworks 5.23.0
QT 5.5.1
Ubuntu 16.04.1 (all updates applied)

Remote INDI server:
Rasp Pi 3
Ubuntu 16.04.1
Latest Indi (this evening)

Kstars crashes as soon as I Start Indi,

Application: KStars (kstars), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f43484508c0 (LWP 2767))]

Thread 2 (Thread 0x7f4345721700 (LWP 2768)):
#0 0x00007f43539dbe8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1 0x00007f434e290c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2 0x00007f434e2928d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3 0x00007f43480a5629 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4 0x00007f4354b7084e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x00007f43562b26fa in start_thread (arg=0x7f4345721700) at pthread_create.c:333
#6 0x00007f43539e7b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f43484508c0 (LWP 2767)):
[KCrash Handler]
#6 0x0000000000646419 in ?? ()
#7 0x000000000059befc in ?? ()
#8 0x00007f4354d7ffca in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9 0x000000000058b622 in ?? ()
#10 0x00000000005d48a5 in ?? ()
#11 0x000000000059b4bc in ?? ()
#12 0x00007f4354d80ea1 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007f4355b2f05c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x00007f4355b34516 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x00007f4354d5162b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007f4354d53a26 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007f4354da7673 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007f435044e1a7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007f435044e400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007f435044e4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007f4354da7a7f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007f4354d4edea in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x00007f4354d56e8c in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x000000000047ca72 in ?? ()
#25 0x00007f4353901830 in __libc_start_main (main=0x47b2a0, argc=1, argv=0x7ffd3709cae8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd3709cad8) at ../csu/libc-start.c:291
#26 0x0000000000486579 in _start ()
7 years 6 months ago #10295

Please Log in or Create an account to join the conversation.

  • Posts: 50
  • Thank you received: 11
[Update} I switched over to a Windows box with ASCOM and verified that all hardware is working properly.

I may have narrowed down the problem a little. It took the Raspberry Pi 3 out of the mix and run both kstars client and INDI server on an i3 Ubuntu 16.04 machine with a fresh install of everything. I even replaced the serial<>USB adapter. It happens while connecting to the Maxdome II module.

Debug logging (below) doesn't have any errors.

indi_maxdomeii_2016-09-20T16\:50\:28.log
INFO 16.568711 sec : Session log file /tmp/indi_maxdomeii_2016-09-20T16:50:28.log
INFO 22.647198 sec : Opening port ...
INFO 22.648246 sec : Connecting ...
INFO 22.653294 sec : Dome is online.
INFO 22.668954 sec : New park position set. 1 0
INFO 22.669236 sec : Auto park is disabled.
DEBUG 22.669370 sec : Configuration successfully loaded.

--

Segfault output:

Application: KStars (kstars), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fedc02e08c0 (LWP 2697))]

Thread 2 (Thread 0x7fedbdbe5700 (LWP 2698)):
#0 0x00007fedccdd4e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1 0x00007fedc76afc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2 0x00007fedc76b18d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3 0x00007fedbff37629 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4 0x00007fedcdf6984e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x00007fedcf6a86fa in start_thread (arg=0x7fedbdbe5700) at pthread_create.c:333
#6 0x00007fedccde0b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fedc02e08c0 (LWP 2697)):
[KCrash Handler]
#6 0x0000000000646459 in ?? ()
#7 0x000000000059befc in ?? ()
#8 0x00007fedce178fca in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9 0x000000000058b622 in ?? ()
#10 0x00000000005d48a5 in ?? ()
#11 0x000000000059b4bc in ?? ()
#12 0x00007fedce179ea1 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007fedcef2605c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x00007fedcef2b516 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x00007fedce14a62b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007fedce14ca26 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007fedce1a0673 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007fedc984f1a7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007fedc984f400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007fedc984f4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007fedce1a0a7f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007fedce147dea in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x00007fedce14fe8c in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x000000000047ca72 in ?? ()
#25 0x00007fedcccfa830 in __libc_start_main (main=0x47b2a0, argc=1, argv=0x7ffcbfcd1fd8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffcbfcd1fc8) at ../csu/libc-start.c:291
#26 0x0000000000486579 in _start ()
Last edit: 7 years 6 months ago by Ollie.
7 years 6 months ago #10333

Please Log in or Create an account to join the conversation.

The crash looks related to Qt itself. If you connect to everything else then no crash and ONLY when MaxDome II is connected then you have crash?
7 years 6 months ago #10347

Please Log in or Create an account to join the conversation.

  • Posts: 50
  • Thank you received: 11
I just updated everything (kstars-bleeding, Ubuntu and indi server on the Rasp Pi 3, etc.) and now it all seems to be working. Not sure what changed but it seems better now. I'll be able to test more this weekend.
7 years 6 months ago #10361

Please Log in or Create an account to join the conversation.

  • Posts: 50
  • Thank you received: 11
kstars-bleeding (updated this morning) is still crashing when attempting to connect to the MaxDome II module. Same Qt errors. I'll do a fresh re-install of everything and try again.
7 years 6 months ago #10433

Please Log in or Create an account to join the conversation.

I tested both on my machine and within Ekos VM and can't reproduce the crash with my rolloff driver. and the crash doesn't provide any useful information as to the cause of the issue

EDIT: Found problem, solved. PPA tomorrow should have the fix. Thanks.
The following user(s) said Thank You: Ollie
Last edit: 7 years 6 months ago by Jasem Mutlaq.
7 years 6 months ago #10439

Please Log in or Create an account to join the conversation.

  • Posts: 50
  • Thank you received: 11
I don't know if this is related to what you found but I rebuilt an Ubuntu i3 PC from scratch, loaded 16.04 LTS, kstars-bleeding, and INDI server all on the same machine and now MaxDome does not crash when connected. The only thing I found is that ~/.indi/MaxDome II_config.xml.default is present on this new system whereas it was missing on the system that kept crashing.

Thanks for looking in to this! Your time and contributions to this project are appreciated!
7 years 6 months ago #10451

Please Log in or Create an account to join the conversation.

  • Posts: 50
  • Thank you received: 11
I spoke too soon. kstars is still crashing. I'm not sure I have the latest release with the fix. I'll wait for the PPA to come back online, download, and try again.
7 years 5 months ago #10469

Please Log in or Create an account to join the conversation.

  • Posts: 50
  • Thank you received: 11
Everything is now working after compiling kstars from source.
7 years 5 months ago #10492

Please Log in or Create an account to join the conversation.

Time to create page: 1.093 seconds