Created attachment 156233 [details] 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!
Created attachment 156234 [details] Profile Editor screenshot from crashed session
Created attachment 156235 [details] CCD panel screenshot from crashed session
Ok this build should include fixes for both the QML rendering bug and the port selector not showing up bug reported in this bug post. www.indilib.org/jdownloads/kstars/beta/kstars-3.6.3.dmg Please try it out and let me know if it fixes it.
Ok I think this is all fixed in the repo
I'm still getting the same behavior after a fresh re-install of the new version. The optical train does not load when a mount and camera are connected manually, and KStars crashes when I try to capture an image. It may not be a significant issue so long as Automatic connection is enabled in the Profile setup, unless there are other underlying issues.
There is an updated DMG uploaded today. Not sure if it will help. At any rate, I tried to re-create this under Linux but couldn't get the issue, the train editor showed up fine even with auto-connect off.
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!