You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setting hardware.pulseaudio.enable to true while setting sound.extraConfig to any non-empty value will cause a build failure because alsa.nix and pulseaudio.nix both attempt to create /etc/asound.conf. The correct result would be for the contents of sound.extraConfig to be written out at the end of /etc/asound.conf, after the stanzas provided by pulseaudio.
Somewhat relatedly, the ! in pcm.!default and ctl.!default in pulseaudio's generated config doesn't make a whole lot of sense. ! means "override", currently there is nothing for it to override, and we would like user config to override generated config, not the other way around. However, as long as user config is placed in the file after generated config then I don't think the ! actually makes any difference.
The text was updated successfully, but these errors were encountered:
Setting
hardware.pulseaudio.enable
totrue
while settingsound.extraConfig
to any non-empty value will cause a build failure because alsa.nix and pulseaudio.nix both attempt to create /etc/asound.conf. The correct result would be for the contents ofsound.extraConfig
to be written out at the end of /etc/asound.conf, after the stanzas provided by pulseaudio.Somewhat relatedly, the
!
inpcm.!default
andctl.!default
in pulseaudio's generated config doesn't make a whole lot of sense.!
means "override", currently there is nothing for it to override, and we would like user config to override generated config, not the other way around. However, as long as user config is placed in the file after generated config then I don't think the!
actually makes any difference.The text was updated successfully, but these errors were encountered: