https://bugs.kde.org/show_bug.cgi?id=451687
Bug ID: 451687
Summary: Attempted Meridian Flip causes great confusion
Product: kstars
Version: 3.5.7
Platform: macOS (DMG)
OS: macOS
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: mutla...@ikarustech.com
Reporter: jbry...@comcast.net
Target Milestone: ---
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
Running KStars/Ekos remotely on a MacBook Pro, controlling with an iMac in the
house.
Using PHD2 to guide.
I had split the job into a pre-meridian sequence, darks, and post-meridian,
imaging M 106.
At the conclusion of the dark acquisition, the mount was reporting only about
three minutes to the flip.
I paused the Scheduler, leaving the mount tracking and PHD2 guiding.
When it came time for the flip, it reported failure, and said it would try
again in three-something minutes.
I noticed that the mount was offset somewhat from the target.
I tried to capture and slew to it, but the mount wouldn't move.
I selected a number of other objects in the vicinity and had no problem solving
and centering them.
No matter what I tried, it would no longer solve and center M 106 in the
reticle.
I eventually realized that PHD2 was interfering somehow (though no longer
guiding), and killed and restarted it.
I was then able to capture, solve and slew to M 106.
I deleted the pre-meridian and dark jobs in the scheduler, re-started it and
completed the post-meridian job.
STEPS TO REPRODUCE
1.
2.
3.
OBSERVED RESULT
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Windows:
macOS: 11.6.4
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
