The problem is related to a secondary CCD camera driver in INDI when it is not connected. Steps to reproduce: 1. Run KStars. 2. Run a local INDI server with Ekos: EQMod (simulation mode), GPhoto (simulation mode) and QHY or ZWO (no camera connected) Aux 1 driver. 3. Load a session in the Ekos Scheduler. 4. Execute the Scheduler session. Outcome: KStars shows a wrong dialog "an other INDI server is running. Stop it? Yes or No". If the answer is Yes then KStars crashes, if No then duplicate EQMod and GPhoto tabs appear in the INDI window and the Ekos Scheduler fails to execute the session. The problem is not specific to the INDI drivers, the simulation mode or remote/local INDI server. It is reproducible always. It is maybe related to the fact that a non-powered QHY or ZWO camera driver does not appear at all in the INDI window? Then KStars thinks that the INDI client session in KStars and the INDI server are not the same.
I haven't checked it but when you run QHY/ZWO with NO camera attached, no driver is defined and therefore Ekos might think that it is an incomplete invalid startup (it is) and then pops this question to restart the process?
Strangely enough, things go wrong only if a Scheduler session is started. Capturing an image, alignment does not exhibit the same problem.
is this still reproducible with GIT?
Of course.
Please check with latest KStars v3.5.4 and report back if you can.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!