dist-upgrade in noble fails when using TPM FDE
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
foo2zjs (Ubuntu) |
Fix Released
|
Undecided
|
Till Kamppeter |
Bug Description
When doing a dist-upgrade of noble during the devel cycle I'm hitting this upgrade bug in the package. /lib/firmware is read-only because it's provided by the pc-kernel snap.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
libpoppler134 poppler-utils
The following packages will be upgraded:
printer-
1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
416 not fully installed or removed.
Need to get 0 B/142 kB of archives.
After this operation, 12.3 kB of additional disk space will be used.
Do you want to continue? [Y/n]
(Reading database ... 140132 files and directories currently installed.)
Preparing to unpack .../printer-
Unpacking printer-
dpkg: error processing archive /var/cache/
:
error creating directory './lib/
dpkg: error while cleaning up:
unable to remove newly-extracted version of '/lib/firmware/hp': Read-only file system
Errors were encountered while processing:
/var/cache/
E: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: printer-
ProcVersionSign
Uname: Linux 6.8.0-11-generic x86_64
NonfreeKernelMo
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckR
Date: Wed Apr 10 09:39:01 2024
InstallationDate: Installed on 2024-03-08 (33 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240306)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-
XDG_RUNTIME_
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: foo2zjs
UpgradeStatus: No upgrade log present (probably fresh install)
This means that /lib/firmware is repurposed, at least on some systems.
So no problem for me to move the firmware directory to /usr/lib or /usr/share.
Questions is now, do we have a kernel Snap on standard *.deb-based Ubuntu? If we had kernel Snaps only on Ubuntu Core (Desktop) there the printer- driver- foo2zjs package does not make sense. We work with the CUPS Snap on such systems and printer drivers work only in the new Printer Application format. For the printers supported by foo2zjs one would use the Ghostscript Printer Application.