https://bugs.kde.org/show_bug.cgi?id=431755
--- Comment #5 from tomtomtomreportin...@gmail.com --- 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. -- You are receiving this mail because: You are watching all bug changes.
