问题[bluetooth](ubuntu)

内核版本： *6.11.0-21-generic*

sudo dmesg | grep -i bluetooth | tail -n 30

[    3.686609] usb 3-3: Product: Bluetooth Radio
[    5.272165] Bluetooth: Core ver 2.22
[    5.272217] NET: Registered PF_BLUETOOTH protocol family
[    5.272220] Bluetooth: HCI device and connection manager initialized
[    5.272227] Bluetooth: HCI socket layer initialized
[    5.272231] Bluetooth: L2CAP socket layer initialized
[    5.272239] Bluetooth: SCO socket layer initialized
[    5.399632] Bluetooth: hci0: urb 000000006b6bc71e failed to resubmit (2)
[    7.443428] Bluetooth: hci0: Opcode 0x0c03 failed: -110
[    8.555200] Bluetooth: hci0: unexpected event for opcode 0x0c03
[    8.556660] Bluetooth: hci0: unexpected event for opcode 0x0000
[    8.765298] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    8.765307] Bluetooth: BNEP filters: protocol multicast
[    8.765315] Bluetooth: BNEP socket layer initialized
[    8.768694] Bluetooth: MGMT ver 1.23
[   17.810960] Bluetooth: RFCOMM TTY layer initialized
[   17.810981] Bluetooth: RFCOMM socket layer initialized
[   17.810995] Bluetooth: RFCOMM ver 1.11

LSUSB

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 13d3:3601 IMC Networks Bluetooth Radio
Bus 003 Device 003: ID 04f2:b729 Chicony Electronics Co., Ltd Chicony USB2.0 Camera
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

usb-devices | grep -A 20 -i bluetooth

    S:  Product=Bluetooth Radio
    S:  SerialNumber=00e04c000001
    C:  #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=500mA
    I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
    E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
    E:  Ad=81(I) Atr=03(Int.) MxPS=  16 Ivl=1ms
    E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
    I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
    E:  Ad=03(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms
    E:  Ad=83(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms
    
    T:  Bus=03 Lev=01 Prnt=02 Port=03 Cnt=01 Dev#=  3 Spd=480  MxCh= 0
    D:  Ver= 2.01 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs=  1
    P:  Vendor=04f2 ProdID=b729 Rev=27.39
    S:  Manufacturer=CHICONY
    S:  Product=Chicony USB2.0 Camera
    S:  SerialNumber=200901010001
    C:  #Ifs= 3 Cfg#= 1 Atr=80 MxPwr=500mA
    I:  If#= 0 Alt= 0 #EPs= 1 Cls=0e(video) Sub=01 Prot=00 Driver=uvcvideo
    E:  Ad=83(I) Atr=03(Int.) MxPS=  32 Ivl=4ms
    I:  If#= 1 Alt= 0 #EPs= 0 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo

lsmod | grep -i bluetooth

    bluetooth            1028096  44 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm

这是 8BitDo SN30 pro+ 控制器。它通过 USB 蓝牙适配器连接。它以前工作得很好。但在最近的升级之后的某个时候，整个行为都变差了。它以前在连接时会振动 - 现在再也不会了。它可以在连接后立即随机断开连接。不知何故，通过重新启动和重新配对，我最近确实让它在 Steam 游戏中工作了几次。但这太痛苦了。

blueman-applet我看到它在和 中已配对、信任并连接bluetoothctl info。但 Steam 检测不到它：Steam > 设置 > 控制器显示“未检测到控制器”。

而且我没有在 下看到任何与控制器相关的内容/dev。即根据Arch Gamepad wiki，它应该在 下显示为/dev/input/jsX和/dev/input/by-id/。在我的情况下，没有jsX设备，/dev/input/只包含eventX和mice。mouse0我在下面看到的/dev/input/by-id/只有我的键盘和鼠标。 下还有更多内容/dev/input/by-path/：

$ ls /dev/input/by-path/ -l
total 0
lrwxrwxrwx 1 root root 9 Feb  8 03:31 pci-0000:09:00.4-usb-0:2:1.1-event-mouse -> ../event3
lrwxrwxrwx 1 root root 9 Feb  8 03:31 pci-0000:09:00.4-usb-0:2:1.1-mouse -> ../mouse0
lrwxrwxrwx 1 root root 9 Feb  8 03:31 pci-0000:09:00.4-usbv2-0:2:1.1-event-mouse -> ../event3
lrwxrwxrwx 1 root root 9 Feb  8 03:31 pci-0000:09:00.4-usbv2-0:2:1.1-mouse -> ../mouse0
lrwxrwxrwx 1 root root 9 Feb  8 03:31 platform-eeepc-wmi-event -> ../event4
lrwxrwxrwx 1 root root 9 Feb  8 03:31 platform-i8042-serio-0-event-kbd -> ../event2

我认为i8042是键盘驱动程序。我不确定是什么platform-eeepc-wmi-event。

所以，我猜测，蓝牙连接了设备，但控制器无法被识别。

当我journalctl -f通过蓝牙连接时，我得到了这个：

dunst[10327]: CRITICAL: Source ID 73 was not found when attempting to remove it
kernel: nintendo 0005:057E:2009.0008: unknown main item tag 0x0
kernel: nintendo 0005:057E:2009.0008: hidraw3: BLUETOOTH HID v80.01 Gamepad [Pro Controller] on 44:01:bb:ad:a0:55
kernel: nintendo 0005:057E:2009.0008: Failed to get joycon info; ret=-110
kernel: nintendo 0005:057E:2009.0008: Failed to retrieve controller info; ret=-110
kernel: nintendo 0005:057E:2009.0008: Failed to initialize controller; ret=-110
kernel: nintendo 0005:057E:2009.0008: probe - fail = -110
kernel: nintendo: probe of 0005:057E:2009.0008 failed with error -110

那么，它被识别为任天堂控制器但无法初始化？我该如何解决这个问题？我应该为控制器安装一些驱动程序吗？

更新：我还将控制器上的 FW 更新为最新支持的版本 v6.01。但仍然nintendo ... failed to initialize the controller出现相同的错误journalctl -f。

我的新ABS 桌面上安装了 Ubuntu 24.04 ，尽管 hciconfig、bluetoothctl 没有显示任何错误，但在扫描期间我却看不到任何设备。

$ hciconfig
hci0:   Type: Primary  Bus: USB
        BD Address: FC:B0:DE:38:30:96  ACL MTU: 1021:8  SCO MTU: 255:12
        UP RUNNING PSCAN ISCAN
        RX bytes:5389 acl:0 sco:0 events:539 errors:0
        TX bytes:19604 acl:0 sco:0 commands:519 errors:0

手动使用 bluetoothctl 执行以下操作：

$ bluetoothctl
Waiting to connect to bluetoothd...[bluetooth]# Agent registered
[bluetooth]# agent on
Agent is already registered
[bluetooth]# default-agent
[bluetooth]# Default agent request successful
[bluetooth]# scan on
[bluetooth]# SetDiscoveryFilter success
[bluetooth]# Discovery started
[bluetooth]# [CHG] Controller FC:B0:DE:38:30:96 Discovering: yes
[bluetooth]#

据我所知， lsmod 没有显示任何有趣的东西：

$ lsmod | grep btusb
btusb                  77824  0
btrtl                  32768  1 btusb
btintel                57344  1 btusb
btbcm                  24576  1 btusb
btmtk                  12288  1 btusb
bluetooth            1028096  46 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm

~ ⌚ 13:34:42
$ lsmod | grep bluetooth
bluetooth            1028096  46 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm
ecdh_generic           16384  2 bluetooth

以下是 的输出lsusb; sudo dmesg | egrep -i 'blue|firm'：

$ lsusb; sudo dmesg | egrep -i 'blue|firm'
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 0489:e112 Foxconn / Hon Hai Bluetooth Radio
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
[    1.157720] usb 3-1: Product: Bluetooth Radio
[    4.892212] systemd[1]: Mounting snap-firmware\x2dupdater-127.mount - Mount unit for firmware-updater, revision 127...
[    4.893131] systemd[1]: Mounting snap-firmware\x2dupdater-147.mount - Mount unit for firmware-updater, revision 147...
[    5.078863] Bluetooth: Core ver 2.22
[    5.103287] NET: Registered PF_BLUETOOTH protocol family
[    5.103290] Bluetooth: HCI device and connection manager initialized
[    5.103294] Bluetooth: HCI socket layer initialized
[    5.103296] Bluetooth: L2CAP socket layer initialized
[    5.103303] Bluetooth: SCO socket layer initialized
[    5.319068] rtw89_8851be 0000:08:00.0: loaded firmware rtw89/rtw8851b_fw.bin
[    5.319858] rtw89_8851be 0000:08:00.0: Firmware version 0.29.41.3 (65cefb31), cmd version 0, type 5
[    5.319861] rtw89_8851be 0000:08:00.0: Firmware version 0.29.41.3 (65cefb31), cmd version 0, type 3
[    6.292072] [drm] Loading DMUB firmware via PSP: version=0x05000F00
[    6.292458] [drm] Found VCN firmware Version ENC: 1.30 DEC: 3 VEP: 0 Revision: 4
[    6.292464] amdgpu 0000:0b:00.0: amdgpu: Will use PSP to load VCN firmware
[    7.299392] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    7.299396] Bluetooth: BNEP filters: protocol multicast
[    7.299401] Bluetooth: BNEP socket layer initialized
[    7.300285] Bluetooth: MGMT ver 1.22
[    9.138499] Bluetooth: RFCOMM TTY layer initialized
[    9.138505] Bluetooth: RFCOMM socket layer initialized
[    9.138508] Bluetooth: RFCOMM ver 1.11
[ 7300.714099] audit: type=1400 audit(1738440042.768:183): apparmor="DENIED" operation="open" class="file" profile="snap.firmware-updater.firmware-notifier" name="/proc/sys/vm/max_map_count" pid=28130 comm="firmware-notifi" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[18100.787075] audit: type=1400 audit(1738450842.532:184): apparmor="DENIED" operation="open" class="file" profile="snap.firmware-updater.firmware-notifier" name="/proc/sys/vm/max_map_count" pid=74038 comm="firmware-notifi" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

此时我已经没有主意了，非常感谢任何帮助。为了“好玩”，这是我尝试使用 chat-gpt 进行的调试会话

我使用的是 Acer Nitro V ANV15，它使用联发科蓝牙 MT7921 来实现 WiFi 和蓝牙。我的系统是 Ubuntu 24.04.01 LTS，内核是 6.8.0-51-generic。

我尝试重新启动并检查蓝牙的状态，它确实显示服务正在运行。但是，尝试通过 GNOME 设置打开蓝牙时，切换按钮无法工作。使用带有 bluetoothctl 的终端也显示没有默认控制器。

奇怪的是，WiFi 部分仍然正常工作。我甚至尝试将其关闭，以防它干扰蓝牙，但没有成功。为了确保万无一失，我还运行了 sudo apt update and upgrade。

此外，我使用 Windows 进行双启动，蓝牙在该操作系统上正常工作。在双启动安装过程中，WiFi 开箱即用（运行 sudo apt update and upgrade 一次后）。

鉴于我看过关于 ~5.0 Linux 内核的此问题的报告，这似乎不是一个老问题。这个新版本有修复吗？

编辑：Jeremy31 询问的附加信息：

lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 0408:403a Quanta Computer, Inc. ACER HD User Facing
Bus 003 Device 003: ID 13d3:3606 IMC Networks Wireless_Device
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

sudo dmesg | egrep -i 'blue|firm'
[    0.149202] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    2.048553] Bluetooth: Core ver 2.22
[    2.048577] NET: Registered PF_BLUETOOTH protocol family
[    2.048578] Bluetooth: HCI device and connection manager initialized
[    2.048582] Bluetooth: HCI socket layer initialized
[    2.048584] Bluetooth: L2CAP socket layer initialized
[    2.048588] Bluetooth: SCO socket layer initialized
[    2.371476] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/adlp_dmc.bin (v2.20)
[    2.384614] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.20.0
[    2.384620] i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
[    2.743129] mt7921e 0000:3e:00.0: WM Firmware Version: ____010000, Build Time: 20240219111038
[    3.103798] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    3.103803] Bluetooth: BNEP filters: protocol multicast
[    3.103807] Bluetooth: BNEP socket layer initialized
[    3.774665] sof-audio-pci-intel-tgl 0000:00:1f.3: Firmware paths/files for ipc type 0:
[    3.774670] sof-audio-pci-intel-tgl 0000:00:1f.3:  Firmware file:     intel/sof/sof-rpl.ri
[    3.775861] sof-audio-pci-intel-tgl 0000:00:1f.3: Firmware info: version 2:2:0-57864
[    3.775866] sof-audio-pci-intel-tgl 0000:00:1f.3: Firmware: ABI 3:22:1 Kernel ABI 3:23:0
[    3.864754] sof-audio-pci-intel-tgl 0000:00:1f.3: Firmware info: version 2:2:0-57864
[    3.864759] sof-audio-pci-intel-tgl 0000:00:1f.3: Firmware: ABI 3:22:1 Kernel ABI 3:23:0
[    4.450398] Bluetooth: hci0: Opcode 0x0c03 failed: -110
[ 1380.079922] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.20.0
[ 1380.079926] i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
[ 1380.940420] audit: type=1400 audit(1736591719.235:249): apparmor="DENIED" operation="open" class="file" profile="snap.firmware-updater.firmware-notifier" name="/proc/sys/vm/max_map_count" pid=16622 comm="firmware-notifi" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[ 5091.766316] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.20.0
[ 5091.766330] i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
[ 5121.929122] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.20.0
[ 5121.929127] i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
[ 5123.394812] audit: type=1400 audit(1736612644.852:267): apparmor="DENIED" operation="open" class="file" profile="snap.firmware-updater.firmware-notifier" name="/proc/sys/vm/max_map_count" pid=42330 comm="firmware-notifi" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

No message appears for dkms status after installing it

在使用 UE MEGABOOM 时遇到问题后，我尝试取消配对并重新配对。但是，配对不断失败 - 我尝试过重新启动，以及使用 Blueman 和 进行配对bluetoothctl。

我收到的只是一条消息，告诉妈妈配对失败。bluetoothctl给了我：

Failed to pair: org.bluez.Error.AuthenticationFailed

怎么回事？

我的耳机已在 ubuntu (24.04.1 LTS) 上与蓝牙配对，但当我单击“连接”时，操作失败。每次我想要连接时，我都必须断开耳机（从配对设备列表中）并再次修复。如何解决这个问题？

我的新蓝牙耳机（HONOR CHOICE 开放式耳塞）出了点问题。我可以将它们与我的 Ubuntu 24.10 PC（一台带有蓝牙适配器的台式电脑）配对，配对后它们工作正常，直到我重新启动电脑（或重新启动服务bluetooth），这时它就无法连接了。我之前的蓝牙耳机没有出现这种情况，在 Ubuntu 上运行良好。

重启后，我连接耳机的唯一方法是经过另一个配对过程：经过一些调整（关闭耳机或适配器并反复尝试连接）后，Ubuntu 要求我确认一个 6 位数的代码，单击“确认”后，耳机即可再次工作。（顺便说一句，6 位数的代码本身很奇怪：以前的耳机不需要代码，而且耳机无论如何都无法显示代码，所以我实际上并没有将该代码与任何东西进行比较。）

完成此过程后，LinkKeyin/var/lib/bluetooth/XX:XX:XX:XX:XX:XX/XX:XX:XX:XX:XX:XX/info会发生变化；此外，我安装的蓝牙管理器程序（blueman包）在标有“蓝牙配对请求”的通知中显示相同的代码。这让我有理由确信这实际上是另一次配对。

此问题特定于 Ubuntu：在同一台计算机上安装 Windows 11 时不会发生此问题，重启后重新连接没有任何问题。（请注意，这不是在双启动的情况下必须在两个不同的操作系统之间同步蓝牙密钥的问题：在这里我将耳机与 Ubuntu 配对，然后再次重新启动到 Ubuntu，根本不触及 Windows。我只提到 Windows 以将问题缩小到 Ubuntu，而不是耳机或 PC 硬件。）

如果我尝试通过命令行连接耳机，它会产生以下错误消息（我删除了设备的地址）：

$ bluetoothctl connect XX:XX:XX:XX:XX:XX
Attempting to connect to XX:XX:XX:XX:XX:XX
[CHG] Device XX:XX:XX:XX:XX:XX Connected: yes
Failed to connect: org.bluez.Error.Failed br-connection-unknown

我该如何修复此问题？

编辑：我发现了这个btmon工具，它似乎可以转储计算机与其交互的设备之间交换的蓝牙消息的完整痕迹。

在失败的连接尝试的跟踪中，我发现了以下交换：

> HCI Event: Link Key Request (0x17) plen 6                                                                                                                                                                          #55 [hci0] 13.039915
        Address: XX:XX:XX:XX:XX:XX (Tiinlab Corporation)
< HCI Command: Link Key Request Negative Reply (0x01|0x000c) plen 6                                                                                                                                                  #56 [hci0] 13.039939
        Address: XX:XX:XX:XX:XX:XX (Tiinlab Corporation)

以下是成功连接尝试的跟踪的相应部分（配对之后和重启之前）：

> HCI Event: Link Key Request (0x17) plen 6                                                                                                                                  #34 [hci0] 13.524821
        Address: XX:XX:XX:XX:XX:XX (Tiinlab Corporation)
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22                                                                                                                  #35 [hci0] 13.524834
        Address: XX:XX:XX:XX:XX:XX (Tiinlab Corporation)
        Link key[16]: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

看来，Ubuntu 在服务bluetooth重启后不记得它有一个该设备的链接密钥。

和许多用户一样，我也遇到了蓝牙问题。我使用的Linux 6.8.0-45-generic on x86_64 #45-Ubuntu 24.04.1 LTS是刚刚安装的。
当我继续Settings -> Bluetooth并单击启用开关时，它会立即自行禁用。

我的笔记本电脑刚刚购买，您可以在此处查看完整规格

我尝试遵循

• 我无法在 Ubuntu 22.04 LTS 中打开蓝牙
• https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592

没有人能解决问题。
我无法从笔记本电脑中取出电池，因此我尝试了在 BIOS 上禁用/启用的技巧，但没有帮助。

报告的主要错误信息是：

• 蓝牙：hci0：操作码 0x0c03 失败：-110

sudo dmesg | grep -i blue
[    2.511496] Bluetooth: Core ver 2.22
[    2.511532] NET: Registered PF_BLUETOOTH protocol family
[    2.511535] Bluetooth: HCI device and connection manager initialized
[    2.511548] Bluetooth: HCI socket layer initialized
[    2.511553] Bluetooth: L2CAP socket layer initialized
[    2.511561] Bluetooth: SCO socket layer initialized
[    4.437283] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    4.437291] Bluetooth: BNEP filters: protocol multicast
[    4.437307] Bluetooth: BNEP socket layer initialized
[    4.675379] Bluetooth: hci0: Opcode 0x0c03 failed: -110

但与许多其他报告错误的人不同的是，当我检查bluetooth.service的状态时，它显示active：

sudo systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
     Active: active (running) since Tue 2024-09-17 13:17:46 BST; 21min ago
       Docs: man:bluetoothd(8)
   Main PID: 949 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 37564)
     Memory: 2.8M (peak: 3.1M)
        CPU: 51ms
     CGroup: /system.slice/bluetooth.service
             └─949 /usr/libexec/bluetooth/bluetoothd

Sep 17 13:17:46 matrix bluetoothd[949]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
Sep 17 13:17:46 matrix bluetoothd[949]: src/plugin.c:plugin_init() System does not support micp plugin
Sep 17 13:17:46 matrix bluetoothd[949]: src/plugin.c:plugin_init() System does not support vcp plugin
Sep 17 13:17:46 matrix bluetoothd[949]: src/plugin.c:plugin_init() System does not support mcp plugin
Sep 17 13:17:46 matrix bluetoothd[949]: src/plugin.c:plugin_init() System does not support bass plugin
Sep 17 13:17:46 matrix bluetoothd[949]: src/plugin.c:plugin_init() System does not support bap plugin
Sep 17 13:17:46 matrix bluetoothd[949]: Bluetooth management interface 1.22 initialized
Sep 17 13:17:46 matrix systemd[1]: Starting bluetooth.service - Bluetooth service...
Sep 17 13:17:46 matrix (uetoothd)[949]: bluetooth.service: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (>
Sep 17 13:17:46 matrix systemd[1]: Started bluetooth.service - Bluetooth service.

有人能给我一些建议吗？我可以尝试/检查什么？

lsusb已编辑：根据要求 添加输出。

$ lsusb; sudo dmesg| grep -i firm
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 003: ID 13d3:3585 IMC Networks Wireless_Device
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 05e3:0620 Genesys Logic, Inc. GL3523 Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 2b7e:c858 Kingcome FHD WebCam
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

它是一个内置蓝牙，而不是 USB 蓝牙...但是为了防止我遗漏某些东西，我还是添加了它。

我意识到尽管我使用的是蓝牙鼠标，但 Ubuntu 上的蓝牙连接已关闭。几天来，指针一直无法平稳移动，所以我正在寻找可能的原因。我认为鼠标通过其 USB 适配器进行蓝牙通信，但我想知道我是否也应该在 Ubuntu 上启用蓝牙连接。但是打开它并没有帮助解决问题。

在尝试使用 Kubuntu 和 NobaraOS进行双启动时，我调整了主 Kubuntu 分区的大小以获得更多空间，并删除了其他分区，因为无法使其工作。问题就是从那时开始的。当我在重置或睡眠 PC 后登录时，wifi 不会自动连接，最糟糕的是，键盘不工作。如果我忘记了设备并重新配对，我只能连接到它。但这样就不起作用了。如果我断开连接并在重新配对后再次连接，它只会在我输入某些内容时连接，但它不起作用。 sudo btom输出：

Bluetooth monitor ver 5.72
btmon[144343]: = Note: Linux version 6.8.0-41-generic (x86_64)                                        0.863664
btmon[144343]: = Note: Bluetooth subsystem version 2.22                                               0.863666
= New Index: C8:CB:9E:45:0D:70 (Primary,USB,hci0)                                              [hci0] 0.863667
= Open Index: C8:CB:9E:45:0D:70                                                                [hci0] 0.863667
= Index Info: C8:CB:9E:45:0D:70 (Intel Corp.)                                                  [hci0] 0.863668
bluetoothd[1329]: @ MGMT Open: bluetoothd (privileged) version 1.22                          {0x0001} 0.863668
> HCI Event: LE Meta Event (0x3e) plen 44                                                   #1 [hci0] 2.910177
      LE Extended Advertising Report (0x0d)
        Num reports: 1
        Entry 0
          Event type: 0x0013
            Props: 0x0013
              Connectable
              Scannable
              Use legacy advertising PDUs
            Data status: Complete
          Legacy PDU Type: ADV_IND (0x0013)
          Address type: Random (0x01)
          Address: DB:EB:F8:89:54:5D (Static)
          Primary PHY: LE 1M
          Secondary PHY: No packets
          SID: no ADI field (0xff)
          TX power: 127 dBm
          RSSI: -53 dBm (0xcb)
          Periodic advertising interval: 0.00 msec (0x0000)
          Direct address type: Public (0x00)
          Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
          Data length: 0x12
        03 19 c1 03 02 01 06 03 03 12 18 06 ff 06 00 03  ................
        00 80                                            ..              
        Appearance: Keyboard (0x03c1)
        Flags: 0x06
          LE General Discoverable Mode
          BR/EDR Not Supported
        16-bit Service UUIDs (complete): 1 entry
          Human Interface Device (0x1812)
        Company: Microsoft (6)
          Data: 030080
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6                             #2 [hci0] 2.910299
        Extended scan: Disabled (0x00)
        Filter duplicates: Disabled (0x00)
        Duration: 0 msec (0x0000)
        Period: 0.00 sec (0x0000)
> HCI Event: Command Complete (0x0e) plen 4                                                 #3 [hci0] 2.912156
      LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
        Status: Success (0x00)
< HCI Command: LE Extended Create Connection (0x08|0x0043) plen 26                          #4 [hci0] 2.912270
        Filter policy: Accept list is not used (0x00)
        Own address type: Public (0x00)
        Peer address type: Random (0x01)
        Peer address: DB:EB:F8:89:54:5D (Static)
        Initiating PHYs: 0x01
        Entry 0: LE 1M
          Scan interval: 60.000 msec (0x0060)
          Scan window: 60.000 msec (0x0060)
          Min connection interval: 30.00 msec (0x0018)
          Max connection interval: 50.00 msec (0x0028)
          Connection latency: 0 (0x0000)
          Supervision timeout: 420 msec (0x002a)
          Min connection length: 0.000 msec (0x0000)
          Max connection length: 0.000 msec (0x0000)
> HCI Event: Command Status (0x0f) plen 4                                                   #5 [hci0] 2.914018
      LE Extended Create Connection (0x08|0x0043) ncmd 2
        Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 31                                                   #6 [hci0] 2.992163
      LE Enhanced Connection Complete (0x0a)
        Status: Success (0x00)
        Handle: 2048
        Role: Central (0x00)
        Peer address type: Random (0x01)
        Peer address: DB:EB:F8:89:54:5D (Static)
        Local resolvable private address: 00:00:00:00:00:00 (Non-Resolvable)
        Peer resolvable private address: 00:00:00:00:00:00 (Non-Resolvable)
        Connection interval: 45.00 msec (0x0024)
        Connection latency: 0 (0x0000)
        Supervision timeout: 420 msec (0x002a)
        Central clock accuracy: 0x00
@ MGMT Event: Device Connected (0x000b) plen 31                                       {0x0001} [hci0] 2.992222
        LE Address: DB:EB:F8:89:54:5D (Static)
        Flags: 0x00000008
          Connection Locally Initiated
        Data length: 18
        Appearance: Keyboard (0x03c1)
        Flags: 0x06
          LE General Discoverable Mode
          BR/EDR Not Supported
        16-bit Service UUIDs (complete): 1 entry
          Human Interface Device (0x1812)
        Company: Microsoft (6)
          Data: 030080
btmon[144343]: @ RAW Open: btmon (privileged) version 2.22                                   {0x0002} 2.992424
btmon[144343]: @ RAW Close: btmon                                                            {0x0002} 2.992431
> HCI Event: LE Meta Event (0x3e) plen 4                                                    #7 [hci0] 2.992856
      LE Channel Selection Algorithm (0x14)
        Handle: 2048 Address: DB:EB:F8:89:54:5D (Static)
        Algorithm: #2 (0x01)
< HCI Command: LE Read Remote Used Features (0x08|0x0016) plen 2                            #8 [hci0] 2.997145
        Handle: 2048 Address: DB:EB:F8:89:54:5D (Static)
> HCI Event: Command Status (0x0f) plen 4                                                   #9 [hci0] 2.997852
      LE Read Remote Used Features (0x08|0x0016) ncmd 1
        Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 12                                                  #10 [hci0] 3.065181
      LE Read Remote Used Features (0x04)
        Status: Success (0x00)
        Handle: 2048 Address: DB:EB:F8:89:54:5D (Static)
        Features: 0x05 0x41 0x00 0x00 0x00 0x00 0x00 0x00
          LE Encryption
          Extended Reject Indication
          LE 2M PHY
          Channel Selection Algorithm #2
< HCI Command: LE Start Encryption (0x08|0x0019) plen 28                                   #11 [hci0] 3.066105
        Handle: 2048 Address: DB:EB:F8:89:54:5D (Static)
        Random number: 0x0000000000000000
        Encrypted diversifier: 0x0000
        Long term key: d791b06ae853105526976c5feb3f9e83
bluetoothd[1329]: = src/service.c:service_accept() input-hog profile accept failed for DB:EB:F8:8..   3.066387
> HCI Event: Command Status (0x0f) plen 4                                                  #12 [hci0] 3.066893
      LE Start Encryption (0x08|0x0019) ncmd 1
        Status: Success (0x00)
> HCI Event: Encryption Change (0x08) plen 4                                               #13 [hci0] 3.334920
        Status: PIN or Key Missing (0x06)
        Handle: 2048 Address: DB:EB:F8:89:54:5D (Static)
        Encryption: Disabled (0x00)
< HCI Command: Disconnect (0x01|0x0006) plen 3                                             #14 [hci0] 3.335145
        Handle: 2048 Address: DB:EB:F8:89:54:5D (Static)
        Reason: Authentication Failure (0x05)
> HCI Event: Command Status (0x0f) plen 4                                                  #15 [hci0] 3.335883
      Disconnect (0x01|0x0006) ncmd 1
        Status: Success (0x00)
> HCI Event: Disconnect Complete (0x05) plen 4                                             #16 [hci0] 3.425144
        Status: Success (0x00)
        Handle: 2048 Address: DB:EB:F8:89:54:5D (Static)
        Reason: Connection Terminated By Local Host (0x16)
@ MGMT Event: Device Disconnected (0x000c) plen 8                                     {0x0001} [hci0] 3.425340
        LE Address: DB:EB:F8:89:54:5D (Static)
        Reason: Connection terminated due to authentication failure (0x04)
bluetoothd[1329]: = profiles/deviceinfo/deviceinfo.c:read_pnpid_cb() Error reading PNP_ID value:...   3.425723
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 13                       #17 [hci0] 3.441333
        Own address type: Public (0x00)
        Filter policy: Ignore not in accept list (0x01)
        PHYs: 0x05
        Entry 0: LE 1M
          Type: Passive (0x00)
          Interval: 60.000 msec (0x0060)
          Window: 30.000 msec (0x0030)
        Entry 1: LE Coded
          Type: Passive (0x00)
          Interval: 180.000 msec (0x0120)
          Window: 90.000 msec (0x0090)
> HCI Event: Command Complete (0x0e) plen 4                                                #18 [hci0] 3.441878
      LE Set Extended Scan Parameters (0x08|0x0041) ncmd 1
        Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6                            #19 [hci0] 3.442035
        Extended scan: Enabled (0x01)
        Filter duplicates: Enabled (0x01)
        Duration: 0 msec (0x0000)
        Period: 0.00 sec (0x0000)
> HCI Event: Command Complete (0x0e) plen 4                                                #20 [hci0] 3.442835
      LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
        Status: Success (0x00)

*我的意思是我进入 KDE 分区管理器并将我的 Ubuntu 分区大小调整为 300gb

有关我的 Linux 的信息：操作系统：Kubuntu 24.04 LTS x86_64 DE：Plasma 5.27.11