https://bugs.kde.org/show_bug.cgi?id=465720
Bug ID: 465720 Summary: Train not identified on manual connection profiles, crashes when capturing an image Classification: Applications Product: kstars Version: 3.6.3 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: george.bec...@ucr.edu Target Milestone: --- Created attachment 156233 --> https://bugs.kde.org/attachment.cgi?id=156233&action=edit Log file from crashed session 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 *** Some Ekos profiles with manual connections cannot be assigned an optical train. KStars then crashes when attempting to capture an image. The steps to reproduce below are one example. Similar cases where the train does or does not load are also given. STEPS TO REPRODUCE 1. Launch Ekos 2. Create a profile with only Mount=Telescope Simulator and Camera 1=CCD Simulator. In the Profile Editor, Uncheck Auto Connect. 3. Start Ekos 4. In the INDI Control Panel, Connect both the CCD Simulator and Telescope Simulator 5. In the CCD panel, attempt to capture an image or a preview. OBSERVED RESULT The Optical Train window does not appear when the profile is started. The Train field is greyed out in all panels. It shows no value and cannot be edited. In the CCD panel the cooler fields are also greyed out, and the Live Video button is crossed out. KStars crashes immediately when the Preview or Start Sequence buttons are clicked. EXPECTED RESULT I would expect the result to be the same when connecting the devices either manually or automatically. When the same setup is created with Auto Connect enabled, Optical Train window appears when the profile is started for the first time. The Train field is populated in the Ekos panels and can be edited. The Cooler and Live Video controls also work. Capturing an image works as expected. The crash seems to occur occur only when both a mount and a camera are present and they are being connected manually. The same behavior happens when a real camera is used instead of the simulated camera. If only a camera is used and no mount, then it can be connected either manually or automatically without crashing. If I edit a profile that crashes and change the connection mode from manual to auto, then everything works; the Optical Trains window appears when the Profile is started after Auto Connect is enabled. If I edit a Profile that is working and change the connection from auto to manual then it still works; the train information appears to be saved. SOFTWARE/OS VERSIONS Windows: macOS: 12.5.1 Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION A log from a crashed session is attached. I'm happy to re-run with logging enabled if needed. Thank you in advance for your help! -- You are receiving this mail because: You are watching all bug changes.