Bug 293905

Summary: restore last session (after reboot) really a good choise?
Product: [Unmaintained] ksmserver Reporter: FabiB <plusfabi>
Component: generalAssignee: Lubos Lunak <l.lunak>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: cfeck, nate
Priority: NOR    
Version First Reported In: 4.8.x   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description FabiB 2012-02-12 15:08:48 UTC 
Version:           Git (using KDE 4.8.0) 
OS:                Linux

Sometimes if a open a root window and shutdown i get after the bootup a message that kdesudo can not find the app and will close now. if i reboot another time the same message will pop up as long as i can not clear the old session it will come again and again. the same thing is with some wired apps they are crashed or "not really open anymore but not closed in some way". it isnt in many chases not gut to restore this apps. and the system memory will go down as well as the buutup time without resore.
so my request is not to deactivate at all but to start some research what users uses, what they want and to change this setting after that.

Reproducible: Sometimes

Steps to Reproduce:
Start some wine application, root application, and reboot

Actual Results:  
the application will opended after reboot

Expected Results:  
its maybe not the best choise to restore alle apps that where open at shutdown time
Comment 1 Christoph Feck 2012-02-13 19:11:05 UTC 
> start some research what users uses

Yes, please use the forum for a poll, not the bug tracker :)

I personally like to boot into a clean desktop, without restoring any session data. But that's because I only reboot once or month or so ...

On the other hand, with modern power management offering suspend-to-disk and suspend-to-ram, we probably do not need to use X11 session saving either.

To be decided by ksmserver developers, if poll results have been added.
Comment 2 Nate Graham 2020-09-29 03:45:29 UTC 

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