| Summary: | Spinning Beachball during Alignment Capture | ||
|---|---|---|---|
| Product: | [Applications] kstars | Reporter: | MountainAirCA |
| Component: | general | Assignee: | Jasem Mutlaq <mutlaqja> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | grave | ||
| Priority: | NOR | ||
| Version First Reported In: | 3.4.2 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | macOS | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Spinning beachball log | ||
|
Description
MountainAirCA
2020-06-18 07:53:26 UTC
I was able to capture logs of the spinning beachball capture problem, but I couldn't send them that night because I was in the middle of the desert with no Internet access. Today I fired up KStars, opened the logs directory... and the only logs I had were from today. Does KStarts automatically delete logs for previous days? If so, can this be configurable with a 10-day default? For what it's worth, the last time I was at the same dark-sky site with the same equipment and the same network gear, this beachball behavior on each image capture did not occur. There were no other changes in running software, etc. Unfortunately these intermittent issues are the worst to track down, but if it happens again I will capture the log. Created attachment 130071 [details]
Spinning beachball log
Spinnig beachball delay between exposures on Mac.
Hi Jasem, I was able to reproduce the spinning beachball problem (log attached), but I'm unsure why this happens some nights and not others. I can see a roughly ~30s delay between exposures in the log. This is perhaps not a great example because it happened during the polar alignment wizard, but I'm pretty sure it was not a plate-solving delay. Thanks for looking into it! Happens also in 3.5.0? 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! I am not sure if this still occurs, as I stopped using remote connections from one Kstars/Ekos to another. However, due to another issue with memory use on RPi-4 and full-frame cameras, I will need to test remote connections the next time I am at my dark-sky site. I will report back at that time. 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! |