我在一台笔记本电脑上运行 Xubuntu 16.04.5，而 18.04 不支持 nVidia 驱动程序，所以我卡在这里（我需要专有驱动程序）。前段时间，每当我启动这台机器时，都会弹出错误对话框。我不指望修复，但我想找出故障软件并重新安装或删除它。
所以我的问题是：我识别的错误消息涉及哪些软件包。顺便说一句，我看到一些关于蓝牙的引用，据我所知，这款戴尔 inspiron 1720 没有蓝牙硬件，只有 wifi。如果我幸运的话，那么我可以禁用一些无论如何都无法工作的东西。
我查看了 /var/log/syslog，发现可能相关的错误报告。我不能确定，因为对话框中没有提示到底是什么失败了，只是给出了是否“报告”失败的选择。
当我在 vim 中查看系统日志时，我看到这些行上有红色突出显示。
Sep 11 20:08:40 Roisin-x org.a11y.Bus[1452]: ** (process:1569): WARNING **: Failed to register client:
以及两次
Sep 11 20:08:52 Roisin-x org.blueman.Mechanism[679]: Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Sep 11 20:08:52 Roisin-x org.blueman.Mechanism[679]: Unable to init server: Could not connect: Connection refused
最后
Sep 11 20:08:52 Roisin-x org.blueman.Mechanism[679]: Failed to connect to Mir: Failed to connect to server socket: No such file or directory
如果需要更多背景信息，以下是发生该情况的部分
Sep 11 20:08:37 Roisin-x ntpd[1224]: Soliciting pool server 96.126.122.39
Sep 11 20:08:37 Roisin-x ntpd[1224]: Soliciting pool server 2001:470:0:50::2
Sep 11 20:08:38 Roisin-x ntpd[1224]: Soliciting pool server 91.189.89.198
Sep 11 20:08:40 Roisin-x org.a11y.Bus[1452]: ** (process:1569): WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
Sep 11 20:08:40 Roisin-x org.a11y.Bus[1452]: Activating service name='org.a11y.atspi.Registry'
Sep 11 20:08:40 Roisin-x org.a11y.Bus[1452]: Successfully activated service 'org.a11y.atspi.Registry'
Sep 11 20:08:40 Roisin-x org.a11y.atspi.Registry[1584]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Sep 11 20:08:40 Roisin-x systemd[1297]: Time has been changed
Sep 11 20:08:40 Roisin-x systemd[1120]: Time has been changed
Sep 11 20:08:40 Roisin-x systemd[1]: Time has been changed
Sep 11 20:08:44 Roisin-x rtkit-daemon[1186]: Successfully made thread 1867 of process 1867 (n/a) owned by '1000' high priority at nice level -11.
Sep 11 20:08:44 Roisin-x rtkit-daemon[1186]: Supervising 4 threads of 2 processes of 2 users.
Sep 11 20:08:44 Roisin-x rtkit-daemon[1186]: Supervising 4 threads of 2 processes of 2 users.
Sep 11 20:08:44 Roisin-x rtkit-daemon[1186]: Successfully made thread 1873 of process 1867 (n/a) owned by '1000' RT at priority 5.
Sep 11 20:08:44 Roisin-x rtkit-daemon[1186]: Supervising 5 threads of 2 processes of 2 users.
Sep 11 20:08:44 Roisin-x rtkit-daemon[1186]: Supervising 5 threads of 2 processes of 2 users.
Sep 11 20:08:44 Roisin-x rtkit-daemon[1186]: Successfully made thread 1874 of process 1867 (n/a) owned by '1000' RT at priority 5.
Sep 11 20:08:44 Roisin-x rtkit-daemon[1186]: Supervising 6 threads of 2 processes of 2 users.
Sep 11 20:08:45 Roisin-x rtkit-daemon[1186]: Successfully made thread 1917 of process 1917 (n/a) owned by '1000' high priority at nice level -11.
Sep 11 20:08:45 Roisin-x rtkit-daemon[1186]: Supervising 7 threads of 3 processes of 2 users.
Sep 11 20:08:45 Roisin-x pulseaudio[1917]: [pulseaudio] pid.c: Daemon already running.
Sep 11 20:08:46 Roisin-x dbus[679]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
Sep 11 20:08:46 Roisin-x systemd[1]: Starting Daemon for power management...
Sep 11 20:08:47 Roisin-x dbus[679]: [system] Successfully activated service 'org.freedesktop.UPower'
Sep 11 20:08:47 Roisin-x systemd[1]: Started Daemon for power management.
Sep 11 20:08:50 Roisin-x dbus[679]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
Sep 11 20:08:50 Roisin-x systemd[1]: Starting Disk Manager...
Sep 11 20:08:50 Roisin-x udisksd[2082]: udisks daemon version 2.1.7 starting
Sep 11 20:08:50 Roisin-x dbus[679]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Sep 11 20:08:50 Roisin-x systemd[1]: Started Disk Manager.
Sep 11 20:08:50 Roisin-x udisksd[2082]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Sep 11 20:08:50 Roisin-x org.gtk.vfs.AfcVolumeMonitor[1452]: Volume monitor alive
Sep 11 20:08:52 Roisin-x obexd[2108]: OBEX daemon 5.37
Sep 11 20:08:52 Roisin-x dbus[679]: [system] Activating service name='org.blueman.Mechanism' (using servicehelper)
Sep 11 20:08:52 Roisin-x kernel: [ 57.624679] Bluetooth: RFCOMM TTY layer initialized
Sep 11 20:08:52 Roisin-x kernel: [ 57.624692] Bluetooth: RFCOMM socket layer initialized
Sep 11 20:08:52 Roisin-x kernel: [ 57.624701] Bluetooth: RFCOMM ver 1.11
Sep 11 20:08:52 Roisin-x org.blueman.Mechanism[679]: Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Sep 11 20:08:52 Roisin-x org.blueman.Mechanism[679]: Unable to init server: Could not connect: Connection refused
Sep 11 20:08:52 Roisin-x org.blueman.Mechanism[679]: Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Sep 11 20:08:52 Roisin-x org.blueman.Mechanism[679]: Unable to init server: Could not connect: Connection refused
Sep 11 20:08:52 Roisin-x blueman-mechanism: Starting blueman-mechanism
Sep 11 20:08:52 Roisin-x dbus[679]: [system] Successfully activated service 'org.blueman.Mechanism'
Sep 11 20:08:52 Roisin-x org.blueman.Mechanism[679]: (blueman-mechanism:2172): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
Sep 11 20:08:52 Roisin-x blueman-mechanism: loading Network
Sep 11 20:08:52 Roisin-x blueman-mechanism: loading Ppp
Sep 11 20:08:52 Roisin-x blueman-mechanism: loading RfKill
Sep 11 20:08:52 Roisin-x blueman-mechanism: loading Rfcomm
Sep 11 20:09:14 Roisin-x systemd[1]: Starting Stop ureadahead data collection...
Sep 11 20:09:14 Roisin-x systemd[1]: Stopped Read required files in advance.
@Javier Ochoa，我运行了该命令并输出以下输出：
root@Roisin-x:~# systemctl disable bluetooth.service
Synchronizing state of bluetooth.service with SysV init with /lib/systemd/systemd-sysv-install...
Executing /lib/systemd/systemd-sysv-install disable bluetooth
insserv: warning: current start runlevel(s) (empty) of script `bluetooth' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `bluetooth' overrides LSB defaults (0 1 6).
Removed symlink /etc/systemd/system/dbus-org.bluez.service.
root@Roisin-x:~#
当我启用无线功能（通过这台笔记本电脑上的开关）并运行“rfkill list”时，我得到了
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
inxi -c 5 -b 命令生成
System: Host: Roisin-x Kernel: 4.4.0-135-generic x86_64 (64 bit) Desktop: Xfce 4.12.3
Distro: Ubuntu 16.04 xenial
Machine: System: Dell (portable) product: Inspiron 1720 serial: 10SSGF1
Mobo: Dell model: 0UK437 serial: .10SSGF1.CN486437CJ6132. Bios: Dell v: A09 date: 07/11/2008
CPU: Dual core Intel Core2 Duo T7250 (-MCP-) speed/max: 1200/2001 MHz
Graphics: Card: NVIDIA G84M [GeForce 8600M GT]
Display Server: X.org 1.18.4 drivers: nvidia (unloaded: fbdev,vesa,nouveau)
tty size: 133x78 Advanced Data: N/A for root
Network: Card-1: Broadcom BCM4401-B0 100Base-TX driver: b44
Card-2: Intel PRO/Wireless 3945ABG [Golan] Network Connection driver: iwl3945
Drives: HDD Total Size: 1031.6GB (1.6% used)
Info: Processes: 175 Uptime: 8 min Memory: 292.8/1998.5MB Client: Shell (bash) inxi: 2.2.35
重新启动后，我登录时系统不再显示错误对话框。系统日志中有错误和失败，但它们不同，而且可能并不重要。
我还是不明白为什么关掉开关会出现“系统程序错误”的对话框。这真是令人苦恼。
最终解决方案：重新安装 vi“apt-get install --reinstall linux-firmware”似乎已经消除了无线禁用时重新启动的问题。
答案1
我认为这不是 blueman 机制的问题。顺便问一下，你运行的是哪个桌面环境？这将有助于找到正确的解决方案。现在，我会尽力帮助你。请在终端上运行此命令：rfkill list 输出必须只显示 wifi 卡（软阻止否和硬阻止否）并且不显示蓝牙设备。然后，你能在启动应用程序中查看是否启用了任何蓝牙程序以在启动过程中加载吗？否则，你可以查看声音偏好设置以查看是否有蓝牙设备在使用。最后，你也可以禁用我之前提到的启动 bluethoot.service，在终端中运行此命令：sudo systemctl disable bluetooth.service，尽管你的计算机中没有 bluethoot 设备。