Bluetooth headset connects then immediately disconnects after SteamOS update; BlueZ rejects the headset's re-pair request (fixed by JustWorksRepairing = always)
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 48/100
- Tipo de issue
- Error
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- linux
- Área
- networking, operating-systems
Línea de trabajo
Start by reviewing the attached btmon capture and the report’s reproduction steps, then compare the behavior with JustWorksRepairing = always in /etc/bluetooth/main.conf. Check whether the SteamOS update changed the Bluetooth configuration or bond-repair behavior; the issue is resolved when a previously paired headset connects and stays connected with the default configuration.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Your system information
- SteamOS version: 3.9.5
- Model: Oled 1TB
- Update channel: Stable
- Opted into Steam client beta: No
- Opted into SteamOS beta: No
Describe your issue in as much detail as possible:
After the latest SteamOS update, my Bluetooth earbuds show "connected" and then disconnect immediately, every attempt. It happens in Desktop Mode, and also when switching from Gaming Mode to Desktop Mode. Restarts, removing and re-pairing the device, and clearing Bluetooth configs did not help. The same earbuds work normally on a phone, so the problem is on the Deck.
Running sudo systemctl restart bluetooth fixed it temporarily, but it came back after about a day of use.
What the capture shows (btmon, attached as btmon.txt):
- The headset connects and A2DP/HFP setup completes normally.
- About 0.6 seconds later the headset initiates SSP re-pairing.
- BlueZ immediately sends User Confirmation Request Negative Reply. No prompt is shown to the user, and a pairing agent is registered.
- Simple Pairing Complete / Auth Complete = Authentication Failure (0x05).
- The headset then terminates the link (Remote User Terminated Connection).
The controller (hci0) behaves normally throughout. bluetoothctl output shows the same pattern: the headset connects, endpoints appear, then it disconnects with "Connection terminated by remote user", repeatedly.
Workaround that fixes it:
Setting JustWorksRepairing = always in /etc/bluetooth/main.conf and restarting bluetooth.service. After that the earbuds pair, connect, and stay connected. With the default value (never), BlueZ rejects the re-pair request from a device it already has bonded, and the connection is torn down. A SteamOS update may overwrite main.conf and bring the problem back.
Expected behavior:
Earbuds connect and stay connected without manual configuration changes.
Steps to reproduce:
- Have a Bluetooth headset already paired with the Deck.
- Connect it in Desktop Mode (or switch from Gaming Mode to Desktop Mode with it connected).
- It reports connected, then disconnects right away.
Notes:
I have not isolated a specific trigger such as sleep/wake. This appears to be a bond-handling regression introduced with the latest SteamOS update.
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 2.7k
- Forks
- 89
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de ValveSoftware/SteamOS
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
ValveSoftware/SteamOS#3037 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
ValveSoftware/SteamOS#2983 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
ValveSoftware/SteamOS#2927 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
ValveSoftware/SteamOS#2875 · 1 comentario ·
-
steam-short-session-tracker: incorrect registry backup path resets settings during automatic repairAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
ValveSoftware/SteamOS#2829 ·
Todos los issues de ValveSoftware/SteamOS
Issues similares
-
complexity: easy good first issue impact: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
ueberdosis/hocuspocus#1211 ·
Los mantenedores suelen responder en 1 día
-
kind/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
krahabb/meross_lan#740 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Los mantenedores suelen responder en 4 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
FujiNetWIFI/fujinet-firmware#2341 ·
Los mantenedores suelen responder en 1 día