[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Dimitri John Ledkov
1845801 at bugs.launchpad.net
Mon Aug 17 09:22:00 UTC 2020
We could use gfxpalyload blacklist, to mark certain nvidia cards there.
And then gfxpayload will not be set to keep, and then vt.handoff will
not be appended.
See grub-gfxpayload-lists package, and files in /usr/share/grub-
gfxpayload-lists/blacklist/
My current preference would be the gdm3 fix. And migrate the rest of the
login managers to tty1 too.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 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:
Triaged
Status in gdm3 package in Ubuntu:
Confirmed
Status in gnome-session package in Ubuntu:
Confirmed
Status in grub2 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
Confirmed
Bug description:
[ Impact ]
In some platforms with specific Nvidia cards, auto-login will fail due to the old vt-handoff patch in grub2.
[ Test Case ]
1. Boot ubuntu into desktop environment.
2. Enabled auto login in System->Users
3. Reboot the system
[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 ]
Low, the patch just removes vt.handoff part in grub2 package, and I can't find any regression in several runs of stress tests.
PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-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.0000.01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0000:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019
GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 28 19:55:42 2019
DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
DistroCodename: eoan
DistroVariant: ubuntu
DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
InstallationDate: Installed on 2019-09-14 (13 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: MSI MS-7A67
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
dmi.bios.date: 01/25/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.60
dmi.board.asset.tag: Default string
dmi.board.name: H270I GAMING PRO AC (MS-7A67)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.family: Default string
dmi.product.name: MS-7A67
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: MSI
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions
More information about the foundations-bugs
mailing list