因此，我目前仍在使用 14.04，并且我知道本月底将终止支持，除非您延长了安全维护（我没有）。
但是，我有点困惑到底会发生什么。在网上搜索，我看到了两个术语：支持终止和生命终止。据我所知，两者都与 Canonical 在提及版本生命周期时的含义不同。我遇到的麻烦是告诉两者之间是否有区别。我阅读的一些页面可以互换处理它们，而其他页面则没有。我读过的一些帖子使用寿命终止来指代存储库何时移动/存档；从而防止诸如自动更新之类的事情起作用。
不管哪个是哪个，Ubuntu 存储库什么时候存档？在信息页面上似乎没有提到这一点，我发现的在线帖子只是提到它发生了，而不是什么时候发生。
当两个远程服务器不使用相同的协议时，是否可以直接在两个远程服务器之间传输文件？我在 serverA 上有很多文件（至少现在必须使用 SFTP 访问），并希望将它们复制到 serverB（必须使用 FTP 访问）。不幸的是，我不能在服务器本身上做任何事情，因为我是两者的外部客户端。
我从搜索中知道，这在过去几年中已经多次出现。然而，大多数解决方案只是确保正确设置 .Xautority 的所有权，并将 777 设置为 /tmp 的权限。就我而言，这些都不是问题。我检查了。我发现的另一个常见原因是 Nvidia 与 Nouveau 图形驱动程序的对比。但是，自从我上次更改图形驱动程序以来，我已经重新启动并使用了几次计算机并且没有任何问题。
这些问题是在我允许 AutoUpdate 程序安装一些更新后开始的。值得注意的是，这些更新有点可疑。它昨天想安装它们，我最初说不。然后我手动运行更新程序，它说没有更新。今天当它再次问我时，我说是的，它做了它的事。然后它要求我重新启动我所做的计算机。那是麻烦开始的时候。下面是各种 .xsession-errors 文件的内容。
用户 1 次尝试 1
Script for ibus started at run_im.
Script for auto started at run_im.
Script for default started at run_im.
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: gnome-session (Unity) main process (2563) terminated with status 1
init: unity-settings-daemon main process (2537) killed by TERM signal
init: logrotate main process (2458) killed by TERM signal
init: update-notifier-crash (/var/crash/_usr_bin_nautilus.1000.crash) main process (2496) killed by TERM signal
init: update-notifier-release main process (2502) killed by TERM signal
init: xsession-init main process (2531) killed by TERM signal
init: hud main process (2550) killed by TERM signal
init: unity-panel-service main process (2576) killed by TERM signal
init: Disconnected from notified D-Bus bus
init: window-stack-bridge main process (2488) killed by KILL signal
用户 1 尝试 2
Script for ibus started at run_im.
Script for auto started at run_im.
Script for default started at run_im.
init: gnome-session (Unity) main process (2010) terminated with status 1
init: unity-settings-daemon main process (2002) killed by TERM signal
init: Disconnected from notified D-Bus bus
init: logrotate main process (1928) killed by TERM signal
init: window-stack-bridge main process (1959) killed by TERM signal
init: update-notifier-release main process (1978) killed by TERM signal
init: hud main process (2006) killed by TERM signal
init: indicator-bluetooth main process (2088) killed by TERM signal
init: indicator-power main process (2094) killed by TERM signal
init: indicator-datetime main process (2095) killed by TERM signal
init: indicator-sound main process (2098) killed by TERM signal
init: indicator-printers main process (2103) killed by TERM signal
init: indicator-session main process (2108) killed by TERM signal
init: indicator-application main process (2148) killed by TERM signal
用户 2 尝试 1
Script for ibus started at run_im.
Script for auto started at run_im.
Script for default started at run_im.
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: gnome-session (Unity) main process (2642) terminated with status 1
init: unity-settings-daemon main process (2634) killed by TERM signal
init: logrotate main process (2427) killed by TERM signal
init: update-notifier-release main process (2468) killed by TERM signal
init: upstart-dbus-session-bridge main process (2472) terminated with status 1
init: xsession-init main process (2631) killed by TERM signal
init: hud main process (2638) killed by TERM signal
init: unity-panel-service main process (2648) killed by TERM signal
init: at-spi2-registryd main process (2687) terminated with status 1
init: Disconnected from notified D-Bus bus
编辑：
我发现的另一个常见解决方案是通过重命名现有的 .Xauthority 来强制创建新的 .Xauthority。我试过这个，它也没有用。
用户 1 尝试 3
Script for ibus started at run_im.
Script for auto started at run_im.
Script for default started at run_im.
init: gnome-session (Unity) main process (2022) terminated with status 1
init: Disconnected from notified D-Bus bus
init: logrotate main process (1939) killed by TERM signal
init: window-stack-bridge main process (1970) killed by TERM signal
init: update-notifier-release main process (1990) killed by TERM signal
init: hud main process (2018) killed by TERM signal
init: indicator-bluetooth main process (2099) killed by TERM signal
init: indicator-power main process (2101) killed by TERM signal
init: indicator-datetime main process (2105) killed by TERM signal
init: indicator-sound main process (2110) killed by TERM signal
init: indicator-printers main process (2114) killed by TERM signal
init: indicator-session main process (2119) killed by TERM signal
init: indicator-application main process (2133) killed by TERM signal
编辑：
万一这些信息有帮助，当我运行时：
sudo apt-get -f install
它所做的只是列出我可以使用“自动删除”删除的包；除了其中一个之外，所有这些都用于以前的内核版本。
编辑：
以 root 身份登录不起作用，但这次我确实收到了一条错误消息。
我还尝试重新运行 Nvidia 的配置脚本，但这也无济于事。
当我在 TTY 中时，我尝试使用“lshw”查看驱动程序信息如何查找我的系统上正在使用的视频驱动程序？. 它有“*-display UNCLAIMED”和“configuration：latency=0”这行。
我还检查了旧的 xorg.conf，发现它完全是空的。这就是为什么我尝试回到 Nouveau 驱动程序失败的原因吗？