主要问题

我正在尝试为我的系统自动加载驱动程序。驱动程序是手动构建的，必须手动加载。另一个需要注意的是，必须先加载和卸载其中一个系统驱动程序，然后才能手动插入构建的驱动程序。在 CLI 中，它看起来像这样：

modprobe gspca_main && rmmod gspca_main && modprobe videodev && insmod gspca_main.ko && insmod gspca_kinect2.ko

选项

我想在启动时自动执行此操作，这样我就不必每次都运行上述内容。正如我目前所看到的，我有几个选择：

1. 克朗

看起来我可以在这里使用@reboot 字符串来运行脚本

2. 在里面

或者，我考虑过创建一个init脚本，但我不一定需要对runlevel's 或执行时间的所有控制。在这里，我没有看到任何Exec“另一件事”所必需的 multiples 实例。

3. 模组探针

在下面添加一个conf文件/etc/modprobe.d似乎最有意义，因为毕竟我正在尝试加载一些驱动程序。这个选项的唯一问题是我不确定驱动程序是否可以顺序加载然后卸载。

另一件事

所有这一切的另一部分是在加载驱动程序后，我还需要运行一个脚本：

#!/bin/sh
sudo rmmod v4l2loopback
sudo modprobe v4l2loopback video_nr=10 card_label="Kinect v2"
ffmpeg \
    -i /dev/video0 \
    -vsync drop \
    -filter:v fps=30,scale=1280:-1,hflip \
    -pix_fmt yuyv422 \
    -color_trc bt709 \
    -color_primaries bt709 \
    -color_range tv \
    -f v4l2 \
    /dev/video10

哪个似乎更适合cronor init。

哪个选项是稳定性和易于配置的最佳折衷方案？

提前感谢您的任何/所有帮助！

我有以下命令要绑定到 Ubuntu 中的键盘快捷键：

node ~/Executables/harmonyHubCLI/harmonyHubCli.js -l 10.0.0.59 -d 'Samsung TV' -c 'InputHdmi3'

在终端会话中工作正常。但是，在键盘快捷键设置 GUI 中使用此命令不会产生任何结果 - 但是，如果我将命令更改为“nautilus”之类的命令，它就可以正常工作。我也在整个命令周围尝试了双引号 - 结果相同。

这种事情是不可能的吗？

使用以下命令安装 docker 后：

[user@localhost ~]$ curl -fsSL https://get.docker.com -o get-docker.sh
[user@localhost ~]$ sudo sh get-docker.sh
[user@localhost ~]$ sudo usermod -aG docker $USER

并重新启动，我的wlan0设备不再可用（并被替换为docker0）。我禁用了 docker 服务systemctl disable docker）并再次重新启动。我现在有以下调试信息：

sterlingbutters@butters-ubuntu:~$ uname -a
Linux butters-ubuntu 5.3.0-43-generic #36-Ubuntu SMP Mon Mar 16 13:29:01 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

sterlingbutters@butters-ubuntu:~$ sudo lspci -vs 04:00.0
04:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] (rev 10)
    Subsystem: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak]
    Flags: bus master, fast devsel, latency 0, IRQ 69, NUMA node 0
    Memory at 92d00000 (64-bit, non-prefetchable) [size=8K]
    Capabilities: [c8] Power Management version 3
    Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
    Capabilities: [40] Express Endpoint, MSI 00
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [140] Device Serial Number a0-af-bd-ff-ff-c3-3f-52
    Capabilities: [14c] Latency Tolerance Reporting
    Capabilities: [154] L1 PM Substates
    Kernel driver in use: iwlwifi
    Kernel modules: iwlwifi

sterlingbutters@butters-ubuntu:~$ dmesg | grep iwl
[   35.811059] iwlwifi 0000:04:00.0: enabling device (0000 -> 0002)
[   36.762569] iwlwifi 0000:04:00.0: loaded firmware version 29.1654887522.0 op_mode iwlmvm
[   38.612055] iwlwifi 0000:04:00.0: Detected Intel(R) Dual Band Wireless AC 3168, REV=0x220
[   38.629869] iwlwifi 0000:04:00.0: Can't parse phy_sku in B0, empty sections
[   38.629872] iwlwifi 0000:04:00.0: Failed to read NVM: -61
[   38.629873] iwlwifi 0000:04:00.0: Collecting data: trigger 16 fired.
[   38.631034] iwlwifi 0000:04:00.0: Start IWL Error Log Dump:
[   38.631035] iwlwifi 0000:04:00.0: Status: 0x00000080, count: 6
[   38.631036] iwlwifi 0000:04:00.0: Loaded firmware version: 29.1654887522.0
[   38.631037] iwlwifi 0000:04:00.0: 0x00000084 | NMI_INTERRUPT_UNKNOWN       
[   38.631038] iwlwifi 0000:04:00.0: 0x000002F0 | trm_hw_status0
[   38.631039] iwlwifi 0000:04:00.0: 0x00000000 | trm_hw_status1
[   38.631039] iwlwifi 0000:04:00.0: 0x0004171E | branchlink2
[   38.631040] iwlwifi 0000:04:00.0: 0x000446B2 | interruptlink1
[   38.631041] iwlwifi 0000:04:00.0: 0x000446B2 | interruptlink2
[   38.631041] iwlwifi 0000:04:00.0: 0x00000000 | data1
[   38.631042] iwlwifi 0000:04:00.0: 0x00000080 | data2
[   38.631042] iwlwifi 0000:04:00.0: 0x07030000 | data3
[   38.631043] iwlwifi 0000:04:00.0: 0x00000000 | beacon time
[   38.631044] iwlwifi 0000:04:00.0: 0x000011FD | tsf low
[   38.631044] iwlwifi 0000:04:00.0: 0x00000000 | tsf hi
[   38.631045] iwlwifi 0000:04:00.0: 0x00000000 | time gp1
[   38.631046] iwlwifi 0000:04:00.0: 0x000011FD | time gp2
[   38.631046] iwlwifi 0000:04:00.0: 0x00000009 | uCode revision type
[   38.631047] iwlwifi 0000:04:00.0: 0x0000001D | uCode version major
[   38.631047] iwlwifi 0000:04:00.0: 0x62A39462 | uCode version minor
[   38.631048] iwlwifi 0000:04:00.0: 0x00000220 | hw version
[   38.631049] iwlwifi 0000:04:00.0: 0x00C89200 | board version
[   38.631049] iwlwifi 0000:04:00.0: 0x00110188 | hcmd
[   38.631050] iwlwifi 0000:04:00.0: 0x00022000 | isr0
[   38.631051] iwlwifi 0000:04:00.0: 0x00000000 | isr1
[   38.631051] iwlwifi 0000:04:00.0: 0x00000002 | isr2
[   38.631052] iwlwifi 0000:04:00.0: 0x004000C0 | isr3
[   38.631052] iwlwifi 0000:04:00.0: 0x00000000 | isr4
[   38.631053] iwlwifi 0000:04:00.0: 0x00110188 | last cmd Id
[   38.631054] iwlwifi 0000:04:00.0: 0x00000000 | wait_event
[   38.631054] iwlwifi 0000:04:00.0: 0x00000094 | l2p_control
[   38.631055] iwlwifi 0000:04:00.0: 0x00000000 | l2p_duration
[   38.631056] iwlwifi 0000:04:00.0: 0x00000000 | l2p_mhvalid
[   38.631056] iwlwifi 0000:04:00.0: 0x00000000 | l2p_addr_match
[   38.631057] iwlwifi 0000:04:00.0: 0x00000007 | lmpm_pmg_sel
[   38.631057] iwlwifi 0000:04:00.0: 0x16070617 | timestamp
[   38.631058] iwlwifi 0000:04:00.0: 0x00341018 | flow_handler
[   38.631065] iwlwifi 0000:04:00.0: Fseq Registers:
[   38.631070] iwlwifi 0000:04:00.0: 0x00000000 | FSEQ_ERROR_CODE
[   38.631075] iwlwifi 0000:04:00.0: 0x00000000 | FSEQ_TOP_INIT_VERSION
[   38.631080] iwlwifi 0000:04:00.0: 0x00000000 | FSEQ_CNVIO_INIT_VERSION
[   38.631085] iwlwifi 0000:04:00.0: 0x00000000 | FSEQ_OTP_VERSION
[   38.631089] iwlwifi 0000:04:00.0: 0x00000000 | FSEQ_TOP_CONTENT_VERSION
[   38.631094] iwlwifi 0000:04:00.0: 0x00000000 | FSEQ_ALIVE_TOKEN
[   38.631099] iwlwifi 0000:04:00.0: 0x00000000 | FSEQ_CNVI_ID
[   38.631104] iwlwifi 0000:04:00.0: 0x00000000 | FSEQ_CNVR_ID
[   38.631108] iwlwifi 0000:04:00.0: 0x00000000 | CNVI_AUX_MISC_CHIP
[   38.631113] iwlwifi 0000:04:00.0: 0x00000000 | CNVR_AUX_MISC_CHIP
[   38.631118] iwlwifi 0000:04:00.0: 0x00000000 | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[   38.631123] iwlwifi 0000:04:00.0: 0x00000000 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[   38.631127] iwlwifi 0000:04:00.0: Firmware not running - cannot dump error
[   38.642872] iwlwifi 0000:04:00.0: Failed to run INIT ucode: -61

sterlingbutters@butters-ubuntu:~$ ifconfig -a
enp0s31f6: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 70:85:c2:52:23:dd  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 16  memory 0x92f00000-92f20000  

enp5s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 70:85:c2:52:23:df  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device memory 0x92c00000-92c1ffff  

enx00e04c680d9c: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 00:e0:4c:68:0d:9c  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 5519  bytes 399125 (399.1 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 5519  bytes 399125 (399.1 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

sterlingbutters@butters-ubuntu:~$ cat /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback

sterlingbutters@butters-ubuntu:~$ sudo lshw -c network
  *-network                 
       description: Network controller
       product: Dual Band Wireless-AC 3168NGW [Stone Peak]
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:04:00.0
       version: 10
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list
       configuration: driver=iwlwifi latency=0
       resources: irq:69 memory:92d00000-92d01fff
  *-network
       description: Ethernet interface
       product: I211 Gigabit Network Connection
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:05:00.0
       logical name: enp5s0
       version: 03
       serial: 70:85:c2:52:23:df
       capacity: 1Gbit/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi msix pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=igb driverversion=5.6.0-k firmware=0. 4-1 latency=0 link=no multicast=yes port=twisted pair
       resources: irq:17 memory:92c00000-92c1ffff ioport:3000(size=32) memory:92c20000-92c23fff
  *-network
       description: Ethernet interface
       product: Ethernet Connection (2) I219-V
       vendor: Intel Corporation
       physical id: 1f.6
       bus info: pci@0000:00:1f.6
       logical name: enp0s31f6
       version: 00
       serial: 70:85:c2:52:23:dd
       capacity: 1Gbit/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.6-k firmware=0.2-4 latency=0 link=no multicast=yes port=twisted pair
       resources: irq:47 memory:92f00000-92f1ffff
  *-network
       description: Ethernet interface
       physical id: 1
       bus info: usb@1:5.2
       logical name: enx00e04c680d9c
       serial: 00:e0:4c:68:0d:9c
       size: 10Mbit/s
       capacity: 1Gbit/s
       capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8152 driverversion=v1.09.11 duplex=half link=no multicast=yes port=MII speed=10Mbit/s

sterlingbutters@butters-ubuntu:~$ lsmod | grep iwl 
iwlmvm                401408  0
mac80211              851968  1 iwlmvm
iwlwifi               348160  1 iwlmvm
cfg80211              712704  3 iwlmvm,iwlwifi,mac80211

任何想法为什么我的无线接口会因为 docker 而消失？提前致谢

背景

转到普通设置应用程序，很明显 WiFi 或 BT UI 没有任何功能。开/关开关不起作用，没有可见的 wifi 或 BT 设备。因此，我不得不更深入地挖掘。

关于WiFi

我有一个华擎太极 X299 主板。MoBo 带有 WiFi 和 BT。但是，可能值得注意的是，为了在 Windows（双启动系统）中启用它们，我必须使用驱动程序安装光盘上的华擎网络实用程序（或类似的东西）。我还插入了我自己的加密狗（仍然连接着），看看我能不能得到任何东西。运行sudo lshw -class network产量：

*-network DISABLED
description: Wireless interface product: Intel Corporation vendor: Intel Corporation physical id: 0 bus info: pci@0000:04:00.0 logical name: wlp4s0 version: 10 serial: a0:af:bd:c3:3f:52 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.13.0-38-generic firmware=29.610311.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:69 memory:92d00000-92d01fff *-network description: Ethernet interface product: I211 Gigabit Network Connection vendor: Intel Corporation physical id: 0 bus info: pci@0000:05:00.0 logical name: enp5s0 version: 03 serial: 70:85:c2:52:23:df capacity: 1Gbit/s width: 32 bits clock: 33MHz capabilities: pm msi msix pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=igb driverversion=5.4.0-k firmware=0. 4-1 latency=0 link=no multicast=yes port=twisted pair resources: irq:17 memory:92c00000-92c1ffff ioport:3000(size=32) memory:92c20000-92c23fff *-network description: Ethernet interface product: Ethernet Connection (2) I219-V vendor: Intel Corporation physical id: 1f.6 bus info: pci@0000:00:1f.6 logical name: enp0s31f6 version: 00 serial: 70:85:c2:52:23:dd size: 100Mbit/s capacity: 1Gbit/s width: 32 bits clock: 33MHz capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.6-k duplex=full firmware=0.2-4 ip=10.0.0.199 latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s resources: irq:50 memory:92f00000-92f1ffff *-network description: Ethernet interface physical id: 1 logical name: enx00e04c680d9c serial: 00:e0:4c:68:0d:9c size: 10Mbit/s capacity: 1Gbit/s capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8152 driverversion=v1.09.9 duplex=half link=no multicast=yes port=MII speed=10Mbit/s

其中DISABLED网络是WiFi接口。运行rfkill list产量：

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

但我不知道如何移除台式电脑上的硬块。我所看到的大多数解决此问题的方法都与具有相应物理“开关”的笔记本电脑有关。也许BIOS中有什么东西？（但我仍然不确定要寻找什么）

关于蓝牙

有趣的是rfkill list，如上所述，它的输出没有提供任何有关蓝牙被阻止的信息。但是，如果我运行lsusb，我会得到几个条目，但分别是：

Bus 001 Device 003: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth 我倾向于说这是我插入的加密狗，而不是 MoBo BT（我找不到使用lshw它；尽管我可能会错过它）。

我在 Synaptic 包管理器中安装了： bluez-tools, bluez, bluez-cups, bluez-dbg, bluez-obexd, bluez-tests, libbluetooth3, libbluetooth3-dbg blueman, 。bluetooth我在 Ubuntu 软件中安装了蓝牙管理器，希望它能知道我不知道的东西。

尝试运行蓝牙管理器时，我得到：“与 BlueZ 的连接失败 - Bluez 守护程序未运行...未检测到蓝牙适配器或蓝牙守护程序未启动。”

如果我运行sudo service bluetooth restart并检查sudo service bluetooth status，我会得到以下信息：

● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: inactive (dead) Docs: man:bluetoothd(8)

我不确定如何强制启动服务（如果这是我的问题）。

所以，我不确定 WiFi/BT 问题是否相关，但我无法工作。幸运的是，我是通过以太网连接的，但如果我需要它，我想选择 WiFi 和 BT 只是因为。我意识到这有很多事情要做，所以感谢所有帮助，谢谢！

更新：我刚刚尝试了一个不同的 BT 加密狗，它可以正常工作。我猜我的 MoBo BT 或其他加密狗在 linux 下都不受支持。仍然想知道他们是否会进行额外的设置，但这个其他加密狗现在可以工作。

编辑： lspci -nnk | grep 0280 -A3输出：

04:00.0 Network controller [0280]: Intel Corporation Device [8086:24fb] (rev 10) Subsystem: Intel Corporation Device [8086:2110] Kernel modules: iwlwifi, wl 05:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03)

cat /etc/modules输出：

# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.

^ 文件显示为空？应该是吗？

背景

我正在尝试对我的 Ubuntu 系统进行非常全面的备份。我正在运行以下rsync命令：

sudo rsync -aAEHSXxv --progress --delete --exclude={/home/sterlingbutters/Butters-Ubuntu-Backup/*, /home/*/.cache/*, /home/*/.local/share/Trash/*, /dev/*, /proc/*, /sys/*, /tmp/*, /mnt/*, /media/*, /lost+found} / /home/sterlingbutters/Butters-Ubuntu-Backup

文件结构应该很明显的地方。

问题

1. 我得到以下关于不存在的文件/目录的输出：

   rsync: change_dir "/home/*/.cache" failed: No such file or directory (2)
   rsync: change_dir "/home/*/.local/share/Trash" failed: No such file or directory (2)
   rsync: link_stat "/dev/*," failed: No such file or directory (2)
   rsync: link_stat "/proc/*," failed: No such file or directory (2)
   rsync: link_stat "/sys/*," failed: No such file or directory (2)
   rsync: link_stat "/tmp/*," failed: No such file or directory (2)
   rsync: link_stat "/mnt/*," failed: No such file or directory (2)
   rsync: link_stat "/media/*," failed: No such file or directory (2)
   rsync: link_stat "/lost+found}" failed: No such file or directory (2)
   created directory /home/sterlingbutters/Butters-Ubuntu-Backup
   IO error encountered -- skipping file deletion
   

   这是否意味着源或目标上不存在该文件？（因为它们清楚地存在于源上）

2. 后来，我开始收到一堆关于.cache我认为我排除的目录的条目：

   ... 
   home/sterlingbutters/.cache/mozilla/firefox/90d4yr8z.default/cache2/entries/76A1426700B3173C5B976F65F04FA6CD01D90D15
   ...
   

3. 我很担心“看看会发生什么”，因为如果没有正确排除目录，我可能会遇到无限复制循环，因为目标目录位于 ~/.

4. 我的代码几乎完全遵循此处文档中指定的模式（我所做的唯一更改我觉得应该仍然可以接受）：我也觉得我的语法遵循我在其他论坛帖子中找到的语法。即使没有，这不会与链接中的文档产生差异吗？

感谢所有帮助 - 谢谢！

我无法弄清楚这一点；我发誓我做的一切都是正确的：

在 BIOS 中：

• 从板载 LAN 唤醒 -> 启用

在窗口中：

• 我已启用每个有能力的 NIC 以唤醒 LAN（魔术包）

• 我已经检查了电源管理选项卡下的所有框以获取相同的 NIC ^ 并且不允许计算机关闭它们

在 ubuntu 中：

ethtool输出：

ethtool enp0s31f6
Settings for enp0s31f6:
    Supported ports: [ TP ]
    Supported link modes:   10baseT/Half 10baseT/Full 
                            100baseT/Half 100baseT/Full 
                            1000baseT/Full 
    Supported pause frame use: No
    Supports auto-negotiation: Yes
    Advertised link modes:  10baseT/Half 10baseT/Full 
                            100baseT/Half 100baseT/Full 
                            1000baseT/Full 
    Advertised pause frame use: No
    Advertised auto-negotiation: Yes
    Speed: 100Mb/s
    Duplex: Full
    Port: Twisted Pair
    PHYAD: 1
    Transceiver: internal
    Auto-negotiation: on
    MDI-X: off (auto)
    Supports Wake-on: pumbg
    Wake-on: g
    Current message level: 0x00000007 (7)
                   drv probe link
    Link detected: yes

为什么我的电脑打不开……我想不通

编辑：我开始怀疑我的网络基础设施是否存在问题，例如防火墙或其他什么？这是真的吗 - https://forums.techguy.org/threads/not-allowed-to-to-set-up-wake-on-lan-on-a-xfinity-modem.1201350/？

我正在为 Ubuntu 寻找具有最少设置的 vnc 服务器。我用vino、x11vnc、tightvnc、realvnc 尝试了几乎所有你能找到的论坛程序。我只需要一个万无一失的 vnc 设置程序。我想在启动等时运行，但在这一点上我只是想要一些工作。

我能想到的因素太多了，为什么我不能让包括显示管理器、桌面（gnome/unity/etc）在内的东西正常工作[我知道 17.10 使用 gnome，但我还没有验证这一点] ）（我也想保留默认桌面），关于wayland & x11（无 xauthority）等

我正在尝试在 Ubuntu 14.04.2 上使用命令启用图形根登录：

sudo passwd root
sudo sh -c 'echo "greeter-show-manual-login=true" >> /etc/lightdm/lightdm.conf'

与 lightdm 相关的部分 VMware 工具崩溃

有什么方法可以在登录菜单中以图形方式启用 root 访问权限而不与 VMware 工具发生冲突？

# ~/.profile: executed by Bourne-compatible login shells.

如果 [ "$BASH" ]; 然后如果 [ -f ~/.bashrc ]; 然后 。~/.bashrc fi fi mesg n

文件目录：

# ~/.bashrc: executed by bash(1) for non-login shells. 
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples

# If not running interactively, don't do anything

[ -z "$PS1" ] && 返回

# don't put duplicate lines in the history. See bash(1) for more options
# ... or force ignoredups and ignorespace

HISTCONTROL=ignoredups:忽略空间

# append to the history file, don't overwrite it

shopt -s histappend

# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)

HISTSIZE=1000 HISTFILESIZE=2000

# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.

shopt -s checkwinsize

# make less more friendly for non-text input files, see lesspipe(1)

[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"

# set variable identifying the chroot you work in (used in the prompt below)

如果 [ -z "$debian_chroot" ] && [ -r /etc/debian_chroot ]; 然后 debian_chroot=$(cat /etc/debian_chroot) fi

# set a fancy prompt (non-color, unless we know we "want" color)

在 xterm-color 中使用“$TERM”）color_prompt=yes;; esac

# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes

如果 [ -n "$force_color_prompt" ]; 然后 if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; 然后 # 我们有颜色支持；假设它符合 Ecma-48 # (ISO/IEC-6429)。（缺少这种支持的情况极为罕见，#a case 倾向于支持 setf 而不是 setaf。）color_prompt=yes else color_prompt= fi fi

如果 [ "$color_prompt" = yes ]; 然后 PS1='${debian_chroot:+($debian_chroot)}[\033[01;32m]\u@\h[\033[00m]:[\033[01;34m]\w[\033[00m] \$ ' else PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ ' fi unset color_prompt force_color_prompt

# If this is an xterm set the title to user@host:dir

在 xterm*|rxvt*) PS1="[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a]$PS1" ;; *);; esac

# enable color support of ls and also add handy aliases

如果 [ -x /usr/bin/dircolors ]; 然后测试 -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)" 别名 ls='ls --color=auto' #alias dir='dir --color=auto' #alias vdir='vdir --color=auto'

alias grep='grep --color=auto'
alias fgrep='fgrep --color=auto'
alias egrep='egrep --color=auto'

菲

# some more ls aliases

别名 ll='ls -alF' 别名 la='ls -A' 别名 l='ls -CF'

# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.

如果 [ -f ~/.bash_aliases ]; 然后 。~/.bash_aliases fi

# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
#if [ -f /etc/bash_completion ] && ! shopt -oq posix; then
#    . /etc/bash_completion
#fi