☰

更新后 GUI 登录陷入循环

tag-icon • tag-icon 14.04 updates login-screen
更新后 GUI 登录陷入循环

我从搜索中得知，这种情况在过去几年中出现过多次。然而，大多数解决方案只是确保正确设置 .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

它所做的只是列出我可以使用“autoremove”删除的软件包；除了一个之外，其他所有软件包都是针对以前的内核版本的。

编辑：

以 root 身份登录不起作用，但这次我确实收到了一条错误消息。 尝试以 root 身份登录时出现错误消息

我也尝试重新运行 Nvidia 的配置脚本，但这也无济于事。

当我在 TTY 中时，我尝试使用“lshw”查看每个驱动程序的信息如何找到我的系统正在使用的视频驱动程序？。它有“*-display UNCLAIMED”和“configuration:latency=0”这两行。

我还检查了旧的 xorg.conf，发现它完全是空的。这就是为什么我尝试重新使用 Nouveau 驱动程序失败的原因吗？

答案1

步骤1：（启用root账户并登录）

  • 在登录窗口中，输入Control- Alt-F1进入文本 tty 屏幕
  • 使用您的正常用户名和密码登录
  • 输入sudo pico /etc/lightdm/lightdm.conf#来编辑此文件

确保文件如下所示...不要删除您在此处看到的任何内容，只需添加缺失的行。使用箭头键在文件中移动，使用Control-o保存，使用Control-x退出编辑器。

[LightDM]
[SeatDefaults]
greeter-show-manual-login=true
[XDMCPServer]
[VNCServer]
  • 输入sudo passwd root#设置root密码
  • 输入您的管理员密码
  • 输入两次新的 root 密码
  • 输入exit#返回图形屏幕
  • 重启电脑
  • 在登录提示符下，按下Down Arrow键，直到登录提示符允许您输入用户名
  • 输入root新的 root 密码
  • 看看是否可以成功登录root

第2步：（修复根.profile）

  • 使用你的用户名/密码登录文本 tty
  • 类型sudo pico /root/.profile
  • 改成mesg n || true​tty -s && mesg n || true
  • 保存文件并退出编辑器
  • 键入exit以返回图形 tty
  • 以 root 身份登录并确认没有 .profile 错误

步骤#3：

由于我们确定您甚至无法以 root 身份登录，因此我们确认存在系统问题，并且与权限无关。

我们将尝试几次重新安装，如果不奏效，您将需要重新安装操作系统（取消选中“格式”框，以便保持您现有的 /home 目录完好无损）。

你需要确保自己已经备份好重要数据，以防万一。您可以通过启动 Ubuntu Live DVD/USB 并将文件复制到外部硬盘或 USB 闪存驱动器来进行手动备份。

  • 使用你的用户名/密码登录文本 tty

输入以下内容...

sudo apt-get install --reinstall lightdm gnome-session
sudo dpkg-reconfigure lightdm # and choose lightdm
reboot

尝试登录。如果不行，请重新安装操作系统。

更新＃1：

重新安装 Nvidia 驱动程序解决了该问题。

相关内容