https://bugs.kde.org/show_bug.cgi?id=397969
--- Comment #3 from TallFurryMan <eric.dejouha...@gmail.com> --- To clarify, the state machine of the startup sequence is not event-driven. It requests operations and considers that once they are done, they are immuable. As a result, scheduler is only looking at the state of the startup sequence from the point of view of the state machine, which may differ from the real state. I think the mount parking state was handled differently because of the possibility to park the mount during calibrations such as flat frames, which had to be reverted afterwards. -- You are receiving this mail because: You are watching all bug changes.
