Issue/Bug Description:
When attempting to enter password to unencrypt drive during boot, the GUI crashes to terminal and brings erroneous characters. This makes it impossible to enter just the password, as you have to start typing, then delete, then start typing again.
The GUI does come back afterwords.
Steps to reproduce (if you know):
Reboot the computer, then enter encryption password when prompted.
Expected behavior:
The GUI shouldn't crash and, even if it does, you should be able to enter the password without any backspaces, as the lack of a GUI isn't really an issue to the boot process.
Other Notes:
This happened before, then stopped happening for a while, and just today started again.
jacobgkau
commented
1 year ago
Distribution (run
cat /etc/os-release): VERSION="22.04 LTS" ID=pop ID_LIKE="ubuntu debian" PRETTY_NAME="Pop!_OS 22.04 LTS" VERSION_ID="22.04" HOME_URL="https://pop.system76.com" SUPPORT_URL="https://support.system76.com" BUG_REPORT_URL="https://github.com/pop-os/pop/issues" PRIVACY_POLICY_URL="https://system76.com/privacy" VERSION_CODENAME=jammy UBUNTU_CODENAME=jammy LOGO=distributor-logo-pop-osRelated Application and/or Package Version (run
apt policy $PACKAGE NAME): cryptsetup: Installed: 2:2.4.3-1ubuntu1.1 Candidate: 2:2.4.3-1ubuntu1.1 Version table: *** 2:2.4.3-1ubuntu1.1 500 500 http://apt.pop-os.org/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 2:2.4.3-1ubuntu1 500 500 http://apt.pop-os.org/ubuntu jammy/main amd64 PackagesIssue/Bug Description: When attempting to enter password to unencrypt drive during boot, the GUI crashes to terminal and brings erroneous characters. This makes it impossible to enter just the password, as you have to start typing, then delete, then start typing again. The GUI does come back afterwords.
Steps to reproduce (if you know): Reboot the computer, then enter encryption password when prompted.
Expected behavior: The GUI shouldn't crash and, even if it does, you should be able to enter the password without any backspaces, as the lack of a GUI isn't really an issue to the boot process.
Other Notes: This happened before, then stopped happening for a while, and just today started again.