this post was submitted on 20 Jan 2024
7 points (100.0% liked)

Linux

1823 readers
1 users here now

Everything about Linux

RULES

founded 1 year ago
MODERATORS
 

My dream: I want a way to arbitrarily close and later open groups of applications including their states such as open files, window arrangement, scrollback, even undo histories etc. So working on a specific project I can close everything neatly and return to it later.

In my research/experiments here is what I come up with, do you agree?:

  1. in the terminal-only environment this would be tmux or another multiplexer

  2. But when you start including GUI applications (which I must), then it is something else that doesn't exactly exist

  3. Applications store their current states in a variety of places and some of them don't really do restoring in any way so it would be hard to force.

  4. the best option for this is something like xpra where you can have multiple sessions. If you had a machine that stayed powered-on all the time it might be possible to create sessions, log in remotely and use them that way.

  5. Using xpra or similar the sessions are never really actually closed. You would only close the connection from the local machine. If the machine faces a power off then too bad. As far as I can se there is basically no way to accomplish this goal where power-offs are accommodated.

I have tried some remote-login options but they are too slow for normal use. I tend to have pretty low-end hardware running (because so far it works for most things) so maybe if I upgraded it would improve.

  1. is it plausible?
  2. how to estimate hardware/performance needs of host, client and LAN? anything else to consider?

I typically use manjaro + XFCE but would be willing to try something different to accomplish the goal. I only want to do this locally on LAN not remotely.

re XFCE session managerXFCE has session management but the majority of programs don't totally work with. Like maybe the application will re-open when the session is restored but no files will be open even if they were when session was saved. Or distribution through workspaces, window size etc will not be restored.

top 4 comments
sorted by: hot top controversial new old
[–] echo64@lemmy.world 4 points 10 months ago

What you are basically finding out here is that most gui applications are written expecting only one user to be active and that weird things can/will start happening as a result.

Multi-user Gui was a bit of a momentum 20 years ago, but it's not really found a real use, so no one bothers making it work well.

However, we have hypervisors and containerized operating systems now, so if you really wanted to do this I would look into setting up an os for a project in a container, if you can get graphical applications going (you can, it's a hassle but you can) then you've a fully self contained system dedicated to that one thing.

[–] lurch@sh.itjust.works 1 points 10 months ago

You can pause VMs from VMware and Virtualbox. If you had a session with xpra or screen inside, you can restore it afterwards.

[–] aodhsishaj@lemmy.world 1 points 10 months ago
[–] Rustmilian@lemmy.world 1 points 10 months ago

It's called Compositor Hand-offs, it's coming in the future and is Wayland only.
It's likely going to be in Plasma 6 come 2024.
Restoring application state isn't the only thing it does either. It also allow for graceful crash recovery, true-full-poweroff hibernation and hot swiping supported compositors.

Cross-post : https://lemmy.world/comment/6867173