Created attachment 684825 [details] emerge --info Since version 5.0.0 Pulseeffects has switched to exclusively using PipeWire as audio server (see https://github.com/wwmm/pulseeffects/blob/master/CHANGELOG.md for version 5.0.0). This causes the following error if PipeWire is not running/the default audio server: pulseeffects-ERROR **: 00:30:07.736: pipe_manager: context connection failed There is a "legacy" PulseAudio branch available in the repository, but this is not reflected in the package. Users are not being told about this change during/after emerging, so there is no way to know that the switch has occurred until they do an update and find that Pulseeffects is no longer working. Is there perhaps a way to automatically mask the new version or prevent installation e.g. if the global "pulseaudio" USE flag is set? In any case, I think that the package emerge should at least tell the user that PulseAudio is no longer supported. Thanks, Marcus
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=84bd9686689ebbd57daff119d52b853c319c2881 commit 84bd9686689ebbd57daff119d52b853c319c2881 Author: Matthew Thode <prometheanfire@gentoo.org> AuthorDate: 2021-01-26 22:33:49 +0000 Commit: Matthew Thode <prometheanfire@gentoo.org> CommitDate: 2021-01-26 22:34:21 +0000 media-sound/pulseeffects: add warning about switching to pipewire Closes: https://bugs.gentoo.org/767370 Package-Manager: Portage-3.0.13, Repoman-3.0.2 Signed-off-by: Matthew Thode <prometheanfire@gentoo.org> media-sound/pulseeffects/pulseeffects-5.0.0.ebuild | 11 +++++++++++ media-sound/pulseeffects/pulseeffects-9999.ebuild | 11 +++++++++++ 2 files changed, 22 insertions(+)
*** Bug 773631 has been marked as a duplicate of this bug. ***
