Bug 398635

Summary: When capture suspends because of guiding deviation, and capture is stopped, UI is in invalid state
Product: [Applications] kstars Reporter: TallFurryMan <eric.dejouhanet>
Component: generalAssignee: Jasem Mutlaq <mutlaqja>
Status: RESOLVED WORKSFORME    
Severity: normal    
Priority: NOR    
Version First Reported In: git   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description TallFurryMan 2018-09-14 19:51:39 UTC 
When capturing a target, it may happen than guiding deviation suspends the capture until the guide star is repositioned to the lock position. If the Capture module is stopped by the Scheduler at that moment (programmatically as opposed to through the UI), the Capture module enters a weird state where the start/stop icon expectedly displays as a "start", but where it is not possible to load a new sequence or request a preview.

Clicking the "start" button at that moment reveals that the state of the module is actually still "capturing" although no capture is taking place or can take place anymore. After clicking, the "start" button remains in state "start", but suddenly features are working again.

This seems to be a side-effect or regression of the introduction of the suspend state. Stopping the capture programmatically doesn't restore the initial configuration.
Comment 1 Jasem Mutlaq 2018-09-14 20:51:39 UTC 
Are you sure it's not CAPTURE_SUSPENDED? The logs should indicate why it was stopped (stopped, aborted, or suspended)
Comment 2 Jasem Mutlaq 2021-09-13 08:04:29 UTC 
Is this still an issue in GIT?
Comment 3 Bug Janitor Service 2021-09-28 04:35:51 UTC 
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!
Comment 4 Bug Janitor Service 2021-10-13 04:35:41 UTC 
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!
Comment 5 TallFurryMan 2021-10-17 09:11:06 UTC 
Capture has changed so much that the description doesn't match anymore. I think this should remain closed now.