Bug 223285 - Don't lose session state on a crash
Summary: Don't lose session state on a crash
Status: RESOLVED DUPLICATE of bug 60894
Alias: None
Product: ksmserver
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-18 15:17 UTC by Michael Schuerig
Modified: 2020-09-29 03:28 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Schuerig 2010-01-18 15:17:38 UTC
Version:            (using KDE 4.3.4)
OS:                Linux
Installed from:    Debian testing/unstable Packages

Sessions crash. It's been a fact of life and it will remain so in the future. The fault can lie with any number of components inside and outside of KDE.

As of KDE 4.3, the state of a session, roughly, which applications and windows are open, is only saved (unless prevented by a preference setting) when the session is orderly closed. Obviously, a crash is the opposite of orderly.

After a crash, when the user starts a new session, what they get is not the last state they've seen in their previous, ill-fated session. Rather, the state of the last orderly terminated session is resurrected. For people who regularly put their computers to sleep instead of shutting them down, this state can be days, even weeks, old.

This behavior is at best counter-intuitive and at times rather annoying. At any rate, it destroys work the user has done and does it in such a devious way that it can't even be prevented by regular backups.

So, my plea is, to not only save session state when the session is closed, but rather do it periodically, say every few minutes.
Comment 1 Nate Graham 2020-09-29 03:27:00 UTC
Yeah, this is really annoying.
Comment 2 Nate Graham 2020-09-29 03:27:30 UTC
*** Bug 311605 has been marked as a duplicate of this bug. ***
Comment 3 Nate Graham 2020-09-29 03:28:00 UTC

*** This bug has been marked as a duplicate of bug 60894 ***