Pi400 Bluetooth device not being recognised, Bluetooth manager and Bluetooth adaptors commands show no screen output and appear inoperative

[Tony Molloy]

Trying to use a Bluetooth mouse with Pi400 running latest Mate 20.10 desktop,to save using a USB port. The mouse does not get recognised, double clicking either Bluetooth Adaptors or Bluetooth Manager has no effect. Full update run this morning.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: bluetooth 5.55-0ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-1006.9-raspi 5.8.14
Uname: Linux 5.8.0-1006-raspi aarch64
ApportVersion: 2.20.11-0ubuntu50
Architecture: arm64
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Fri Nov 6 10:31:06 2020
ImageMediaBuild: 20201028
InterestingModules: bnep bluetooth
Lspci-vt: -[0000:00]---00.0-[01]----00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no username)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1920x1080M@60 video=HDMI-A-2:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:E0:8E:57 vc_mem.mem_base=0x3eb00000 vc_mem.mem_size=0x3ff00000 net.ifnames=0 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:

hciconfig:

rfkill:
 0: phy0: Wireless LAN
  Soft blocked: yes
  Hard blocked: no

[Henry Sprog (henry-sprog)]

I can confirm all of the above. Also looking at the Pi OS the in which the bluetooth works it lists BCM2711-rpi-400.dts. Also unblocking the soft block has no effect.

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1903048, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.