| Summary: | possible pipewire/wireplumber issue with electron-based applications | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Michelangelo Scopelliti <kernelpanic> |
| Component: | Current packages | Assignee: | Sam James <sam> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | normal | CC: | 89q1r14hd, leio |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Michelangelo Scopelliti
2022-06-24 18:15:59 UTC
Perhaps this issue https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2473 or https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2418 which might be same bug or not. If possible, please try the 9999 ebuild and with any luck it will be fixed there. If so, please let us know, since then it will hopefully also work with the next version. If that's too complicated, you can try `emerge -v1 =media-video/pipewire-0.3.51-r2` and then restart the daemons with either: systemd: systemctl --user daemon-reload && systemctl --user restart pipewire{,-pulse}.socket OpenRC (sorry in advance if I got the launcher's name wrong) : gentoo-pipewire-launcher. If you're already using 0.3.51, trying the 9999 is still a good idea but obviously it's not a regression in 0.3.52. I'll pre-emptively say that even if 9999 works, I'm not sure if it's worth trying to find and backport any fixes since that version is likely to get removed from the tree as soon as upstream makes a new release. (In reply to Niklāvs Koļesņikovs from comment #1) > Perhaps this issue > https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2473 or > https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2418 which might > be same bug or not. > > If possible, please try the 9999 ebuild and with any luck it will be fixed > there. If so, please let us know, since then it will hopefully also work > with the next version. If that's too complicated, you can try `emerge -v1 > =media-video/pipewire-0.3.51-r2` and then restart the daemons with either: > > systemd: systemctl --user daemon-reload && systemctl --user restart > pipewire{,-pulse}.socket > > OpenRC (sorry in advance if I got the launcher's name wrong) : > gentoo-pipewire-launcher. > > If you're already using 0.3.51, trying the 9999 is still a good idea but > obviously it's not a regression in 0.3.52. > > I'll pre-emptively say that even if 9999 works, I'm not sure if it's worth > trying to find and backport any fixes since that version is likely to get > removed from the tree as soon as upstream makes a new release. OK, maybe I wasn't thorough enough in my report. Up to pipewire-0.3.51-r2, everything was OK. After the upgrade to 0.3.52-r1, I started to notice microphone (and only microphone) issues. It appears that, while {microsoft,electron,chromium}-based packages are able to find and (apparently) connect to the device, they disconnect from the device (and/or are unable to find it any more). Such a failure is silent to me -- at least in the sense that these applications do not leave a log I am able to find. So, long story short: 0.3.51 works with such software; 0.3.52 don't. [...]
> So, long story short: 0.3.51 works with such software; 0.3.52 don't.
Oops. s/don't/doesn't/. Sorry.
Apparently is fixed in pipewire-0.3.54. What about closing as WORKFORME? |