Bug 266202

Summary:	Wrong session is restored at startup
Product:	[I don't know] kde	Reporter:	underline
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	alvaro.aguilera, nate
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description underline 2011-02-13 15:06:59 UTC

Version:           unspecified (using KDE 4.5.1) 
OS:                Linux

I had kept getting Kontact application at startup (which I didn't want also) until I selected in the session managemet the option Restore manually saves session and saved with other applications. Since that time I get Kontact and Krusader run on startup. I kept trying saving new session with different options, changed options on the session management - no help.

Reproducible: Always



Expected Results:  
Session should be saved and restored correctly.

Comment 1 Alvaro Aguilera 2011-07-13 21:24:09 UTC

I have a similar problem with ktorrent. If I manually close ktorrent and then shut down the computer, ktorrent is automatically started next time I turn on the computer.

Comment 2 Andrew Crouthamel 2018-11-06 15:07:59 UTC

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!

Comment 3 Andrew Crouthamel 2018-11-17 04:58:03 UTC

Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!

Comment 4 Nate Graham 2020-09-28 23:23:58 UTC

No response; assuming it was fixed since then.