[arch-general] headless box audio with pipewire
Hello ! I have a box, where I can login through SSH, start ncmpcpp to play something with mpd, and then logout, leaving the box playing music, but with no user logged in. At times, I also want to start Xorg (eventually Wayland), and use pipewire for sound and even using bluetooth audio devices (easy with pipewire/pulse). While logged in, I can use pipewire even in console. But once logged out, sound is gone. So pipewire doesn't really work headless by default, is there a way to make it work headless (no one logged in, and still having audio enabled and playing music for example), how so? With alsa, no pipewire, no pulse, all this is pretty simple, since it executes as root, headless audio (no one logged in), audio on console (no Xorg, no Wayland), audio on graphical environmet (Xorg or Wayland). Complex thing with alsa, like using bluetooth devices, or selecting devices is complex. An alternative would be having an easy way to use bluetooth devices with plain alsa (no need for command line for example, since not all users will be able to do that). I think bluez-alsa-git on AUR can help using bluetooth audio devices with plain alsa, but it's somehow complex for non CLI users. Perhaps it's easier to get a box, which when headless, somehow allows alsa to work, and when logged in, pipewire/pulse takes over. But things don't work that way when pipewire/pulse is present, audio is gone when not logged in. Thanks ! -- Javier
On January 30, 2022 4:37:26 AM GMT+01:00, Javier via arch-general <arch-general@lists.archlinux.org> wrote:
I have a box, where I can login through SSH, start ncmpcpp to play something with mpd, and then logout, leaving the box playing music, but with no user logged in. At times, I also want to start Xorg (eventually Wayland), and use pipewire for sound and even using bluetooth audio devices (easy with pipewire/pulse).
While logged in, I can use pipewire even in console. But once logged out, sound is gone. So pipewire doesn't really work headless by default, is there a way to make it work headless (no one logged in, and still having audio enabled and playing music for example), how so?
For your user@.service to remain running (and be automatically started during boot) you will want to enable linger [1]. This allows for your pipewire user service (which runs in the scope of your user's user@.service) to automatically run on boot and keep running without you having a session (which is the usual way for systemd to start your user's user@.service). Best, David [1] https://wiki.archlinux.org/title/Systemd/User#Automatic_start-up_of_systemd_... -- https://sleepmap.de
On 1/30/22 02:23, David Runge wrote:
On January 30, 2022 4:37:26 AM GMT+01:00, Javier via arch-general <arch-general@lists.archlinux.org> wrote:
I have a box, where I can login through SSH, start ncmpcpp to play something with mpd, and then logout, leaving the box playing music, but with no user logged in. At times, I also want to start Xorg (eventually Wayland), and use pipewire for sound and even using bluetooth audio devices (easy with pipewire/pulse).
While logged in, I can use pipewire even in console. But once logged out, sound is gone. So pipewire doesn't really work headless by default, is there a way to make it work headless (no one logged in, and still having audio enabled and playing music for example), how so?
For your user@.service to remain running (and be automatically started during boot) you will want to enable linger [1]. This allows for your pipewire user service (which runs in the scope of your user's user@.service) to automatically run on boot and keep running without you having a session (which is the usual way for systemd to start your user's user@.service).
Best, David
[1] https://wiki.archlinux.org/title/Systemd/User#Automatic_start-up_of_systemd_...
Thanks ! -- Javier
Hi,
Thanks !
I stumbled upon a similar problem, even with lingering enabled pipewire-media-session ended after some hours while being logged out. Then I tried wireplumper and it was "worse", the sound stopped just when logging out - also with lingering enabled. On IRC in #pipewire me was told to copy /usr/share/wireplumber/bluetooth.lua.d/30-bluez-monitor.lua to /usr/share/wireplumber/bluetooth.lua.d/30-bluez-monitor.lua of my user and then comment out 'load_optional_module("logind")' - now the output is fine. HTH Bjoern
On 1/30/22 09:47, Bjoern Franke via arch-general wrote:
... On IRC in #pipewire me was told to copy /usr/share/wireplumber/bluetooth.lua.d/30-bluez-monitor.lua to /usr/share/wireplumber/bluetooth.lua.d/30-bluez-monitor.lua of my user and then comment out 'load_optional_module("logind")' - now the output is fine.
HTH Bjoern
Ohh, interesting, thanks a lot ! -- Javier
participants (3)
-
Bjoern Franke
-
David Runge
-
Javier