Sudo dnf update: requires pulseaudio, but none of the providers can be installed

doesn’t seem like just “wait a while and try again” ??

shall I sudo dnf upgrade --best --allowerasing ??

and

Removing dependent packages:
pulseaudio-qubes x86_64 4.0.31-1.fc32 @qubes-vm-r4.0-current 41 k
qubes-vm-recommended noarch 4.0.7-1.fc32 @qubes-builder-vm-r4.0-current-testing


Problem 1: package pulseaudio-qubes-4.0.31-1.fc32.x86_64 requires pulseaudio = 13.99.1, but none of the providers can be installed

  • cannot install both pulseaudio-14.0-1.fc32.x86_64 and pulseaudio-13.99.1-4.fc32.x86_64
  • cannot install both pulseaudio-13.99.1-3.fc32.x86_64 and pulseaudio-14.0-1.fc32.x86_64
  • cannot install the best update candidate for package pulseaudio-qubes-4.0.31-1.fc32.x86_64
  • cannot install the best update candidate for package pulseaudio-13.99.1-4.fc32.x86_64
    Problem 2: problem with installed package pulseaudio-qubes-4.0.31-1.fc32.x86_64
  • package pulseaudio-qubes-4.0.31-1.fc32.x86_64 requires pulseaudio = 13.99.1, but none of the providers can be installed
  • package pulseaudio-13.99.1-4.fc32.x86_64 requires pulseaudio-libs(x86-64) = 13.99.1-4.fc32, but none of the providers can be installed
  • package pulseaudio-13.99.1-3.fc32.x86_64 requires pulseaudio-libs(x86-64) = 13.99.1-3.fc32, but none of the providers can be installed
  • cannot install both pulseaudio-libs-14.0-1.fc32.x86_64 and pulseaudio-libs-13.99.1-4.fc32.x86_64
  • cannot install both pulseaudio-libs-13.99.1-3.fc32.x86_64 and pulseaudio-libs-14.0-1.fc32.x86_64
  • cannot install the best update candidate for package pulseaudio-libs-13.99.1-4.fc32.x86_64
    Problem 3: package qubes-vm-recommended-4.0.7-1.fc32.noarch requires pulseaudio-qubes, but none of the providers can be installed
  • package pulseaudio-qubes-4.0.31-1.fc32.x86_64 requires pulseaudio = 13.99.1, but none of the providers can be installed
  • package pulseaudio-qubes-4.0.29-1.fc32.x86_64 requires pulseaudio = 13.99.1, but none of the providers can be installed
  • package pulseaudio-qubes-4.0.30-1.fc32.x86_64 requires pulseaudio = 13.99.1, but none of the providers can be installed
  • cannot install both pulseaudio-14.0-1.fc32.x86_64 and pulseaudio-13.99.1-4.fc32.x86_64
  • cannot install both pulseaudio-13.99.1-3.fc32.x86_64 and pulseaudio-14.0-1.fc32.x86_64
  • package pulseaudio-module-bluetooth-14.0-1.fc32.x86_64 requires libpulsecore-14.0.so()(64bit), but none of the providers can be installed
  • package pulseaudio-module-bluetooth-14.0-1.fc32.x86_64 requires pulseaudio(x86-64) = 14.0-1.fc32, but none of the providers can be installed
  • cannot install the best update candidate for package qubes-vm-recommended-4.0.7-1.fc32.noarch
  • cannot install the best update candidate for package pulseaudio-module-bluetooth-13.99.1-4.fc32.x86_64
    Problem 4: problem with installed package qubes-vm-recommended-4.0.7-1.fc32.noarch
  • package qubes-vm-recommended-4.0.7-1.fc32.noarch requires pulseaudio-qubes, but none of the providers can be installed
  • package pulseaudio-qubes-4.0.31-1.fc32.x86_64 requires pulseaudio = 13.99.1, but none of the providers can be installed
  • package pulseaudio-qubes-4.0.29-1.fc32.x86_64 requires pulseaudio = 13.99.1, but none of the providers can be installed
  • package pulseaudio-qubes-4.0.30-1.fc32.x86_64 requires pulseaudio = 13.99.1, but none of the providers can be installed
  • cannot install both pulseaudio-14.0-1.fc32.x86_64 and pulseaudio-13.99.1-4.fc32.x86_64
  • cannot install both pulseaudio-13.99.1-3.fc32.x86_64 and pulseaudio-14.0-1.fc32.x86_64
  • package pulseaudio-module-x11-14.0-1.fc32.x86_64 requires libpulsecore-14.0.so()(64bit), but none of the providers can be installed
  • package pulseaudio-module-x11-14.0-1.fc32.x86_64 requires pulseaudio(x86-64) = 14.0-1.fc32, but none of the providers can be installed
  • cannot install the best update candidate for package pulseaudio-module-x11-13.99.1-4.fc32.x86_64

It’s a recurring problem with Qubes, though it hasn’t happen for a while I think. Maybe someone can explain it. The best think you can do is to wait for the developers to fix this (and potentially get an early update from the testing repo).

And by the way, --allowerasing is probably dangerous, but this is Qubes, so you can easily see what happens on a copy of your template.

ok thanks i’ll just ignore it and wait a month or so

Known bug; fix on the way:

1 Like

This problem is happening because we need to include Pulseaudio headers into the gui-agent which force us to track new version happening very often. All of this because of missing user API. I’ve made two days ago a helper script to automatize the pull of the headers. Next step is like for kernel to have automatic PR for that. We are even considering to move to PipeWire.

1 Like

(@Clodius, I’ve made the title to make it more specific to the problem so others in a similar situation find it quickly)

fed32 appears to now be happy and gear icons goes away

1 Like