nvidia-settings not installed after off-line install of kinetic

Bug #1990535 reported by Brian Murray
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
livecd-rootfs (Ubuntu)
Triaged
Undecided
Unassigned
Jammy
Triaged
Undecided
Unassigned
ubiquity (Ubuntu)
Confirmed
High
Unassigned
Jammy
Confirmed
High
Unassigned

Bug Description

I followed the UEFI SecureBoot nVidia off-line install test case and discovered that after rebooting nvidia-settings was not available. However, when doing an on-line install nvidia-settings is available.

ProblemType: BugDistroRelease: Ubuntu 22.10
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 21 16:59:46 2022
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash ---
InstallationDate: Installed on 2022-09-21 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220920)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bashSourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Brian Murray (brian-murray) wrote :
tags: added: foundations-triage-discuss
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubiquity (Ubuntu):
status: New → Confirmed
Revision history for this message
Brian Murray (brian-murray) wrote :

The duplicate bug indicates that this also happens with Jammy.

tags: added: iso-testing
Changed in ubiquity (Ubuntu):
importance: Undecided → High
Changed in ubiquity (Ubuntu Jammy):
importance: Undecided → High
status: New → Confirmed
tags: added: foundations-todo
removed: foundations-triage-discuss
description: updated
Changed in ubiquity (Ubuntu):
milestone: none → ubuntu-22.10
Revision history for this message
Brian Murray (brian-murray) wrote :

nvidia-driver-470 ends up being installed and it recommends on nvidia-settings so it seems to me not having the recommends installed is a fail.

Revision history for this message
Brian Murray (brian-murray) wrote :

Julian - you had some good insight into what is going on here. Could you add that to this bug?

Revision history for this message
Julian Andres Klode (juliank) wrote :

There is a recommends from the driver to the nvidia-settings, but nvidia-setting has a dependency which is not in the pool because the dependency was in the ubiquity layer and removed after the install, and we wrongly calculate the pool content from that layer rather than the installed layer.

Revision history for this message
Julian Andres Klode (juliank) wrote :

So this might actually need to be fixed in livecd-rootfs by adding the dependency to the pool again.

Steve Langasek (vorlon)
Changed in livecd-rootfs (Ubuntu):
status: New → Triaged
Changed in livecd-rootfs (Ubuntu Jammy):
status: New → Triaged
Revision history for this message
Brian Murray (brian-murray) wrote :

I ran into this again today when testing an installation of the Jammy point release with image serial 20230217.1.

Changed in ubiquity (Ubuntu):
milestone: ubuntu-22.10 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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