| Summary: | Krita continues running in the background after closing session manager | ||
|---|---|---|---|
| Product: | [Applications] krita | Reporter: | tomtomtomreportingin |
| Component: | General | Assignee: | Krita Bugs <krita-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | halla, tamtamy.tymona, vitamorus.art |
| Priority: | NOR | ||
| Version: | 4.4.1 | ||
| Target Milestone: | --- | ||
| Platform: | Appimage | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
tomtomtomreportingin
2021-01-17 20:45:53 UTC
What do you mean with "the session manager"? And where do you find "General -> Miscellaneous"? You can enable the session manager by going to Settings -> Configure Krita -> General -> Miscellaneous tab -> When Krita starts: Show session manager. Ah, thanks for the clarification! I had completely forgotten about that feature... And yes, I can confirm the issue, Krita keeps running. Thanks for the report :-) > 3. When the session manager appears, close it.
> Krita should properly exit.
By "running in the background" I guess you mean that there is no window open, but the Krita process is somewhere on the system running?
Is that really the expected behaviour that Krita would close? I mean I would expect Krita in that case to just open fully with no images open.
I'm not sure what behavior would be preferable as I don't really use this feature. Currently: * Double-clicking a session opens the session and closes the session manager. * The "Switch to" button opens the session and leaves the session manager open. Closing that session manager leaves the Krita session open. * Hitting the x-button or Close without any Krita session open leaves Krita running as a background process that must be killed with ksysguard or so on. I would suggest adding a "Default session" button that would perform the way you described, and making close actions (when a session isn't already running) not leave behind a background process. I think that would be the best option, too. Maybe not "Default session" but "Empty session" though, since default suggests that there is a session that you marked as default, while empty clearly says that it will be empty. Git commit b93943afaba69b3038e29c1ff49cfb4656e9ebd6 by Alvin Wong. Committed on 14/08/2023 at 16:04. Pushed by alvinwong into branch 'master'. Show main window when closing session manager Don't just leave the Krita process running in the background, give the user something to work with. M +6 -0 libs/ui/dialogs/KisSessionManagerDialog.cpp https://invent.kde.org/graphics/krita/-/commit/b93943afaba69b3038e29c1ff49cfb4656e9ebd6 Git commit b294f3b28f2b42151725855dc77422f252049fd7 by Alvin Wong. Committed on 14/08/2023 at 16:04. Pushed by alvinwong into branch 'krita/5.2'. Show main window when closing session manager Don't just leave the Krita process running in the background, give the user something to work with. (cherry picked from commit b93943afaba69b3038e29c1ff49cfb4656e9ebd6) M +6 -0 libs/ui/dialogs/KisSessionManagerDialog.cpp https://invent.kde.org/graphics/krita/-/commit/b294f3b28f2b42151725855dc77422f252049fd7 Alvin's patch solves the main issue of this bug report so I'll mark it as resolved. It's arguably a bit weird in terms of UX, though, so I've filed a wishlist report (Bug 497371) for further discussion. |