×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

align: crash when downloading index files

  • Posts: 971
  • Thank you received: 94
Hi everyone
Been trying over 24h to download two remaining indices:
Is there perhaps an alternative url I could try?

(gdb) bt
#0 0x00007ffff14e5fd8 in QObject::disconnect(QMetaObject::Connection const&) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#1 0x0000555555e2a60e in Ekos::OpsAstrometryIndexFiles::disconnectDownload(QMetaObject::Connection*, QMetaObject::Connection*, QMetaObject::Connection*)
(percentConnection=0x7ffff134fb57 <QString::QString(int, Qt::Initialization)+39>, replyConnection=0x7fffffffd0c0, cancelConnection=<optimised out>, this=<optimised out>)
at ./kstars/ekos/align/opsastrometryindexfiles.cpp:532
#2 operator() (__closure=0x55555de474b0)
at ./kstars/ekos/align/opsastrometryindexfiles.cpp:429
#3 QtPrivate::FunctorCall<QtPrivate::IndexesList<>, QtPrivate::List<>, void, Ekos::OpsAstrometryIndexFiles::downloadIndexFile(const QString&, const QString&, QCheckBox*, int, int, double)::<lambda()> >::call (arg=<optimised out>, f=...)
at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:146
#4 QtPrivate::Functor<Ekos::OpsAstrometryIndexFiles::downloadIndexFile(const QString&, const QString&, QCheckBox*, int, int, double)::<lambda()>, 0>::call<QtPrivate::List<>, void>
(arg=<optimised out>, f=...)
at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:256
#5 QtPrivate::QFunctorSlotObject<Ekos::OpsAstrometryIndexFiles::downloadIndexFile(const QString&, const QString&, QCheckBox*, int, int, double)::<lambda()>, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *)
(which=<optimised out>, this_=0x55555de474a0, r=<optimised out>, a=<optimised out>, ret=<optimised out>) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:443
#6 0x00007ffff14f1793 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#7 0x00007ffff14f57fe in QTimer::timeout(QTimer::QPrivateSignal) ()
--Type <RET> for more, q to quit, c to continue without paging--
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#8 0x00007ffff14e733f in QObject::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#9 0x00007ffff216c713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x00007ffff14b9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007ffff15123eb in QTimerInfoList::activateTimers() ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007ffff1512cec in () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007ffff091bd3b in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x00007ffff0971258 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x00007ffff09193e3 in g_main_context_iteration ()
at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007ffff15130b8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007ffff14b875b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007ffff14c0cf4 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x00005555556ec2fa in main(int, char**) (argc=<optimised out>, argv=<optimised out>)
at ./kstars/main.cpp:386
(gdb)




log attached,
TIA,
Steve
Last edit: 9 months 2 weeks ago by alacant.
9 months 2 weeks ago #94000
Attachments:

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

  • Posts: 1187
  • Thank you received: 370
Unfortunately, neither the log nor the stack trace give an indication why this happens. Am I right, are you trying to download several index files in parallel? Maybe you should try downloading them sequentially - but that's just guessing...

HTH
Wolfgang
The following user(s) said Thank You: alacant
9 months 2 weeks ago #94024

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

  • Posts: 109
  • Thank you received: 8
To be on the safe side, take a look at dmesg and see if there's any filesystem and/or storage error.
Writing big files can sometimes bring out hardware issues.
The following user(s) said Thank You: alacant
9 months 2 weeks ago #94065

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

Time to create page: 0.347 seconds