First of all, I want to thanks very much to our BDFL for merging on current the Wayland/Plasma5 changes proposed previously!
Please consider applying the following one-line patch to KWin:
Code:
diff -urN kwin-5.21.4.orig/plugins/screencast/screencastmanager.cpp kwin-5.21.4/plugins/screencast/screencastmanager.cpp
--- kwin-5.21.4.orig/plugins/screencast/screencastmanager.cpp 2021-04-06 15:27:01.000000000 +0300
+++ kwin-5.21.4/plugins/screencast/screencastmanager.cpp 2021-04-19 10:58:00.395022083 +0300
@@ -131,7 +131,7 @@
connect(waylandStream, &KWaylandServer::ScreencastStreamV1Interface::finished, stream, &PipeWireStream::stop);
connect(stream, &PipeWireStream::stopStreaming, waylandStream, [stream, waylandStream] {
waylandStream->sendClosed();
- delete stream;
+ stream->deleteLater();
});
connect(stream, &PipeWireStream::streamReady, stream, [waylandStream] (uint nodeid) {
waylandStream->sendCreated(nodeid);
It was merged for Plasma 5.22 there:
https://invent.kde.org/plasma/kwin/-/merge_requests/852
BUT, I believe that it's very important and useful to us, to apply along with now Plasma 5.21.4 and future Plasma 5.21.5, because it fixes an old caveat of Wayland/Plasma5 regarding the PipeWire video streams: KWin crashes (dragging the entire desktop with it) when PipeWire daemons stops working from whatever reasons - be it a crash or an user's manual restart of them. At least this is my past experience.
Please note that I use since several days this patch with no collateral issues and it's just about hardening the current Wayland/Plasma5 stack.
Also, it has ZERO influence on the traditional X11/Plasma5 because it's specific to
kwin_wayland.
Secondly, please consider the completition of the Wayland/Plasma5 stack, by adding also the
xdg-desktop-portal :
https://github.com/flatpak/xdg-desktop-portal
It is used by the Wayland/Plasma5 for streaming and/or recording the desktop via PipWire video streams. This means that applications like
TeamViever or any other remote desktop solution on Wayland will no work without it.
Please note that
xdg-desktop-portal-kde which actually is included offers the frontend (e.g. dialogs) and integration on Plasma5, but the backend is this
xdg-desktop-portal .
Please note also that actually the
xdg-desktop-portal is NOT used on Slackware-current by any other application beyond the Wayland/Plasma5, then I believe that is quite safe to consider that there no influence on the Slackware-current stack. Eventually, it's a hard dependency for an eventual (custom installed)
FlatPak package, as originally it's supposed.
The third proposal is just cosmetic - the daemon supervisor made by
@raforg was added on
N series, but its main purpose is of generic daemon capable to run (and supervise) programs on background, for example on init scripts.
It's integration with elogind was added specifically for Slackware, on a feature request made by @ZhaoLin1457, and it's an optional feature. Then we could use it well also for its original purpose.
From what I known, we can say that that daemon of
@raforg is the little brother of the more known
daemontools of D. J. Bernstein :
https://cr.yp.to/daemontools.html
That's WHY I believe that its place is probably best on the
A series along with init system and elogind - after all, it has no network capabilities and it's a (init) system tool.
