|Summary:||net-im/discord-0.0.17: no audio for notifications (call, message, etc) while using media-video/pipewire|
|Product:||Gentoo Linux||Reporter:||Randall <ran.dall>|
|Component:||Current packages||Assignee:||Randall <ran.dall>|
|Severity:||major||CC:||89q1r14hd, asturm, gentoo, jstein, leio, proxy-maint, sam, sarnex|
|Package list:||Runtime testing required:||---|
emerge --info pipewire wireplumber
Description Randall 2022-03-06 18:58:19 UTC
Symptom: Discord notifications (incoming call, outgoing call, messages, etc) don't have audio while using Pipewire. Call audio still works, however, though you don't hear the ringing. Supposed Fix: Apparently, it's a known issue, and there are a few places to find a fix. The best resource I found was: https://www.reddit.com/r/archlinux/comments/t45chj/discord_pipewire_no_notification_sounds/ , which basically states to fix, you need to... 1: Update `pulse.min.quantum` in `/etc/pipewire/pipewire-pulse.conf` (which needs to be copied there in Gentoo), mine is attached. 2: Restart Pipewire (which I'm doing with systemd via `systemctl --user restart pipewire`) Outcome: That does fix the issue with the audio for notifications, however, it causes another issue with WebRTC and Discord; in which, Discord will not connect to calls anymore and be stuck on "WebRTC Connecting" essentially breaking the most important functionality. Reproducible: Always
Comment 1 Randall 2022-03-06 18:58:51 UTC
Created attachment 766441 [details] /etc/pipewire/pipewire-pulse.conf
Comment 2 Randall 2022-03-06 19:03:08 UTC
I forget to add, even after updating `pulse.min.quantum` and executing a restart or a logoff/login, the audio for notifications on Discord goes back to being no existantant until you restart Pipewire (`systemctl --user restart pipewire`) but then you get back to having WebRTC break.
Comment 3 Emily Rowlands 2022-03-06 19:10:56 UTC
What version of Pipewire is this? Can you attach `emerge --info media-video/pipewire media-video/wireplumber`? There was a bug very recently fixed that seems similar to this, see links: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2189 https://bugs.gentoo.org/834624
Comment 4 Randall 2022-03-06 19:40:55 UTC
Hey Emily. Thanks for the heads up. Upon first glance, that doesn't really seem to be what I'm experiencing; as all my audio works fine, at least on everything I've used but Discord. Regardless, I've attached the output you requested, if it helps any.
Comment 5 Randall 2022-03-06 19:41:19 UTC
Created attachment 766442 [details] emerge --info pipewire wireplumber
Comment 6 Sam James 2022-03-06 23:54:10 UTC
I would've said the same as Emily. Bleh. I think this is going to be need a report upstream.
Comment 7 Randall 2022-03-07 00:35:19 UTC
Hey Sam, thanks for chiming in. I dunno; I would find it hard to explain since audio works otherwise, and it's strictly just the audio for notifications. That said, I was able to get past the WebRTC issue. So now, the audio for notifications works only if you have updated `pulse.min.quantum` in `/etc/pipewire/pipewire-pulse.conf` (as suggested on that Reddit post) and you restart Pipewire (at least once) after logging into a session. The restarting of Pipewire must happen AT LEAST ONCE, EVERY SESSION.
Comment 8 Randall 2022-03-08 19:58:56 UTC
Just to document, the way I got around the WebRTC error was just restarting Discord.
Comment 9 Sam James 2022-03-08 20:09:12 UTC
(In reply to Randall from comment #7) > Hey Sam, thanks for chiming in. > No problem :) > I dunno; I would find it hard to explain since audio works otherwise, and > it's strictly just the audio for notifications. > I get that, but on the other hand, this isn't a downstream-induced bug, and even if you find it hard to describe, they're ultimately the people who can fix this properly, and know the right questions to ask. They're used to strange-ish problems like this, trust me. And they're nice. :) Just give us a link here once you've reported it (and link them to this bug too).
Comment 10 Randall 2022-03-09 01:14:37 UTC
> Just give us a link here once you've reported it (and link them to this bug too). I submitted a ticket (#22336059) to Discord.
Comment 11 Sam James 2022-03-09 01:15:47 UTC
(In reply to Randall from comment #10) > > Just give us a link here once you've reported it (and link them to this bug too). > > I submitted a ticket (#22336059) to Discord. Sorry, I meant Pipewire, but that's not a bad idea too. :)
Comment 12 Randall 2022-03-09 01:24:24 UTC
> Sorry, I meant Pipewire, but that's not a bad idea too. :) Lol. https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2197
Comment 13 Nick Sarnie 2023-01-14 05:36:11 UTC
This was broken for me and none of the workarounds worked, but somehow 0.0.24 works. Can anyone else confirm?
Comment 14 Randall 2023-01-14 15:27:55 UTC
This is still a hit or miss with certain systems and/or setups. Generally, it's been getting better though, but I do know some Skylake systems still have this issue. My newer systems don't have this issue though.