Chris,
With the following packages installed and the workaround removed the
issue no longer occurs for me when enabling Automatic Login via
Settings. I have tested rebooting and starting from off several times
and it worked as expected each time. Previously the issue occurred on
every boot.
gdm3 (3.36.3-0ubuntu0.20.04.1)
libgdm1 (3.36.3-0ubuntu0.20.04.1)
gir1.2-gdm-1.0:amd64 (3.36.3-0ubuntu0.20.04.1)
nvidia-driver-450 (450.66-0ubuntu0.20.04.1)
/etc/default/grub
```
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
```
Of note, when the desktop loaded I was greeted with the Ubuntu new user
"Connect Your Online Accounts" setup screen and what appeared to be a
fresh users settings. If this happens to anyone here there's a helpful
README.txt in ~/ reminding you that you encrypted your home directory,
and to run ecryptfs-mount-private to gain access. Oh yeah...
You can also expect to be prompted to unlock your login keyring at some
random moment a few minutes after the desktop loads.
Anyway, wonderful work, and thanks to everyone who helped fix this, at
least for me. :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1845801
Title:
[nvidia] Automatic login fails and then all subsequent logins fail.
Killing gnome-session-binary fixes it, or just not using automatic
login.
Status in OEM Priority Project:
In Progress
Status in gdm3 package in Ubuntu:
Fix Released
Status in gnome-session package in Ubuntu:
Invalid
Status in grub2 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-390 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-430 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-440 package in Ubuntu:
Invalid
Status in gdm3 source package in Focal:
Fix Committed
Status in gnome-session source package in Focal:
Invalid
Status in grub2 source package in Focal:
Invalid
Status in nvidia-graphics-drivers-390 source package in Focal:
Invalid
Status in nvidia-graphics-drivers-430 source package in Focal:
Invalid
Status in nvidia-graphics-drivers-435 source package in Focal:
Invalid
Status in nvidia-graphics-drivers-440 source package in Focal:
Invalid
Bug description:
[ Impact ]
In some platforms with specific Nvidia cards (with nvidia-driver-440), enable
auto-login (either during installation or after installation) will fail (either
stuck in gdm login screen and not able to login even typing correct password).
[ Test Case ]
Here are two scenario of auto login with groovy (20.10) daily build[1]:
1) Checked "Install third-party software" (e.g. nvidia-driver) with
enabling "Login automatically" during installation.
2) Install groovy daily build with default options, after installation
completed:
2.1) Install nvidia-driver-440 (450.66-0ubuntu1) from ubuntu-archive.
2.2) Enable "Login automatically" from system settings.
Then reboot.
[Expected result]
System will boot into desktop environment without the login page.
[Actual result]
System boots to login page, and can't login to desktop environment with the
correct password.
[ Regression potential ]
Medium, the patch comes from upstream[2] to use /dev/tty1 (instead of tty0)
to prevent the auto-login user gets tty1. I did verified gdm3 from my PPA[3]
and it works good. It passed the 30 times reboot stress test by using
stress/reboot_30 from checkbox.
[1] sha256sum:
bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822
[2] https://gitlab.gnome.org/GNOME/gdm/-/commit/f843233ad4
https://gitlab.gnome.org/GNOME/gdm/-/commit/690b3c01
[3] https://launchpad.net/~os369510/+archive/ubuntu/gdm3-1845801
---
I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
login screen (which I shouldn't; I have auto login enabled), and
logging in just takes me back to the same user selection screen even
though the password is correct.
If I switch to a TTY and run `sudo pkill gnome-session-binary`,
logging in through GDM starts working again.
I should add that the do-release-upgrade was rocky; I did it in a
terminal from within gnome, went away for a while, and when I
returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
dpkg --configure -a` and complete the upgrade, but I don't know if
something's still messed up due to that.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default
