Bug 421929

Summary:	Launching independent KCMs now acts over existing systemsettings instance
Product:	[Applications] systemsettings	Reporter:	bluescreenavenger
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED INTENTIONAL
Severity:	normal	CC:	nate, notmart
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:

Description bluescreenavenger 2020-05-22 19:41:40 UTC

SUMMARY
This is a recent master build.

It seems that you can't start a KCM outside of SystemSettings anymore, without your existing instance of SystemSettings getting changed. Notably if you try to right click "Configure Network Connections" off the NetworkManager plasmoid, if you are working in another KCM in SystemSettings

STEPS TO REPRODUCE
1. In systemsettings, open up a KCM, like "Application Style"
2. Make an un-applied settings change, like clicking on a theme without pressing "apply"
3. Go to the NetworkManager icon, right click "Configure Network Connections"
4. Observe that instead of starting a new instance, the current instance gets taken over. Sometimes 

5. Also, If you hit "Cancel" when it prompts you to save changes, it changes KCMs anyway.



EXPECTED RESULT
This must be the change to give a full instance of SystemSettings when you launch an independent KCM. Personally though I think it might be better to start a second instance, rather than have it unexpectedly interrupt another instance of systemsettings5. 

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian
(available in About System)
KDE Plasma Version: 20.07.70
KDE Frameworks Version: 5.71.0
Qt Version: 5.15.0

ADDITIONAL INFORMATION

Comment 1 Marco Martin 2020-05-27 09:13:06 UTC

this is done by purpose.
is not possible to have 2 kcms instances open and everything must be done in order to avoid to ever have such a situation.

Comment 2 bluescreenavenger 2020-05-27 12:19:21 UTC

I guess, 
I am not sure if the new Windows 10 like behavior is best though, where opening a KCM from krunner or a context menu of a plasmoid, tries to open a full instance of System Settings, which then just takes over your existing instance, instead of opening a new window.

Comment 3 Nate Graham 2020-05-27 13:02:33 UTC

Yeah. See bug 402790. We got persistent complaints about the old behavior, so we changed it to this.

Also, for me when you switch to another KCM, if the already-open KCM has unsaved changes, it prompts me to save them. If you're seeing otherwise, it's probably a bug in that KCM itself rather than in the whole mechanism.