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 *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT When a Plate Solve is initiated, and the system detects the camera as busy, the Plate Solve routine goes into a series of waits at 10 sec, 20 sec, 40 sec, etc etc waiting for the camera to become unbusy. Often times (more like usually) the camera is not busy. The system thinks the camera is busy, but there is no apparent indication to the user. The problem is that, when the Plate Solver starts these delays as the user searches for why the system thinks the camera is busy, the STOP button is grayed out! Sometimes the only solution is to quit the session, then restart. The simple solution would seem to be to let the user STOP the process as soon as the Plate Solve routine says the camera is busy so the user can find where the system thinks the camera is busy before the Ekos embarks on a long wait sequence. One example of where the system thinks the camera is busy when it is not is the Focus module. If the camera is doing loop capture and the STOP button is hit in the Focus module, the Plate Solve module will always say the camera is busy. After hitting STOP when doing Focus looping, run the camera once in a Single Shot mode. That usually clears the conflict. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION