Aleksei,
On 2022-11-19 18:49, Aleksei Bavshin wrote:
On 11/18/22 18:27, Philip Rhoades wrote:
People,
Has anybody thought about / done any work on this?
When I try and replicate my Fedora KDE + Sway desktop environment on my old Zenbook with only 4gb RAM, I drive it into the ground . . I am doing more road trips now but I can't afford a new laptop ATM so I am thinking of using the old laptop like a Chromebook or remoting to my desktop and letting the desktop do all the heavy lifting.
Hi Philip,
That's odd. Minimal requirements for GNOME edition are lower than that. Are there some problems with GPU drivers and hardware acceleration or there's just not enough RAM for your work?
I think it is just not enough RAM? - but now that I think about it more - even on the desktop with 32gb RAM, running three browsers, many windows and tabs eventually grinds to a halt too after about a week or so (I leave the desktop and servers on 24x7) - and the RAM is still not maxed out . . so I guess it is really a browser problem?
Anyways, i3 may fare better on that kind of hardware, as it's less demanding to the graphics stack and has less mandatory components. And there's always a possibility of disabling optional components and decreasing resource usage with Sway.
Well that's what I would have thought . .
In the old days I played around with running remote X applications which worked but was a bit kludgey . . maybe it would be / could be nicer with Wayland?
There's two applications I'm aware of, both available in Fedora:
- wayvnc, a VNC server compatible with Sway. It will attach to an
existing session and share a single output.
Yes, I have used VNC in the past - it is good for some things . .
- waypipe, a proxy for Wayland client. It gives an experience closest
to `ssh -X app` (including the part where connection loss causes application termination).
I tried this in the last few days - quite nice . .
I'm using either of the options in my LAN whenever I need to test a random GUI app on another OS, and finding both satisfactory for that scenario. Can't tell much about suitability for remote work.
I think those would be fine for your use cases and for a minimal connection in my use case.
Just remember that Wayland was not designed for network transparency and in the case of waypipe it'll send complete rendered buffers over the network. Don't expect it to be better than X11 :)
Right - I tested it at home on the LAN and even then it was a bit laggy . .
Like a graphical version of tmux, it would be very nice to have something where I could leave my full desktop workstation setup running and then just remote into the whole desktop on a remote display . . and with a snappy connection . .
Thanks for responding!
P.