#KDE #Plasma on #postmarketOS turned my Xiaomi Pad 5 Pro tablet into a laptop replacement. I've been using this for #OpenRGB development when out and about due to its smaller size and way better battery life and I've been very happy with it. The only real downside is performance, but with #OpenVPN and a decent connection I can use #waypipe to remotely use one of my Arch desktops for the more demanding things like compiling.
#waypipe
One of the saddest changes in desktop UNIX/LINUX has been the death of X11; kids these days who never ran that full GUI app elsewhere just can't understand the stunning elegance of X11.
But 👉 waypipe 👈 . Setup is a bit fidgety due to GPU expectations; yet, it works. This calculator is running elsewhere.
#wayland #waypipe #linux
i had the slight intuition that #alacritty is a bit faster if i run it on the remote computer using #waypipe . i used #termbench-pro to bench the difference is impressive:
```
ll 5 tests finished.
---------------------
many_lines: 0.0400 seconds, 80.000 MB/s (normalized: 26.649 KB/s)
long_lines: 0.0270 seconds, 118.519 MB/s (normalized: 39.480 KB/s)
sgr_fg_lines: 0.0127 seconds, 251.969 MB/s (normalized: 83.935 KB/s)
sgr_fg_bg_lines: 0.0130 seconds, 246.154 MB/s (normalized: 81.998 KB/s)
binary: 0.0368 seconds, 86.957 MB/s (normalized: 28.967 KB/s)
all tests: 1.0295 seconds, 123.552 MB/s (normalized: 41.157 KB/s)
screen size: 106x29
data size: 32.000 MB
```
vs
```
All 5 tests finished.
---------------------
many_lines: 2.0411 seconds, 13.273 MB/s (normalized: 4.421 KB/s)
long_lines: 1.0678 seconds, 19.070 MB/s (normalized: 6.353 KB/s)
sgr_fg_lines: 1.0697 seconds, 18.857 MB/s (normalized: 6.282 KB/s)
sgr_fg_bg_lines: 1.0786 seconds, 17.917 MB/s (normalized: 5.968 KB/s)
binary: 2.0604 seconds, 12.289 MB/s (normalized: 4.094 KB/s)
all tests: 10.0176 seconds, 15.723 MB/s (normalized: 5.238 KB/s)
screen size: 106x29
data size: 32.000 MB
```
This is sway, running as a nested session inside my GNOME session. This is cool, but not the coolest part of this screenshot: Sway is running on my server while GNOME is running on my laptop. And I'm not even at home where my server is, and it still hasn't much lag.
$ waypipe --no-gpu ssh server sway
See also: https://mastodon.social/@mntmn/115780763594657097 by @mntmn
#waypipe on #postmarketOS is the best solution I've ever used for running applications on my desktop at home on my phone while I'm away. It's seamless and apps show up natively alongside local apps with proper touchscreen control, mouse control (via #TouchpadEmulator), #squeekboard OSK, and scaling. I used to think ssh -X was the only thing I missed about X11, but after trying waypipe no way. X11 is dead. I don't miss it at all.
Created a textual form for this my attempt to create a software development sandbox.
#qemu #sandbox #softwareDevelopment #tinyproxy #pihole #wayland #waypipe
Here's also demonstration video for it: https://www.youtube.com/watch?v=8eDKgZFgyEs
It works fine also when running multiple Chromium windows, on monitors with different refresh rates.
With waypipe, it's quite simple to open GUI in host's Wayland compositor for apps running in containers in QEMU.
I've created a guide for this:
https://kravemir.org/how-to/run-wayland-apps-in-podman-qemu-vm-with-waypipe-through-vsock/
Currently, I'm often #NapTrapped and couldn't really keep up to @teamtype's development speed for the #IntelliJ plugin. My little 14 year old laptop cannot really run IntelliJ anymore. Really annoying how much RAM it consumes.
My desktop PC can: with waypipe and wayback-x11 one can run it remotely. Here is a sketched CLI invocation:
wayback ssh user@host wayback-session idea
I must use wayback-session because #Wakefield of #OpenJDK isn't merged into mainline, yet.
Waypipe in Action: Wayland Remote GUI Over SSH
One adavantage to handle it at the SSH transport level would be to not break graphical apps ? #waypipe
@j_r Which is to say: my post was frankly in part a bit of a fishing excursion, hoping I can find anyone to help me figure out how to get the damn #VirtualBox GUI application to work over #Waypipe 😸
@nekohayo I very much know about #waypipe but:
(1) It needs to be explicitly installed on both ends and never is by default, which is not really the case with the classic `ssh -X` or so approach
(2) In zero cases where it would have been useful for me has it actually worked, no matter what I have done. If for example you can give me the right invocations and/or setup steps to get Waypipe to work for the #VirtualBox GUI, please do, I will be forever grateful!
(1) It needs to be explicitly installed on both ends and never is by default, which is not really the case with the classic `ssh -X` or so approach
(2) In zero cases where it would have been useful for me has it actually worked, no matter what I have done. If for example you can give me the right invocations and/or setup steps to get Waypipe to work for the #VirtualBox GUI, please do, I will be forever grateful!
@danielfoster @halcy @mcc There's two problems with #waypipe that I can't help but see:
It isn't just there out of box as an inherent part of SSH and the display server, you have to manually install it on the server and client. That's a huge regression from X11 forwarding, where it's just available in basically every install and one wouldn't have to be a sysadmin on both systems to be able to install it.
While I can get it working sluggishly but fine in some test scenarios (visibly laggier on my setups that
ssh -X), any time I actually would want to use it for some practical purpose it just ends up not working. For example it has been years now and I've never figured out any environment variables or other wizardry to get the VirtualBox GUI to work with waypipe.
It is nearly the year 2025 and #Wayland still doesn't have anything that works like `ssh -X` as far as I can tell.
Like, #waypipe exists but I have yet to be able to launch a single program I wanted to with it. Meanwhile, Wayland sessions have made X11 forwarding increasingly flaky, but it at least sometimes and somewhat works . . .
Like, #waypipe exists but I have yet to be able to launch a single program I wanted to with it. Meanwhile, Wayland sessions have made X11 forwarding increasingly flaky, but it at least sometimes and somewhat works . . .
Today's bug is a small performance problem of `waypipe` when used as a client on `ChromeOS` linux VM: https://gitlab.freedesktop.org/mstoeckl/waypipe/-/issues/87
There `waypipe` uses SHM to send buffers around and performs poorly: 5-10 FPS for applications with heavy window updates.
Normally `waypipe` uses `DMABUF`s on linux and is able to optimize their transfer using a video codec. But SHM handling does not have this optimization in `waypipe`. Don't know if it's unfeasible or just a rare case.
I just played a game of Go and a game of Reversi on my #SailfishOS device. #kigo and #kreversi running on my laptop, their interface on the Phone.
Made possible through #waypipe, a kind of X11 forwarding for wayland.
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst