×

INDI Library v1.9.6 Released (21 May 2022)

Bi-monthly INDI Library released with new drivers and bug fixes.

KStars crash...

  • Posts: 280
  • Thank you received: 43

KStars crash... was created by Markku

Hi,

Trying to run for first time using KStars version 3.5.7, Build: 2022-03-04T10:42:19Z but when trying to take a image with SXVR-H9 KStars just crash :( everything else seems to work, noticed that a image using the LodestarX2 within the guiderwindow  in Ekos does not crash but when the fitsviewer comes up then KStars just dies.

Everything is up to date both Ubuntu, KStars and also the drivers.

Runing in gdb this is the result:

Thread 1 "kstars" received signal SIGSEGV, Segmentation fault.
0x00007ffff5210202 in QString::operator=(QString const&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
(gdb)
(gdb) bt
#0  0x00007ffff5210202 in QString::operator=(QString const&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x0000555555fd43ae in SSolver::Parameters::operator= (this=0x55555d4245a8)
    at /usr/include/libstellarsolver/parameters.h:304
#2  StellarSolver::setParameters (parameters=..., this=0x55555d4244e0)
    at /usr/include/libstellarsolver/stellarsolver.h:226
#3  FITSSEPDetector::findSourcesAndBackground (this=0x55555e625890, boundary=...)
    at ./kstars/fitsviewer/fitssepdetector.cpp:110
#4  0x0000555555fd1bfa in QtConcurrent::StoredMemberFunctionPointerCall1<bool, FITSSEPDetector, QRect const&, QRect>::runFunctor (this=0x55555e5d88f0)
    at /usr/include/x86_64-linux-gnu/qt5/QtConcurrent/qtconcurrentstoredfunctioncall.h:549
#5  0x000055555573d87d in QtConcurrent::RunFunctionTask<bool>::run (this=0x55555e5d88f0)
    at /usr/include/x86_64-linux-gnu/qt5/QtCore/qmutex.h:240
#6  0x00007ffff5191d62 in QThreadPoolPrivate::stealAndRunRunnable(QRunnable*) ()
   from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007ffff5196262 in QFutureInterfaceBase::waitForFinished() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00005555558cb925 in QFuture<bool>::waitForFinished (this=0x7fffffffd200)
    at /usr/include/x86_64-linux-gnu/qt5/QtCore/qfuture.h:95
#9  FITSView::searchStars (this=0x55555de4c180) at ./kstars/fitsviewer/fitsview.cpp:1865
#10 0x0000555555a25fe5 in FITSTab::processData (this=0x55555e401270) at ./kstars/fitsviewer/fitstab.cpp:473
#11 0x0000555555a297a7 in FITSTab::loadData (this=this@entry=0x55555e401270, data=...,
    mode=mode@entry=FITS_NORMAL, filter=filter@entry=FITS_NONE) at ./kstars/fitsviewer/fitstab.cpp:532
#12 0x0000555555a140b3 in FITSViewer::loadData (this=0x55555e0d21c0, data=..., imageName=...,
    tab_uid=tab_uid@entry=0x7fffffffd414, mode=mode@entry=FITS_NORMAL, filter=filter@entry=FITS_NONE,
--Type <RET> for more, q to quit, c to continue without paging--
    previewText=...) at ./kstars/fitsviewer/fitsviewer.cpp:462
#13 0x00005555559e92d0 in ISD::CCD::handleImage (this=0x55555d4c8970, targetChip=0x55555d4c1690, filename=...,
    bp=<optimized out>, data=...) at /usr/include/c++/9/bits/atomic_base.h:413
#14 0x00005555559ed0a1 in ISD::CCD::processBLOB (this=0x55555d4c8970, bp=<optimized out>)
    at /usr/include/c++/9/bits/atomic_base.h:318
#15 0x00007ffff5382328 in QMetaObject::activate(QObject*, int, int, void**) ()
   from /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x0000555555936636 in ClientManager::newINDIBLOB (this=<optimized out>, _t1=<optimized out>)
    at ./obj-x86_64-linux-gnu/kstars/KStarsLib_autogen/FRI4DANIHA/moc_clientmanager.cpp:368
#17 0x00007ffff5382c2a in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007ffff5d70a66 in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
   from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x00007ffff5d7a0f0 in QApplication::notify(QObject*, QEvent*) ()
   from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x00007ffff535680a in QCoreApplication::notifyInternal2(QObject*, QEvent*) ()
   from /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007ffff5359488 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) ()
   from /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007ffff53aee37 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x00007ffff442617d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x00007ffff4426400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x00007ffff44264a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x00007ffff53ae435 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
--Type <RET> for more, q to quit, c to continue without paging--
   from /lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x00007ffff53553ab in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
   from /lib/x86_64-linux-gnu/libQt5Core.so.5
#28 0x00007ffff535d116 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#29 0x00005555556ccdf4 in main (argc=<optimized out>, argv=<optimized out>) at ./kstars/main.cpp:382
(gdb)

So what do I do now ??

Br,
/Markku
EQ8, Small scope SW200, Big scope SW300, Xagyl FW, Guidescope Celestron 80mm, SX LodestarX2, SXVR-H9.
RPi4, Ubuntu Server 20.04.3 LTS x64, and many Arduinos..
3 months 2 weeks ago #81423

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

  • Posts: 2722
  • Thank you received: 760

Replied by Rob Lancaster on topic KStars crash...

Could you possibly use the latest master in KStars instead of 3.5.7?  The problem is that I upgraded to a new version 2 in Stellarsolver with a new API.  I did update KStars to work with that new API, but 3.5.7 was not designed to work with the new version, it was designed to work with Stellarsolver 1.  But then the new solver got put in the PPA and 3.5.7 is not really compatible.  We did release a patch for it to make it work, but it isn't the best solution because it was not designed for it.  3.5.8 has been re-designed for using StellarSolver 2.  So if you can update, that would be a good solution.  It is *almost* ready for release so should be mostly stable.
3 months 2 weeks ago #81428

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

  • Posts: 2722
  • Thank you received: 760

Replied by Rob Lancaster on topic KStars crash...

Sorry for the inconvenience.  I did work really hard to try to avoid this kind of conflict, working on the 2nd version in a branch for 3 weeks so there wouldn't be any conflicts, and then trying to update both repos at the same time so we wouldn't get a mismatch.  But then when Stellarsolver 2.0 got in the PPA, KStars 3.5.7 tried to use it as well as the latest KStars.  That was not good.
3 months 2 weeks ago #81429

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

  • Posts: 16
  • Thank you received: 0

Replied by Lenny on topic KStars crash...

I also am experiencing KSTARS crashing tonight, first time I used it since I updated it. There is nothing being reported in the logging and I can take preview images with both of my cameras AA26C and AA130GPCAM. I can slew the telescope without issue. However, if I attempt to use the focus module or the plate solve module or the guider module KSTARS shuts down with no warning. Any ideas of whats going on?



  
3 months 2 weeks ago #81432
Attachments:

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

  • Posts: 16
  • Thank you received: 0

Replied by Lenny on topic KStars crash...

I also am experiencing KSTARS crashing tonight, first time I used it since I updated it. There is nothing being reported in the logging and I can take preview images with both of my cameras AA26C and AA130GPCAM. I can slew the telescope without issue. However, if I attempt to use the focus module or the plate solve module or the guider module KSTARS shuts down with no warning. Any ideas of whats going on?
Apologies post seems to have gone in twice.



    



  
Last edit: 3 months 2 weeks ago by Lenny.
3 months 2 weeks ago #81433
Attachments:

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

  • Posts: 2722
  • Thank you received: 760

Replied by Rob Lancaster on topic KStars crash...

Yes, if it is related to plate solving or SEP based star detection, it is likely the same issue that I explained above.  You might try the latest nightly build?
3 months 2 weeks ago #81440

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

  • Posts: 280
  • Thank you received: 43

Replied by Markku on topic KStars crash...

Hi Rob,

Thank you for the advise, I'll try that later today.
While I was debugging the fog came in and I had to stop my session :(
There was one funny thing I found out, when removing and reinstalled KStars then there was no crash with the fitsviewer but only when trying to resolve.

@Lenny, well, now we know what to do :)

Br,
/Markku
EQ8, Small scope SW200, Big scope SW300, Xagyl FW, Guidescope Celestron 80mm, SX LodestarX2, SXVR-H9.
RPi4, Ubuntu Server 20.04.3 LTS x64, and many Arduinos..
3 months 2 weeks ago #81441

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

  • Posts: 16
  • Thank you received: 0

Replied by Lenny on topic KStars crash...

Hi Rob,
Thanks for the feed back do you mean do the following?
sudo apt-add-repository ppa:mutlaqja/indinightly
sudo apt-get update
sudo apt-get install indi-full kstars-bleeding gsc

Is there a plan to roll back the current Bi-monthly update until its resolved or is there a fix to be worked instead?

Thanks again,
Lenny.
3 months 2 weeks ago #81442

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

Time to create page: 0.419 seconds