Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pulseaudio and sound.extraConfig step on each other #25790

Closed
dfoxfranke opened this issue May 15, 2017 · 3 comments
Closed

Pulseaudio and sound.extraConfig step on each other #25790

dfoxfranke opened this issue May 15, 2017 · 3 comments

Comments

@dfoxfranke
Copy link
Contributor

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.

@rybern
Copy link
Contributor

rybern commented Jun 16, 2017

I am having this issue as well. Easily replicated by setting those two options.

@Mic92
Copy link
Member

Mic92 commented Jun 17, 2017

Can you make a pull request?

@bennofs
Copy link
Contributor

bennofs commented Jul 17, 2017

Should be fixed with #27000. If there still is a problem, please reopen this issue.

@bennofs bennofs closed this as completed Jul 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants