Can confirm this is a bug affecting Fedora Silverblue 31.20200319.0.

I try to connect to a bluetooth speaker, connect successfully, but can only get the "system sounds" (the volume indicator sound) to play. Rhythmbox, Chrome, etc. all refuse to play out of the Bluetooth speaker and only play on the computer's speaker.

pulseaudio 13.99.1-rebootstrapped

Can confirm this broke in Wayland sessions as well, with the 13.99.1 pulseaudio update.
Downgrading to 13.0-2 fixes it. Upgrading to the 13.99.1-2 in updates-testing does *not* fix it.

journalctl --user -u pulseaudio contains the following from the bad version:

Mar 23 15:00:45 delyank-fedora-96HJ5Q2 systemd[3147]: Starting Sound Service...
Mar 23 15:00:46 delyank-fedora-96HJ5Q2 systemd[3147]: Started Sound Service.
Mar 23 15:01:21 delyank-fedora-96HJ5Q2 pulseaudio[3163]: W: [pulseaudio] module-loopback.c: Cannot set requested source latency of 66.67 ms, adjusting to 68.54 ms
Mar 23 15:01:35 delyank-fedora-96HJ5Q2 pulseaudio[3163]: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to a2dp_sink: Not connected
Mar 23 15:01:38 delyank-fedora-96HJ5Q2 pulseaudio[3163]: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to a2dp_sink: Not connected
Mar 23 15:01:40 delyank-fedora-96HJ5Q2 pulseaudio[3163]: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to a2dp_sink: Not connected
Mar 23 15:06:07 delyank-fedora-96HJ5Q2 pulseaudio[3163]: W: [pulseaudio] module.c: After module unload, module 'module-null-sink' was still loaded!
Mar 23 15:06:07 delyank-fedora-96HJ5Q2 systemd[3147]: pulseaudio.service: Succeeded.

No such output is present with the good version.

Problem still here with the recent update for pulseaudio.x86_64 13.99.1-3.fc32

It might be caused by pipewire taking over bluetooth,  >= pipewire-0.3.2-2.fc32 should have a fix

I’ve got pipewire-0.3.2-3.fc32

Confirm this bug occurs after upgrading Fedora 31 to Fedora 32.

Same exact actual results specified by @Grant (Comment 1) and issue reporter.

Bluetooth devices:
- UE (Ultimate Ears) ROLL 2
- Samsung Galaxy Buds

Packages installed (potentially related):
- pipewire-0.3.2-3.fc32
- pulseaudio-13.99.1-3.fc32

NO related log errors are output to journalctl.

Additionally to my previous comment (comment 6),

Confirm this bug occurs on Fedora 33 (either Wayland or Xorg).

Same bluetooth devices.

Packages installed (potentially related):
- pipewire-0.3.21-2.fc33
- pulseaudio-14.0-2.fc33

Following the journalctl log below, it looks like the devices is being added as a 
bluetooth keyboard instead of bluetooth earbuds/speaker.

journalctl log:
Feb 22 12:44:27 systemd[1687]: Reached target Bluetooth.
Feb 22 12:44:28 kernel: input: Galaxy Buds (50E2) (AVRCP) as /devices/virtual/input/input26
Feb 22 12:44:28 systemd-logind[876]: Watching system buttons on /dev/input/event24 (Galaxy Buds (50E2) (AVRCP))
Feb 22 12:44:28 /usr/libexec/gdm-x-session[1730]: (II) config/udev: Adding input device Galaxy Buds (50E2) (AVRCP) (/dev/input/event24)
Feb 22 12:44:28 /usr/libexec/gdm-x-session[1730]: (**) Galaxy Buds (50E2) (AVRCP): Applying InputClass "evdev keyboard catchall"
Feb 22 12:44:28 /usr/libexec/gdm-x-session[1730]: (**) Galaxy Buds (50E2) (AVRCP): Applying InputClass "libinput keyboard catchall"
Feb 22 12:44:28 /usr/libexec/gdm-x-session[1730]: (**) Galaxy Buds (50E2) (AVRCP): Applying InputClass "system-keyboard"
Feb 22 12:44:28 /usr/libexec/gdm-x-session[1730]: (II) Using input driver 'libinput' for 'Galaxy Buds (50E2) (AVRCP)'
Feb 22 12:44:28 /usr/libexec/gdm-x-session[1730]: (II) systemd-logind: got fd for /dev/input/event24 13:88 fd 65 paused 0
Feb 22 12:44:28 /usr/libexec/gdm-x-session[1730]: (**) Galaxy Buds (50E2) (AVRCP): always reports core events
Feb 22 12:44:28 /usr/libexec/gdm-x-session[1730]: (**) Option "Device" "/dev/input/event24"
Feb 22 12:44:28 /usr/libexec/gdm-x-session[1730]: (**) Option "_source" "server/udev"
Feb 22 12:44:28 /usr/libexec/gdm-x-session[1730]: (II) event24 - Galaxy Buds (50E2) (AVRCP): is tagged by udev as: Keyboard
Feb 22 12:44:28 /usr/libexec/gdm-x-session[1730]: (II) event24 - Galaxy Buds (50E2) (AVRCP): device is a keyboard
Feb 22 12:44:28 /usr/libexec/gdm-x-session[1730]: (II) event24 - Galaxy Buds (50E2) (AVRCP): device removed
Feb 22 12:44:28 /usr/libexec/gdm-x-session[1730]: (**) Option "config_info" "udev:/sys/devices/virtual/input/input26/event24"
Feb 22 12:44:28 /usr/libexec/gdm-x-session[1730]: (II) XINPUT: Adding extended input device "Galaxy Buds (50E2) (AVRCP)" (type: KEYBOARD, id 21)
Feb 22 12:44:28 /usr/libexec/gdm-x-session[1730]: (**) Option "xkb_layout" "us,il"
Feb 22 12:44:28 /usr/libexec/gdm-x-session[1730]: (**) Option "xkb_variant" ","
Feb 22 12:44:28 /usr/libexec/gdm-x-session[1730]: (**) Option "xkb_options" "grp:alt_shift_toggle"
Feb 22 12:44:28 /usr/libexec/gdm-x-session[1730]: (II) event24 - Galaxy Buds (50E2) (AVRCP): is tagged by udev as: Keyboard
Feb 22 12:44:28 /usr/libexec/gdm-x-session[1730]: (II) event24 - Galaxy Buds (50E2) (AVRCP): device is a keyboard
Feb 22 12:44:28 /usr/libexec/gdm-x-session[2768]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Feb 22 12:44:28 /usr/libexec/gdm-x-session[2768]: > Internal error:   Could not resolve keysym XF86FullScreen
Feb 22 12:44:28 /usr/libexec/gdm-x-session[2768]: Errors from xkbcomp are not fatal to the X server
Feb 22 12:44:31 bluetoothd[781]: /org/bluez/hci0/dev_00_FA_21_1C_50_E2/sep1/fd0: fd(47) ready
Feb 22 12:44:31 rtkit-daemon[798]: Supervising 3 threads of 1 processes of 1 users.
Feb 22 12:44:31 rtkit-daemon[798]: Successfully made thread 2773 of process 1702 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
Feb 22 12:44:31 rtkit-daemon[798]: Supervising 4 threads of 1 processes of 1 users.

I have nothing in journalctl except 
Mar 19 17:46:16 amphib kernel: Bluetooth: hci0: advertising data len corrected 20 -> 19

That's it. I need this to work! PANDEMIC!!!!

I have a connected device: WF-1000XM3
No sound
Removed pipewire
No sound

I would like to strangle whoever removed device management from pulseaudio settings! Everything USED to work without problems until someone had too much damned time on their hands and fixed what wasn't broken.

5.10.23-200.fc33.x86_64

This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.