Re: bluetooth pairing problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 4/24/22 07:32, stan via users wrote:
On Sat, 23 Apr 2022 19:31:57 -0700
ToddAndMargo via users <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

On 4/23/22 09:56, Joe Zeff wrote:
On 4/23/22 09:56, stan via users wrote:
Then it
becomes a manual process of listing the pulseaudio packages you
have installed, the corresponding pipewire packages available, and
installing the pipewire packages and removing the pulseaudio
packages.

Wouldn't "dnf erase *pulseaudio*" work?

# dnf erase pulseaudio*
want to erase 435 packages (2.6 GB).  It would be a disaster


# dnf swap pulseaudio pipewire
Package pipewire-0.3.50-1.fc35.x86_64 is already installed.
No match for argument: pulseaudio
No packages marked for removal.

# rpm -qa pulse*
pulseaudio-libs-15.0-2.fc35.x86_64
pulseaudio-libs-glib2-15.0-2.fc35.x86_64
pulseaudio-utils-15.0-2.fc35.x86_64
pulseaudio-libs-15.0-2.fc35.i686


What next?

If Ed's idea doesn't solve the problem, here are a couple of
suggestions.

Try
dnf swap pulseaudio\* pipewire\*
so that everything is considered in the swap.

If that doesn't work, you should try the opposite, reverting your
system to pulseaudio only, by removing all of pipewire. If everything
on your system still has dependencies on pulseaudio, it might work to do
dnf remove pipewire\*
without the huge dependency erase.  Then, run the swap command, the
inclusive one, and it should work.  Or, once pipewire is removed, just
continue using pulseaudio, as either will work, they just conflict if
both are installed (in my experience).  You won't face the problem
again until f36 or f37.

Ed it right about the cart and the horse.  Without
the pair, sound and file sharing are a moot point.

And from this:

$ rpm -qa pulse*
pulseaudio-libs-15.0-2.fc35.x86_64
pulseaudio-libs-glib2-15.0-2.fc35.x86_64
pulseaudio-utils-15.0-2.fc35.x86_64
pulseaudio-libs-15.0-2.fc35.i686

I believe I am already on pipewire and am just
looking
at pipewire's pulse plugins


_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux