When a scheduler job list is loaded, and contains a non-existent or invalid sequence file, a warning is displayed. If that warning is not dismissed, and another scheduler job list is loaded, dismissing the warning afterwards crashes kstars.
Is this still an issue in GIT?
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!
Seems this is still possible: bool Capture::loadSequenceQueue(const QString &fileURL) { QFile sFile(fileURL); if (!sFile.open(QIODevice::ReadOnly)) { QString message = i18n("Unable to open file %1", fileURL); KSNotification::sorry(message, i18n("Could Not Open File")); return false; } (...)
What's the solution to this? make it auto-close?
Making the KSNotification::sorry auto-close would probably not fix the problem, e.g. when multiple consecutive ESL files contain invalid sequence files. Making the error blocking, and eventually auto-close to bypass the current item, is probably a good solution. A better solution would probably be to warn about the problem in the table directly before starting the Scheduler, say with an icon. That check could be done while evaluating, I believe there is a place we could do that when Scheduler computes the item duration. Although I think we don't necessarily evaluate before trying to open the sequence file, we would not in this case display any warning pop-up while running.
Please check against KStars 3.6.1 and report back.