[opensuse-support] How to keep X session in background active?
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. The most annoying side effect of that is network connections being terminated, but it also has other effects like the analog clock widget being halted so you see the cursor jump after you switch back to that session. Sometimes the secondary X session also locks the screen as you switch to it, because it suddenly awoke from its slumber and noticed that it should be locked already after that time. What's the reason for this behaviour? Is there any way to keep everything active and running in inactive X sessions? regards
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?
The most annoying side effect of that is network connections being terminated, but it also has other effects like the analog clock widget being halted so you see the cursor jump after you switch back to that session.
--- Hmmm....How do you get a 'session'? Like in a virtual machine? Well, yeah, if something is suspending them, then they won't respond with 'keepalives' and the host that was connected will time them out. -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 04/03/2019 13:36, 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?
Back in the day I used to run multiple X sessions all the time, I'd run one per screen and they'd share mouse / keyboard. It meant that while you couldn't drag windows between screens you could change workspace / virtual desktop on one montor and it wouldn't change on the other. Not sure if any DE's support that properly anymore but enlightenment implements the functionality without needing multiple x servers. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
* Simon Lees <sflees@suse.de> [03-03-19 23:15]:
On 04/03/2019 13:36, 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?
Back in the day I used to run multiple X sessions all the time, I'd run one per screen and they'd share mouse / keyboard. It meant that while you couldn't drag windows between screens you could change workspace / virtual desktop on one montor and it wouldn't change on the other. Not sure if any DE's support that properly anymore but enlightenment implements the functionality without needing multiple x servers.
startx /usr/bin/<de> -- :0 startx /usr/bin/<de> -- :1 startx /usr/bin/<de> -- :2 no problem running multi X sessions, each in a different screen -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 04/03/2019 23:30, Patrick Shanahan wrote:
* Simon Lees <sflees@suse.de> [03-03-19 23:15]:
On 04/03/2019 13:36, 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?
Back in the day I used to run multiple X sessions all the time, I'd run one per screen and they'd share mouse / keyboard. It meant that while you couldn't drag windows between screens you could change workspace / virtual desktop on one montor and it wouldn't change on the other. Not sure if any DE's support that properly anymore but enlightenment implements the functionality without needing multiple x servers.
startx /usr/bin/<de> -- :0 startx /usr/bin/<de> -- :1 startx /usr/bin/<de> -- :2
no problem running multi X sessions, each in a different screen
How well all DE's support this is another question however, given they might be trying to write temporary config to the same location. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Simon Lees composed on 2019-03-07 18:36 (UTC+1030):
Patrick Shanahan wrote:
startx /usr/bin/<de> -- :0 startx /usr/bin/<de> -- :1 startx /usr/bin/<de> -- :2
no problem running multi X sessions, each in a different screen
How well all DE's support this is another question however, given they might be trying to write temporary config to the same location.
Is Egbert Eich's startx instruction no longer valid? It did still work for me less than a week ago. WINDOWMANAGER=/usr/bin/<de> startx -- :1 https://bugzilla.opensuse.org/show_bug.cgi?id=929016 https://bugzilla.opensuse.org/show_bug.cgi?id=971885 -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
* Felix Miata <mrmazda@earthlink.net> [03-07-19 03:08]:
Simon Lees composed on 2019-03-07 18:36 (UTC+1030):
Patrick Shanahan wrote:
startx /usr/bin/<de> -- :0 startx /usr/bin/<de> -- :1 startx /usr/bin/<de> -- :2
no problem running multi X sessions, each in a different screen
How well all DE's support this is another question however, given they might be trying to write temporary config to the same location.
Is Egbert Eich's startx instruction no longer valid? It did still work for me less than a week ago.
WINDOWMANAGER=/usr/bin/<de> startx -- :1
did you try any/either of the above? perhaps this would not have been necessary? all work for me but the examples I listed are less typing -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
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?
I can do it easily enough while using XFCE. Exit Menu, Switch user. I can then start another session as another user with Plasma, for instance. Nother method. In my notes I have: startx kde -- :1 that would start another desktop, bypassing the window manager. The collisions I have seen were when using the same user for both sessions, because the desktops would use the same files for writing, twice. 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. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
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.
I don't mind it pausing audio, but is there really no way to keep network connections of inactive KDE sessions running?
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.
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. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
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.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2019-03-05 a las 18:38 +0100, Maximilian Trummer escribió:
Am Dienstag, 5. März 2019, 11:35:51 CET schrieb Carlos E. R.:
...
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.
Yes, that's the wording, I'm now on another machien that uses NM. Well, unless you find some configuration for sddm (I don't know where, now), I would report in bugzilla and see... - -- Cheers Carlos E. R. (from openSUSE Leap 15.0 x86_64 (Minas Tirith)) -----BEGIN PGP SIGNATURE----- iJIEAREIADoWIQQt/vKEw5659AgM/X2NrxRtxRYzXAUCXH8sJxwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJEI2vFG3FFjNcm0oBAJuigs9GCv6vG99CnhKr b4k/hp7MlgVn0XUvOiQuchzQAQCJRT7nJjvczAvOu6Ljf1woI8T3a9SQ9AZlXM6/ FF79wA== =Wr2r -----END PGP SIGNATURE-----
Op woensdag 6 maart 2019 03:10:47 CET schreef Carlos E. R.:
El 2019-03-05 a las 18:38 +0100, Maximilian Trummer escribió:
Am Dienstag, 5. März 2019, 11:35:51 CET schrieb Carlos E. R.: ...
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.
If the network is encrypted you also need to set the passphrase to be readable to all users in the security tab of KDE's NM settings.
Yes, that's the wording, I'm now on another machien that uses NM.
Well, unless you find some configuration for sddm (I don't know where, now), I would report in bugzilla and see...
-- Cheers Carlos E. R.
(from openSUSE Leap 15.0 x86_64 (Minas Tirith))
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 3/5/19 10:05 PM, Knurpht-openSUSE wrote:
Op woensdag 6 maart 2019 03:10:47 CET schreef Carlos E. R.:
El 2019-03-05 a las 18:38 +0100, Maximilian Trummer escribió:
Am Dienstag, 5. März 2019, 11:35:51 CET schrieb Carlos E. R.: ...
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. If the network is encrypted you also need to set the passphrase to be readable to all users in the security tab of KDE's NM settings. Yes, that's the wording, I'm now on another machien that uses NM.
Well, unless you find some configuration for sddm (I don't know where, now), I would report in bugzilla and see...
-- Cheers Carlos E. R.
(from openSUSE Leap 15.0 x86_64 (Minas Tirith))
So I could be totally out in left field, and please excuse me if I am, but I use 'loginctl' to manage X11 sessions on Gnome. Specifically, 'loginctl list-sessions' and 'loginctl session-status <session id>' might be a good place to start, if Plasma uses systemd. I believe that multiple sessions would have different 'seats', and you can detect which one is active in the 'State' field of session-status (or use 'loginctl activate...' to activate one or the other). From there, you would have to figure out what 'active' means (with respect to audio, network, etc.). Still, how you would keep more than one X11 session active if you have only one monitor-mouse-keyboard, I am not sure. -- Patrick McNeil Université de Montréal - TI Pav. Roger-Gaudry, X-205 ☎ Téléphone: (514) 343-6111, poste 5247 📧 Courriel: patrick.mcneil@umontreal.ca 📠 Télécopie/FAX: (514) 343-2155
participants (8)
-
Carlos E. R. -
Felix Miata -
Knurpht-openSUSE -
L A Walsh -
Maximilian Trummer -
Patrick McNeil -
Patrick Shanahan -
Simon Lees