更新后GUI登录陷入循环

我从搜索中得知,这在过去几年中已多次出现。 但是,大多数解决方案只是为了确保正确设置.Xautority的所有权,并将777设置为/ tmp的权限。 就我而言,这些都不是问题; 我检查了。 我发现的另一个常见原因是Nvidia vs. 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”查看每个驱动程序信息如何在系统中找到正在使用的video驱动程序? 。 它有“* -display UNCLAIMED”和“configuration:latency = 0”这一行。

我还检查了旧的xorg.conf,发现它是空的。 这是为什么我试图回到Nouveau司机失败了?

步骤1 🙁启用root帐户并登录)

  • 在登录窗口中,键入ControlAltF1以进入文本tty屏幕
  • 使用您的普通用户名和密码登录
  • 输入sudo pico /etc/lightdm/lightdm.conf来编辑这个文件

确保文件看起来像这样……不要删除你在那里看到的任何东西,只需添加缺失的行。 使用箭头键在文件中移动,使用Controlo保存,使用Controlx退出编辑器。

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

第2步:(修复root .profile)

  • 使用您的用户名/密码登录文本tty
  • 输入sudo pico /root/.profile
  • 改变mesg n || true 对于tty -s && mesg n || true 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驱动程序解决了这个问题。