SUMMARY The options "Load previous session" and "Save when Krita closes" options do nothing if the user has no sessions created by using the session manager. Not a regression of Krita 5. STEPS TO REPRODUCE 1. Without any sessions, enable those options in General -> Misc. 2. With an open saved document, close Krita and restart. OBSERVED RESULT A default Krita window is opened to the welcome screen. EXPECTED RESULT There should be some default session resource that the program uses/creates in such a case. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian sid KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.12.11 (Appimage)
Actually only observed in Krita 4 so far as https://bugs.kde.org/show_bug.cgi?id=443652 technically makes observing this bug in Krita 5 impossible. I guess I got confused while testing various versions.
Would this behaviour be the expected one: 1. Krita closes with "Save session on close" enabled, but there is no session in use. 2. Krita creates a new/default session file in the resources folder and saves its name to the configuration. 3. Next time when Krita opens, it's the same session being used if "Load previous session" is enabled. I have a few questions: 1. Should it always be the same session file (so overwriting over the previous session file when you repeat steps 1-3 multiple times)? Or a new one created every time the user closes Krita? (That could create way too many of them, tbh, I think the first option might be more universally useful). 2. If yes, what name should it be? I guess something that the user wouldn't use themselves? Something like "AutosavedSession.ksn"? 3. If no, I guess something like "AutosavedSession_[date-and-time].ksn"? Note that it will appear in the Sessions dialog.
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!
Sorry for the late response. The expected behavior you describe sounds fine. There should only be one autosaved session with some name like AutosavedSession.ksn. It doesn't really make sense for autosaved sessions to make use of backups, unless there were like only one or two backups.
Hey. I can confirm with the Krita Version: 5.2.0-prealpha (git 5c98a72) Appimage with Qt 5.15.7
Remove triaged keyword from CONFIRMED bugs