非常沮丧。尝试了关于 Ubuntu 无法检测到蓝牙适配器的众多解决方案，但都无济于事。我尝试了 Bluez、蓝牙管理器和 Blueman。
我不是程序员。我复制粘贴了几十行代码建议，但仍然无法让 Ubuntu 检测到加密狗。我不知道在终端中输入什么才能显示输出。
我使用的是旧款 Acer 笔记本电脑，曾经运行 Windows 7，现在仅运行 Ubuntu 18.04。
请帮忙。
我不知道这是否有帮助......
这是 lsusb 的输出
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 064e:a133 Suyin Corp.
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
我不太理解第二部分，也不认为我做得正确：
journalctl -f
-- Logs begin at Sat 2019-04-06 15:01:12 EDT. --
May 31 17:50:57 triumph dbus-daemon[1115]: [session uid=1000 pid=1115] Successfully activated service 'org.gnome.Nautilus'
May 31 17:50:57 triumph dbus-daemon[1115]: [session uid=1000 pid=1115] Successfully activated service 'org.gnome.Terminal'
May 31 17:50:57 triumph systemd[922]: Started GNOME Terminal Server.
May 31 17:50:57 triumph dbus-daemon[1115]: [session uid=1000 pid=1115] Successfully activated service 'org.gnome.Calendar'
May 31 17:50:57 triumph dbus-daemon[1115]: [session uid=1000 pid=1115] Successfully activated service 'org.gnome.seahorse.Application'
May 31 17:50:57 triumph nautilus[4617]: g_key_file_load_from_file: assertion 'file != NULL' failed
May 31 17:50:57 triumph nautilus[4617]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology”
May 31 17:50:58 triumph nautilus[4617]: g_queue_pop_head: assertion 'queue != NULL' failed
May 31 17:50:58 triumph nautilus[4617]: g_queue_foreach: assertion 'queue != NULL' failed
May 31 17:50:58 triumph nautilus[4617]: g_queue_free: assertion 'queue != NULL' failed
May 31 17:52:47 triumph org.gnome.Shell.desktop[1487]: [2268:2268:0531/175247.128775:ERROR:buffer_manager.cc(488)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error from previous GL command
May 31 17:55:04 triumph systemd-resolved[628]: Using degraded feature set (UDP) for DNS server 2607:fea8:6920:8a4:be4d:fbff:fed4:6342.
May 31 17:55:08 triumph systemd-resolved[628]: Using degraded feature set (TCP) for DNS server 2607:fea8:6920:8a4:be4d:fbff:fed4:6342.
May 31 17:55:22 triumph systemd-resolved[628]: Using degraded feature set (UDP) for DNS server 2607:fea8:6920:8a4:be4d:fbff:fed4:6342.
May 31 17:55:26 triumph systemd-resolved[628]: Using degraded feature set (TCP) for DNS server 2607:fea8:6920:8a4:be4d:fbff:fed4:6342.
May 31 17:55:31 triumph systemd-resolved[628]: Using degraded feature set (UDP) for DNS server 2607:fea8:6920:8a4:be4d:fbff:fed4:6342.
May 31 17:55:31 triumph systemd-resolved[628]: Using degraded feature set (TCP) for DNS server 2607:fea8:6920:8a4:be4d:fbff:fed4:6342.
May 31 17:55:33 triumph systemd-resolved[628]: Using degraded feature set (UDP) for DNS server 2607:fea8:6920:8a4:be4d:fbff:fed4:6342.
May 31 17:55:35 triumph systemd-resolved[628]: Using degraded feature set (TCP) for DNS server 2607:fea8:6920:8a4:be4d:fbff:fed4:6342.
May 31 17:55:37 triumph systemd-resolved[628]: Using degraded feature set (UDP) for DNS server 2607:fea8:6920:8a4:be4d:fbff:fed4:6342.
May 31 17:55:37 triumph systemd-resolved[628]: Using degraded feature set (TCP) for DNS server 2607:fea8:6920:8a4:be4d:fbff:fed4:6342.
May 31 17:55:41 triumph systemd-resolved[628]: Using degraded feature set (UDP) for DNS server 2607:fea8:6920:8a4:be4d:fbff:fed4:6342.
May 31 17:55:41 triumph systemd-resolved[628]: Using degraded feature set (TCP) for DNS server 2607:fea8:6920:8a4:be4d:fbff:fed4:6342.
May 31 17:55:43 triumph systemd-resolved[628]: Using degraded feature set (UDP) for DNS server 2607:fea8:6920:8a4:be4d:fbff:fed4:6342.
May 31 17:55:46 triumph systemd-resolved[628]: Using degraded feature set (TCP) for DNS server 2607:fea8:6920:8a4:be4d:fbff:fed4:6342.
May 31 17:55:48 triumph systemd-resolved[628]: Using degraded feature set (UDP) for DNS server 2607:fea8:6920:8a4:be4d:fbff:fed4:6342.
May 31 17:55:49 triumph systemd-resolved[628]: Using degraded feature set (TCP) for DNS server 2607:fea8:6920:8a4:be4d:fbff:fed4:6342.
May 31 17:55:51 triumph systemd-resolved[628]: Using degraded feature set (UDP) for DNS server 2607:fea8:6920:8a4:be4d:fbff:fed4:6342.
May 31 17:55:52 triumph systemd-resolved[628]: Using degraded feature set (TCP) for DNS server 2607:fea8:6920:8a4:be4d:fbff:fed4:6342.
May 31 17:55:53 triumph systemd-resolved[628]: Using degraded feature set (UDP) for DNS server 2607:fea8:6920:8a4:be4d:fbff:fed4:6342.
May 31 17:55:55 triumph systemd-resolved[628]: Using degraded feature set (TCP) for DNS server 2607:fea8:6920:8a4:be4d:fbff:fed4:6342.
May 31 17:55:57 triumph systemd-resolved[628]: Using degraded feature set (UDP) for DNS server 2607:fea8:6920:8a4:be4d:fbff:fed4:6342.
May 31 17:55:58 triumph systemd-resolved[628]: Using degraded feature set (TCP) for DNS server 2607:fea8:6920:8a4:be4d:fbff:fed4:6342.
May 31 17:55:59 triumph systemd-resolved[628]: Using degraded feature set (UDP) for DNS server 2607:fea8:6920:8a4:be4d:fbff:fed4:6342.
May 31 17:56:00 triumph systemd-resolved[628]: Using degraded feature set (TCP) for DNS server 2607:fea8:6920:8a4:be4d:fbff:fed4:6342.
May 31 17:56:03 triumph systemd-resolved[628]: Using degraded feature set (UDP) for DNS server 2607:fea8:6920:8a4:be4d:fbff:fed4:6342.
May 31 17:56:05 triumph systemd-resolved[628]: Using degraded feature set (TCP) for DNS server 2607:fea8:6920:8a4:be4d:fbff:fed4:6342.
May 31 17:56:06 triumph systemd-resolved[628]: Using degraded feature set (UDP) for DNS server 2607:fea8:6920:8a4:be4d:fbff:fed4:6342.
May 31 17:56:07 triumph systemd-resolved[628]: Using degraded feature set (TCP) for DNS server 2607:fea8:6920:8a4:be4d:fbff:fed4:6342.
May 31 17:56:08 triumph systemd-resolved[628]: Using degraded feature set (UDP) for DNS server 2607:fea8:6920:8a4:be4d:fbff:fed4:6342.
May 31 17:56:09 triumph systemd-resolved[628]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
May 31 17:56:09 triumph systemd-resolved[628]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
May 31 17:56:09 triumph systemd-resolved[628]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
May 31 17:56:09 triumph systemd-resolved[628]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
May 31 17:56:09 triumph systemd-resolved[628]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
May 31 17:56:09 triumph systemd-resolved[628]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
May 31 17:56:09 triumph systemd-resolved[628]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
May 31 17:56:09 triumph systemd-resolved[628]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
May 31 17:56:09 triumph systemd-resolved[628]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
May 31 17:56:09 triumph systemd-resolved[628]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
May 31 17:56:09 triumph systemd-resolved[628]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
May 31 17:56:09 triumph systemd-resolved[628]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
May 31 17:56:09 triumph systemd-resolved[628]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
May 31 17:56:09 triumph systemd-resolved[628]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
May 31 17:56:09 triumph systemd-resolved[628]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
May 31 17:56:12 triumph systemd-resolved[628]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
May 31 17:56:12 triumph systemd-resolved[628]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
May 31 17:57:14 triumph wpa_supplicant[793]: wlp7s0: WPA: Group rekeying completed with bc:4d:fb:d4:63:48 [GTK=TKIP]
May 31 17:57:33 triumph org.gnome.Shell.desktop[1487]: [2268:2268:0531/175733.446350:ERROR:buffer_manager.cc(488)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error from previous GL command