| Summary: | Multiple named sessions | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Alex Radu <AlexRadu01> |
| Component: | Session Management | Assignee: | Lubos Lunak <l.lunak> |
| Status: | CONFIRMED --- | ||
| Severity: | wishlist | CC: | adam.richard2023, aspotashev, david, jhb, kde.org, m.wege, nate, r.bauer, st99 |
| Priority: | HI | ||
| Version: | 5.27.5 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Mandrake RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Alex Radu
2003-08-05 06:44:07 UTC
Just addressing the part of windows not showing in the right places: sometimes, it's not KDE's fault that applications do not restore themselves to the right place where they should have. KDE applications are supposed to and, if they don't, you can bug their maintainers. Also note that session support is application-specific. Not all applications support session saving (KDE applications are supposed to) and some may not support multiple session saving (again, KDE applications are supposed to as well). If your applications are bugging you with these items, report to each application's maintainers. For your Control Center request, please note that they are mostly global configurations, not session options. You could file a wishlist report requesting some options be kept per session, but I highly doubt it'll get implemented (mainly because sessions are generally ephemerous while settings are permanent). Reminds me of the 'Memento' 'design pattern'. *** Bug 92060 has been marked as a duplicate of this bug. *** *** Bug 84384 has been marked as a duplicate of this bug. *** Something similar to this is hibernate. If you can turn off your computer and restore the contents of the RAM later (which you can in Linux, though I heard it's not super stable), it's perhaps better, and certainly much easier to implement, than session saving, *for desktops being used by a single user*. When you have multiple users logging in and out, you do in fact need something better. I wonder, though, whether it's really practical to have KDE do complete session saving. If it's up to the application to implement it, then it certainly can't work well for non-KDE applications, which are a good chunk of the worthwhile free applications out there. If KDE becomes the dominant desktop on Linux, then maybe it's a good idea; but even then, cross-platform applications might not be willing to add Linux-specific session management support. My idea, though I don't know whether it would work, is to have a system-wide hibernate-like feature for when users log on and log off. The program would save the state (memory contents) of all running programs *that were started from that login process* when the user logs off, and reload them when (s)he logs back on. This way you'd have reliable, simple to implement session-management which isn't KDE or even GUI-specific. If there are no problems with this idea (I suspect there are), then I'd say there's no point in improving KDE's session management. *** Bug 108218 has been marked as a duplicate of this bug. *** *** Bug 116785 has been marked as a duplicate of this bug. *** i have implemented AppGroups, a way to save several several apps that you can save/restore just like a session, but you can have as many open as you want. it lives in work/kdebase_appgroups and I am working to make it stable enough to merge in :-) @#8 AppGroups seems to be what I was just going to put on the wish list :-) I think that's just a wrapper around the normal session handling, the app shouldn't even notice, right? This feature should include the possibility to save several sessions of an application. The context menu should be extended (in case there is at least one saved session for that app) by a submenu "open as sassion A, B, C...". And there should be a "save as session <enter name>" pull down menu when you keep the close button pressed for a second (or with a control key). I would like to comment on a duplicate of this bug which seems to cover something slightly different: http://bugs.kde.org/show_bug.cgi?id=108218 Such a feature might be helpful in case KDE crashes or hangs at startup due to an app with a corrupted configuration. I think it's important to allow the user an easy reset/fallback to a working state at every level of IT. In this respect this feature would accomplish a similar goal like this one (by me): http://bugs.kde.org/show_bug.cgi?id=70288 *** Bug 146254 has been marked as a duplicate of this bug. *** Hello, I have technical notes about this bug listed at http://fulldecent.blogspot.com/2010/08/technical-notes-about-kde-ksmserver.html from my original attempt to fix it. *** Bug 199839 has been marked as a duplicate of this bug. *** |