Immolo posted on Mon, 27 Oct 2025 11:27:37 +0000 as excerpted: > Afterwards all that should be required is a reboot, however in the > unlikely event of issues then check out how to configure PipeWire for > your purposes. > [1][2]
In case others run into the problems I did... maybe update the wiki pipewire page? I just last week upgraded alsa-only -> pipewire here, on a (kde/plasma systemd no-policykit starting plasma from a CLI login) system running gentoo ~amd64 and rolling-updated for over two decades (since 2004) and Mandrake cooker before that, and... It did *not* go as smoothly as the above implies it should have. Short- form: pipewire/wireplumber weren't launching. Long story short, CLI logins on systemd systems may in some cases not have a running user systemd, which thus won't start the pipewire units. But they don't have the alternative gentoo-pipewire-launcher script the gentoo wiki pipewire page mentions either, because pipewire[systemd] doesn't install it. Workaround: Put pipewire and wireplumber in package.use set -systemd, so the launcher script and associated xdg autostart file get installed. That worked for me (they auto-started after that as expected). Second troubleshooting tip I could have used that I didn't see on that wiki page: Users with an alsa configured via /etc/asound.conf may have to rename that file for pipewire to work correctly. More detail on the below bug. (The current theory on why I wasn't getting a systemd user session is that it's due to the way I migrated my UID from Mandrake over 20 years ago, so systemd/pam are seeing my UID as a system UID not a human-user UID, but that's not yet tested as I've been working a different bug this week.) https://bugs.gentoo.org/show_bug.cgi?id=968425 -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
