Am Freitag, 21. September 2018, 20:29:11 schrieb s2 johnm:
Any hope to fix this year?
Well, it probably won't get fixed by mentioning it *here*... ;-) X11 Session management is a client/server protocol (in this case, Plasma/ksmserver is the "server" and Chrome/Chromium is the "client"), it needs to be implemented correctly by *both* sides to make it work as expected. So, the main question is which side is "wrong", I suppose. As it works with other clients AFAICT, one could argue that the problem lies rather with Chrome/Chromium than with Plasma/ksmserver, but it might be an edge case. Maybe you could provide references to your statement that both sides say it's a problem on the other side? (to have more context) What *might* happen is that Chrome/Chromium doesn't respond in time to the request to save its state, and so gets killed by ksmserver (which actually *is* part of the protocol AFAIK). I don't have Chrome or Chromium installed myself though, so can't tell what happens. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org