Am Dienstag, 5. März 2019, 11:35:51 CET schrieb Carlos E. R.:
On 04/03/2019 18.34, Maximilian Trummer wrote:
Am Montag, 4. März 2019, 10:26:55 CET schrieb Carlos E. R.:
On 04/03/2019 04.06, L A Walsh wrote:
On 2/28/2019 1:09 PM, Maximilian Trummer wrote:
When running two X sessions (KDE Plasma), I've found that the currently inactive one seems to get "hibernated" somehow. I couldn't find an answer online because all questions I found were about SSH timeouts and whatnot.
---
What do you mean by 'two X sessions'? Starting 2 copies of
the X server? Wouldn't they, by default, collide on ports?
Exit Menu, Switch user. I can then start another session as another user with Plasma, for instance.
Yes, that's exactly what I meant by 'sessions' here - just KDE's 'switch user' feature that shows SDDM again and lets you start a new KDE Plasma session. The second session is running as a different user.
When using the first described method, typically going from one desktop to the other (ctrl-alt-f8 or f7) locks the departing desktop, and I suspect it switches the "seat". Sound stops on the departing desktop, for instance. Maybe Plasma does more, like "pseudo hibernate" the departing session to conserve resources in the machine for the active seat.
Indeed, KDE seems to basically halt the entire session including audio playback. Possibly, this is a feature of the display manager, sddm. IMHO, it should be configurable. Thanks for the hint.
I don't mind it pausing audio, but is there really no way to keep network connections of inactive KDE sessions running? Do you have that network connection marked as system or use by other users or similar words?
If it is, perhaps it is a bug. It's an ethernet connection managed by NetworkManager, KDE's settings dialog says something like "all users may connect to this network" in the connection's settings.