[qxl] installing with lvm and encryption requires arrow key spam after reboot to get to encryption passphrase prompt

Bug #2033533 reported by Tim Andersson
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Release Notes for Ubuntu
New
Undecided
Unassigned
plymouth (Ubuntu)
New
Undecided
Unassigned

Bug Description

This also happens with the canary image and is happening with the Mantic daily image.

When installing with LVM and encryption, after the "remove installation medium and press enter to reboot", the user is greeted with a permanent black screen. After pressing arrow keys, the gui prompt is then shown to prompt the user to put in the encryption passphrase.

It is also somehow possible to not get the black screen by changing the grub prior to installing by removing splash from the grub options. The user is then greeted with a text-only passphrase prompt after rebooting.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: subiquity (unknown)
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 30 16:39:39 2023
InstallationDate: Installed on 2023-08-30 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
SourcePackage: subiquity
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-08-30 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
 /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
     |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: ubiquity
PackageArchitecture: amd64
ProcCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcEnviron:
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
ProcFB: 0 qxldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Tags: mantic third-party-packages wayland-session
TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Uname: Linux 6.3.0-7-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages. If that does not work, then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
_MarkForUpload: True
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.16.0-debian-1.16.0-5
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-7.2
dmi.modalias: dmi:bvnSeaBIOS:bvr1.16.0-debian-1.16.0-5:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.2:cvnQEMU:ct1:cvrpc-q35-7.2:sku:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-7.2
dmi.sys.vendor: QEMU

Revision history for this message
Tim Andersson (andersson123) wrote :
Revision history for this message
Tim Andersson (andersson123) wrote : CurrentDmesg.txt

apport information

tags: added: apport-collected third-party-packages
description: updated
Revision history for this message
Tim Andersson (andersson123) wrote : Dependencies.txt

apport information

Revision history for this message
Tim Andersson (andersson123) wrote : EtcDefaultGrub.txt

apport information

Revision history for this message
Tim Andersson (andersson123) wrote : Lspci.txt

apport information

Revision history for this message
Tim Andersson (andersson123) wrote : Lspci-vt.txt

apport information

Revision history for this message
Tim Andersson (andersson123) wrote : Lsusb-v.txt

apport information

Revision history for this message
Tim Andersson (andersson123) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Tim Andersson (andersson123) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Tim Andersson (andersson123) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Tim Andersson (andersson123) wrote : ProcModules.txt

apport information

Revision history for this message
Tim Andersson (andersson123) wrote : UdevDb.txt

apport information

Revision history for this message
Tim Andersson (andersson123) wrote : acpidump.txt

apport information

Revision history for this message
Tim Andersson (andersson123) wrote : Re: installing with lvm and encryption requires arrow key spam after reboot to get to encryption passphrase prompt

I've added extra information regarding what happens on the ubiquity installer. However one thing to note is after spamming up/down it doesn't go to a gui prompt, but rather to a terminal prompt for the encryption passphrase.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Daniel, any idea about that? The description suggest it could have to do with plymouth but the package didn't change since lunar so maybe due to interactions with other components

Revision history for this message
Tim Andersson (andersson123) wrote :

I'm also really interested in how changing the grub settings when booting into the ISO pre-install is changing behaviour after rebooting post-install

Revision history for this message
Daniel van Vugt (vanvugt) wrote (last edit ):

Using the same 20230829 image I can't reproduce the bug on two ThinkPads that I've tried. After a fresh install the encryption passphrase prompt is displayed and works correctly in both cases.

However I am reminded of two known issues:
 * Bug 2012698 which I assumed was caused by OLED panels because it didn't happen on any other machine I knew of.
 * Historically some systems (sometimes) boot to the wrong VT (you just see a black screen) so require pressing Alt+Fn.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I see your VM is using the qxl kernel driver for graphics. Can you try assigning a different graphics adapter type to it? This might be a kernel regression in qxl.

Please also collect a Plymouth debug log:
https://gitlab.freedesktop.org/plymouth/plymouth/-/blob/main/docs/development.txt#L78

Revision history for this message
Tim Andersson (andersson123) wrote :

Hey, I just tested this using a VGA graphics driver instead of a qxl driver, and it worked, so it looks like it's a kernel regression in qxl as you stated. Is the Plymouth log still necessary given this?

Revision history for this message
Daniel van Vugt (vanvugt) wrote (last edit ):

Yes a Plymouth log would still help.

I'm wondering if this is a regression at all, or just the first time anyone has tried testing disk encryption in a VM without KMS/DRM graphics support. It could have been broken forever and Red Hat (Plymouth maintainers) wouldn't notice because they use SimpleDRM in their kernels (I think) to always avoid situations like this. Canonical has a plan to do the same (bug 1965303).

Revision history for this message
Tim Andersson (andersson123) wrote :

it's randomly been working for me today. I think I maybe clicked the black screen after reboot.

Revision history for this message
Tim Andersson (andersson123) wrote :
Revision history for this message
Tim Andersson (andersson123) wrote :

I added a plymouth debug log. It's perhaps working now because I added plymouth debugging? very confusing

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Sorry it looks like I was completely wrong. qxl *does* support the preferred "modern" DRM/KMS graphics interface as shown in your log files. This seems to be some kind of qxl kernel bug or maybe Plymouth race condition.

I can only suggest collecting more Plymouth debug logs until the bug happens again.

affects: subiquity → ubuntu
no longer affects: ubuntu
affects: ubiquity (Ubuntu) → linux (Ubuntu)
tags: added: qxl
summary: - installing with lvm and encryption requires arrow key spam after reboot
- to get to encryption passphrase prompt
+ [qxl] installing with lvm and encryption requires arrow key spam after
+ reboot to get to encryption passphrase prompt
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Tim Andersson (andersson123) wrote :

So I've just double checked, and enabling plymouth debug in the grub prior to installation means you're not greeted with a black screen, and don't need to press an arrow key. Could that be a helpful indicator at all? I can't collect logs because when I do ... the issue is gone

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

> I can't collect logs because when I do ... the issue is gone

This supports the theory that it's a Plymouth race condition, fixed by booting more slowly. Plymouth might be wanting to display the password prompt before graphics support has "booted" in the kernel.

Actually now that I've said that and we know it's DRM it reminds me of bug 1869655 which might be the same issue. And we might get a permanent workaround by switching to SimpleDRM in the kernel (bug 1965303).

Revision history for this message
Tim Andersson (andersson123) wrote :

Great stuff :) Let me know if you need anything else o7

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Removed the kernel task because there's no evidence yet the qxl driver is doing anything wrong.

I might attempt a Plymouth fix for bug 1869655 and this before 23.10 but that wouldn't be without risks.

no longer affects: linux (Ubuntu)
tags: added: cuqa-manual-testing
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2033533

tags: added: iso-testing
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.