| 2025-07-29 14:05:21 |
Juerg Haefliger |
bug |
|
|
added bug |
| 2025-07-29 15:21:14 |
Juerg Haefliger |
summary |
Installation fails in a container |
Installation fails in a chroot |
|
| 2025-07-29 15:21:28 |
Juerg Haefliger |
description |
postinst calls update-grub which fails if the package is installed in a container/chroot. This breaks Ubuntu Studio livefs builds:
https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/noble/ubuntustudio
From a build log:
Processing triggers for dbus (1.14.10-4ubuntu4.1) ...
Processing triggers for libgtk-3-0t64:amd64 (3.24.41-4ubuntu1.3) ...
Processing triggers for shared-mime-info (2.4-4) ...
Processing triggers for libgtk2.0-0t64:amd64 (2.24.33-4ubuntu1.1) ...
Processing triggers for desktop-file-utils (0.27-2build1) ...
Processing triggers for initramfs-tools (0.142ubuntu25.5) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for libc-bin (2.39-0ubuntu8.5) ...
Processing triggers for man-db (2.12.0-4build2) ...
Processing triggers for dictionaries-common (1.29.7) ...
Processing triggers for linux-image-6.14.0-24-generic (6.14.0-24.24~24.04.3) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.14.0-24-generic
cryptsetup: ERROR: Couldn't resolve device overlay
cryptsetup: WARNING: Couldn't determine root device
cryptsetup: ERROR: Couldn't resolve device /dev/vdb
Errors were encountered while processing:
lowlatency-kernel |
postinst calls update-grub which fails if the package is installed in a chroot. This breaks Ubuntu Studio livefs builds:
https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/noble/ubuntustudio
From a build log:
Processing triggers for dbus (1.14.10-4ubuntu4.1) ...
Processing triggers for libgtk-3-0t64:amd64 (3.24.41-4ubuntu1.3) ...
Processing triggers for shared-mime-info (2.4-4) ...
Processing triggers for libgtk2.0-0t64:amd64 (2.24.33-4ubuntu1.1) ...
Processing triggers for desktop-file-utils (0.27-2build1) ...
Processing triggers for initramfs-tools (0.142ubuntu25.5) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for libc-bin (2.39-0ubuntu8.5) ...
Processing triggers for man-db (2.12.0-4build2) ...
Processing triggers for dictionaries-common (1.29.7) ...
Processing triggers for linux-image-6.14.0-24-generic (6.14.0-24.24~24.04.3) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.14.0-24-generic
cryptsetup: ERROR: Couldn't resolve device overlay
cryptsetup: WARNING: Couldn't determine root device
cryptsetup: ERROR: Couldn't resolve device /dev/vdb
Errors were encountered while processing:
lowlatency-kernel |
|
| 2025-07-29 15:46:23 |
Juerg Haefliger |
nominated for series |
|
Ubuntu Noble |
|
| 2025-07-29 15:46:23 |
Juerg Haefliger |
bug task added |
|
lowlatency-kernel (Ubuntu Noble) |
|
| 2025-07-29 15:46:23 |
Juerg Haefliger |
nominated for series |
|
Ubuntu Plucky |
|
| 2025-07-29 15:46:23 |
Juerg Haefliger |
bug task added |
|
lowlatency-kernel (Ubuntu Plucky) |
|
| 2025-07-29 15:57:50 |
Juerg Haefliger |
nominated for series |
|
Ubuntu Questing |
|
| 2025-07-29 15:57:50 |
Juerg Haefliger |
bug task added |
|
lowlatency-kernel (Ubuntu Questing) |
|
| 2025-07-29 17:40:25 |
Juerg Haefliger |
lowlatency-kernel (Ubuntu Questing): assignee |
|
Juerg Haefliger (juergh) |
|
| 2025-07-29 17:40:27 |
Juerg Haefliger |
lowlatency-kernel (Ubuntu Plucky): assignee |
|
Juerg Haefliger (juergh) |
|
| 2025-07-29 17:40:29 |
Juerg Haefliger |
lowlatency-kernel (Ubuntu Noble): assignee |
|
Juerg Haefliger (juergh) |
|
| 2025-07-29 20:42:49 |
Paride Legovini |
lowlatency-kernel (Ubuntu Noble): milestone |
|
ubuntu-24.04.3 |
|
| 2025-07-30 15:59:35 |
Juerg Haefliger |
summary |
Installation fails in a chroot |
Ubuntu Studio CD image build fails |
|
| 2025-07-30 16:00:09 |
Juerg Haefliger |
summary |
Ubuntu Studio CD image build fails |
Ubuntu Studio CD image build failure |
|
| 2025-07-30 16:02:54 |
Juerg Haefliger |
description |
postinst calls update-grub which fails if the package is installed in a chroot. This breaks Ubuntu Studio livefs builds:
https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/noble/ubuntustudio
From a build log:
Processing triggers for dbus (1.14.10-4ubuntu4.1) ...
Processing triggers for libgtk-3-0t64:amd64 (3.24.41-4ubuntu1.3) ...
Processing triggers for shared-mime-info (2.4-4) ...
Processing triggers for libgtk2.0-0t64:amd64 (2.24.33-4ubuntu1.1) ...
Processing triggers for desktop-file-utils (0.27-2build1) ...
Processing triggers for initramfs-tools (0.142ubuntu25.5) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for libc-bin (2.39-0ubuntu8.5) ...
Processing triggers for man-db (2.12.0-4build2) ...
Processing triggers for dictionaries-common (1.29.7) ...
Processing triggers for linux-image-6.14.0-24-generic (6.14.0-24.24~24.04.3) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.14.0-24-generic
cryptsetup: ERROR: Couldn't resolve device overlay
cryptsetup: WARNING: Couldn't determine root device
cryptsetup: ERROR: Couldn't resolve device /dev/vdb
Errors were encountered while processing:
lowlatency-kernel |
Ubuntu Studio uses the lowlatency kernel. With 6.14, the lowlatency kernel is just the generic kernel with some bootargs to make it lowlatency. This breaks the Ubuntu Studio livefs and CD image builds.
Problem 1)
postinst calls update-grub which fails if the package is installed in a chroot. This breaks Ubuntu Studio livefs builds:
https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/noble/ubuntustudio
From a build log:
Processing triggers for dbus (1.14.10-4ubuntu4.1) ...
Processing triggers for libgtk-3-0t64:amd64 (3.24.41-4ubuntu1.3) ...
Processing triggers for shared-mime-info (2.4-4) ...
Processing triggers for libgtk2.0-0t64:amd64 (2.24.33-4ubuntu1.1) ...
Processing triggers for desktop-file-utils (0.27-2build1) ...
Processing triggers for initramfs-tools (0.142ubuntu25.5) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for libc-bin (2.39-0ubuntu8.5) ...
Processing triggers for man-db (2.12.0-4build2) ...
Processing triggers for dictionaries-common (1.29.7) ...
Processing triggers for linux-image-6.14.0-24-generic (6.14.0-24.24~24.04.3) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.14.0-24-generic
cryptsetup: ERROR: Couldn't resolve device overlay
cryptsetup: WARNING: Couldn't determine root device
cryptsetup: ERROR: Couldn't resolve device /dev/vdb
Errors were encountered while processing:
lowlatency-kernel |
|
| 2025-07-30 16:04:17 |
Juerg Haefliger |
description |
Ubuntu Studio uses the lowlatency kernel. With 6.14, the lowlatency kernel is just the generic kernel with some bootargs to make it lowlatency. This breaks the Ubuntu Studio livefs and CD image builds.
Problem 1)
postinst calls update-grub which fails if the package is installed in a chroot. This breaks Ubuntu Studio livefs builds:
https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/noble/ubuntustudio
From a build log:
Processing triggers for dbus (1.14.10-4ubuntu4.1) ...
Processing triggers for libgtk-3-0t64:amd64 (3.24.41-4ubuntu1.3) ...
Processing triggers for shared-mime-info (2.4-4) ...
Processing triggers for libgtk2.0-0t64:amd64 (2.24.33-4ubuntu1.1) ...
Processing triggers for desktop-file-utils (0.27-2build1) ...
Processing triggers for initramfs-tools (0.142ubuntu25.5) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for libc-bin (2.39-0ubuntu8.5) ...
Processing triggers for man-db (2.12.0-4build2) ...
Processing triggers for dictionaries-common (1.29.7) ...
Processing triggers for linux-image-6.14.0-24-generic (6.14.0-24.24~24.04.3) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.14.0-24-generic
cryptsetup: ERROR: Couldn't resolve device overlay
cryptsetup: WARNING: Couldn't determine root device
cryptsetup: ERROR: Couldn't resolve device /dev/vdb
Errors were encountered while processing:
lowlatency-kernel |
Ubuntu Studio uses the lowlatency kernel. With 6.14, the lowlatency kernel is just the generic kernel with some bootargs to make it lowlatency. This breaks the Ubuntu Studio livefs and CD image builds.
https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/noble/ubuntustudio
Problem 1)
The postinst hook of the lowlatency-kernel package calls update-grub unconditionally which fails if the package is installed in a chroot.
From a livefs build log:
Processing triggers for dbus (1.14.10-4ubuntu4.1) ...
Processing triggers for libgtk-3-0t64:amd64 (3.24.41-4ubuntu1.3) ...
Processing triggers for shared-mime-info (2.4-4) ...
Processing triggers for libgtk2.0-0t64:amd64 (2.24.33-4ubuntu1.1) ...
Processing triggers for desktop-file-utils (0.27-2build1) ...
Processing triggers for initramfs-tools (0.142ubuntu25.5) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for libc-bin (2.39-0ubuntu8.5) ...
Processing triggers for man-db (2.12.0-4build2) ...
Processing triggers for dictionaries-common (1.29.7) ...
Processing triggers for linux-image-6.14.0-24-generic (6.14.0-24.24~24.04.3) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.14.0-24-generic
cryptsetup: ERROR: Couldn't resolve device overlay
cryptsetup: WARNING: Couldn't determine root device
cryptsetup: ERROR: Couldn't resolve device /dev/vdb
Errors were encountered while processing:
lowlatency-kernel |
|
| 2025-07-30 18:48:31 |
Juerg Haefliger |
description |
Ubuntu Studio uses the lowlatency kernel. With 6.14, the lowlatency kernel is just the generic kernel with some bootargs to make it lowlatency. This breaks the Ubuntu Studio livefs and CD image builds.
https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/noble/ubuntustudio
Problem 1)
The postinst hook of the lowlatency-kernel package calls update-grub unconditionally which fails if the package is installed in a chroot.
From a livefs build log:
Processing triggers for dbus (1.14.10-4ubuntu4.1) ...
Processing triggers for libgtk-3-0t64:amd64 (3.24.41-4ubuntu1.3) ...
Processing triggers for shared-mime-info (2.4-4) ...
Processing triggers for libgtk2.0-0t64:amd64 (2.24.33-4ubuntu1.1) ...
Processing triggers for desktop-file-utils (0.27-2build1) ...
Processing triggers for initramfs-tools (0.142ubuntu25.5) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for libc-bin (2.39-0ubuntu8.5) ...
Processing triggers for man-db (2.12.0-4build2) ...
Processing triggers for dictionaries-common (1.29.7) ...
Processing triggers for linux-image-6.14.0-24-generic (6.14.0-24.24~24.04.3) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.14.0-24-generic
cryptsetup: ERROR: Couldn't resolve device overlay
cryptsetup: WARNING: Couldn't determine root device
cryptsetup: ERROR: Couldn't resolve device /dev/vdb
Errors were encountered while processing:
lowlatency-kernel |
Ubuntu Studio uses the lowlatency kernel. With 6.14, the lowlatency kernel is just the generic kernel with some bootargs to make it lowlatency. This breaks the Ubuntu Studio livefs and CD image builds.
https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/noble/ubuntustudio
Problem 1)
The postinst hook of the lowlatency-kernel package calls update-grub unconditionally which fails if the package is installed in a chroot.
From a livefs build log:
Processing triggers for dbus (1.14.10-4ubuntu4.1) ...
Processing triggers for libgtk-3-0t64:amd64 (3.24.41-4ubuntu1.3) ...
Processing triggers for shared-mime-info (2.4-4) ...
Processing triggers for libgtk2.0-0t64:amd64 (2.24.33-4ubuntu1.1) ...
Processing triggers for desktop-file-utils (0.27-2build1) ...
Processing triggers for initramfs-tools (0.142ubuntu25.5) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for libc-bin (2.39-0ubuntu8.5) ...
Processing triggers for man-db (2.12.0-4build2) ...
Processing triggers for dictionaries-common (1.29.7) ...
Processing triggers for linux-image-6.14.0-24-generic (6.14.0-24.24~24.04.3) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.14.0-24-generic
cryptsetup: ERROR: Couldn't resolve device overlay
cryptsetup: WARNING: Couldn't determine root device
cryptsetup: ERROR: Couldn't resolve device /dev/vdb
Errors were encountered while processing:
lowlatency-kernel
Problem 2)
The kernel flavor name changed from 'lowlatency' to 'generic'. This breaks livecd-rootfs. |
|
| 2025-07-30 18:48:47 |
Juerg Haefliger |
bug task added |
|
livecd-rootfs (Ubuntu) |
|
| 2025-07-30 18:52:50 |
Juerg Haefliger |
attachment added |
|
lowlatency-kernel_1.3.debdiff https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2119012/+attachment/5894868/+files/lowlatency-kernel_1.3.debdiff |
|
| 2025-07-30 18:53:32 |
Juerg Haefliger |
attachment added |
|
lowlatency-kernel_1.3~24.04.1.debdiff https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2119012/+attachment/5894869/+files/lowlatency-kernel_1.3~24.04.1.debdiff |
|
| 2025-07-30 18:54:47 |
Juerg Haefliger |
attachment added |
|
livecd-rootfs_24.04.91.debdiff https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2119012/+attachment/5894870/+files/livecd-rootfs_24.04.91.debdiff |
|
| 2025-07-30 18:56:03 |
Juerg Haefliger |
merge proposal linked |
|
https://code.launchpad.net/~juergh/livecd-rootfs/+git/livecd-rootfs/+merge/489967 |
|
| 2025-07-30 19:43:31 |
Dan Bungert |
livecd-rootfs (Ubuntu Plucky): status |
New |
Won't Fix |
|
| 2025-07-30 19:43:42 |
Dan Bungert |
livecd-rootfs (Ubuntu Noble): status |
New |
In Progress |
|
| 2025-07-30 19:43:44 |
Dan Bungert |
livecd-rootfs (Ubuntu Questing): status |
New |
In Progress |
|
| 2025-07-30 19:43:46 |
Dan Bungert |
livecd-rootfs (Ubuntu Noble): assignee |
|
Dan Bungert (dbungert) |
|
| 2025-07-30 19:43:47 |
Dan Bungert |
livecd-rootfs (Ubuntu Questing): assignee |
|
Dan Bungert (dbungert) |
|
| 2025-07-30 23:15:07 |
Dan Bungert |
livecd-rootfs (Ubuntu Questing): status |
In Progress |
New |
|
| 2025-07-30 23:15:09 |
Dan Bungert |
livecd-rootfs (Ubuntu Questing): assignee |
Dan Bungert (dbungert) |
|
|
| 2025-07-30 23:15:12 |
Dan Bungert |
livecd-rootfs (Ubuntu Noble): assignee |
Dan Bungert (dbungert) |
|
|
| 2025-07-30 23:15:14 |
Dan Bungert |
livecd-rootfs (Ubuntu Noble): status |
In Progress |
Fix Committed |
|
| 2025-07-31 00:28:17 |
Ubuntu Foundations Team Bug Bot |
tags |
|
patch |
|
| 2025-07-31 09:02:58 |
Juerg Haefliger |
description |
Ubuntu Studio uses the lowlatency kernel. With 6.14, the lowlatency kernel is just the generic kernel with some bootargs to make it lowlatency. This breaks the Ubuntu Studio livefs and CD image builds.
https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/noble/ubuntustudio
Problem 1)
The postinst hook of the lowlatency-kernel package calls update-grub unconditionally which fails if the package is installed in a chroot.
From a livefs build log:
Processing triggers for dbus (1.14.10-4ubuntu4.1) ...
Processing triggers for libgtk-3-0t64:amd64 (3.24.41-4ubuntu1.3) ...
Processing triggers for shared-mime-info (2.4-4) ...
Processing triggers for libgtk2.0-0t64:amd64 (2.24.33-4ubuntu1.1) ...
Processing triggers for desktop-file-utils (0.27-2build1) ...
Processing triggers for initramfs-tools (0.142ubuntu25.5) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for libc-bin (2.39-0ubuntu8.5) ...
Processing triggers for man-db (2.12.0-4build2) ...
Processing triggers for dictionaries-common (1.29.7) ...
Processing triggers for linux-image-6.14.0-24-generic (6.14.0-24.24~24.04.3) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.14.0-24-generic
cryptsetup: ERROR: Couldn't resolve device overlay
cryptsetup: WARNING: Couldn't determine root device
cryptsetup: ERROR: Couldn't resolve device /dev/vdb
Errors were encountered while processing:
lowlatency-kernel
Problem 2)
The kernel flavor name changed from 'lowlatency' to 'generic'. This breaks livecd-rootfs. |
Ubuntu Studio uses the lowlatency kernel. With 6.14, the lowlatency kernel is just the generic kernel with some bootargs to make it lowlatency. This breaks the Ubuntu Studio livefs and CD image builds.
https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/noble/ubuntustudio
Problem 1)
The postinst hook of the lowlatency-kernel package calls update-grub unconditionally which fails if the package is installed in a chroot.
From a livefs build log:
Processing triggers for dbus (1.14.10-4ubuntu4.1) ...
Processing triggers for libgtk-3-0t64:amd64 (3.24.41-4ubuntu1.3) ...
Processing triggers for shared-mime-info (2.4-4) ...
Processing triggers for libgtk2.0-0t64:amd64 (2.24.33-4ubuntu1.1) ...
Processing triggers for desktop-file-utils (0.27-2build1) ...
Processing triggers for initramfs-tools (0.142ubuntu25.5) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for libc-bin (2.39-0ubuntu8.5) ...
Processing triggers for man-db (2.12.0-4build2) ...
Processing triggers for dictionaries-common (1.29.7) ...
Processing triggers for linux-image-6.14.0-24-generic (6.14.0-24.24~24.04.3) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.14.0-24-generic
cryptsetup: ERROR: Couldn't resolve device overlay
cryptsetup: WARNING: Couldn't determine root device
cryptsetup: ERROR: Couldn't resolve device /dev/vdb
Errors were encountered while processing:
lowlatency-kernel
Problem 2)
The kernel flavor name changed from 'lowlatency' to 'generic'. This breaks livecd-rootfs.
[2025-07-30 21:10:37] No catalog entry template for standard.live
[2025-07-30 21:10:38] P: Begin unmounting filesystems...
[2025-07-30 21:10:38] P: Saving caches...
[2025-07-30 21:10:38] No kernel output for lowlatency!
[2025-07-30 21:10:38] P: Begin unmounting filesystems...
[2025-07-30 21:10:38] P: Saving caches...
[2025-07-30 21:10:38] Build failed |
|
| 2025-07-31 13:39:36 |
Paride Legovini |
lowlatency-kernel (Ubuntu Noble): status |
New |
In Progress |
|
| 2025-07-31 13:50:39 |
Juerg Haefliger |
description |
Ubuntu Studio uses the lowlatency kernel. With 6.14, the lowlatency kernel is just the generic kernel with some bootargs to make it lowlatency. This breaks the Ubuntu Studio livefs and CD image builds.
https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/noble/ubuntustudio
Problem 1)
The postinst hook of the lowlatency-kernel package calls update-grub unconditionally which fails if the package is installed in a chroot.
From a livefs build log:
Processing triggers for dbus (1.14.10-4ubuntu4.1) ...
Processing triggers for libgtk-3-0t64:amd64 (3.24.41-4ubuntu1.3) ...
Processing triggers for shared-mime-info (2.4-4) ...
Processing triggers for libgtk2.0-0t64:amd64 (2.24.33-4ubuntu1.1) ...
Processing triggers for desktop-file-utils (0.27-2build1) ...
Processing triggers for initramfs-tools (0.142ubuntu25.5) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for libc-bin (2.39-0ubuntu8.5) ...
Processing triggers for man-db (2.12.0-4build2) ...
Processing triggers for dictionaries-common (1.29.7) ...
Processing triggers for linux-image-6.14.0-24-generic (6.14.0-24.24~24.04.3) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.14.0-24-generic
cryptsetup: ERROR: Couldn't resolve device overlay
cryptsetup: WARNING: Couldn't determine root device
cryptsetup: ERROR: Couldn't resolve device /dev/vdb
Errors were encountered while processing:
lowlatency-kernel
Problem 2)
The kernel flavor name changed from 'lowlatency' to 'generic'. This breaks livecd-rootfs.
[2025-07-30 21:10:37] No catalog entry template for standard.live
[2025-07-30 21:10:38] P: Begin unmounting filesystems...
[2025-07-30 21:10:38] P: Saving caches...
[2025-07-30 21:10:38] No kernel output for lowlatency!
[2025-07-30 21:10:38] P: Begin unmounting filesystems...
[2025-07-30 21:10:38] P: Saving caches...
[2025-07-30 21:10:38] Build failed |
[ Impact ]
Ubuntu Studio uses the lowlatency kernel. With 6.14, the lowlatency kernel is just the generic kernel with some bootargs to make it lowlatency. This breaks the Ubuntu Studio livefs and CD image builds.
https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/noble/ubuntustudio
Problem 1)
The postinst hook of the lowlatency-kernel package calls update-grub unconditionally which fails if the package is installed in a chroot.
From a livefs build log:
Processing triggers for dbus (1.14.10-4ubuntu4.1) ...
Processing triggers for libgtk-3-0t64:amd64 (3.24.41-4ubuntu1.3) ...
Processing triggers for shared-mime-info (2.4-4) ...
Processing triggers for libgtk2.0-0t64:amd64 (2.24.33-4ubuntu1.1) ...
Processing triggers for desktop-file-utils (0.27-2build1) ...
Processing triggers for initramfs-tools (0.142ubuntu25.5) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for libc-bin (2.39-0ubuntu8.5) ...
Processing triggers for man-db (2.12.0-4build2) ...
Processing triggers for dictionaries-common (1.29.7) ...
Processing triggers for linux-image-6.14.0-24-generic (6.14.0-24.24~24.04.3) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.14.0-24-generic
cryptsetup: ERROR: Couldn't resolve device overlay
cryptsetup: WARNING: Couldn't determine root device
cryptsetup: ERROR: Couldn't resolve device /dev/vdb
Errors were encountered while processing:
lowlatency-kernel
Problem 2)
The kernel flavor name changed from 'lowlatency' to 'generic'. This breaks livecd-rootfs.
[2025-07-30 21:10:37] No catalog entry template for standard.live
[2025-07-30 21:10:38] P: Begin unmounting filesystems...
[2025-07-30 21:10:38] P: Saving caches...
[2025-07-30 21:10:38] No kernel output for lowlatency!
[2025-07-30 21:10:38] P: Begin unmounting filesystems...
[2025-07-30 21:10:38] P: Saving caches...
[2025-07-30 21:10:38] Build failed
[ Test Plan ]
Trigger an Ubuntu Studio livefs build and watch it succeed.
[ Where Problems Could Occur ]
Other consumers of livecd-rootfs could fail, i.e., other livefs builds might fail due to livecd-rootfs changes.
Machines that have then lowlatency-kernel package installed might not update grub.cfg and hence not switch the kernel to lowlatency but continue to run with generic settings. |
|
| 2025-07-31 14:39:39 |
Dan Bungert |
lowlatency-kernel (Ubuntu Noble): status |
In Progress |
Fix Committed |
|
| 2025-07-31 17:51:02 |
Andreas Hasenack |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2025-07-31 17:51:08 |
Andreas Hasenack |
tags |
patch |
patch verification-needed verification-needed-noble |
|
| 2025-07-31 21:25:02 |
Launchpad Janitor |
livecd-rootfs (Ubuntu): status |
New |
Confirmed |
|
| 2025-07-31 21:25:02 |
Launchpad Janitor |
lowlatency-kernel (Ubuntu): status |
New |
Confirmed |
|
| 2025-07-31 21:25:02 |
Launchpad Janitor |
lowlatency-kernel (Ubuntu Plucky): status |
New |
Confirmed |
|
| 2025-08-01 06:19:43 |
Juerg Haefliger |
tags |
patch verification-needed verification-needed-noble |
patch verification-done-noble verification-needed |
|
| 2025-08-01 10:47:24 |
Launchpad Janitor |
lowlatency-kernel (Ubuntu Questing): status |
Confirmed |
Fix Released |
|
| 2025-08-01 13:00:31 |
Juerg Haefliger |
merge proposal linked |
|
https://code.launchpad.net/~juergh/debian-cd/+git/ubuntu/+merge/490092 |
|
| 2025-08-01 13:02:03 |
Juerg Haefliger |
description |
[ Impact ]
Ubuntu Studio uses the lowlatency kernel. With 6.14, the lowlatency kernel is just the generic kernel with some bootargs to make it lowlatency. This breaks the Ubuntu Studio livefs and CD image builds.
https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/noble/ubuntustudio
Problem 1)
The postinst hook of the lowlatency-kernel package calls update-grub unconditionally which fails if the package is installed in a chroot.
From a livefs build log:
Processing triggers for dbus (1.14.10-4ubuntu4.1) ...
Processing triggers for libgtk-3-0t64:amd64 (3.24.41-4ubuntu1.3) ...
Processing triggers for shared-mime-info (2.4-4) ...
Processing triggers for libgtk2.0-0t64:amd64 (2.24.33-4ubuntu1.1) ...
Processing triggers for desktop-file-utils (0.27-2build1) ...
Processing triggers for initramfs-tools (0.142ubuntu25.5) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for libc-bin (2.39-0ubuntu8.5) ...
Processing triggers for man-db (2.12.0-4build2) ...
Processing triggers for dictionaries-common (1.29.7) ...
Processing triggers for linux-image-6.14.0-24-generic (6.14.0-24.24~24.04.3) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.14.0-24-generic
cryptsetup: ERROR: Couldn't resolve device overlay
cryptsetup: WARNING: Couldn't determine root device
cryptsetup: ERROR: Couldn't resolve device /dev/vdb
Errors were encountered while processing:
lowlatency-kernel
Problem 2)
The kernel flavor name changed from 'lowlatency' to 'generic'. This breaks livecd-rootfs.
[2025-07-30 21:10:37] No catalog entry template for standard.live
[2025-07-30 21:10:38] P: Begin unmounting filesystems...
[2025-07-30 21:10:38] P: Saving caches...
[2025-07-30 21:10:38] No kernel output for lowlatency!
[2025-07-30 21:10:38] P: Begin unmounting filesystems...
[2025-07-30 21:10:38] P: Saving caches...
[2025-07-30 21:10:38] Build failed
[ Test Plan ]
Trigger an Ubuntu Studio livefs build and watch it succeed.
[ Where Problems Could Occur ]
Other consumers of livecd-rootfs could fail, i.e., other livefs builds might fail due to livecd-rootfs changes.
Machines that have then lowlatency-kernel package installed might not update grub.cfg and hence not switch the kernel to lowlatency but continue to run with generic settings. |
[ Impact ]
Ubuntu Studio uses the lowlatency kernel. With 6.14, the lowlatency kernel is just the generic kernel with some bootargs to make it lowlatency. This breaks the Ubuntu Studio livefs and CD image builds.
https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/noble/ubuntustudio
Problem 1)
The postinst hook of the lowlatency-kernel package calls update-grub unconditionally which fails if the package is installed in a chroot.
From a livefs build log:
Processing triggers for dbus (1.14.10-4ubuntu4.1) ...
Processing triggers for libgtk-3-0t64:amd64 (3.24.41-4ubuntu1.3) ...
Processing triggers for shared-mime-info (2.4-4) ...
Processing triggers for libgtk2.0-0t64:amd64 (2.24.33-4ubuntu1.1) ...
Processing triggers for desktop-file-utils (0.27-2build1) ...
Processing triggers for initramfs-tools (0.142ubuntu25.5) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for libc-bin (2.39-0ubuntu8.5) ...
Processing triggers for man-db (2.12.0-4build2) ...
Processing triggers for dictionaries-common (1.29.7) ...
Processing triggers for linux-image-6.14.0-24-generic (6.14.0-24.24~24.04.3) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.14.0-24-generic
cryptsetup: ERROR: Couldn't resolve device overlay
cryptsetup: WARNING: Couldn't determine root device
cryptsetup: ERROR: Couldn't resolve device /dev/vdb
Errors were encountered while processing:
lowlatency-kernel
Problem 2)
The kernel flavor name changed from 'lowlatency' to 'generic'. This breaks livecd-rootfs.
[2025-07-30 21:10:37] No catalog entry template for standard.live
[2025-07-30 21:10:38] P: Begin unmounting filesystems...
[2025-07-30 21:10:38] P: Saving caches...
[2025-07-30 21:10:38] No kernel output for lowlatency!
[2025-07-30 21:10:38] P: Begin unmounting filesystems...
[2025-07-30 21:10:38] P: Saving caches...
[2025-07-30 21:10:38] Build failed
Problem 3)
[ Test Plan ]
1. Trigger an Ubuntu Studio livefs build and watch it succeed.
2. Boot a resulting CD image and verify the running kernel is lowlatency.
3. Install Ubuntu Studio and verify the running kernel is lowlatency.
[ Where Problems Could Occur ]
Other consumers of livecd-rootfs could fail, i.e., other livefs builds might fail due to livecd-rootfs changes.
Machines that have then lowlatency-kernel package installed might not update grub.cfg and hence not switch the kernel to lowlatency but continue to run with generic settings. |
|
| 2025-08-01 13:08:28 |
Andreas Hasenack |
tags |
patch verification-done-noble verification-needed |
patch verification-needed verification-needed-noble |
|
| 2025-08-01 15:26:58 |
Juerg Haefliger |
description |
[ Impact ]
Ubuntu Studio uses the lowlatency kernel. With 6.14, the lowlatency kernel is just the generic kernel with some bootargs to make it lowlatency. This breaks the Ubuntu Studio livefs and CD image builds.
https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/noble/ubuntustudio
Problem 1)
The postinst hook of the lowlatency-kernel package calls update-grub unconditionally which fails if the package is installed in a chroot.
From a livefs build log:
Processing triggers for dbus (1.14.10-4ubuntu4.1) ...
Processing triggers for libgtk-3-0t64:amd64 (3.24.41-4ubuntu1.3) ...
Processing triggers for shared-mime-info (2.4-4) ...
Processing triggers for libgtk2.0-0t64:amd64 (2.24.33-4ubuntu1.1) ...
Processing triggers for desktop-file-utils (0.27-2build1) ...
Processing triggers for initramfs-tools (0.142ubuntu25.5) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for libc-bin (2.39-0ubuntu8.5) ...
Processing triggers for man-db (2.12.0-4build2) ...
Processing triggers for dictionaries-common (1.29.7) ...
Processing triggers for linux-image-6.14.0-24-generic (6.14.0-24.24~24.04.3) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.14.0-24-generic
cryptsetup: ERROR: Couldn't resolve device overlay
cryptsetup: WARNING: Couldn't determine root device
cryptsetup: ERROR: Couldn't resolve device /dev/vdb
Errors were encountered while processing:
lowlatency-kernel
Problem 2)
The kernel flavor name changed from 'lowlatency' to 'generic'. This breaks livecd-rootfs.
[2025-07-30 21:10:37] No catalog entry template for standard.live
[2025-07-30 21:10:38] P: Begin unmounting filesystems...
[2025-07-30 21:10:38] P: Saving caches...
[2025-07-30 21:10:38] No kernel output for lowlatency!
[2025-07-30 21:10:38] P: Begin unmounting filesystems...
[2025-07-30 21:10:38] P: Saving caches...
[2025-07-30 21:10:38] Build failed
Problem 3)
[ Test Plan ]
1. Trigger an Ubuntu Studio livefs build and watch it succeed.
2. Boot a resulting CD image and verify the running kernel is lowlatency.
3. Install Ubuntu Studio and verify the running kernel is lowlatency.
[ Where Problems Could Occur ]
Other consumers of livecd-rootfs could fail, i.e., other livefs builds might fail due to livecd-rootfs changes.
Machines that have then lowlatency-kernel package installed might not update grub.cfg and hence not switch the kernel to lowlatency but continue to run with generic settings. |
[ Impact ]
Ubuntu Studio uses the lowlatency kernel. With 6.14, the lowlatency kernel is just the generic kernel with some bootargs to make it lowlatency. This breaks the Ubuntu Studio livefs and CD image builds.
https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/noble/ubuntustudio
Problem 1)
The postinst hook of the lowlatency-kernel package calls update-grub unconditionally which fails if the package is installed in a chroot.
From a livefs build log:
Processing triggers for dbus (1.14.10-4ubuntu4.1) ...
Processing triggers for libgtk-3-0t64:amd64 (3.24.41-4ubuntu1.3) ...
Processing triggers for shared-mime-info (2.4-4) ...
Processing triggers for libgtk2.0-0t64:amd64 (2.24.33-4ubuntu1.1) ...
Processing triggers for desktop-file-utils (0.27-2build1) ...
Processing triggers for initramfs-tools (0.142ubuntu25.5) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for libc-bin (2.39-0ubuntu8.5) ...
Processing triggers for man-db (2.12.0-4build2) ...
Processing triggers for dictionaries-common (1.29.7) ...
Processing triggers for linux-image-6.14.0-24-generic (6.14.0-24.24~24.04.3) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.14.0-24-generic
cryptsetup: ERROR: Couldn't resolve device overlay
cryptsetup: WARNING: Couldn't determine root device
cryptsetup: ERROR: Couldn't resolve device /dev/vdb
Errors were encountered while processing:
lowlatency-kernel
Problem 2)
The kernel flavor name changed from 'lowlatency' to 'generic'. This breaks livecd-rootfs.
[2025-07-30 21:10:37] No catalog entry template for standard.live
[2025-07-30 21:10:38] P: Begin unmounting filesystems...
[2025-07-30 21:10:38] P: Saving caches...
[2025-07-30 21:10:38] No kernel output for lowlatency!
[2025-07-30 21:10:38] P: Begin unmounting filesystems...
[2025-07-30 21:10:38] P: Saving caches...
[2025-07-30 21:10:38] Build failed
Problem 3)
[ Test Plan ]
1. Trigger an Ubuntu Studio livefs build and watch it succeed.
2. Boot a resulting CD image and verify the running kernel is lowlatency.
3. Install Ubuntu Studio and verify the running kernel is lowlatency.
[ Where Problems Could Occur ]
Other consumers of livecd-rootfs could fail, i.e., other livefs builds might fail due to livecd-rootfs changes.
Machines that have the lowlatency-kernel package installed might not update grub.cfg and hence not switch the kernel to lowlatency but continue to run with generic settings. |
|
| 2025-08-02 07:59:40 |
Juerg Haefliger |
description |
[ Impact ]
Ubuntu Studio uses the lowlatency kernel. With 6.14, the lowlatency kernel is just the generic kernel with some bootargs to make it lowlatency. This breaks the Ubuntu Studio livefs and CD image builds.
https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/noble/ubuntustudio
Problem 1)
The postinst hook of the lowlatency-kernel package calls update-grub unconditionally which fails if the package is installed in a chroot.
From a livefs build log:
Processing triggers for dbus (1.14.10-4ubuntu4.1) ...
Processing triggers for libgtk-3-0t64:amd64 (3.24.41-4ubuntu1.3) ...
Processing triggers for shared-mime-info (2.4-4) ...
Processing triggers for libgtk2.0-0t64:amd64 (2.24.33-4ubuntu1.1) ...
Processing triggers for desktop-file-utils (0.27-2build1) ...
Processing triggers for initramfs-tools (0.142ubuntu25.5) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for libc-bin (2.39-0ubuntu8.5) ...
Processing triggers for man-db (2.12.0-4build2) ...
Processing triggers for dictionaries-common (1.29.7) ...
Processing triggers for linux-image-6.14.0-24-generic (6.14.0-24.24~24.04.3) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.14.0-24-generic
cryptsetup: ERROR: Couldn't resolve device overlay
cryptsetup: WARNING: Couldn't determine root device
cryptsetup: ERROR: Couldn't resolve device /dev/vdb
Errors were encountered while processing:
lowlatency-kernel
Problem 2)
The kernel flavor name changed from 'lowlatency' to 'generic'. This breaks livecd-rootfs.
[2025-07-30 21:10:37] No catalog entry template for standard.live
[2025-07-30 21:10:38] P: Begin unmounting filesystems...
[2025-07-30 21:10:38] P: Saving caches...
[2025-07-30 21:10:38] No kernel output for lowlatency!
[2025-07-30 21:10:38] P: Begin unmounting filesystems...
[2025-07-30 21:10:38] P: Saving caches...
[2025-07-30 21:10:38] Build failed
Problem 3)
[ Test Plan ]
1. Trigger an Ubuntu Studio livefs build and watch it succeed.
2. Boot a resulting CD image and verify the running kernel is lowlatency.
3. Install Ubuntu Studio and verify the running kernel is lowlatency.
[ Where Problems Could Occur ]
Other consumers of livecd-rootfs could fail, i.e., other livefs builds might fail due to livecd-rootfs changes.
Machines that have the lowlatency-kernel package installed might not update grub.cfg and hence not switch the kernel to lowlatency but continue to run with generic settings. |
[ Impact ]
Ubuntu Studio uses the lowlatency kernel. With 6.14, the lowlatency kernel is just the generic kernel with some bootargs to make it lowlatency. This breaks the Ubuntu Studio livefs and CD image builds.
https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/noble/ubuntustudio
Problem 1)
The postinst hook of the lowlatency-kernel package calls update-grub unconditionally which fails if the package is installed in a chroot.
From a livefs build log:
Processing triggers for dbus (1.14.10-4ubuntu4.1) ...
Processing triggers for libgtk-3-0t64:amd64 (3.24.41-4ubuntu1.3) ...
Processing triggers for shared-mime-info (2.4-4) ...
Processing triggers for libgtk2.0-0t64:amd64 (2.24.33-4ubuntu1.1) ...
Processing triggers for desktop-file-utils (0.27-2build1) ...
Processing triggers for initramfs-tools (0.142ubuntu25.5) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for libc-bin (2.39-0ubuntu8.5) ...
Processing triggers for man-db (2.12.0-4build2) ...
Processing triggers for dictionaries-common (1.29.7) ...
Processing triggers for linux-image-6.14.0-24-generic (6.14.0-24.24~24.04.3) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.14.0-24-generic
cryptsetup: ERROR: Couldn't resolve device overlay
cryptsetup: WARNING: Couldn't determine root device
cryptsetup: ERROR: Couldn't resolve device /dev/vdb
Errors were encountered while processing:
lowlatency-kernel
Problem 2)
The kernel flavor name changed from 'lowlatency' to 'generic'. This breaks livecd-rootfs.
[2025-07-30 21:10:37] No catalog entry template for standard.live
[2025-07-30 21:10:38] P: Begin unmounting filesystems...
[2025-07-30 21:10:38] P: Saving caches...
[2025-07-30 21:10:38] No kernel output for lowlatency!
[2025-07-30 21:10:38] P: Begin unmounting filesystems...
[2025-07-30 21:10:38] P: Saving caches...
[2025-07-30 21:10:38] Build failed
Problem 3)
The ISO kernel is the generic kernel now so needs additional boot args to make it lowlatency. Otherwise 'Try Ubuntu Studio' will run the generic kernel which is likely not what we want.
[ Test Plan ]
1. Trigger an Ubuntu Studio livefs build and watch it succeed.
2. Boot a resulting CD image and verify the running kernel is lowlatency.
3. Install Ubuntu Studio and verify the running kernel is lowlatency.
[ Where Problems Could Occur ]
Other consumers of livecd-rootfs could fail, i.e., other livefs builds might fail due to livecd-rootfs changes.
Machines that have the lowlatency-kernel package installed might not update grub.cfg and hence not switch the kernel to lowlatency but continue to run with generic settings. |
|
| 2025-08-04 09:29:48 |
Launchpad Janitor |
lowlatency-kernel (Ubuntu Noble): status |
Fix Committed |
Fix Released |
|
| 2025-08-04 09:34:09 |
Launchpad Janitor |
livecd-rootfs (Ubuntu Noble): status |
Fix Committed |
Fix Released |
|
| 2025-08-15 10:19:40 |
Timo Aaltonen |
lowlatency-kernel (Ubuntu Plucky): status |
Confirmed |
Fix Committed |
|
| 2025-08-15 10:19:44 |
Timo Aaltonen |
tags |
patch verification-needed verification-needed-noble |
patch verification-needed verification-needed-noble verification-needed-plucky |
|
| 2025-08-19 07:56:55 |
Juerg Haefliger |
tags |
patch verification-needed verification-needed-noble verification-needed-plucky |
patch verification-done-plucky verification-needed verification-needed-noble |
|
| 2025-08-19 07:58:59 |
Juerg Haefliger |
tags |
patch verification-done-plucky verification-needed verification-needed-noble |
patch verification-done-noble verification-done-plucky verification-needed |
|
| 2025-08-26 04:06:07 |
Launchpad Janitor |
lowlatency-kernel (Ubuntu Plucky): status |
Fix Committed |
Fix Released |
|
| 2025-08-26 04:06:12 |
Chris Halse Rogers |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
