debcrafters-packages team mailing list archive

[Ural Tunaboyu <2113469@xxxxxxxxxxxxxxxxxx>]

Hello and thanks for the bug report.

Can you provide more information using `apport-collect 2113469`?
Additionally you can provide further logs by running `dmesg >
dmesg_xxx.log` and attach the file here.

** Also affects: linux (Ubuntu)
   Importance: Undecided
       Status: New

** Tags added: dcr-freezer

-- 
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/2113469

Title:
  Logitech MX Anywhere and MX Keys need to re-pair after suspend after
  upgrading to 25.04

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  After upgrading from Ubuntu 24.10 to 25.04 my Logitech MX Keys
  keyboard and MX Anywhere mouse need to be re-paired after the laptop
  is suspended. My headphones and phone do not. I am using the built-in
  Bluetooth interface of a Dell Latitude 7280.

  The Logitech devices seem to increment their MAC addresses whenever
  they reconnect as a privacy feature. This did not cause a problem with
  previous Ubuntu releases. They get "(random)" appended in the results
  of a bluetoothctl info.

  I'm running bluez 5.79-2ubuntu1 and kernel 6.14.0-15-generic with
  default Bluetooth settings.

  Device [omitted]:D3 (random)
  	Name: MX Anywhere 3
  	Alias: MX Anywhere 3
  	Appearance: 0x03c2 (962)
  	Icon: input-mouse
  	Paired: yes
  	Bonded: yes
  	Trusted: yes
  	Blocked: no
  	Connected: yes
  	WakeAllowed: yes
  	LegacyPairing: no
  	UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
  	UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
  	UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
  	UUID: Battery Service           (0000180f-0000-1000-8000-00805f9b34fb)
  	UUID: Human Interface Device    (00001812-0000-1000-8000-00805f9b34fb)
  	UUID: Vendor specific           (00010000-0000-1000-8000-011f2000046d)
  	Modalias: usb:v046DpB025d0014
  	AdvertisingFlags:
    05                                               .               
  	Battery Percentage: 0x3c (60)

  After a suspend/resume, this device is now [omitted]:D4, then
  [omitted]:D5 etc.

  I have checked that Experimental and KernelExperimental are false in
  /etc/bluetooth/main.conf (and tried setting them to true - no
  difference).

  These devices have worked fine for the last 4 years on all previous
  releases since 20.10.

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