Plasma 5.20 Beta? It is rock solid, excluding the taskbar thumbnails on Wayland - or rather because Pipewire needs "per user" init scripts
by LuckyCyborg from LinuxQuestions.org on (#58CBQ)
Well, I managed to build Plasma 5.20 Beta, with Frameworks 5.74 and Applications 20.08.1 ...
So far so good, as the Plasma 5.20 Beta is surprisingly stable - basically I seen no crash under X11/Plasma5 and everything works as supposed.
Same does Wayland/Plasma5, up to the Pipewire integration for taskbar thumbnails (which works, BTW) and much more important: screen-casting - aka remote desktop tings like TeamViewer, RDP or VNC.
First of all, to bring up this Pipewire support, I needed to add a xdg-desktop-portal package, built from a SlackBuild adapted from SBo.
In the end, manually starting /usr/bin/pipewire from a console, the taskbar thumbnails works for Wayland and/or Qt applications - still no luck with Firefox, which I should keep on X11, because with the Wayland frontend it have serious rendering issues.
However, studying Pipewire, I arrived to conclusion that regarding its init scripts, it is a very special snowflake...
Apparently, we should start /usr/bin/pipewire like a daemon, when the desktop environment - Wayland/Plasma5 is bring up, and only one single instance should ran for this particular user, then to shutdown this particular daemon instance when the DE shutdown.
This should be done PER USER, as there could be several desktops started for different users in a computer.
Basically, on the other distros which are systemd-based, they uses systemd "user target" to do this trick, BUT there is no systemd in Slackware, as it is obviously...
So, I observed that Plasma 5.20 permits to configure and run startup and shutdown scripts, then I imagined something like this:
to have an /etc/user.d/user.pipewire script which is executed with the arguments of "start" or "stop" just like any init script, on startup or shutdown by the Wayland/Plasma5.
To run "/etc/user.d/user.pipewire start" as user - to bring up the Pipewire is rather simple, BUT looks like my Slack-Fu is not good enough to imagine also the "stop" case...
As I said previously, we can have several instances of /usr/bin/pipewire running - one for each user, then we should shutdown precisely the one running for our particular user, so the "killall" way looks out of scope. Rather, I need to kill a precise /usr/bin/pipewire instance.
So, I ask the Slackware Gurus to be kind to help me to imagine this special init script for Pipewire, running "as user" and "per user".
Any suggestions are appreciated.
Attached Thumbnails
So far so good, as the Plasma 5.20 Beta is surprisingly stable - basically I seen no crash under X11/Plasma5 and everything works as supposed.
Same does Wayland/Plasma5, up to the Pipewire integration for taskbar thumbnails (which works, BTW) and much more important: screen-casting - aka remote desktop tings like TeamViewer, RDP or VNC.
First of all, to bring up this Pipewire support, I needed to add a xdg-desktop-portal package, built from a SlackBuild adapted from SBo.
In the end, manually starting /usr/bin/pipewire from a console, the taskbar thumbnails works for Wayland and/or Qt applications - still no luck with Firefox, which I should keep on X11, because with the Wayland frontend it have serious rendering issues.
However, studying Pipewire, I arrived to conclusion that regarding its init scripts, it is a very special snowflake...
Apparently, we should start /usr/bin/pipewire like a daemon, when the desktop environment - Wayland/Plasma5 is bring up, and only one single instance should ran for this particular user, then to shutdown this particular daemon instance when the DE shutdown.
This should be done PER USER, as there could be several desktops started for different users in a computer.
Basically, on the other distros which are systemd-based, they uses systemd "user target" to do this trick, BUT there is no systemd in Slackware, as it is obviously...
So, I observed that Plasma 5.20 permits to configure and run startup and shutdown scripts, then I imagined something like this:
to have an /etc/user.d/user.pipewire script which is executed with the arguments of "start" or "stop" just like any init script, on startup or shutdown by the Wayland/Plasma5.
To run "/etc/user.d/user.pipewire start" as user - to bring up the Pipewire is rather simple, BUT looks like my Slack-Fu is not good enough to imagine also the "stop" case...
As I said previously, we can have several instances of /usr/bin/pipewire running - one for each user, then we should shutdown precisely the one running for our particular user, so the "killall" way looks out of scope. Rather, I need to kill a precise /usr/bin/pipewire instance.
So, I ask the Slackware Gurus to be kind to help me to imagine this special init script for Pipewire, running "as user" and "per user".
Any suggestions are appreciated.
Attached Thumbnails