Bluetooth headset connects then immediately disconnects after SteamOS update; BlueZ rejects the headset's re-pair request (fixed by JustWorksRepairing = always)

オープン
  • 何か問題がありますか？
#3,038 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
48/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
linux
領域
networking, operating-systems

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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):

  1. The headset connects and A2DP/HFP setup completes normally.
  2. About 0.6 seconds later the headset initiates SSP re-pairing.
  3. BlueZ immediately sends User Confirmation Request Negative Reply. No prompt is shown to the user, and a pairing agent is registered.
  4. Simple Pairing Complete / Auth Complete = Authentication Failure (0x05).
  5. 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:

  1. Have a Bluetooth headset already paired with the Deck.
  2. Connect it in Desktop Mode (or switch from Gaming Mode to Desktop Mode with it connected).
  3. 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.

btmon.txt

主要言語
言語のデータがありません
スター
2.7k
フォーク
89
30日以内にマージされた PR はありません

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

ValveSoftware/SteamOS のほかの issue

ValveSoftware/SteamOS の issue をすべて見る

似ている issue

Networking の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。