I'm slightly confused. Can you abbreviate the problem description? Sounds like maybe a kernel issue too, rather than gdm3.
** Package changed: gdm3 (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1851146 Title: No Virtual Terminals Status in linux package in Ubuntu: Incomplete Bug description: I'll start this bug report with my first disclaimer: I'm filing this report from a fixed system. The original system that I'm going to reference has been installed over with the current system I'm filing this report from. The first install was UEFI, minimal install, not connected to the internet during installation. Now, I'll continue with my story. So, when doing the first install, I realized I had screwed up my username when doing the install. But you can't do a lot of the 'usermod' commands from the user you're logged in as. Since I was having to log in as a regular user, and then run 'sudo usermod', it was stating that the user I was trying to modify was currently logged in. So I logged out, and then attempted to switch to a tty, as I didn't need a graphical login for root. When trying to access virtual TTYs from Ctrl+Alt+F{3,4,5,6}, there were no terminals to access. I did some googling and didn't find anything directly related. Most were related to either accessing virtual terminals, or getting back to a graphical desktop if you mistakenly get to a vtty. So I took to IRC (#ubuntu on freenode). After someone did a '!tty' to really rub salt in the wound, someone recommended that I try uncommenting 'GRUB_TERMINAL=console' and regenerating grub.cfg, I took them up on the offer. So I open /etc/default/grub, and scroll down to that line. I immediately see it says 'grub-pc only'. I knew my install was UEFI, but since it was a fresh install I ignored the warning and did it anyway. Uncommented GRUB_TERMINAL=console did a 'sudo update-grub'. I went down for a reboot...and my system did not boot again. I considered chrooting and fixing it, but I thought it may be less annoying to just re-install. However, this time I elected to do a full install while connected to wifi. After booting up the first time, I try switch over to a TTY and *POOF!*, I have ttys now. So I'm not sure if my install the first time was simply busted, or the difference of doing a minimal install vs a full install is what caused my vtty issue. But anyway. Thought I'd open a bug. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 3 11:06:00 2019 InstallationDate: Installed on 2019-11-03 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
