I want to use bluez/avahi support in Pulseaudio and here is the issue.
In all-packages.nix there are pulseaudio and pulseaudioFull, the first one comes without bluez and avahi because there is no point in including support for them when pulseaudio is built as a dependency of other derivations (according to a comment). But the pulseaudio module in NixOS adds pulseaudioFull to the system environment, so it might seem that everything is OK. But.
When I log into my system pulseaudio is launched by someone else, not me. I believe it is being autostarted when KDE (phonon) tries to connect to it. Well, because KDE knows nothing about my great pulseaudio with bluez and avahi support it spawns the other one.
I’m not really sure how to fix this. looks like the only way to go is disabling pulseaudio autostart by default and spawning it explicitly from the session init scripts or something. (BTW I wasn’t following systemd development lately, so how far are we from using systemd as the user session manager?)
I want to use bluez/avahi support in Pulseaudio and here is the issue.
In
all-packages.nix
there arepulseaudio
andpulseaudioFull
, the first one comes without bluez and avahi because there is no point in including support for them when pulseaudio is built as a dependency of other derivations (according to a comment). But the pulseaudio module in NixOS addspulseaudioFull
to the system environment, so it might seem that everything is OK. But.When I log into my system pulseaudio is launched by someone else, not me. I believe it is being autostarted when KDE (phonon) tries to connect to it. Well, because KDE knows nothing about my great pulseaudio with bluez and avahi support it spawns the other one.
I’m not really sure how to fix this. looks like the only way to go is disabling pulseaudio autostart by default and spawning it explicitly from the session init scripts or something. (BTW I wasn’t following systemd development lately, so how far are we from using systemd as the user session manager?)