Installer disappears/crashes when OK the keyboard layout

[fossfreedom]

See installer.tar for a tarball of /var/log/installer

The installer on first boot of my ryzen laptop with UB 24.10 beta (19th Sept .3) frequently just disappears on various points of the first few screens.

It took me 4 attempts to restart the installer from the live-session desktop icon to eventually install

The installer.tar here was capture for one of this installer houdini actions when it disappears after clicking the OK button on the keyboard layout.

Note - I had no issues with virtualbox 7 with 3D host graphics chosen. This issue only occurs on my physical ryzen 4 based laptop.

[fossfreedom (fossfreedom)]

enc is /var/log/syslog

grep installer syslog shows

syslog:2024-09-19T19:51:40.520756+00:00 ubuntu-budgie systemd[2441]: Starting ubuntu-budgie-installer.service - Ubuntu Budgie Installer...
syslog:2024-09-19T19:51:56.886611+00:00 ubuntu-budgie sh[3330]: flutter: INFO ubuntu_bootstrap: Logging to /var/log/installer/ubuntu_bootstrap.log
syslog:2024-09-19T19:52:13.592145+00:00 ubuntu-budgie sh[3330]: flutter: DEBUG telemetry: Writing report to /var/log/installer/telemetry
syslog:2024-09-19T19:52:26.186954+00:00 ubuntu-budgie systemd[2441]: ubuntu-budgie-installer.service: Main process exited, code=exited, status=1/FAILURE
syslog:2024-09-19T19:53:56.409412+00:00 ubuntu-budgie systemd[2441]: ubuntu-budgie-installer.service: State 'stop-post' timed out. Terminating.
syslog:2024-09-19T19:53:56.409974+00:00 ubuntu-budgie systemd[2441]: ubuntu-budgie-installer.service: Control process exited, code=killed, status=15/TERM
syslog:2024-09-19T19:53:56.410137+00:00 ubuntu-budgie systemd[2441]: ubuntu-budgie-installer.service: Failed with result 'exit-code'.
syslog:2024-09-19T19:53:56.410869+00:00 ubuntu-budgie systemd[2441]: Failed to start ubuntu-budgie-installer.service - Ubuntu Budgie Installer.
grep: Desktop: Is a directory
grep: Documents: Is a directory
grep: Downloads: Is a directory
grep: Music: Is a directory
grep: Pictures: Is a directory
grep: Public: Is a directory
grep: Templates: Is a directory
grep: Videos: Is a directory
grep: installer.tar: binary file matches
grep: snap: Is a directory
syslog:2024-09-19T19:51:40.520756+00:00 ubuntu-budgie systemd[2441]: Starting ubuntu-budgie-installer.service - Ubuntu Budgie Installer...
syslog:2024-09-19T19:51:56.886611+00:00 ubuntu-budgie sh[3330]: flutter: INFO ubuntu_bootstrap: Logging to /var/log/installer/ubuntu_bootstrap.log
syslog:2024-09-19T19:52:13.592145+00:00 ubuntu-budgie sh[3330]: flutter: DEBUG telemetry: Writing report to /var/log/installer/telemetry
syslog:2024-09-19T19:52:26.186954+00:00 ubuntu-budgie systemd[2441]: ubuntu-budgie-installer.service: Main process exited, code=exited, status=1/FAILURE
syslog:2024-09-19T19:53:56.409412+00:00 ubuntu-budgie systemd[2441]: ubuntu-budgie-installer.service: State 'stop-post' timed out. Terminating.
syslog:2024-09-19T19:53:56.409974+00:00 ubuntu-budgie systemd[2441]: ubuntu-budgie-installer.service: Control process exited, code=killed, status=15/TERM
syslog:2024-09-19T19:53:56.410137+00:00 ubuntu-budgie systemd[2441]: ubuntu-budgie-installer.service: Failed with result 'exit-code'.
syslog:2024-09-19T19:53:56.410869+00:00 ubuntu-budgie systemd[2441]: Failed to start ubuntu-budgie-installer.service - Ubuntu Budgie Installer.
ubuntu-budgie@ubuntu-budgie:~$

[Ubuntu QA Website (ubuntuqa)]

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

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

[Sebastien Bacher (seb128)]

Unsure if that's the issue but the subiquity log has this warning

WARNING subiquity.models.locale:50 Could not localectl set-locale: CalledProcessError(1, ['localectl', 'set-locale', 'en_US.UTF-8'], '', 'Failed to issue method call: Access denied\n')

[Dan Bungert (dbungert)]

> localectl

Yes, that's only a warning. That line is from here: https://github.com/canonical/subiquity/blob/c56f96a3714e06fb481ff6df57864833fac3000d/subiquity/models/locale.py#L50 which is a non-fatal error.

I'm going to mark this invalid for Subiquity as I think there is nothing actionable on the backend, please let me know if you believe otherwise.