Bug 20173

Summary:	"Restore previous session" does not restart a number of programs.
Product:	Mageia	Reporter:	w unruh <unruh>
Component:	RPM Packages	Assignee:	KDE maintainers <kde>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	plasma5?	CVE:
Status comment:

Description w unruh 2017-01-24 18:39:10 CET

Description of problem:In SystemSettings->StartupandShutdown->DesktopSetting I have "Restore previous session" clicked on. But a number of programs are not restarted even if they were running in the session when I logged out or shut down the system.

Thus the following did startup again on the previous session
Konsole, audacity, libreoffice, firefox, konqueror, Network Center,

The following did not start up again automatically
Chrome, xmaple, klatexformula, VLC

The especially annoying one is chrome. 


Version-Release number of selected component (if applicable):


How reproducible:
Always at least with chrome. I have not tested the others extensively enough.

Steps to Reproduce:
1.Open chrome on the plasma 5 desktop.
2.logout or shutdown from the desktop "right click-> Leave->Logout"
3.login again to Plasma 5. No chrome.

Comment 1 Marja Van Waes 2017-01-24 20:27:28 CET

The same issue was fixed before , see bug 18813 and bug 16850 ... don't know why it happens again :-/

CC: (none) => marja11
Assignee: bugsquad => kde

Comment 2 w unruh 2017-01-25 00:12:57 CET

Perhaps different programs. As I said, some are restored, and some are not. 
You can add gimp to the list of the ones that are restored. 

Looking over those other bug numbers, one thing is that my .config/session has about 120 entries in it. Konqueror (I never use konqueror so not sure why they are there) , konsole, are the dominant ones, dating back to when I installed Mga6.
dolphin has a few. So something is also not erasing things which should be erased. No idea if this is related to the above bug however.

Comment 3 w unruh 2018-07-12 09:24:13 CEST

Although this was a year and a half ago the latest mass update to kde in Mga6 seems to have solved this problem.

Status: NEW => RESOLVED
Resolution: (none) => FIXED