Summary: | Train not identified on manual connection profiles, crashes when capturing an image | ||
---|---|---|---|
Product: | [Applications] kstars | Reporter: | George Becker <george.becker> |
Component: | general | Assignee: | Rob <rlancaste> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | mutlaqja |
Priority: | NOR | ||
Version: | 3.6.3 | ||
Target Milestone: | --- | ||
Platform: | macOS (DMG) | ||
OS: | macOS | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
Log file from crashed session
Profile Editor screenshot from crashed session CCD panel screenshot from crashed session |
Description
George Becker
2023-02-14 16:55:27 UTC
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! |