How to Fix Bluetooth Headphones Connecting but No Sound in Ubuntu 24.04

Your Bluetooth headphones connect without any error. Ubuntu 24.04 shows them as paired and connected, the battery level appears, and everything looks healthy. Then you press play and hear nothing at all, or the sound keeps coming out of your laptop speakers instead.

This is one of the most common Bluetooth frustrations on Ubuntu, and it is rarely a broken headset. Usually the audio is routed to the wrong output, the wrong profile is selected, or the PipeWire audio system has lost track of the device. This guide takes you through the checks in the right order, from the simple volume and output settings to restarting services and fixing profile problems.

Quick Answer

Open Settings, go to Sound, and select your headphones as the output device instead of the speakers. Then check the headphone profile is set to a stereo music profile such as A2DP or aptX, not the low-quality headset profile. If sound is still missing, restart the audio stack with systemctl --user restart pipewire wireplumber and reconnect the headphones.

How Sound Travels to Bluetooth Headphones in Ubuntu 24.04

Ubuntu 24.04 uses PipeWire for audio, with WirePlumber managing devices and sessions. Your headphones connect through BlueZ, the Bluetooth stack, and then PipeWire presents them as an audio output. A failure can happen at any of these three layers, which is why the fix depends on finding the right layer.

Output Routing

Connecting headphones does not always switch the output automatically, especially if you connected them before opening your music or video app, or if you previously set a fixed output. Ubuntu may happily keep sending sound to speakers or an HDMI monitor with no speakers attached.

Profiles Decide Quality and Direction

Bluetooth audio profiles control what the headphones do. A stereo profile sends high-quality music to the headphones. A headset profile opens the microphone but drops quality sharply, and some apps or buggy profile switches leave the device in a half-active state where nothing plays at all. If the wrong profile is stuck, connected can still mean silent.

Step 1: Check Volume, Output, and the Obvious Things

1. Play something continuous, like a long video, so you can hear the moment sound returns.
2. Click the system menu in the top-right corner and confirm the volume slider is up and not muted.
3. Open Settings > Sound and look at the Output Device list.
4. Select your headphones by name. Do not assume the selection changed when they connected.
5. Use the Test button in Sound settings and listen for the test voice in each ear.
6. Check the volume on the headphones themselves, as many models keep their own volume level separate from the system.
7. Disconnect the headphones from your phone or any other device. Most headphones can only play from one active source, and a phone holding the connection is a classic hidden cause.

Also open the volume panel’s per-app section or install pavucontrol with sudo apt install pavucontrol. In its Playback tab you can see each app and the device it is sending sound to. A single app aimed at the wrong output explains sound in a browser but silence in a music player, or the reverse.

Step 2: Fix the Audio Profile

1. In Settings > Sound, select your headphones and open the profile or configuration options if shown.
2. Choose a stereo music profile. Names vary, but look for High Fidelity Playback, A2DP Sink, or a codec name such as SBC, AAC, or aptX.
3. Avoid the Headset Head Unit or HSP/HFP profile for music. Use it only when you need the headphone microphone for calls.
4. In pavucontrol, open the Configuration tab, find your headphones, and set the profile there if Settings does not show it.
5. After changing the profile, stop and restart playback. Some players need a fresh start to pick up the new route.

If you need the microphone and stereo sound together, understand the Bluetooth limit: the classic headset profile is mono and low quality by design. For calls, accept the headset profile during the call, then switch back to the stereo profile for music. Our guide to fixing Bluetooth headphone microphones on Linux explains call setups and PipeWire microphone options in more depth.

Step 3: Restart PipeWire and WirePlumber

If the output and profile look right but silence continues, restart the user audio services. This clears stuck states without a full reboot.

1. Pause your playback.
2. Open a terminal and run systemctl --user restart pipewire pipewire-pulse wireplumber.
3. Wait five seconds, then check status with systemctl --user status pipewire wireplumber if problems continue.
4. Disconnect and reconnect the headphones from the Bluetooth menu.
5. Select the headphones as the output again, because a service restart can reset the choice.
6. Play your test sound.

You can inspect what PipeWire sees with wpctl status, which lists audio devices and shows which output is currently the default, marked with a star. The official PipeWire documentation explains how sinks, sources, and session management fit together if you want the background behind these commands.

Step 4: Remove and Pair the Headphones Again

A corrupted pairing record can survive many reconnects. A clean pairing fixes stubborn cases.

1. Open Settings > Bluetooth, select your headphones, and choose Remove Device.
2. Turn Bluetooth off, wait ten seconds, and turn it on again.
3. Put the headphones into pairing mode properly, usually by holding the power or Bluetooth button until the light flashes in the pairing pattern. A normal power-on is not always pairing mode.
4. Select the headphones when they appear, complete pairing, and wait for the connected message.
5. Go straight to Sound settings, select them as output, and test before opening other apps.

From the terminal, bluetoothctl devices lists known devices, and bluetoothctl info followed by your device address shows pairing and connection details. The Ubuntu help pages collected under the official Ubuntu Bluetooth documentation cover pairing basics and device-specific notes.

Step 5: Check for Conflicts and Deeper Faults

• HDMI stealing output: If an external monitor is connected, Ubuntu may default to HDMI. Select the headphones again after plugging or unplugging displays.
• App-level muting: Check the player’s own volume and mute button. Some apps remember a muted state per device.
• Another user session: If someone else is logged in on the same machine, their session can hold the audio device. Log out other sessions for testing.
• Kernel and firmware updates: Run sudo apt update && sudo apt full-upgrade, then reboot. Bluetooth audio bugs are often fixed in kernel or firmware packages.
• Test with a different device: Pair a second Bluetooth speaker or headset. If it also has no sound, the fault is in Ubuntu’s audio stack, not your headphones.
• Check logs: Run journalctl --user -u wireplumber -n 50 after a failed attempt and look for profile or codec errors.

Common Mistakes and Helpful Tips

• Assuming connected means selected: Connection and output selection are two different steps. Always verify the output device by name.
• Staying on the headset profile: After a call ends, switch back to the stereo profile manually if Ubuntu does not do it for you.
• Forgetting the phone: Turn off Bluetooth on your phone during testing to rule out the headphones serving two masters.
• Restarting the whole computer first: Restarting the PipeWire user services is faster and tells you which layer was stuck.
• Testing with silence: Use a continuous sound source and the built-in speaker test, not a short notification beep you might miss.
• Ignoring distance and interference: USB 3 hubs and crowded Wi-Fi can disturb Bluetooth. Test close to the laptop with a clear path.

Conclusion

Bluetooth headphones with no sound in Ubuntu 24.04 are almost always a routing, profile, or stuck-service problem. Select the headphones as the output, use a stereo profile for music, restart PipeWire and WirePlumber if the state looks stuck, and re-pair cleanly if the problem survives. Work through those layers in order and you will find the silent step quickly, without reinstalling Ubuntu or replacing a healthy headset.

Frequently Asked Questions

Why do my headphones work for calls but not for music?

The headset profile is active, which is designed for calls. Switch the device profile to a stereo A2DP option in Sound settings or pavucontrol for music, and expect lower quality whenever the microphone profile is in use.

Why does sound come from the speakers even though headphones are connected?

Ubuntu kept the speakers as the selected output. Open Settings, go to Sound, and choose the headphones in the Output Device list. A service restart or display change can reset this choice.

What is the difference between PipeWire and PulseAudio in Ubuntu 24.04?

PipeWire is the audio system in 24.04, and it provides a PulseAudio-compatible layer so older tools like pavucontrol still work. Restart PipeWire and WirePlumber user services when the audio state gets stuck.

How do I make Ubuntu switch to headphones automatically?

WirePlumber normally remembers your last choice. If switching fails, disconnect other outputs you never use in pavucontrol’s Configuration tab by setting their profile to Off, so the headphones become the clear default.

Why is there sound in one app but not another?

Each app has its own playback route and volume memory. Open pavucontrol while the silent app is playing and check which device its stream is aimed at, then move it to the headphones.