Package: bluez Version: 5.62-2 Followup-For: Bug #995399 Dear Maintainer,
yesterday I switch to win10 (dual boot) and bluetooth works so isn't a hardware problem (good new!). Back to Debian I done new tests. Again the bluetoothd is up when I move the mouse and goes down if not, but I've noticed a new line in system.log Dec 29 10:36:43 G5045 bluetoothd[1386]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down after that the bluetooth is definitely disable! Thanks -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (903, 'unstable'), (500, 'testing'), (400, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:it Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages bluez depends on: ii dbus 1.12.20-3 ii init-system-helpers 1.61 ii kmod 29-1 ii libasound2 1.2.5.1-1 ii libc6 2.33-1 ii libdbus-1-3 1.12.20-3 ii libdw1 0.186-1 ii libglib2.0-0 2.70.2-1 ii libreadline8 8.1-2 ii libudev1 249.7-1 ii lsb-base 11.1.0 ii udev 249.7-1 bluez recommends no packages. Versions of packages bluez suggests: pn pulseaudio-module-bluetooth <none> -- Configuration Files: /etc/bluetooth/main.conf changed: [General] ControllerMode = dual [BR] [LE] EnableAdvMonInterleaveScan=0 [GATT] [AVDTP] [Policy] AutoEnable=true [AdvMon] /etc/default/bluetooth changed: BLUETOOTH_ENABLED=1 HID2HCI_ENABLED=1 HID2HCI_UNDO=1 -- no debconf information
