| 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> |
| Status: | UNCONFIRMED --- | ||
| Severity: | major | CC: | 89q1r14hd, asturm, gentoo, jstein, leio, proxy-maint, sam, sarnex |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
/etc/pipewire/pipewire-pulse.conf
emerge --info pipewire wireplumber |
||
|
Description
Randall
2022-03-06 18:58:19 UTC
Created attachment 766441 [details]
/etc/pipewire/pipewire-pulse.conf
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. 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 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. Created attachment 766442 [details]
emerge --info pipewire wireplumber
I would've said the same as Emily. Bleh. I think this is going to be need a report upstream. 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. Just to document, the way I got around the WebRTC error was just restarting Discord. (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). > 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.
(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. :) > Sorry, I meant Pipewire, but that's not a bad idea too. :) Lol. https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2197 This was broken for me and none of the workarounds worked, but somehow 0.0.24 works. Can anyone else confirm? 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. |
