Setting up a Fedora 42 Server computer as bluetooth receiver

I have a Fedora Server computer acting as a personal server for my music, movies and TV shows library that has been working phenomenally (kudos to the team!).

I also have a very nice bluetooth speaker my parents purchased me back in 2012 for my 18th birthday that, despite its age, still has excelent sound quality and which I’m happy i’ve kept.

Regrettably, considering its age, it, of course, doesn’t come with Bluetooth (it comes with AUX and with one of those proprietary Apple ports that were used pre-lightning and which is extremely useless at this point). My intention is to hook up the AUX to my Server computer, and then let the server computer act as a high-quality bluetooth receiver which I can connect all my devices to.

I have found some stuff oddly specific to the Raspberry Pi:

I have refrained from using any of these as I wouldn’t want to apply any Raspbian-specific or Raspberry-specific tweaks to my distro…

Would anyone give me a hand here? Thank you my friends :wink:

Probably because R. Pi is a small low power device that can hidden near speakers.
Do you use Gnome or KDE GUI on the server? Both provide GUI tools to set up audio output from a paired device.

Note that dual boot may add complications with pairing. Arch linux often has excellent documentation that applies to all linux distros with a bit of effort to deal with a differences in the package manager and package names. Look at https://wiki.archlinux.org/title/Bluetooth.

Do you use Gnome or KDE GUI on the server? Both provide GUI tools to set up audio output from a paired device.

Not at all. Pure Fedora Server. No GUI, just CLI.

Note that dual boot may add complications with pairing

There’s no dual boot here.

Arch linux often has excellent documentation that applies to all linux distros with a bit of effort to deal with a differences in the package manager and package names. Look at Bluetooth - ArchWiki.

Didn’t see anything there that applied. Have I missed something?

You can ignore all the GUI sections. Arch Linux makes heavy use of console tools. See:

1.1 Front-ends
1.1.1 Console

Then Section 2 starts with:

This section describes directly configuring bluez via the bluetoothctl(1) command line tool, which might not be necessary if you are using an alternative front-end tool (such as GNOME Bluetooth).

I have Fedora Server in a VM – pipewire is installed, but you probably need to add BlueTooth utilities.