Summary: | media-sound/pulseaudio-daemon ("media-sound/pulseaudio-daemon" is soft blocking media-video/pipewire-0.3.56) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Gary E. Miller <gem> |
Component: | Current packages | Assignee: | Igor V. Kovalenko <igor.v.kovalenko> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | Adrian.Bassett, gem, leio, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 744622 |
Description
Gary E. Miller
2022-07-30 21:35:08 UTC
The issue is: - media-sound/paprefs (this really does need pulseaudio-daemo, it wants 'paprefs') - media-sound/pulseaudio-ctl (this really does need pulseaudio-daemon, see https://github.com/graysky2/pulseaudio-ctl/issues/68, it wants 'pacmd') - net-wireless/blueman (I think we can ignore this one and it's noise from the above issues, its deps allow PipeWire) So, your options are: 1. emerge --depclean those first two, or 2. stick with pulseaudio-daemon. (In reply to Sam James from comment #1) > The issue is: > - media-sound/paprefs (this really does need pulseaudio-daemo, it wants > 'paprefs') > - media-sound/pulseaudio-ctl (this really does need pulseaudio-daemon, see > https://github.com/graysky2/pulseaudio-ctl/issues/68, it wants 'pacmd') And those two are very important deps. Almost impossible for me to manage without those two. > - net-wireless/blueman (I think we can ignore this one and it's noise from > the above issues, its deps allow PipeWire) I wish. I don't care for blueman, but it is buried deep in my dependencies, like a bloated tick. > So, your options are: > 1. emerge --depclean those first two, or That's not gonna happen, without working replacements. And I already tried that, many more dependencies then appear. > 2. stick with pulseaudio-daemon. That ship sailed many months ago. Far too much now demands pipewire. I did have pulseaudio and pipewire, sort of cooperating, but not after I tried to follow the news item. I reverted the changes from the news item and get back to a dual system. The news item should warn people about how they are about to wsate hours if the act on its contents. I sure hope this situation stabilizes soon, breaking my audio every few days is a PITA. (In reply to Gary E. Miller from comment #2) > (In reply to Sam James from comment #1) > > The issue is: > > - media-sound/paprefs (this really does need pulseaudio-daemo, it wants > > 'paprefs') > > - media-sound/pulseaudio-ctl (this really does need pulseaudio-daemon, see > > https://github.com/graysky2/pulseaudio-ctl/issues/68, it wants 'pacmd') > > And those two are very important deps. Almost impossible for me to manage > without those two. > > > - net-wireless/blueman (I think we can ignore this one and it's noise from > > the above issues, its deps allow PipeWire) > > I wish. I don't care for blueman, but it is buried deep in my dependencies, > like a bloated tick. > I meant ignore in the sense that it's not a problem. > > So, your options are: > > 1. emerge --depclean those first two, or > > That's not gonna happen, without working replacements. And I already tried > that, many more dependencies then appear. > OK, don't then. > > 2. stick with pulseaudio-daemon. > > That ship sailed many months ago. Far too much now demands pipewire. I did > have pulseaudio and pipewire, sort of cooperating, but not after I tried to > follow the news item. That doesn't sound right. Nothing should be requiring PipeWire as your pulseaudio daemon. Things might require PipeWire _installed_ and possibly _running_, but not acting for sound. You are free to use PulseAudio as the news item describes but still have PipeWire installed (just have USE=-sound-server on PipeWire). > > I reverted the changes from the news item and get back to a dual system. > The news item should warn people about how they are about to wsate hours if > the act on its contents. I sure hope this situation stabilizes soon, > breaking my audio every few days is a PITA. Yes, that's exactly what the point of the news item was, to stabilise the situation. It wasn't intended to "waste hours" and I spent a lot of time on trying to improve the situation. All it does is ask you to make your choice explicit. No further changes should occur after this. (to be clear, a "dual system" is still allowed by the news item, and the previous situation was just that things worked by chance.) (In reply to Sam James from comment #3) > > That ship sailed many months ago. Far too much now demands pipewire. I did > > have pulseaudio and pipewire, sort of cooperating, but not after I tried to > > follow the news item. > > That doesn't sound right. Nothing should be requiring PipeWire as your > pulseaudio daemon. Here are three: media-sound/easyeffects-6.2.8 (>=media-video/pipewire-0.3.41) media-sound/helvum-0.3.4-r2 (media-video/pipewire) media-video/wireplumber-0.4.11-r2 (>=media-video/pipewire-0.3.53-r1) I really like easyeffects, but every update breaks or fixes something different in it. > Things might require PipeWire _installed_ and possibly > _running_, but not acting for sound. All easyeffects does is sound. > You are free to use PulseAudio as the news item describes but still have > PipeWire installed (just have USE=-sound-server on PipeWire). Yes, what it was, before I tried to follow the news item. I have reverted to that, for now. > > I reverted the changes from the news item and get back to a dual system. > > The news item should warn people about how they are about to wsate hours if > > the act on its contents. I sure hope this situation stabilizes soon, > > breaking my audio every few days is a PITA. > > Yes, that's exactly what the point of the news item was, to stabilise the > situation. Well, not stable yet. Given how fast pipewire mutates, that will be hard in the short term. > It wasn't intended to "waste hours" and I spent a lot of time on trying > to improve the situation. A perfect time to thank you for all your hard work on this, and other gentoo issues. I never intended to imply anything more than that pipewire has been a PITA for everyone. At least, compared to pulseaudio, the problems are being worked on, with tantalizing glimpses of nice new features. Interspersed with weekly pain. > All it does is ask you to make your choice > explicit. I followed the news item because I really want that feature set. I really applaud the effort. But its not ready for stable yet. > No further changes should occur after this. Oh, my, with so much broken about pipewire, I sure hope progress does no stop now... (In reply to Sam James from comment #4) > (to be clear, a "dual system" is still allowed by the news item, and the > previous situation was just that things worked by chance.) If it needed chance, then I would never have gotten it to work. I followed explicit instructions from the Gentoo Wiki. Thanks! We'll get there, it's just hard. I've been really frustrated with how they keep shuffling stuff around too. what I'm confused about is, paprefs uses gsettings stuff to specifically change the settings in PulseAudio's daemon. If you're using PipeWire as your Pulse daemon, it should have 0 effect (how could it?). If you're using PulseAudio as your Pulse daemon, it should work, but then Helvum and friends won't. The exception I _think_ is if helvum etc is using non-pulse to speak to pipewire (like alsa, or jack). So, either paprefs isn't doing anything or that non-pulse is being used by some applications. - I think the same applies for at least some of media-sound/pulseaudio-ctl, but it should be easy to migrate to pacmd: https://www.reddit.com/r/archlinux/comments/ly3ycb/whats_a_replacement_for_pulseaudioctl_after/. (In reply to Sam James from comment #7) > Thanks! We'll get there, it's just hard. I've been really frustrated with > how they keep shuffling stuff around too. Two steps forward, one step back. Every few days. They do seem to me making progress, so I'll follow along. > what I'm confused about is, paprefs uses gsettings stuff to specifically > change the settings in PulseAudio's daemon. I spoke too fast. I see I have removed paprefs from some of my systems, and looking at the files, I can get rid of it completely on al my systems. > If you're using PipeWire as your > Pulse daemon, it should have 0 effect (how could it?). If you're using > PulseAudio as your Pulse daemon, it should work, but then Helvum and friends > won't. I've never got helvum to give me anything but a black window... > So, either paprefs isn't doing anything or that non-pulse is being used by > some applications. You are correct, not doing anything. My memory on what was in that package was wrong. Gone now on my hosts. > I think the same applies for at least some of media-sound/pulseaudio-ctl, I use pulseaudio-ctl to map keys and knobs to volume controls. > but it should be easy to migrate to pacmd: > https://www.reddit.com/r/archlinux/comments/ly3ycb/ > whats_a_replacement_for_pulseaudioctl_after/. You mean pactl? From the libpulse package? That could work. That info should be in the news item. So I removed those two (paprefs and pulseaudio-ctl) and the blueman blocker suddenly disappeared... I was able to emerge world per the news item. Maybe this info should be in the news item too. Thanks for the suggestions Gary. Let me try make some changes to the item... The bug has been closed via the following commit(s): https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=fbf0d8c39742d6bcedb75f94b9c94216f57ce888 commit fbf0d8c39742d6bcedb75f94b9c94216f57ce888 Author: Sam James <sam@gentoo.org> AuthorDate: 2022-07-31 03:23:58 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-07-31 03:23:58 +0000 2022-07-29-pipewire-sound-server: give advice re pulseaudio-daemon only pkgs Closes: https://bugs.gentoo.org/862402 Signed-off-by: Sam James <sam@gentoo.org> .../2022-07-29-pipewire-sound-server.en.txt | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) |