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
nixos/gdm: use Fedora's PulseAudio configuration #61746
Conversation
I'm not sure if we should have this fix in nixpkgs. There's lots of reports of issues with GDM and Pulseaudio upstream and it's of my opinion that this is
Note that this actual fix, while documented in distro's wikis, I couldn't find it actually being implemented. |
It's true, I only found mentions of this fix in Debian mailing list and ArchWiki (as mentioned in a comment) and this was for Bluetooth, I needed to extend it to fix network support too.
As for whether we should fix this: I feel we should because first mentions of this bug are several years old [1] and I don't see any actual movement there. Meanwhile PulseAudio networking doesn't work at all with GDM so if we have a known fix we should provide it for our users. Finally it's non-trivial for someone to fix it in their configuration using e.g. steps from ArchWiki because we are so different.
1: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805414
…On May 20, 2019 3:00:59 PM GMT+03:00, worldofpeace ***@***.***> wrote:
I'm not sure if we should have this *fix* in nixpkgs.
There's lots of reports of issues with GDM and Pulseaudio upstream and
it's of my opinion that this is
where they should be resolved.
* https://gitlab.gnome.org/GNOME/gdm/issues/487
* https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/673
* https://gitlab.gnome.org/GNOME/gdm/issues/486
* https://gitlab.gnome.org/GNOME/gdm/issues/485
* https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/667
Note that this actual fix, while documented in distro's wikis, I
couldn't find it actually being implemented.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#61746 (comment)
--
Nikolay.
|
Latest traction to fix this issue upstream appears to be https://gitlab.freedesktop.org/pulseaudio/pulseaudio/merge_requests/10 from gazing at that debian bug thread. Though that does nothing for the networking issue. It seems arch users use https://aur.archlinux.org/packages/pulseaudio-bluetooth-a2dp-gdm-fix/ so perhaps if we want to have this we can put it in the wiki adapted so it's trivial to get working in NixOS? |
We could put this to the wiki but I'm still in favor of fixing this by default for our users; why not fix upstream now and drop the fix later when we have something proper in place? I just don't see any serious disadvantages given even Debian a11y team didn't seem to have big objections. Generally fixing upstream bugs and stacking additional patches is what distros do, provided they also report it upstream.
…On May 20, 2019 3:48:49 PM GMT+03:00, worldofpeace ***@***.***> wrote:
Latest traction to fix this issue upstream appears to be
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/merge_requests/10
from gazing at that debian bug thread. Though that does nothing for the
networking issue.
It seems arch users use
https://aur.archlinux.org/packages/pulseaudio-bluetooth-a2dp-gdm-fix/
so perhaps if we want to have this we can put it in the wiki adapted so
it's trivial to get working in NixOS?
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#61746 (comment)
--
Nikolay.
|
After more thoughts specifically about networking: it's somewhat of NixOS issue too. The same conflict will happen if there are two users logged in at the same time because we load networking modules in system-wide |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I find it reasonable to ship this in NixOS. As @abbradar says, not fixing it means users will have to do it manually.
So, no objections for merging this? |
It seems that fedora does some specific configuration for gdm and pulseaudio https://src.fedoraproject.org/rpms/gdm/blob/master/f/gdm.spec#_155 https://src.fedoraproject.org/rpms/gdm/blob/master/f/default.pa-for-gdm |
@worldofpeace Nice find! So they whitelist plugins instead of blacklisting them as I do. Pros for my solution:
Cons for my solution:
Pros for their solution:
Cons:
I say let's use Fedora's solution. |
Sounds good @abbradar. I don't have any objections to this now, I think what fedora's done with whitelisting makes more sense. I'll be testing this today 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested it and I don't seem to experience the issue with GDM catching the A2DP bluetooth sink.
So the A2DP sink works normally.
Tested on a Live system GNOME3 with GDM.
This is needed to avoid GDM PulseAudio instance acting as a network source/sink or grabing the A2DP bluetooth sink making A2DP unusable for any other user. In the future having this fixed in PulseAudio would be preferred [0]. Current possible upstream fix could be [1]. [0]: NixOS#61746 (comment) [1]: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/merge_requests/10
Thanks @abbradar ✨ |
This is needed to avoid GDM PulseAudio instance acting as a network
source/sink which is most certainly don't wanted.
Motivation for this change
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nix-review --run "nix-review wip"
./result/bin/
)nix path-info -S
before and after)