Created attachment 114389 [details] Session log - check the last activities to see the problem While looking for an issue with slewing proceeding while not required, I created a scheduler job with a sequence that by chance went near the meridian, and caused a meridian flip. Because the scheduler job is not requiring tracking, the capture module should not request a meridian flip. We could add a warning for this when building the scheduler job. However, when the Capture module executed the flip, the mount obliged but the flip timed out. The Capture module retried, but no timeout was configured and as the mount did not reply or something else went wrong that didn't gave the relevant notification, the Capture module hung there and the whole Scheduler+Capture got stuck. Log attached.
What I didn't say is that the mount was pointing at the north pole. When requested to do a meridian flip, that is, just slew to the target again, it does nothing special as it is pointing at DEC=90. That seems to be the root cause: the Capture module is unable to see that at DEC=90 whatever it requests the mount to do will end up with HA=0, thus will trigger a meridian flip. That should be fairly easy to work around.
Fixed by https://phabricator.kde.org/D14684 Committed as https://phabricator.kde.org/R321:b7e3810b105f2c2ee19ffe37f84ceb6aa0b37228