Duncan <[email protected]> writes: > 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?
Wiki accounts are free. But also, it's not actually clear what went wrong for you, or what the right edits would be. You're the best person to do that. > > 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. That is very much working around another problem. If systemd --user isn't working, as the article tells you to use, you debug that. It doesn't make sense for us to provide a workaround for it not working as that's both: a) not something I've heard of before until now; b) avoiding the real issue. > > 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.) I would expect a lot of other things to be broken in that case and for the PipeWire wiki page to not be the right place for that, beyond perhaps a tiny bit in the Troubleshooting section. > > https://bugs.gentoo.org/show_bug.cgi?id=968425
signature.asc
Description: PGP signature
