debcrafters-packages team mailing list archive

[pepelota <2111763@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Kubuntu Version: 24.04 LTS
Hardware: MacBook Pro Late 2015
Bluetooth Controller: Broadcom (integrated, Apple, Inc.)
Affected Device: Nothing Ear 2024 headset (MAC: 2C:BE:EB:76:66:F1)

Summary
The "Nothing Ear 2024" Bluetooth headset randomly disconnects during use. After disconnection, it is impossible to re-establish a connection. Attempting to reconnect often results in an "Already Paired (0x13)" error, and the bluetoothd service cannot be stopped or killed without immediately restarting. The only way to restore Bluetooth functionality and re-connect the headset is to perform a full system reboot.

Description
On Kubuntu 24.04 running on a MacBook Pro Late 2015, my "Nothing Ear 2024" headset randomly disconnects during normal use. The disconnection occurs without a clear pattern or specific trigger (e.g., leaving range, specific audio events).

Once disconnected, the headset cannot be reconnected. Attempting to
reconnect via Kubuntu's Bluetooth settings or bluetoothctl fails. During
these failed reconnection attempts, btmon often reports an "Already
Paired (0x13)" status, suggesting a corrupted or stuck internal state.

Crucially, after a disconnection, the bluetoothd service behaves
erratically: commands like sudo systemctl stop bluetooth and sudo
systemctl kill bluetooth are ineffective, as systemd immediately
restarts the daemon with a new Process ID (PID). This prevents any
attempt to reset the Bluetooth stack from the user-space level.

The problem persists even after trying to remove the device via
bluetoothctl remove 2C:BE:EB:76:66:F1 or by manually deleting the entire
/var/lib/bluetooth/ directory.

The only action that consistently resolves the issue and allows the
headset to be reconnected is a full system reboot. This indicates that
the problematic state resides deeper than the user-space bluetoothd
daemon's configuration, likely within the kernel's Bluetooth stack or
the hardware's transient memory, which only a complete system re-
initialization can clear. No modifications or resets were performed on
the "Nothing Ear 2024" headset itself.

Steps to Reproduce
Connect and use the "Nothing Ear 2024" headset normally.

Wait for the headset to randomly disconnect (this can happen at any time
during use).

Attempt to reconnect the headset via Kubuntu's Bluetooth settings or
bluetoothctl.

Observe the connection failure, often accompanied by an "Already Paired
(0x13)" status in btmon.

Attempt to stop the bluetoothd service using sudo systemctl stop
bluetooth.

Verify its status with systemctl status bluetooth and observe that it
immediately restarts.

Attempt to remove the device using bluetoothctl remove 2C:BE:EB:76:66:F1
and/or manually delete the entire /var/lib/bluetooth/ folder (or its
contents).

Restart the bluetoothd service (or attempt re-pairing without a full
reboot).

Observe that the "Already Paired (0x13)" error persists and reconnection
fails.

Perform a full system reboot.

After reboot, the headset can usually be connected successfully.

Expected Outcome
The "Nothing Ear 2024" headset should maintain a stable connection during use. If a disconnection occurs, it should be possible to reconnect it without requiring a full system reboot. The bluetoothd service should stop when commanded.

Actual Outcome
The headset randomly disconnects. After disconnection, reconnection fails, often showing "Already Paired (0x13)". The bluetoothd service cannot be stopped. Only a full system reboot restores connectivity.

Relevant Information

Kernel Version: Linux MacJuan 6.8.0-60-generic #63-Ubuntu SMP
PREEMPT_DYNAMIC Tue Apr 15 19:04:15 UTC 2025 x86_64 x86_64 x86_64
GNU/Linux

** Affects: bluez (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2111763

Title:
  Random Bluetooth Headset Disconnection; Reconnection Fails Until Full
  System Reboot

Status in bluez package in Ubuntu:
  New

Bug description:
  Kubuntu Version: 24.04 LTS
  Hardware: MacBook Pro Late 2015
  Bluetooth Controller: Broadcom (integrated, Apple, Inc.)
  Affected Device: Nothing Ear 2024 headset (MAC: 2C:BE:EB:76:66:F1)

  Summary
  The "Nothing Ear 2024" Bluetooth headset randomly disconnects during use. After disconnection, it is impossible to re-establish a connection. Attempting to reconnect often results in an "Already Paired (0x13)" error, and the bluetoothd service cannot be stopped or killed without immediately restarting. The only way to restore Bluetooth functionality and re-connect the headset is to perform a full system reboot.

  Description
  On Kubuntu 24.04 running on a MacBook Pro Late 2015, my "Nothing Ear 2024" headset randomly disconnects during normal use. The disconnection occurs without a clear pattern or specific trigger (e.g., leaving range, specific audio events).

  Once disconnected, the headset cannot be reconnected. Attempting to
  reconnect via Kubuntu's Bluetooth settings or bluetoothctl fails.
  During these failed reconnection attempts, btmon often reports an
  "Already Paired (0x13)" status, suggesting a corrupted or stuck
  internal state.

  Crucially, after a disconnection, the bluetoothd service behaves
  erratically: commands like sudo systemctl stop bluetooth and sudo
  systemctl kill bluetooth are ineffective, as systemd immediately
  restarts the daemon with a new Process ID (PID). This prevents any
  attempt to reset the Bluetooth stack from the user-space level.

  The problem persists even after trying to remove the device via
  bluetoothctl remove 2C:BE:EB:76:66:F1 or by manually deleting the
  entire /var/lib/bluetooth/ directory.

  The only action that consistently resolves the issue and allows the
  headset to be reconnected is a full system reboot. This indicates that
  the problematic state resides deeper than the user-space bluetoothd
  daemon's configuration, likely within the kernel's Bluetooth stack or
  the hardware's transient memory, which only a complete system re-
  initialization can clear. No modifications or resets were performed on
  the "Nothing Ear 2024" headset itself.

  Steps to Reproduce
  Connect and use the "Nothing Ear 2024" headset normally.

  Wait for the headset to randomly disconnect (this can happen at any
  time during use).

  Attempt to reconnect the headset via Kubuntu's Bluetooth settings or
  bluetoothctl.

  Observe the connection failure, often accompanied by an "Already
  Paired (0x13)" status in btmon.

  Attempt to stop the bluetoothd service using sudo systemctl stop
  bluetooth.

  Verify its status with systemctl status bluetooth and observe that it
  immediately restarts.

  Attempt to remove the device using bluetoothctl remove
  2C:BE:EB:76:66:F1 and/or manually delete the entire
  /var/lib/bluetooth/ folder (or its contents).

  Restart the bluetoothd service (or attempt re-pairing without a full
  reboot).

  Observe that the "Already Paired (0x13)" error persists and
  reconnection fails.

  Perform a full system reboot.

  After reboot, the headset can usually be connected successfully.

  Expected Outcome
  The "Nothing Ear 2024" headset should maintain a stable connection during use. If a disconnection occurs, it should be possible to reconnect it without requiring a full system reboot. The bluetoothd service should stop when commanded.

  Actual Outcome
  The headset randomly disconnects. After disconnection, reconnection fails, often showing "Already Paired (0x13)". The bluetoothd service cannot be stopped. Only a full system reboot restores connectivity.

  Relevant Information

  Kernel Version: Linux MacJuan 6.8.0-60-generic #63-Ubuntu SMP
  PREEMPT_DYNAMIC Tue Apr 15 19:04:15 UTC 2025 x86_64 x86_64 x86_64
  GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2111763/+subscriptions