[Touch-packages] [Bug 2052646] Re: Errors after upgrading to package linux-image-6.5.0-17-generic 6.5.0-17.17~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exite
*** This bug is a duplicate of bug 798414 *** https://bugs.launchpad.net/bugs/798414 Thank you for taking the time to report this bug and helping to make Ubuntu better. The relevant dpkg terminal log says: cat: write error: No space left on device So generating the initramfs fails because your /boot partition is full. Please cleanup your boot partition. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 798414 update-initramfs should produce a more helpful error message when there isn't enough free space--or provide an automatic tool for removal of old files -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2052646 Title: Errors after upgrading to package linux-image-6.5.0-17-generic 6.5.0-17.17~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: See attached debug information. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-17-generic 6.5.0-17.17~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 7 10:30:45 2024 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-04-30 (1377 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: initramfs-tools Title: package linux-image-6.5.0-17-generic 6.5.0-17.17~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to jammy on 2023-08-08 (182 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2052646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051709] Re: package linux-image-5.15.0-92-generic 5.15.0-92.102 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Yes, your guess was right. The relevant dpkg terminal log says: No space left on device So adjusting the space was the correct solution. Therefore I am closing this bug. ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2051709 Title: package linux-image-5.15.0-92-generic 5.15.0-92.102 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: I feel like this was due to storage available at the time of the virtual build. As it hit capacity, it started to throws errors. I have since adjusted allotted space to 40GB from the default. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-92-generic 5.15.0-92.102 ProcVersionSignature: Ubuntu 6.2.0-1019.19~22.04.1-azure 6.2.16 Uname: Linux 6.2.0-1019-azure x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: linux-modules-extra-5.15.0-92-generic:amd64: Install linux-headers-5.15.0-92:amd64: Install NULL: ConfigurePending Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown Date: Mon Jan 29 10:07:21 2024 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine ProcFB: 0 hyperv_drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1019-azure root=UUID=89ee03ba-6808-4977-a4fb-9b10174744f8 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2 RfKill: SourcePackage: initramfs-tools Title: package linux-image-5.15.0-92-generic 5.15.0-92.102 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2022 dmi.bios.release: 4.1 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.1 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.1 dmi.chassis.asset.tag: 6076-2812-1301-1065-6309-1370-01 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.1 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.1:bd04/06/2022:br4.1:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.1:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.1:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.1:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.1 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2051709/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2046646] Re: package fwupd 1.7.9-1~22.04.3 failed to install/upgrade: installed fwupd package post-installation script subprocess returned error exit status 127
Thank you for taking the time to report this bug and helping to make Ubuntu better. The relevant dpkg terminal log says: /usr/sbin/update-initramfs: 175: awk: Too many levels of symbolic links It looks like a broken setup of the awk alternative. Can you follow the suggestions in https://askubuntu.com/questions/1459281/error-update-initramfs-175-awk-too-many-levels-of-symbolic-links-when-using to solve your issues? ** Changed in: initramfs-tools (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2046646 Title: package fwupd 1.7.9-1~22.04.3 failed to install/upgrade: installed fwupd package post-installation script subprocess returned error exit status 127 Status in initramfs-tools package in Ubuntu: Incomplete Bug description: i don't know lol ProblemType: Package DistroRelease: Ubuntu 22.04 Package: fwupd 1.7.9-1~22.04.3 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Dec 17 12:15:28 2023 DuplicateSignature: package:fwupd:1.7.9-1~22.04.3 Setting up linux-firmware (20220329.git681281e4-0ubuntu3.23) ... /usr/sbin/update-initramfs: 175: awk: Too many levels of symbolic links dpkg: error processing package linux-firmware (--configure): installed linux-firmware package post-installation script subprocess returned error exit status 127 ErrorMessage: installed fwupd package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2023-12-16 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: fwupd Title: package fwupd 1.7.9-1~22.04.3 failed to install/upgrade: installed fwupd package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2046646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2043579] Re: initramfs-tools autopkgtest fails on armhf: stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2
The autopkgtest of initramfs-tools on armhf on noble started to succeed again (roughly on 2023-12-26). ** Changed in: initramfs-tools (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2043579 Title: initramfs-tools autopkgtest fails on armhf: stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 Status in Auto Package Testing: New Status in cryptsetup package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Fix Released Bug description: The autopkgtest of initramfs-tools fails on armhf on noble: ``` qemu-ata-onlySKIP Test lists explicitly supported architectures, but the current architecture armhf isn't listed. unit-tests PASS qemu-klibc FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-busybox FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-virtio-only FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-separate-usrFAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-panic-shell FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-net FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-net-dnsmasq FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 ``` The /usr/sbin/mkinitramfs call in build_initramfs() has following output: ``` cryptsetup: ERROR: Couldn't resolve device /dev/sda2 cryptsetup: WARNING: Couldn't determine root device copying from directory /tmp/autopkgtest.g0n4ix/autopkgtest_tmp/initramfs-test.qV8LgntBoK/rootdir ``` The two cryptsetup log lines are printed by /usr/share/initramfs- tools/hooks/cryptroot (which comes from cryptsetup-initramfs) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/2043579/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052669] Re: update-initramfs: Generating /boot/initrd.img-5.15.0-92-generic E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1. update-initramfs: failed for /boot/in
Thank you for taking the time to report this bug and helping to make
Ubuntu better. From your description it is hard to tell if you
experienced one or multiple bugs. Does running "update-initramfs -u -k
{version}" succeed?
** Changed in: initramfs-tools (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2052669
Title:
update-initramfs: Generating /boot/initrd.img-5.15.0-92-generic E:
/usr/share/initramfs-tools/hooks/btrfs failed with return 1. update-
initramfs: failed for /boot/initrd.img-5.15.0-92-generic with 1.
Status in initramfs-tools package in Ubuntu:
Incomplete
Bug description:
My bare metal server would not restart. After some research, I found
out that I get the following error:
"Kernel Panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)"
I started up in a Rescue, and followed the steps in
https://askubuntu.com/a/41939/36315, to "update-initramfs -u -k
{version}".
Then I got the below message:
update-initramfs: Generating /boot/initrd.img-5.15.0-92-generic
E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1.
update-initramfs: failed for /boot/initrd.img-5.15.0-92-generic with 1.
I found a workaround for it: https://askubuntu.com/a/916283/36315
"sudo chmod -x /usr/share/initramfs-tools/hooks/fixrtc"
I did that for every file in usr/share/initramfs-tools/hooks/*
After that I did
update-initramfs -u -k all
update-grub
I rebooted from Rescue, and then I got the following error:
"Kernel Panic - not syncing: No working init found. Try passing
init= option to kernel."
AFter this, I reinstalled Ubuntu 22.04 on my bare metal server, but
even after reinstall, I get the "No working init found" error message.
I have no idea now how to fix this.
Any help is greatly appreciated!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2052669/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052525] Re: dracut initramfs missing systemd-executor
dracut 060+5-1ubuntu1 fixes the /usr/lib/systemd/systemd-executor failure, but still seems to fail with the new systemd version. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2052525 Title: dracut initramfs missing systemd-executor Status in dracut package in Ubuntu: In Progress Status in systemd package in Ubuntu: New Bug description: The dracut autopkgtest fails when run against systemd v255.2-3ubuntu2. This looks to be the problem: 504s [0;38;5;245mFailed to stat /etc/localtime, ignoring: No such file or directory[0m 504s [0;38;5;245m/etc/localtime doesn't exist yet, watching /etc instead.[0m 504s [0;1;38;5;185mFailed to open executor binary '/usr/lib/systemd/systemd-executor': No such file or directory[0m 504s [0;1;31mFailed to allocate manager object: No such file or directory[0m 504s [[0;1;31m!![0m] Failed to allocate manager object. 504s [0;1;39mRebooting in 10s...[0m 514s [0;1;39mRebooting now...[0m 514s [ 12.571123] ACPI: PM: Preparing to enter system sleep state S5 514s [ 12.573098] reboot: Restarting system 514s [ 12.574688] reboot: machine restart 515s TEST: root filesystem on a ext3 filesystem [0;31m [FAILED] [0;39m 515s see /tmp/autopkgtest.Vd8poK/autopkgtest_tmp/dracut-test.Fz28KvLkEv/TEST-01-BASIC/test.log 515s make[1]: Leaving directory '/tmp/autopkgtest.Vd8poK/autopkgtest_tmp/dracut-test.Fz28KvLkEv/TEST-01-BASIC' 515s make[1]: *** [../Makefile.testdir:4: all] Error 1 515s make: *** [Makefile:4: TEST-01-BASIC] Error 2 515s make: Leaving directory '/tmp/autopkgtest.Vd8poK/autopkgtest_tmp/dracut-test.Fz28KvLkEv' 515s autopkgtest [03:42:52]: test upstream-dracut-core: ---] I.e., the systemd-executor binary (which is new in systemd v255) is not copied into the initramfs. This has already been fixed in upstream dracut. [1] https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-noble/noble/amd64/d/dracut/20240203_093708_6cc09@/log.gz [2] https://github.com/dracutdevs/dracut/commit/bee1c4824a8cd47ce6c01892a548bdc07b1fa678 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2052525/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052669] Re: update-initramfs: Generating /boot/initrd.img-5.15.0-92-generic E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1. update-initramfs: failed for /boot/in
Can you into a rescue/live environment, chroot into the installed system
on the server disk and try to regenerate the initramfs? In case it
succeeds, can you post "ls -alh /boot" and "lsinitramfs
/boot/initrd.img-${version}"?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2052669
Title:
update-initramfs: Generating /boot/initrd.img-5.15.0-92-generic E:
/usr/share/initramfs-tools/hooks/btrfs failed with return 1. update-
initramfs: failed for /boot/initrd.img-5.15.0-92-generic with 1.
Status in initramfs-tools package in Ubuntu:
Incomplete
Bug description:
My bare metal server would not restart. After some research, I found
out that I get the following error:
"Kernel Panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)"
I started up in a Rescue, and followed the steps in
https://askubuntu.com/a/41939/36315, to "update-initramfs -u -k
{version}".
Then I got the below message:
update-initramfs: Generating /boot/initrd.img-5.15.0-92-generic
E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1.
update-initramfs: failed for /boot/initrd.img-5.15.0-92-generic with 1.
I found a workaround for it: https://askubuntu.com/a/916283/36315
"sudo chmod -x /usr/share/initramfs-tools/hooks/fixrtc"
I did that for every file in usr/share/initramfs-tools/hooks/*
After that I did
update-initramfs -u -k all
update-grub
I rebooted from Rescue, and then I got the following error:
"Kernel Panic - not syncing: No working init found. Try passing
init= option to kernel."
AFter this, I reinstalled Ubuntu 22.04 on my bare metal server, but
even after reinstall, I get the "No working init found" error message.
I have no idea now how to fix this.
Any help is greatly appreciated!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2052669/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782802] Re: use dhclient -4 instead of ipconfig in easy cases in 18.10
As mentioned in bug #1790418 there is still one call to ipconfig that hasn't been replaced (as of initramfs-tools 0.142ubuntu19 in noble). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1782802 Title: use dhclient -4 instead of ipconfig in easy cases in 18.10 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: When adding ipv6 netboot support to initramfs-tools in yakkety/zesty, this was initially attempted with replacing ipconfig with dhclient. As described in LP: #1621507, the use of dhclient for ipv4 dhcp was backed out in favor of ipconfig. So at the moment, we are using both ipconfig from klibc-utils and dhclient from isc-dhcp-client in the initramfs. We want to switch off of klibc-utils completely and use isc-dhcp- client for both ipv4 and ipv6 in initramfs-tools. But for cosmic, we'll only do the easy bits. Bug 1790418 is about finishing the job. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1782802/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052739] [NEW] tzdata 2024a release
Public bug reported: [ Impact ] The 2024a release contains the following changes: * Kazakhstan unifies on UTC+5 beginning 2024-03-01. * Palestine springs forward a week later after Ramadan. * zic no longer pretends to support indefinite-past DST. * localtime no longer mishandles Ciudad Juárez in 2422. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2024a * python-icu: test_2024a (only for focal and newer) So the test plan is to check that the autopkgtest succeeds. [ Other Info ] The autopkgtest for chrony is flaky on jammy and newer (see bug #2002910). ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2052739 Title: tzdata 2024a release Status in tzdata package in Ubuntu: New Bug description: [ Impact ] The 2024a release contains the following changes: * Kazakhstan unifies on UTC+5 beginning 2024-03-01. * Palestine springs forward a week later after Ramadan. * zic no longer pretends to support indefinite-past DST. * localtime no longer mishandles Ciudad Juárez in 2422. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2024a * python-icu: test_2024a (only for focal and newer) So the test plan is to check that the autopkgtest succeeds. [ Other Info ] The autopkgtest for chrony is flaky on jammy and newer (see bug #2002910). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052739] Re: tzdata 2024a release
** Also affects: tzdata (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: tzdata (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: tzdata (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2052739 Title: tzdata 2024a release Status in tzdata package in Ubuntu: New Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Mantic: New Bug description: [ Impact ] The 2024a release contains the following changes: * Kazakhstan unifies on UTC+5 beginning 2024-03-01. * Palestine springs forward a week later after Ramadan. * zic no longer pretends to support indefinite-past DST. * localtime no longer mishandles Ciudad Juárez in 2422. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2024a * python-icu: test_2024a (only for focal and newer) So the test plan is to check that the autopkgtest succeeds. [ Other Info ] The autopkgtest for chrony is flaky on jammy and newer (see bug #2002910). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2053153] Re: initramfs-tools broken by libpam-tmpdir and /tmp mounted with noexec
** Bug watch added: Debian Bug tracker #1062756 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062756 ** Also affects: initramfs-tools (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062756 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2053153 Title: initramfs-tools broken by libpam-tmpdir and /tmp mounted with noexec Status in initramfs-tools package in Ubuntu: New Status in initramfs-tools package in Debian: Unknown Bug description: I would like to forward the bug that was reported against Debian "certain update-initramfs actions broken on systems with' from 'cryptsetup-initramfs: cryptkeyctl script fails to discover decrypt_keyctl even when present" [1] to upstream initramfs-tools, which I think is here. To reproduce this bug in Debian: 1) sudo apt install libpam-tmpdir 2) Mount /tmp with noexec. This breaks the cryptkeyctl hook. Could you fix initramfs-tools compatibility with libpam-tmpdir and /tmp mounted with noexec please? Is there some more appropriate temporary folder for update-initramfs to use? By comparison, dracut has no such issue. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062756 (Disclaimer: I am not affiliated with Debian and writing this on my own imitative.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2053153/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052525] Re: dracut initramfs missing systemd-executor
060+5-1ubuntu2 landed in noble. ** Changed in: dracut (Ubuntu) Status: In Progress => Fix Released ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2052525 Title: dracut initramfs missing systemd-executor Status in dracut package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Bug description: The dracut autopkgtest fails when run against systemd v255.2-3ubuntu2. This looks to be the problem: 504s [0;38;5;245mFailed to stat /etc/localtime, ignoring: No such file or directory[0m 504s [0;38;5;245m/etc/localtime doesn't exist yet, watching /etc instead.[0m 504s [0;1;38;5;185mFailed to open executor binary '/usr/lib/systemd/systemd-executor': No such file or directory[0m 504s [0;1;31mFailed to allocate manager object: No such file or directory[0m 504s [[0;1;31m!![0m] Failed to allocate manager object. 504s [0;1;39mRebooting in 10s...[0m 514s [0;1;39mRebooting now...[0m 514s [ 12.571123] ACPI: PM: Preparing to enter system sleep state S5 514s [ 12.573098] reboot: Restarting system 514s [ 12.574688] reboot: machine restart 515s TEST: root filesystem on a ext3 filesystem [0;31m [FAILED] [0;39m 515s see /tmp/autopkgtest.Vd8poK/autopkgtest_tmp/dracut-test.Fz28KvLkEv/TEST-01-BASIC/test.log 515s make[1]: Leaving directory '/tmp/autopkgtest.Vd8poK/autopkgtest_tmp/dracut-test.Fz28KvLkEv/TEST-01-BASIC' 515s make[1]: *** [../Makefile.testdir:4: all] Error 1 515s make: *** [Makefile:4: TEST-01-BASIC] Error 2 515s make: Leaving directory '/tmp/autopkgtest.Vd8poK/autopkgtest_tmp/dracut-test.Fz28KvLkEv' 515s autopkgtest [03:42:52]: test upstream-dracut-core: ---] I.e., the systemd-executor binary (which is new in systemd v255) is not copied into the initramfs. This has already been fixed in upstream dracut. [1] https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-noble/noble/amd64/d/dracut/20240203_093708_6cc09@/log.gz [2] https://github.com/dracutdevs/dracut/commit/bee1c4824a8cd47ce6c01892a548bdc07b1fa678 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2052525/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2045705] Re: FTBFS with default Java 21
https://github.com/canonical/apport/pull/266 got merged upstream.
** Changed in: apport
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2045705
Title:
FTBFS with default Java 21
Status in Apport:
Fix Committed
Status in apport package in Ubuntu:
Triaged
Bug description:
Dear Maintainers,
The package apport ftbfs with default Java 21.
The relevant part of the build log:
---
running build_java_subdir
warning: [options] bootstrap class path not set in conjunction with -source 7
error: Source option 7 is no longer supported. Use 8 or later.
error: Target option 7 is no longer supported. Use 8 or later.
Traceback (most recent call last):
File "/<>/setup.py", line 119, in
DistUtilsExtra.auto.setup(
File "/usr/lib/python3/dist-packages/DistUtilsExtra/auto.py", line 125, in
setup
setuptools.setup(**attrs)
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 107, in
setup
return distutils.core.setup(**attrs)
^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
185, in setup
return run_commands(dist)
^^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
201, in run_commands
dist.run_commands()
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
969, in run_commands
self.run_command(cmd)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in
run_command
super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
988, in run_command
cmd_obj.run()
File
"/usr/lib/python3/dist-packages/setuptools/_distutils/command/build.py", line
131, in run
self.run_command(cmd_name)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line
318, in run_command
self.distribution.run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in
run_command
super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
988, in run_command
cmd_obj.run()
File "/<>/setuptools_apport/java.py", line 35, in run
subprocess.check_call(javac + glob.glob("com/ubuntu/apport/*.java"))
File "/usr/lib/python3.11/subprocess.py", line 413, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['javac', '-source', '7', '-target',
'7', 'com/ubuntu/apport/ApportUncaughtExceptionHandler.java']' returned
non-zero exit status 2.
E: pybuild pybuild:395: build: plugin distutils failed with: exit code=1:
/usr/bin/python3 setup.py build
dh_auto_build: error: pybuild --build -i python{version} -p "3.12 3.11"
returned exit code 13
make[1]: *** [debian/rules:12: override_dh_auto_build] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
2
Build finished at 2023-12-04T07:37:06Z
---
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2045705/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2043393] Re: Report.get_logind_session fails to determine session on cgroup2 systems
https://github.com/canonical/apport/pull/278 got merged. ** Changed in: apport Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2043393 Title: Report.get_logind_session fails to determine session on cgroup2 systems Status in Apport: Fix Committed Status in apport package in Ubuntu: Triaged Bug description: Ubuntu >= 22.04 uses only cgroup2 (Ubuntu 20.04 used both and Ubuntu 18.04 only cgroup version 1). Report.get_logind_session will fail to determine the logind session and always return None if only cgroup2 is used. get_logind_session searches for cgroup lines with "name=systemd:" and then extracts the session from "/session-". This worked in Ubuntu 16.04 but started failing in 18.04. Content of /proc/self/cgroup when printed from a terminal inside a Ubuntu desktop session: Ubuntu 16.04 (xenial) - ``` 12:cpuset:/ 11:perf_event:/ 10:pids:/user.slice/user-1000.slice 9:blkio:/ 8:hugetlb:/ 7:net_cls,net_prio:/ 6:cpu,cpuacct:/ 5:devices:/user.slice 4:freezer:/ 3:rdma:/ 2:memory:/ 1:name=systemd:/user.slice/user-1000.slice/session-c1.scope ``` Ubuntu 18.04 (bionic) - ``` 12:freezer:/ 11:net_cls,net_prio:/ 10:memory:/ 9:rdma:/ 8:cpu,cpuacct:/ 7:devices:/user.slice 6:perf_event:/ 5:cpuset:/ 4:pids:/user.slice/user-1000.slice/user@1000.service 3:hugetlb:/ 2:blkio:/ 1:name=systemd:/user.slice/user-1000.slice/user@1000.service/gnome-terminal-server.service 0::/user.slice/user-1000.slice/user@1000.service/gnome-terminal-server.service ``` Ubuntu 20.04 (focal) - ``` 13:memory:/user.slice/user-1000.slice/user@1000.service 12:perf_event:/ 11:misc:/ 10:pids:/user.slice/user-1000.slice/user@1000.service 9:hugetlb:/ 8:cpuset:/ 7:blkio:/ 6:devices:/user.slice 5:cpu,cpuacct:/ 4:freezer:/ 3:rdma:/ 2:net_cls,net_prio:/ 1:name=systemd:/user.slice/user-1000.slice/user@1000.service/apps.slice/apps-org.gnome.Terminal.slice/vte-spawn-ad936f4d-0d62-4ac4-bbd8-0e766d8a3b1f.scope 0::/user.slice/user-1000.slice/user@1000.service/apps.slice/apps-org.gnome.Terminal.slice/vte-spawn-ad936f4d-0d62-4ac4-bbd8-0e766d8a3b1f.scope ``` Ubuntu 22.04 (jammy) - ``` 0::/user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-0c3f8b02-b112-4cab-accc-764cbb223bac.scope ``` To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2043393/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054093] Re: /usr/share/apport/apport-gtk:AttributeError:/usr/share/apport/apport-gtk@55:GTKUserInterface
/usr/share/apport/apport-gtk is shipped by apport-gtk and
/usr/lib/python3/dist-packages/apport/ui.py is shipped by
python3-apport.
apport.ui.Action was introduced in commit
36ae3310861f1286eae8875a3195551126290914 in 2.25.0.
apport-gtk depends on python3-apport (>= ${source:Version}) so that
combination should not occur.
** Description changed:
+ Traceback (most recent call last):
+ File "/usr/share/apport/apport-gtk", line 55, in
+ class GTKUserInterface(apport.ui.UserInterface):
+ File "/usr/share/apport/apport-gtk", line 232, in GTKUserInterface
+ ) -> apport.ui.Action:
+ AttributeError: module 'apport.ui' has no attribute 'Action'
+
The Ubuntu Error Tracker has been receiving reports about a problem regarding
apport. This problem was most recently seen with package version
2.27.0-0ubuntu6, the problem page at
https://errors.ubuntu.com/problem/69b52c16ad4a0bf0d8f58af1970fe91f68a05b2e
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2054093
Title:
/usr/share/apport/apport-gtk:AttributeError:/usr/share/apport/apport-
gtk@55:GTKUserInterface
Status in apport package in Ubuntu:
New
Bug description:
Traceback (most recent call last):
File "/usr/share/apport/apport-gtk", line 55, in
class GTKUserInterface(apport.ui.UserInterface):
File "/usr/share/apport/apport-gtk", line 232, in GTKUserInterface
) -> apport.ui.Action:
AttributeError: module 'apport.ui' has no attribute 'Action'
The Ubuntu Error Tracker has been receiving reports about a problem regarding
apport. This problem was most recently seen with package version
2.27.0-0ubuntu6, the problem page at
https://errors.ubuntu.com/problem/69b52c16ad4a0bf0d8f58af1970fe91f68a05b2e
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2054093/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054450] Re: apport arm64 test_core_dump_packaged flaky
** Summary changed:
- apport arm64 autopkgtest flaky
+ apport arm64 test_core_dump_packaged flaky
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2054450
Title:
apport arm64 test_core_dump_packaged flaky
Status in apport package in Ubuntu:
New
Bug description:
The following failure can sometimes be observed on arm64 in noble, for
example, with gnupg2 and sensible-utils:
360s === FAILURES
===
360s __ T.test_core_dump_packaged
___
360s
360s self =
360s
360s def test_core_dump_packaged(self):
360s """Packaged executables create core dumps on proper ulimits."""
360s # for SEGV and ABRT we expect reports and core files
360s for sig in (signal.SIGSEGV, signal.SIGABRT):
360s for kb, exp_file in core_ulimit_table:
360s resource.setrlimit(resource.RLIMIT_CORE, (kb, -1))
360s self.do_crash(
360s expect_corefile=exp_file,
360s expect_corefile_owner=os.geteuid(),
360s sig=sig,
360s )
360s > self.check_report_coredump(self.test_report)
360s
360s
/tmp/autopkgtest.pa788q/autopkgtest_tmp/tests/integration/test_signal_crashes.py:413:
360s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
360s
/tmp/autopkgtest.pa788q/autopkgtest_tmp/tests/integration/test_signal_crashes.py:1114:
in check_report_coredump
360s self.assertIn("\n#2", r.get("Stacktrace"))
360s E AssertionError: '\n#2' not found in '#0 0xf7fd6428 in ??
()\nNo symbol table info available.\n#1 0xf7ffd000 in ?? ()\nNo symbol
table info available.\nBacktrace stopped: previous frame inner to this frame
(corrupt stack?)'
360s - Captured stderr call
-
360s warning: 78 ../sysdeps/unix/sysv/linux/clock_nanosleep.c: No such
file or directory
360s warning: target file /proc/4152/cmdline contained unexpected null
characters
360s warning: 78 ../sysdeps/unix/sysv/linux/clock_nanosleep.c: No such
file or directory
360s warning: target file /proc/4228/cmdline contained unexpected null
characters
360s warning: 78 ../sysdeps/unix/sysv/linux/clock_nanosleep.c: No such
file or directory
360s warning: target file /proc/4308/cmdline contained unexpected null
characters
360s warning: 1972./elf/dl-load.c: No such file or directory
360s warning: target file /proc/4388/cmdline contained unexpected null
characters
360s warning: 1972./elf/dl-load.c: No such file or directory
360s warning: target file /proc/4463/cmdline contained unexpected null
characters
360s warning: 1150./elf/rtld.c: No such file or directory
360s warning: target file /proc/4539/cmdline contained unexpected null
characters
360s === warnings summary
===
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2054450/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054171] Re: dhcpcd hook breaks when using libc6-prof's libc.so.6
Thank you for taking the time to report this bug and contributing to Ubuntu. That is a well prepared bug report. Attached a proposed patch to fix it. Can you have a look and test it? ** Patch added: "0001-Fix-determing-multiarch-dir-when-using-libc6-prof-s-.patch" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2054171/+attachment/5748235/+files/0001-Fix-determing-multiarch-dir-when-using-libc6-prof-s-.patch ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Medium ** Changed in: initramfs-tools (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2054171 Title: dhcpcd hook breaks when using libc6-prof's libc.so.6 Status in initramfs-tools package in Ubuntu: Triaged Bug description: I have the libc6-prof package installed to provide a frame pointer enabled libc.so.6. I have a custom configuration file in /etc/ld.so.conf.d putting /lib/libc6-prof/x86_64-linux-gnu at the front of the dynamic linker search paths. (I really like having frame pointers!) This confuses the `multiarch_dir=$(ldd /usr/sbin/dhcpcd | sed -En 's;^.*/lib/([^/]+)/libc\.so\..*$;\1;p')` line in /usr/share/initramfs- tools/hooks/dhcpcd because the libc.so.6 path is different. Default ldd output: ``` ldd /usr/sbin/dhcpcd linux-vdso.so.1 (0x7fff9a735000) libcrypto.so.3 => /lib/x86_64-linux-gnu/libcrypto.so.3 (0x7f50d280) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f50d240) /lib64/ld-linux-x86-64.so.2 (0x7f50d2f27000) ``` My ldd output: ``` ldd /usr/sbin/dhcpcd linux-vdso.so.1 (0x7fff802db000) libcrypto.so.3 => /lib/x86_64-linux-gnu/libcrypto.so.3 (0x7fce87e0) libc.so.6 => /lib/libc6-prof/x86_64-linux-gnu/libc.so.6 (0x7fce87a0) /lib64/ld-linux-x86-64.so.2 (0x7fce88514000) ``` ``` -libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f50d240) +libc.so.6 => /lib/libc6-prof/x86_64-linux-gnu/libc.so.6 (0x7fce87a0) ``` When running the modified search paths, `ldd /usr/sbin/dhcpcd | sed -En 's;^.*/lib/([^/]+)/libc\.so\..*$;\1;p'` evaluates to an empty string and exits 0. This results in `copy_exec "/usr/lib//dhcpcd/dev/udev.so"`, which breaks that script. This in turn breaks initramfs. ``` Processing triggers for linux-image-6.5.0-17-generic (6.5.0-17.17) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-6.5.0-17-generic E: /usr/share/initramfs-tools/hooks/dhcpcd failed with return 1. update-initramfs: failed for /boot/initrd.img-6.5.0-17-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-6.5.0-17-generic (--configure): installed linux-image-6.5.0-17-generic package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-image-6.5.0-17-generic E: Sub-process /usr/bin/dpkg returned an error code (1) ``` I can work around the issue by hacking up the dhcpcd hook or by modifying the dynamic link path search order, running `ldconfig`, then `update-initramfs -u`. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2054171/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054602] Re: update features UTC+6 to UTC+5 transition for all time zones in Kazakhstan
*** This bug is a duplicate of bug 2052739 *** https://bugs.launchpad.net/bugs/2052739 Thank you for taking the time to report this bug and contributing to Ubuntu. A few hours ago I uploaded the tzdata updates for the stable releases. Hopefully tomorrow they will be accepted in the proposed pocket. See https://wiki.ubuntu.com/StableReleaseUpdates and bug #2052739. ** This bug has been marked a duplicate of bug 2052739 tzdata 2024a release -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2054602 Title: update features UTC+6 to UTC+5 transition for all time zones in Kazakhstan Status in tzdata package in Ubuntu: New Bug description: Please prioritize tzdata-2024a update for all supported Ubuntu versions. Among others, this update features UTC+6 to UTC+5 transition for all time zones in Kazakhstan, which will happen 2024-03-01 at 00:00. Release information: https://mm.icann.org/pipermail/tz-announce/2024-February/81.html We need some time in advance to be prepared for changes and update systems before March To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2054602/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052739] Re: tzdata 2024a release
A few hours ago I uploaded the tzdata updates for the stable releases. They are waiting in the unapproved queue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2052739 Title: tzdata 2024a release Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Focal: Confirmed Status in tzdata source package in Jammy: Confirmed Status in tzdata source package in Mantic: Confirmed Bug description: [ Impact ] The 2024a release contains the following changes: * Kazakhstan unifies on UTC+5 beginning 2024-03-01. * Palestine springs forward a week later after Ramadan. * zic no longer pretends to support indefinite-past DST. * localtime no longer mishandles Ciudad Juárez in 2422. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2024a * python-icu: test_2024a (only for focal and newer) So the test plan is to check that the autopkgtest succeeds. [ Other Info ] The autopkgtest for chrony is flaky on jammy and newer (see bug #2002910). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1892225] Re: apport-gtk consumes 100% CPU for way too long after something crashes
Can you reproduce it? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1892225 Title: apport-gtk consumes 100% CPU for way too long after something crashes Status in apport package in Ubuntu: Confirmed Bug description: Something (related to Cinnamon) crashes, so the usual popup appears telling me that something crashed, and asking me whether I wanted to send a report. I choose Send. Every time this happens, then a process called apport-gtk starts consuming 100% CPU and it goes on for several minutes, so long that I end up killing it. There's no way there is a good reason for consuming so much CPU for so long. If you need to do such an amount of processing just to generate and send a bug report, something is deeply broken. But if the operation actually had to be that computationally expensive, then you must do it in a less intensive way so that it can go on in the background, for no matter how long, without rendering me unable to use my computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27.4 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia ApportLog: ERROR: apport (pid 2908) Wed Aug 19 18:39:29 2020: called for pid 2405, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 2908) Wed Aug 19 18:39:29 2020: executable: /usr/bin/cinnamon (command line "cinnamon --replace") ERROR: apport (pid 2908) Wed Aug 19 18:39:29 2020: debug: session gdbus call: (true,) ERROR: apport (pid 2908) Wed Aug 19 18:39:34 2020: wrote report /var/crash/_usr_bin_cinnamon.1000.crash ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:1000:110:69556:2020-08-19 18:39:33.732794284 +0200:2020-08-19 18:39:34.732794284 +0200:/var/crash/_usr_bin_cinnamon-launcher.1000.crash 640:1000:110:15432562:2020-08-19 18:39:34.466977487 +0200:2020-08-19 18:42:42.722667813 +0200:/var/crash/_usr_bin_cinnamon.1000.crash CurrentDesktop: X-Cinnamon Date: Wed Aug 19 18:42:34 2020 InstallationDate: Installed on 2013-10-11 (2503 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to focal on 2020-07-12 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1892225/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2031919] Re: /usr/share/apport/whoopsie-upload-all:TypeError:/usr/share/apport/whoopsie-upload-all@247:main:collect_info:process_report:add_gdb_info
** Also affects: apport Importance: Undecided Status: New ** Changed in: apport Milestone: None => 2.28.0 ** Changed in: apport Importance: Undecided => Medium ** Changed in: apport Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2031919 Title: /usr/share/apport/whoopsie-upload- all:TypeError:/usr/share/apport/whoopsie-upload- all@247:main:collect_info:process_report:add_gdb_info Status in Apport: Fix Committed Status in apport package in Ubuntu: Fix Released Bug description: ``` Traceback (most recent call last): File "/usr/share/apport/whoopsie-upload-all", line 247, in main() File "/usr/share/apport/whoopsie-upload-all", line 229, in main stamps = collect_info() ^^ File "/usr/share/apport/whoopsie-upload-all", line 160, in collect_info res = process_report(r) ^ File "/usr/share/apport/whoopsie-upload-all", line 108, in process_report r.add_gdb_info() File "/usr/lib/python3/dist-packages/apport/report.py", line 930, in add_gdb_info environ["HOME"] = "/nonexistent" ~~~ TypeError: 'str' object does not support item assignment ``` The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.26.1-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/86a1629347349acf400d91c9774296b42c1ab1f3 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2031919/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2038650] Re: crash reports not sent to the Error Tracker
** Also affects: apport Importance: Undecided Status: New ** Changed in: apport Milestone: None => 2.28.0 ** Changed in: apport Importance: Undecided => High ** Changed in: apport Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2038650 Title: crash reports not sent to the Error Tracker Status in Apport: Fix Committed Status in apport package in Ubuntu: Fix Released Status in apport source package in Lunar: Fix Released Status in apport source package in Mantic: Fix Released Bug description: [ Impact ] Crash reports aren't sent in when going through the UI, unless the user looks at the crash details. [ Test Plan ] 0) Make sure that error reporting is set to manual in the system settings (in Privacy screen) 1) Launch xeyes 2) pkill -11 xeyes 3) Click send in the apport dialog. DO NOT look at the details of the report. 4) ls -lh /var/crash/*xeyes* There should be 3 files: -rw-r- 1 bdmurray whoopsie 3370567 Oct 6 11:53 _usr_bin_xeyes.1000.crash -rw-rw-r-- 1 bdmurray bdmurray0 Oct 6 11:53 _usr_bin_xeyes.1000.upload -rw--- 1 whoopsie whoopsie 37 Oct 6 11:53 _usr_bin_xeyes.1000.uploaded [ Where problems could occur ] If the patch is wrong, we actually see similar bugs for other UI paths, e.g. ticking the "Remember this" box, etc. I tried to cover them during manual testing but I might have missed some. [ Other Info ] If possible I'd like for us not to wait too long for this to mature in -proposed, as this would affect crashes during the upgrade. [ Original report ] From what I can tell when I click the send button to send a crash report to the Error Tracker the crash doesn't actually get sent. My testing process follows: 1) Launch xeyes 2) pkill -11 xeyes 3) Click send in the apport dialog 4) ls -lh /var/crash I would expect there to be three files in /var/crash: -rw-r- 1 bdmurray whoopsie 3370567 Oct 6 11:53 _usr_bin_xeyes.1000.crash -rw-rw-r-- 1 bdmurray bdmurray0 Oct 6 11:53 _usr_bin_xeyes.1000.upload -rw--- 1 whoopsie whoopsie 37 Oct 6 11:53 _usr_bin_xeyes.1000.uploaded However, after step #4 I'm only seeing the .crash file and not a .upload or .uploaded. I was able to get the .upload and .uploaded files created if I chose to "View Report" and then click "Send". It's worth noting though that I did notice the size of the .crash file increase after clicking "Send" so some post-processing was done. ProblemType: BugDistroRelease: Ubuntu 23.10 Package: apport 2.27.0-0ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CrashReports: 640:1000:123:20944237:2023-10-06 12:10:47.809248208 +0100:2023-10-06 12:11:23.340030509 +0100:/var/crash/_usr_bin_mpv.1000.crash CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 12:12:46 2023 InstallationDate: Installed on 2022-01-07 (637 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: allSourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2038650/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051512] Re: apport ftbfs with Python 3.12 as the default
** Also affects: apport
Importance: Undecided
Status: New
** Changed in: apport
Milestone: None => 2.28.0
** Changed in: apport
Status: New => Fix Committed
** Changed in: apport
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2051512
Title:
apport ftbfs with Python 3.12 as the default
Status in Apport:
Fix Committed
Status in apport package in Ubuntu:
Fix Released
Status in python3-defaults package in Ubuntu:
New
Status in python3.12 package in Ubuntu:
New
Status in apport source package in Noble:
Fix Released
Status in python3-defaults source package in Noble:
New
Status in python3.12 source package in Noble:
New
Bug description:
[Description]
Python 3.12 gzip.GZipFile.write() outputs truncated data in some cases
(maybe all?)
[Test Plan]
Run the following script:
import gzip
import io
out = io.BytesIO()
gzip.GzipFile("foo", mode="wb", fileobj=out, mtime=0).write(b"FooFoo")
# print(out.getvalue())
print(gzip.decompress(out.getvalue()))
Expected output (as on Python 3.11):
FooFoo
Buggy output (tail end of the stack trace):
EOFError: Compressed file ended before the end-of-stream marker was reached
[Original report]
debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
tests/run-linters --errors-only
Skipping mypy tests, mypy is not installed
Running pylint...
* Module apport-retrace
bin/apport-retrace:577:44: E0601: Using variable 'crashid' before assignment
(used-before-assignment)
make[1]: *** [debian/rules:23: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: binary] Error 2
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2051512/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2048136] Re: Please support systemd-coredump as core dump handler
Last bit: https://github.com/canonical/apport/pull/290 ** Changed in: apport (Ubuntu) Status: Triaged => Fix Committed ** Changed in: apport Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2048136 Title: Please support systemd-coredump as core dump handler Status in Apport: Fix Committed Status in apport package in Ubuntu: Fix Committed Bug description: There can only be one system core dump handler on a Linux system and Apport is the Ubuntu default core dump handler. Besides Apport other tools offer coredump handler, in particular systemd-coredump. Due to Apport being installed on all Ubuntu system by default none of these alternate system can be installed. There has been some user request for this integration to work. Proper integration between Apport and systemd-coredump would offer a better experience to developers who want to use systemd-coredump. systemd- coredump and coredumpctl provide more documentation and have more users upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2048136/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2044129] Re: ubuntu-bug does not allow for reporting a bug in "other software" manually giving a symptom description
** Changed in: apport Milestone: 2.28.0 => None -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2044129 Title: ubuntu-bug does not allow for reporting a bug in "other software" manually giving a symptom description Status in Apport: Triaged Status in apport package in Ubuntu: Triaged Bug description: the man page of ubuntu-bug/apport-bug (what is the difference? why am I shown the manpage of apport-bug when typing man ubuntu-bug?) says running apport-bug without arguments results in showing me a list of symptoms. When I try to report a bug in some general program that is not related to the other 9 categories - which is most of the 1 apps in Ubuntu - I must chose "Other Problem" - but in contrary to the man page that tells me I am asked about further things, I only get "You need to specific the pakacge or PID". I currently try to report a bug in the things that identifies itself as "Ubuntu Software" in the Dock, but I have no idea what its correct program or package name is, and have no idea how to find that. In PS there is no process with "ubuntu" or "software" in its name. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: apport 2.27.0-0ubuntu5 ProcVersionSignature: Ubuntu 6.2.0-1015.15-lowlatency 6.2.16 Uname: Linux 6.2.0-1015-lowlatency x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 21 14:38:42 2023 InstallationDate: Installed on 2023-08-21 (92 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: apport UpgradeStatus: Upgraded to mantic on 2023-11-05 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2044129/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051512] Re: apport ftbfs with Python 3.12 as the default
** Changed in: apport
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2051512
Title:
apport ftbfs with Python 3.12 as the default
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
Fix Released
Status in python3-defaults package in Ubuntu:
New
Status in python3.12 package in Ubuntu:
New
Status in apport source package in Noble:
Fix Released
Status in python3-defaults source package in Noble:
New
Status in python3.12 source package in Noble:
New
Bug description:
[Description]
Python 3.12 gzip.GZipFile.write() outputs truncated data in some cases
(maybe all?)
[Test Plan]
Run the following script:
import gzip
import io
out = io.BytesIO()
gzip.GzipFile("foo", mode="wb", fileobj=out, mtime=0).write(b"FooFoo")
# print(out.getvalue())
print(gzip.decompress(out.getvalue()))
Expected output (as on Python 3.11):
FooFoo
Buggy output (tail end of the stack trace):
EOFError: Compressed file ended before the end-of-stream marker was reached
[Original report]
debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
tests/run-linters --errors-only
Skipping mypy tests, mypy is not installed
Running pylint...
* Module apport-retrace
bin/apport-retrace:577:44: E0601: Using variable 'crashid' before assignment
(used-before-assignment)
make[1]: *** [debian/rules:23: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: binary] Error 2
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2051512/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2048136] Re: Please support systemd-coredump as core dump handler
** Changed in: apport Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2048136 Title: Please support systemd-coredump as core dump handler Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Committed Bug description: There can only be one system core dump handler on a Linux system and Apport is the Ubuntu default core dump handler. Besides Apport other tools offer coredump handler, in particular systemd-coredump. Due to Apport being installed on all Ubuntu system by default none of these alternate system can be installed. There has been some user request for this integration to work. Proper integration between Apport and systemd-coredump would offer a better experience to developers who want to use systemd-coredump. systemd- coredump and coredumpctl provide more documentation and have more users upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2048136/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2028879] Re: Lack of default dpkg diverts causes test_get_file_package_diversion to fail
** Changed in: apport Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2028879 Title: Lack of default dpkg diverts causes test_get_file_package_diversion to fail Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Bug description: tests/integration/test_packaging_apt_dpkg.py::test_get_file_package_diversion fails if it doesn't detect any dpkg diversions. Apparently something (possibly dash?) stopped diverting something, so now there are no diversions in the autopkgtest environment and therefore this test fails. One option is to add something that does divert something, eg. vim, to the test dependencies. This fixes the issue for now, but isn't really a permanent solution. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2028879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2031919] Re: /usr/share/apport/whoopsie-upload-all:TypeError:/usr/share/apport/whoopsie-upload-all@247:main:collect_info:process_report:add_gdb_info
** Changed in: apport Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2031919 Title: /usr/share/apport/whoopsie-upload- all:TypeError:/usr/share/apport/whoopsie-upload- all@247:main:collect_info:process_report:add_gdb_info Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Bug description: ``` Traceback (most recent call last): File "/usr/share/apport/whoopsie-upload-all", line 247, in main() File "/usr/share/apport/whoopsie-upload-all", line 229, in main stamps = collect_info() ^^ File "/usr/share/apport/whoopsie-upload-all", line 160, in collect_info res = process_report(r) ^ File "/usr/share/apport/whoopsie-upload-all", line 108, in process_report r.add_gdb_info() File "/usr/lib/python3/dist-packages/apport/report.py", line 930, in add_gdb_info environ["HOME"] = "/nonexistent" ~~~ TypeError: 'str' object does not support item assignment ``` The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.26.1-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/86a1629347349acf400d91c9774296b42c1ab1f3 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2031919/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2045705] Re: FTBFS with default Java 21
** Changed in: apport
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2045705
Title:
FTBFS with default Java 21
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
Triaged
Bug description:
Dear Maintainers,
The package apport ftbfs with default Java 21.
The relevant part of the build log:
---
running build_java_subdir
warning: [options] bootstrap class path not set in conjunction with -source 7
error: Source option 7 is no longer supported. Use 8 or later.
error: Target option 7 is no longer supported. Use 8 or later.
Traceback (most recent call last):
File "/<>/setup.py", line 119, in
DistUtilsExtra.auto.setup(
File "/usr/lib/python3/dist-packages/DistUtilsExtra/auto.py", line 125, in
setup
setuptools.setup(**attrs)
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 107, in
setup
return distutils.core.setup(**attrs)
^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
185, in setup
return run_commands(dist)
^^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
201, in run_commands
dist.run_commands()
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
969, in run_commands
self.run_command(cmd)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in
run_command
super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
988, in run_command
cmd_obj.run()
File
"/usr/lib/python3/dist-packages/setuptools/_distutils/command/build.py", line
131, in run
self.run_command(cmd_name)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line
318, in run_command
self.distribution.run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in
run_command
super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
988, in run_command
cmd_obj.run()
File "/<>/setuptools_apport/java.py", line 35, in run
subprocess.check_call(javac + glob.glob("com/ubuntu/apport/*.java"))
File "/usr/lib/python3.11/subprocess.py", line 413, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['javac', '-source', '7', '-target',
'7', 'com/ubuntu/apport/ApportUncaughtExceptionHandler.java']' returned
non-zero exit status 2.
E: pybuild pybuild:395: build: plugin distutils failed with: exit code=1:
/usr/bin/python3 setup.py build
dh_auto_build: error: pybuild --build -i python{version} -p "3.12 3.11"
returned exit code 13
make[1]: *** [debian/rules:12: override_dh_auto_build] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
2
Build finished at 2023-12-04T07:37:06Z
---
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2045705/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2043393] Re: Report.get_logind_session fails to determine session on cgroup2 systems
** Changed in: apport Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2043393 Title: Report.get_logind_session fails to determine session on cgroup2 systems Status in Apport: Fix Released Status in apport package in Ubuntu: Triaged Bug description: Ubuntu >= 22.04 uses only cgroup2 (Ubuntu 20.04 used both and Ubuntu 18.04 only cgroup version 1). Report.get_logind_session will fail to determine the logind session and always return None if only cgroup2 is used. get_logind_session searches for cgroup lines with "name=systemd:" and then extracts the session from "/session-". This worked in Ubuntu 16.04 but started failing in 18.04. Content of /proc/self/cgroup when printed from a terminal inside a Ubuntu desktop session: Ubuntu 16.04 (xenial) - ``` 12:cpuset:/ 11:perf_event:/ 10:pids:/user.slice/user-1000.slice 9:blkio:/ 8:hugetlb:/ 7:net_cls,net_prio:/ 6:cpu,cpuacct:/ 5:devices:/user.slice 4:freezer:/ 3:rdma:/ 2:memory:/ 1:name=systemd:/user.slice/user-1000.slice/session-c1.scope ``` Ubuntu 18.04 (bionic) - ``` 12:freezer:/ 11:net_cls,net_prio:/ 10:memory:/ 9:rdma:/ 8:cpu,cpuacct:/ 7:devices:/user.slice 6:perf_event:/ 5:cpuset:/ 4:pids:/user.slice/user-1000.slice/user@1000.service 3:hugetlb:/ 2:blkio:/ 1:name=systemd:/user.slice/user-1000.slice/user@1000.service/gnome-terminal-server.service 0::/user.slice/user-1000.slice/user@1000.service/gnome-terminal-server.service ``` Ubuntu 20.04 (focal) - ``` 13:memory:/user.slice/user-1000.slice/user@1000.service 12:perf_event:/ 11:misc:/ 10:pids:/user.slice/user-1000.slice/user@1000.service 9:hugetlb:/ 8:cpuset:/ 7:blkio:/ 6:devices:/user.slice 5:cpu,cpuacct:/ 4:freezer:/ 3:rdma:/ 2:net_cls,net_prio:/ 1:name=systemd:/user.slice/user-1000.slice/user@1000.service/apps.slice/apps-org.gnome.Terminal.slice/vte-spawn-ad936f4d-0d62-4ac4-bbd8-0e766d8a3b1f.scope 0::/user.slice/user-1000.slice/user@1000.service/apps.slice/apps-org.gnome.Terminal.slice/vte-spawn-ad936f4d-0d62-4ac4-bbd8-0e766d8a3b1f.scope ``` Ubuntu 22.04 (jammy) - ``` 0::/user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-0c3f8b02-b112-4cab-accc-764cbb223bac.scope ``` To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2043393/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2038650] Re: crash reports not sent to the Error Tracker
** Changed in: apport Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2038650 Title: crash reports not sent to the Error Tracker Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Lunar: Fix Released Status in apport source package in Mantic: Fix Released Bug description: [ Impact ] Crash reports aren't sent in when going through the UI, unless the user looks at the crash details. [ Test Plan ] 0) Make sure that error reporting is set to manual in the system settings (in Privacy screen) 1) Launch xeyes 2) pkill -11 xeyes 3) Click send in the apport dialog. DO NOT look at the details of the report. 4) ls -lh /var/crash/*xeyes* There should be 3 files: -rw-r- 1 bdmurray whoopsie 3370567 Oct 6 11:53 _usr_bin_xeyes.1000.crash -rw-rw-r-- 1 bdmurray bdmurray0 Oct 6 11:53 _usr_bin_xeyes.1000.upload -rw--- 1 whoopsie whoopsie 37 Oct 6 11:53 _usr_bin_xeyes.1000.uploaded [ Where problems could occur ] If the patch is wrong, we actually see similar bugs for other UI paths, e.g. ticking the "Remember this" box, etc. I tried to cover them during manual testing but I might have missed some. [ Other Info ] If possible I'd like for us not to wait too long for this to mature in -proposed, as this would affect crashes during the upgrade. [ Original report ] From what I can tell when I click the send button to send a crash report to the Error Tracker the crash doesn't actually get sent. My testing process follows: 1) Launch xeyes 2) pkill -11 xeyes 3) Click send in the apport dialog 4) ls -lh /var/crash I would expect there to be three files in /var/crash: -rw-r- 1 bdmurray whoopsie 3370567 Oct 6 11:53 _usr_bin_xeyes.1000.crash -rw-rw-r-- 1 bdmurray bdmurray0 Oct 6 11:53 _usr_bin_xeyes.1000.upload -rw--- 1 whoopsie whoopsie 37 Oct 6 11:53 _usr_bin_xeyes.1000.uploaded However, after step #4 I'm only seeing the .crash file and not a .upload or .uploaded. I was able to get the .upload and .uploaded files created if I chose to "View Report" and then click "Send". It's worth noting though that I did notice the size of the .crash file increase after clicking "Send" so some post-processing was done. ProblemType: BugDistroRelease: Ubuntu 23.10 Package: apport 2.27.0-0ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CrashReports: 640:1000:123:20944237:2023-10-06 12:10:47.809248208 +0100:2023-10-06 12:11:23.340030509 +0100:/var/crash/_usr_bin_mpv.1000.crash CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 12:12:46 2023 InstallationDate: Installed on 2022-01-07 (637 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: allSourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2038650/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850804] Re: Tab completion warnings with ubuntu-bug when using alias for ls
** Changed in: apport Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1850804 Title: Tab completion warnings with ubuntu-bug when using alias for ls Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Bug description: When running ubuntu-bug on the command line, and tab completing the package name, the following warnings are printed: /usr/share/apport/symptoms/dist-upgrade.py: No such file or directory grep: /usr/share/apport/symptoms/release-upgrade.py: No such file or directory This happens when following alias is set: alias ls='ls -N --color=yes --time-style=long-iso' ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: apport 2.20.11-0ubuntu8.1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportLog: ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Oct 31 10:54:43 2019 InstallationDate: Installed on 2017-08-16 (805 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to eoan on 2019-10-04 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1850804/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2044129] Re: ubuntu-bug does not allow for reporting a bug in "other software" manually giving a symptom description
** Changed in: apport Milestone: None => 2.28.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2044129 Title: ubuntu-bug does not allow for reporting a bug in "other software" manually giving a symptom description Status in Apport: Triaged Status in apport package in Ubuntu: Triaged Bug description: the man page of ubuntu-bug/apport-bug (what is the difference? why am I shown the manpage of apport-bug when typing man ubuntu-bug?) says running apport-bug without arguments results in showing me a list of symptoms. When I try to report a bug in some general program that is not related to the other 9 categories - which is most of the 1 apps in Ubuntu - I must chose "Other Problem" - but in contrary to the man page that tells me I am asked about further things, I only get "You need to specific the pakacge or PID". I currently try to report a bug in the things that identifies itself as "Ubuntu Software" in the Dock, but I have no idea what its correct program or package name is, and have no idea how to find that. In PS there is no process with "ubuntu" or "software" in its name. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: apport 2.27.0-0ubuntu5 ProcVersionSignature: Ubuntu 6.2.0-1015.15-lowlatency 6.2.16 Uname: Linux 6.2.0-1015-lowlatency x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 21 14:38:42 2023 InstallationDate: Installed on 2023-08-21 (92 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: apport UpgradeStatus: Upgraded to mantic on 2023-11-05 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2044129/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2045705] Re: FTBFS with default Java 21
** Changed in: apport (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2045705
Title:
FTBFS with default Java 21
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
Fix Committed
Bug description:
Dear Maintainers,
The package apport ftbfs with default Java 21.
The relevant part of the build log:
---
running build_java_subdir
warning: [options] bootstrap class path not set in conjunction with -source 7
error: Source option 7 is no longer supported. Use 8 or later.
error: Target option 7 is no longer supported. Use 8 or later.
Traceback (most recent call last):
File "/<>/setup.py", line 119, in
DistUtilsExtra.auto.setup(
File "/usr/lib/python3/dist-packages/DistUtilsExtra/auto.py", line 125, in
setup
setuptools.setup(**attrs)
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 107, in
setup
return distutils.core.setup(**attrs)
^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
185, in setup
return run_commands(dist)
^^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
201, in run_commands
dist.run_commands()
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
969, in run_commands
self.run_command(cmd)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in
run_command
super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
988, in run_command
cmd_obj.run()
File
"/usr/lib/python3/dist-packages/setuptools/_distutils/command/build.py", line
131, in run
self.run_command(cmd_name)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line
318, in run_command
self.distribution.run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in
run_command
super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
988, in run_command
cmd_obj.run()
File "/<>/setuptools_apport/java.py", line 35, in run
subprocess.check_call(javac + glob.glob("com/ubuntu/apport/*.java"))
File "/usr/lib/python3.11/subprocess.py", line 413, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['javac', '-source', '7', '-target',
'7', 'com/ubuntu/apport/ApportUncaughtExceptionHandler.java']' returned
non-zero exit status 2.
E: pybuild pybuild:395: build: plugin distutils failed with: exit code=1:
/usr/bin/python3 setup.py build
dh_auto_build: error: pybuild --build -i python{version} -p "3.12 3.11"
returned exit code 13
make[1]: *** [debian/rules:12: override_dh_auto_build] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
2
Build finished at 2023-12-04T07:37:06Z
---
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2045705/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2043393] Re: Report.get_logind_session fails to determine session on cgroup2 systems
** Changed in: apport (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2043393 Title: Report.get_logind_session fails to determine session on cgroup2 systems Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Committed Bug description: Ubuntu >= 22.04 uses only cgroup2 (Ubuntu 20.04 used both and Ubuntu 18.04 only cgroup version 1). Report.get_logind_session will fail to determine the logind session and always return None if only cgroup2 is used. get_logind_session searches for cgroup lines with "name=systemd:" and then extracts the session from "/session-". This worked in Ubuntu 16.04 but started failing in 18.04. Content of /proc/self/cgroup when printed from a terminal inside a Ubuntu desktop session: Ubuntu 16.04 (xenial) - ``` 12:cpuset:/ 11:perf_event:/ 10:pids:/user.slice/user-1000.slice 9:blkio:/ 8:hugetlb:/ 7:net_cls,net_prio:/ 6:cpu,cpuacct:/ 5:devices:/user.slice 4:freezer:/ 3:rdma:/ 2:memory:/ 1:name=systemd:/user.slice/user-1000.slice/session-c1.scope ``` Ubuntu 18.04 (bionic) - ``` 12:freezer:/ 11:net_cls,net_prio:/ 10:memory:/ 9:rdma:/ 8:cpu,cpuacct:/ 7:devices:/user.slice 6:perf_event:/ 5:cpuset:/ 4:pids:/user.slice/user-1000.slice/user@1000.service 3:hugetlb:/ 2:blkio:/ 1:name=systemd:/user.slice/user-1000.slice/user@1000.service/gnome-terminal-server.service 0::/user.slice/user-1000.slice/user@1000.service/gnome-terminal-server.service ``` Ubuntu 20.04 (focal) - ``` 13:memory:/user.slice/user-1000.slice/user@1000.service 12:perf_event:/ 11:misc:/ 10:pids:/user.slice/user-1000.slice/user@1000.service 9:hugetlb:/ 8:cpuset:/ 7:blkio:/ 6:devices:/user.slice 5:cpu,cpuacct:/ 4:freezer:/ 3:rdma:/ 2:net_cls,net_prio:/ 1:name=systemd:/user.slice/user-1000.slice/user@1000.service/apps.slice/apps-org.gnome.Terminal.slice/vte-spawn-ad936f4d-0d62-4ac4-bbd8-0e766d8a3b1f.scope 0::/user.slice/user-1000.slice/user@1000.service/apps.slice/apps-org.gnome.Terminal.slice/vte-spawn-ad936f4d-0d62-4ac4-bbd8-0e766d8a3b1f.scope ``` Ubuntu 22.04 (jammy) - ``` 0::/user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-0c3f8b02-b112-4cab-accc-764cbb223bac.scope ``` To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2043393/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052739] Re: tzdata 2024a release
Some time ago, I converted all the manual tests from the SRU documentation into autopkgtests. For example https://git.launchpad.net/~ubuntu-core- dev/ubuntu/+source/tzdata/commit/?id=a70967f356720a37571dd0a301c3c99bea11abc7 implements the python3-icu test mentioned on the SRU documentation. The python3-icu uses bin:tzdata-icu (or bin:tzdata on older releases). The python3-icu test is about verifying that python3-icu does not break after tzdata was updated. I am also driving the updates for ESM by preparing them for bionic, xenial, and trusty: https://code.launchpad.net/~ubuntu-core- dev/ubuntu/+source/tzdata/+git/tzdata -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2052739 Title: tzdata 2024a release Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Focal: Confirmed Status in tzdata source package in Jammy: Confirmed Status in tzdata source package in Mantic: Confirmed Bug description: [ Impact ] The 2024a release contains the following changes: * Kazakhstan unifies on UTC+5 beginning 2024-03-01. * Palestine springs forward a week later after Ramadan. * zic no longer pretends to support indefinite-past DST. * localtime no longer mishandles Ciudad Juárez in 2422. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2024a * python-icu: test_2024a (only for focal and newer) So the test plan is to check that the autopkgtest succeeds. [ Other Info ] The autopkgtest for chrony is flaky on jammy and newer (see bug #2002910). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054902] Re: apport test error: /bin/bash not found
** Also affects: apport
Importance: Undecided
Status: New
** Changed in: apport
Importance: Undecided => High
** Changed in: apport
Milestone: None => 2.28.1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2054902
Title:
apport test error: /bin/bash not found
Status in Apport:
New
Status in apport package in Ubuntu:
New
Bug description:
This looks like fallout from the completion of usrmerge.
https://autopkgtest.ubuntu.com/packages/apport
=== FAILURES
===
367s ___ T.test_get_file_package
367s
367s self =
367s
367s def test_get_file_package(self):
367s """get_file_package() on installed files."""
367s > self.assertEqual(impl.get_file_package("/bin/bash"), "bash")
367s E AssertionError: None != 'bash'
367s
367s tests/integration/test_packaging_apt_dpkg.py:158: AssertionError
367s ___ T.test_get_files
___
367s
367s self =
367s
367s def test_get_files(self):
367s """get_files()."""
367s self.assertRaises(ValueError, impl.get_files, "nonexisting")
367s > self.assertIn("/bin/bash", impl.get_files("bash"))
367s E AssertionError: '/bin/bash' not found in ['/.', '/etc',
'/etc/bash.bashrc', '/etc/skel', '/etc/skel/.bash_logout', '/etc/skel/.bashrc',
'/etc/skel/.profile', '/usr', '/usr/bin', '/usr/bin/bash', '/usr/bin/bashbug',
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2054902/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052295] Re: autopkgtest unshare-qemuwrapper failing on amd64
This has been fixed in sbuild 0.85.6 via https://salsa.debian.org/debian/sbuild/-/merge_requests/57 ** Changed in: sbuild (Ubuntu Noble) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cpio in Ubuntu. https://bugs.launchpad.net/bugs/2052295 Title: autopkgtest unshare-qemuwrapper failing on amd64 Status in cpio package in Ubuntu: Fix Released Status in sbuild package in Ubuntu: Fix Released Status in cpio source package in Noble: Fix Released Status in sbuild source package in Noble: Fix Released Status in cpio package in Debian: Fix Released Bug description: While watching Noble openssh migration, I saw this test failing and marking amd64 as regression. Log : https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- noble/noble/amd64/s/sbuild/20240201_000224_2a4c6@/log.gz Relevant part of the log: 1565s Chrooting into /tmp/mmdebstrap.bsT6cbiWIs/ 1565s Setting up cpio (2.15+dfsg-1) ... 1565s update-alternatives: error: alternative path /bin/mt-gnu doesn't exist 1565s dpkg: error processing package cpio (--configure): 1565s installed cpio package post-installation script subprocess returned error exit status 2 It can be reproduced locally, too. The most recent test working is from 01/08/2024: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/s/sbuild/20240108_203545_af566@/log.gz The cpio version in the immediately log above is lower. The same (working) part is: 2188s Chrooting into /tmp/mmdebstrap.qSEp1fU8f3/ 2188s Setting up cpio (2.14+dfsg-1) ... 2188s update-alternatives: using /bin/mt-gnu to provide /bin/mt (mt) in auto mode cpio diff : https://launchpadlibrarian.net/709448424/cpio_2.14+dfsg-1_2.15+dfsg-1.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpio/+bug/2052295/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052739] Re: tzdata 2024a release
Verified successful autopkgtest on https://autopkgtest.ubuntu.com/packages/tzdata: mantic: * amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/t/tzdata/20240223_012444_0f113@/log.gz * arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/arm64/t/tzdata/20240223_001555_7ca29@/log.gz * armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/armhf/t/tzdata/20240223_023357_ee94e@/log.gz * ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/ppc64el/t/tzdata/20240223_001617_0822f@/log.gz * s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/s390x/t/tzdata/20240223_014437_7f723@/log.gz jammy: * amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/t/tzdata/20240223_001452_bda5d@/log.gz * arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/t/tzdata/20240222_232655_62fd6@/log.gz * armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/armhf/t/tzdata/20240222_235619_bdf0b@/log.gz * ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/t/tzdata/20240222_232100_67fd5@/log.gz * s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/t/tzdata/20240223_000331_11f77@/log.gz focal: * amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/t/tzdata/20240223_001845_45d0c@/log.gz * arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/t/tzdata/20240222_235449_caab5@/log.gz * armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/t/tzdata/20240222_235714_29cd7@/log.gz * ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/t/tzdata/20240222_231755_6a4ad@/log.gz * s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/t/tzdata/20240222_233135_dc0df@/log.gz ** Tags removed: verification-needed verification-needed-focal verification-needed-jammy verification-needed-mantic ** Tags added: verification-done verification-done-focal verification-done-jammy verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2052739 Title: tzdata 2024a release Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed Status in tzdata source package in Mantic: Fix Committed Bug description: [ Impact ] The 2024a release contains the following changes: * Kazakhstan unifies on UTC+5 beginning 2024-03-01. * Palestine springs forward a week later after Ramadan. * zic no longer pretends to support indefinite-past DST. * localtime no longer mishandles Ciudad Juárez in 2422. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2024a * python-icu: test_2024a (only for focal and newer) So the test plan is to check that the autopkgtest succeeds. [ Other Info ] The autopkgtest for chrony is flaky on jammy and newer (see bug #2002910). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055055] Re: unmkinitramfs: wrong and unneeded count= in a dd call
Thank you for taking the time to report this bug and contributing to Ubuntu. The count_bytes solution looks better to me. I see four dd calls in unmkinitramfs. Can you check those as well? Debian is affected as well. If you can spare the time, please submit your patch to https://salsa.debian.org/kernel-team/initramfs- tools/-/merge_requests as well. ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Low ** Changed in: initramfs-tools (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2055055 Title: unmkinitramfs: wrong and unneeded count= in a dd call Status in initramfs-tools package in Ubuntu: Triaged Bug description: Speaking about this line in unmkinitramfs: 113: dd < "$initramfs" skip=$start count=$((end - start)) iflag=skip_bytes 2> /dev/null | dd's block size is 512 by default. iflag=skip_bytes does not change that. Both $end and $start are byte-offsets. Hence the count is ($end-$start) blocks or ($end-$start)*512 bytes which is wrong. Anyways, the script just works because the count is unneeded: dd's output is piped into cpio which stops on the first end-of-archive marker, no matter how much data it is fed with. I think it is the best to just drop the count option (the patch is attached). If there is still a need to explicitly limit data fed to cpio, dd is impractical in this case. The only way to count= in bytes is bs=1, which makes dd extremely slow on lengthy data chunks. For example ubuntu-23.10.1-desktop-amd64.iso contains initrd with embedded uncompressed cpio archives of such sizes: 77312 7200768 78615040 A combo of dd+head could be used intead to skip and count respectively: 113: dd < "$initramfs" skip=$start iflag=skip_bytes 2> /dev/null | head -c$((end - start)) | Or even tail+head: 113: tail -c+$((start+1)) "$initramfs" | head -c$((end - start)) | To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2055055/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
Commit 4e7e25c4f ("configure_networking: move the "are we done" check to
end of loop body") from 0.142ubuntu15 allows this bug to appear. This
patch was for fixing bug #2037202.
Can you provide the content of /proc/cmdline?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
Status in initramfs-tools package in Ubuntu:
Confirmed
Status in open-iscsi package in Ubuntu:
Confirmed
Bug description:
we have a bad interaction between initramfs-tools and open-iscsi,
resulting in the boot interface not being configured.
when the iscsi has a static address, the script `local-top/iscsi` from
open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi
interface. The existence of this file makes configure_networking()
skip configuring the BOOTIF later due to this code in
`scripts/functions`:
for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do
if [ -e "$x" ]; then
IP=done
break
fi
done
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
So BOOTIF is set which should translate to DEVICE being set. Let me come
up with a patch.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
Status in initramfs-tools package in Ubuntu:
Confirmed
Status in open-iscsi package in Ubuntu:
Confirmed
Bug description:
we have a bad interaction between initramfs-tools and open-iscsi,
resulting in the boot interface not being configured.
when the iscsi has a static address, the script `local-top/iscsi` from
open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi
interface. The existence of this file makes configure_networking()
skip configuring the BOOTIF later due to this code in
`scripts/functions`:
for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do
if [ -e "$x" ]; then
IP=done
break
fi
done
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055718] Re: timezone changed unexpectedly from EST to America/Adak
** Summary changed: - timezone changed unexpectedly + timezone changed unexpectedly from EST to America/Adak -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2055718 Title: timezone changed unexpectedly from EST to America/Adak Status in tzdata package in Ubuntu: Confirmed Bug description: A user reported this regression on https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739: UPDATE: I don't think it's a regression anymore, see comment #5 """ Hello. After automatic upgrade of tzdata from 2023c-0ubuntu0.22.04.2 to 2024a-0ubuntu0.22.04 the previously set EST time zone was automatically changed to "America/Adak" or "America/Indiana/Indianapolis" on all our servers (50+). Look like a bug in tzdata configure script. """ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2055718/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055718] Re: timezone changed unexpectedly from EST to America/Adak
The test case can be distilled down to: ``` ln -sf /usr/share/zoneinfo/EST /etc/localtime dpkg-reconfigure --frontend noninteractive tzdata ``` On Ubuntu 22.04 (jammy) convert_timezone() in tzdata.config maps EST to America/Indianapolis which is a symlink to America/Indiana/Indianapolis. Bug 1: America/Indianapolis is not an option in debconf and therefore the first geographic area "Adak" is used. Possible bug 2: convert_timezone() in tzdata.config maps EST to America/Indiana/Indianapolis, but EST is not a symlink to America/Indiana/Indianapolis. If I saw that correctly, EST does not take daylight saving into account. ** Summary changed: - timezone changed unexpectedly from EST to America/Adak + timezone changed unexpectedly from EST to America/Adak or America/Indiana/Indianapolis ** Changed in: tzdata (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2055718 Title: timezone changed unexpectedly from EST to America/Adak or America/Indiana/Indianapolis Status in tzdata package in Ubuntu: Triaged Bug description: A user reported this regression on https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739: UPDATE: I don't think it's a regression anymore, see comment #5 """ Hello. After automatic upgrade of tzdata from 2023c-0ubuntu0.22.04.2 to 2024a-0ubuntu0.22.04 the previously set EST time zone was automatically changed to "America/Adak" or "America/Indiana/Indianapolis" on all our servers (50+). Look like a bug in tzdata configure script. """ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2055718/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055718] Re: timezone changed unexpectedly from EST to America/Adak or America/Indiana/Indianapolis
Commit eee799c9b97512f29eb5854ff965dbad79424242 ("Get rid of old SystemV
timezones, as this has been fully removed upstream. Convert existing
configuration to the "new" America/* names.") changed the mapping of EST
from SystemV/EST5 to America/Indianapolis in 2020b-1. Therefore Ubuntu
20.04 "jammy" and newer are affected.
Vladimir, would updating EST to America/Indiana/Indianapolis be okay?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/2055718
Title:
timezone changed unexpectedly from EST to America/Adak or
America/Indiana/Indianapolis
Status in tzdata package in Ubuntu:
Triaged
Bug description:
A user reported this regression on
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739:
UPDATE: I don't think it's a regression anymore, see comment #5
"""
Hello.
After automatic upgrade of tzdata from 2023c-0ubuntu0.22.04.2 to
2024a-0ubuntu0.22.04
the previously set EST time zone was automatically changed to "America/Adak"
or "America/Indiana/Indianapolis" on all our servers (50+).
Look like a bug in tzdata configure script.
"""
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2055718/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
Please test the attached patch. (My initial patch was shorter. It was
using grep but grep is only available in the initramfs when using
busybox).
** Patch added: "0001-Fix-configuring-BOOTIF-when-using-iSCSI.patch"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+attachment/5753358/+files/0001-Fix-configuring-BOOTIF-when-using-iSCSI.patch
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => High
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed => Triaged
** Changed in: open-iscsi (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
Status in initramfs-tools package in Ubuntu:
Triaged
Status in open-iscsi package in Ubuntu:
Invalid
Bug description:
we have a bad interaction between initramfs-tools and open-iscsi,
resulting in the boot interface not being configured.
when the iscsi has a static address, the script `local-top/iscsi` from
open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi
interface. The existence of this file makes configure_networking()
skip configuring the BOOTIF later due to this code in
`scripts/functions`:
for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do
if [ -e "$x" ]; then
IP=done
break
fi
done
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981385] Re: initrd lacks modules to mount boot image from http boot
Re-open due to regression in noble.
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => Medium
** Changed in: initramfs-tools (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1981385
Title:
initrd lacks modules to mount boot image from http boot
Status in initramfs-tools package in Ubuntu:
Fix Committed
Status in initramfs-tools source package in Jammy:
Fix Released
Bug description:
[ Impact ]
* If you use UEFI http boot to boot an image (rather than an EFI
executable) and get all the way to a normal userspace, you can
access the boot image as /dev/pmem0. But this is not accessible in
the initrd; presumably some modules are missing.
* This is desirable because then you can just feed an installer ISO to
a machine via http boot and the installer just works as normal
* Add support for physical pmem devices, and simulation thereof with
the memmap kernel command line parameter
* The initrd is larger
[ Test Plan ]
* unpack an initrd on a Jammy system with the generic kernel
metapackage with unmkinitramfs
* observe that the directories kernel/drivers/{nvdimm,dax,acpi/nfit}
are not present
* install the updated initramfs-tools packages from proposed
* again unpack an initrd on a Jammy system with the generic kernel
metapackage with unmkinitramfs
* observe that the directories kernel/drivers/{nvdimm,dax,acpi/nfit}
are present now
* reboot to confirm that the system still boots
* modify /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT to contain a
memmap entry - memmap=1G!4G seems to work on many systems over 4G of
RAM, or do `dmesg | grep BIOS-e820` to observe the memory regions
and select a usable one.
* update-grub and reboot again
* a /dev/pmem device should now be present on the system
[ Where problems could occur ]
* The growth of the files in /boot will accelerate issues for users
who have a dedicated boot partition that is not large enough
[ Other Info ]
* Details on the memmap kernel command line parameter:
https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt
* PMEM simulation with memmap:
https://docs.pmem.io/persistent-memory/getting-started-guide/creating-development-environments/linux-environments/linux-memmap
[ Original Bug Description ]
If you use UEFI http boot to boot an image (rather than an EFI
executable) and get all the way to a normal userspace, you can access
the boot image as /dev/pmem0. But this is not accessible in the
initrd; presumably some modules are missing. Dimitri added some
modules that are clearly going to be necessary (kernel/drivers/nvdimm)
in 0.140ubuntu14 and I added kernel/drivers/dax too in local
experiments but this appears not to be enough to get it to appear.
This is desirable because then you can just feed an installer ISO to a
machine via http boot and the installer just works as normal (the
speed and, uh, quality, of the implementation of HTTP in a given
machine's firmware may mean this isn't always the best option but it
would be nice if it worked in case someone's machine actually does
this well).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1981385/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054171] Re: dhcpcd hook breaks when using libc6-prof's libc.so.6
** Changed in: initramfs-tools (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2054171 Title: dhcpcd hook breaks when using libc6-prof's libc.so.6 Status in initramfs-tools package in Ubuntu: Fix Committed Bug description: I have the libc6-prof package installed to provide a frame pointer enabled libc.so.6. I have a custom configuration file in /etc/ld.so.conf.d putting /lib/libc6-prof/x86_64-linux-gnu at the front of the dynamic linker search paths. (I really like having frame pointers!) This confuses the `multiarch_dir=$(ldd /usr/sbin/dhcpcd | sed -En 's;^.*/lib/([^/]+)/libc\.so\..*$;\1;p')` line in /usr/share/initramfs- tools/hooks/dhcpcd because the libc.so.6 path is different. Default ldd output: ``` ldd /usr/sbin/dhcpcd linux-vdso.so.1 (0x7fff9a735000) libcrypto.so.3 => /lib/x86_64-linux-gnu/libcrypto.so.3 (0x7f50d280) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f50d240) /lib64/ld-linux-x86-64.so.2 (0x7f50d2f27000) ``` My ldd output: ``` ldd /usr/sbin/dhcpcd linux-vdso.so.1 (0x7fff802db000) libcrypto.so.3 => /lib/x86_64-linux-gnu/libcrypto.so.3 (0x7fce87e0) libc.so.6 => /lib/libc6-prof/x86_64-linux-gnu/libc.so.6 (0x7fce87a0) /lib64/ld-linux-x86-64.so.2 (0x7fce88514000) ``` ``` -libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f50d240) +libc.so.6 => /lib/libc6-prof/x86_64-linux-gnu/libc.so.6 (0x7fce87a0) ``` When running the modified search paths, `ldd /usr/sbin/dhcpcd | sed -En 's;^.*/lib/([^/]+)/libc\.so\..*$;\1;p'` evaluates to an empty string and exits 0. This results in `copy_exec "/usr/lib//dhcpcd/dev/udev.so"`, which breaks that script. This in turn breaks initramfs. ``` Processing triggers for linux-image-6.5.0-17-generic (6.5.0-17.17) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-6.5.0-17-generic E: /usr/share/initramfs-tools/hooks/dhcpcd failed with return 1. update-initramfs: failed for /boot/initrd.img-6.5.0-17-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-6.5.0-17-generic (--configure): installed linux-image-6.5.0-17-generic package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-image-6.5.0-17-generic E: Sub-process /usr/bin/dpkg returned an error code (1) ``` I can work around the issue by hacking up the dhcpcd hook or by modifying the dynamic link path search order, running `ldconfig`, then `update-initramfs -u`. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2054171/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055055] Re: unmkinitramfs: wrong and unneeded count= in a dd call
** Changed in: initramfs-tools (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2055055 Title: unmkinitramfs: wrong and unneeded count= in a dd call Status in initramfs-tools package in Ubuntu: Fix Committed Bug description: Speaking about this line in unmkinitramfs: 113: dd < "$initramfs" skip=$start count=$((end - start)) iflag=skip_bytes 2> /dev/null | dd's block size is 512 by default. iflag=skip_bytes does not change that. Both $end and $start are byte-offsets. Hence the count is ($end-$start) blocks or ($end-$start)*512 bytes which is wrong. Anyways, the script just works because the count is unneeded: dd's output is piped into cpio which stops on the first end-of-archive marker, no matter how much data it is fed with. I think it is the best to just drop the count option (the patch is attached). If there is still a need to explicitly limit data fed to cpio, dd is impractical in this case. The only way to count= in bytes is bs=1, which makes dd extremely slow on lengthy data chunks. For example ubuntu-23.10.1-desktop-amd64.iso contains initrd with embedded uncompressed cpio archives of such sizes: 77312 7200768 78615040 A combo of dd+head could be used intead to skip and count respectively: 113: dd < "$initramfs" skip=$start iflag=skip_bytes 2> /dev/null | head -c$((end - start)) | Or even tail+head: 113: tail -c+$((start+1)) "$initramfs" | head -c$((end - start)) | To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2055055/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056194] Re: Networking broken in early boot on Oracle Native instances
** Project changed: initramfs-tools => initramfs-tools (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2056194
Title:
Networking broken in early boot on Oracle Native instances
Status in cloud-images:
New
Status in cloud-init package in Ubuntu:
New
Status in initramfs-tools package in Ubuntu:
New
Bug description:
BACKGROUND:
cloud-init-local.service runs before networking has started. On non-
Oracle platforms, before networking has come up, cloud-init will
create an ephemeral connection to the cloud's IMDS using DHCP to
retrieve instance metadata. On Oracle, this normally isn't necessary
as we boot with connectivity to the IMDS out of the box. This can be
seen in the following Jammy instance using an SR-IOV NIC:
2024-03-05 14:09:05,351 - url_helper.py[DEBUG]: [0/1] open
'http://169.254.169.254/opc/v2/instance/' with {'url':
'http://169.254.169.254/opc/v2/instance/', 'stream': False, 'allow_redirects':
True, 'method': 'GET', 'timeout': 5.0, 'headers': {'User-Agent'
: 'Cloud-Init/23.3.3-0ubuntu0~22.04.1', 'Authorization': 'Bearer Oracle'}}
configuration
2024-03-05 14:09:05,362 - url_helper.py[DEBUG]: Read from
http://169.254.169.254/opc/v2/instance/ (200, 2663b) after 1 attempts
2024-03-05 14:09:05,362 - ephemeral.py[DEBUG]: Skip ephemeral DHCP setup,
instance has connectivity to {'url': 'http://169.254.169.254/opc/v2/instance/',
'headers': {'Authorization': 'Bearer Oracle'}, 'timeout': 5}
2024-03-05 14:09:05,362 - url_helper.py[DEBUG]: [0/3] open
'http://169.254.169.254/opc/v2/instance/' with {'url':
'http://169.254.169.254/opc/v2/instance/', 'stream': False, 'allow_redirects':
True, 'method': 'GET', 'headers': {'User-Agent': 'Cloud-Init/23
.3.3-0ubuntu0~22.04.1', 'Authorization': 'Bearer Oracle'}} configuration
2024-03-05 14:09:05,368 - url_helper.py[DEBUG]: Read from
http://169.254.169.254/opc/v2/instance/ (200, 2663b) after 1 attempts
Notice the "Skip ephemeral DHCP setup, instance has connectivity".
This means that cloud-init has determined that it already has
connectivity and doesn't need to do any additional setup to retrieve
data from the IMDS.
We can also see the same behavior on a Noble paravirtualized instance:
2024-03-01 20:51:33,482 - url_helper.py[DEBUG]: [0/1] open
'http://169.254.169.254/opc/v2/instance/' with {'url':
'http://169.254.169.254/opc/v2/instance/', 'stream': False, 'allow_redirects':
True, 'method': 'GET', 'timeout': 5.0, 'headers': {'User-Agent':
'Cloud-Init/24.1~7g54599148-0ubuntu1', 'Authorization': 'Bearer Oracle'}}
configuration
2024-03-01 20:51:33,488 - url_helper.py[DEBUG]: Read from
http://169.254.169.254/opc/v2/instance/ (200, 3067b) after 1 attempts
2024-03-01 20:51:33,488 - ephemeral.py[DEBUG]: Skip ephemeral DHCP setup,
instance has connectivity to {'url': 'http://169.254.169.254/opc/v2/instance/',
'headers': {'Authorization': 'Bearer Oracle'}, 'timeout': 5}
2024-03-01 20:51:33,489 - url_helper.py[DEBUG]: [0/3] open
'http://169.254.169.254/opc/v2/instance/' with {'url':
'http://169.254.169.254/opc/v2/instance/', 'stream': False, 'allow_redirects':
True, 'method': 'GET', 'headers': {'User-Agent':
'Cloud-Init/24.1~7g54599148-0ubuntu1', 'Authorization': 'Bearer Oracle'}}
configuration
2024-03-01 20:51:33,500 - url_helper.py[DEBUG]: Read from
http://169.254.169.254/opc/v2/instance/ (200, 3067b) after 1 attempts
2024-03-01 20:51:33,501 - util.py[DEBUG]: Writing to
/run/cloud-init/cloud-id-oracle - wb: [644] 7 bytes
PROBLEM:
On a Noble instance using Hardware-assisted (SR-IOV) networking, this
is not working. cloud-init-local.service no longer has immediate
connectivity to the IMDS. Since it cannot connect, in then attempts to
create an ephemeral connection to the IMDS using DHCP. It is able to
obtain a DHCP lease, but then when it tries to connect to the IMDS,
the call just hangs. The call has no timeout, so this results in an
instance that cannot be logged into even via the serial console
because cloud-init is blocking the rest of boot. A simple cloud-init
workaround is to add something along the lines of `timeout=2` to
https://github.com/canonical/cloud-
init/blob/main/cloudinit/sources/DataSourceOracle.py#L349 . This
allows cloud-init to boot. Looking at the logs, we can see that cloud-
init is unable to connect to the IMDS:
2024-03-05 14:23:54,836 - ephemeral.py[DEBUG]: Received dhcp lease on ens3
for 10.0.0.133/255.255.255.0
2024-03-05 14:23:54,837 - url_helper.py[DEBUG]: [0/3] open
'http://169.254.169.254/opc/v2/instance/' with {'url':
'http://169.254.169.254/opc/v2/instance/', 'stream': False, 'allow_redirects':
True, 'method': 'GET', 'timeout': 2.0, 'headers': {'User-Agent':
'Cloud-Init/24.1~7g54599148-0ubuntu1', 'Authorization': 'Bearer Oracle'}}
configuration
2024-03-05 14:23:56,841 - url_help
[Touch-packages] [Bug 2056194] Re: Networking broken in early boot on Oracle Native instances
Please test the attached patch. This patch adds a dhcpcd hook to the
initramfs to set the interface MTU.
** Patch added: "0001-Set-interface-MTU.patch"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056194/+attachment/5753730/+files/0001-Set-interface-MTU.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2056194
Title:
Networking broken in early boot on Oracle Native instances
Status in cloud-images:
New
Status in cloud-init package in Ubuntu:
New
Status in initramfs-tools package in Ubuntu:
New
Bug description:
BACKGROUND:
cloud-init-local.service runs before networking has started. On non-
Oracle platforms, before networking has come up, cloud-init will
create an ephemeral connection to the cloud's IMDS using DHCP to
retrieve instance metadata. On Oracle, this normally isn't necessary
as we boot with connectivity to the IMDS out of the box. This can be
seen in the following Jammy instance using an SR-IOV NIC:
2024-03-05 14:09:05,351 - url_helper.py[DEBUG]: [0/1] open
'http://169.254.169.254/opc/v2/instance/' with {'url':
'http://169.254.169.254/opc/v2/instance/', 'stream': False, 'allow_redirects':
True, 'method': 'GET', 'timeout': 5.0, 'headers': {'User-Agent'
: 'Cloud-Init/23.3.3-0ubuntu0~22.04.1', 'Authorization': 'Bearer Oracle'}}
configuration
2024-03-05 14:09:05,362 - url_helper.py[DEBUG]: Read from
http://169.254.169.254/opc/v2/instance/ (200, 2663b) after 1 attempts
2024-03-05 14:09:05,362 - ephemeral.py[DEBUG]: Skip ephemeral DHCP setup,
instance has connectivity to {'url': 'http://169.254.169.254/opc/v2/instance/',
'headers': {'Authorization': 'Bearer Oracle'}, 'timeout': 5}
2024-03-05 14:09:05,362 - url_helper.py[DEBUG]: [0/3] open
'http://169.254.169.254/opc/v2/instance/' with {'url':
'http://169.254.169.254/opc/v2/instance/', 'stream': False, 'allow_redirects':
True, 'method': 'GET', 'headers': {'User-Agent': 'Cloud-Init/23
.3.3-0ubuntu0~22.04.1', 'Authorization': 'Bearer Oracle'}} configuration
2024-03-05 14:09:05,368 - url_helper.py[DEBUG]: Read from
http://169.254.169.254/opc/v2/instance/ (200, 2663b) after 1 attempts
Notice the "Skip ephemeral DHCP setup, instance has connectivity".
This means that cloud-init has determined that it already has
connectivity and doesn't need to do any additional setup to retrieve
data from the IMDS.
We can also see the same behavior on a Noble paravirtualized instance:
2024-03-01 20:51:33,482 - url_helper.py[DEBUG]: [0/1] open
'http://169.254.169.254/opc/v2/instance/' with {'url':
'http://169.254.169.254/opc/v2/instance/', 'stream': False, 'allow_redirects':
True, 'method': 'GET', 'timeout': 5.0, 'headers': {'User-Agent':
'Cloud-Init/24.1~7g54599148-0ubuntu1', 'Authorization': 'Bearer Oracle'}}
configuration
2024-03-01 20:51:33,488 - url_helper.py[DEBUG]: Read from
http://169.254.169.254/opc/v2/instance/ (200, 3067b) after 1 attempts
2024-03-01 20:51:33,488 - ephemeral.py[DEBUG]: Skip ephemeral DHCP setup,
instance has connectivity to {'url': 'http://169.254.169.254/opc/v2/instance/',
'headers': {'Authorization': 'Bearer Oracle'}, 'timeout': 5}
2024-03-01 20:51:33,489 - url_helper.py[DEBUG]: [0/3] open
'http://169.254.169.254/opc/v2/instance/' with {'url':
'http://169.254.169.254/opc/v2/instance/', 'stream': False, 'allow_redirects':
True, 'method': 'GET', 'headers': {'User-Agent':
'Cloud-Init/24.1~7g54599148-0ubuntu1', 'Authorization': 'Bearer Oracle'}}
configuration
2024-03-01 20:51:33,500 - url_helper.py[DEBUG]: Read from
http://169.254.169.254/opc/v2/instance/ (200, 3067b) after 1 attempts
2024-03-01 20:51:33,501 - util.py[DEBUG]: Writing to
/run/cloud-init/cloud-id-oracle - wb: [644] 7 bytes
PROBLEM:
On a Noble instance using Hardware-assisted (SR-IOV) networking, this
is not working. cloud-init-local.service no longer has immediate
connectivity to the IMDS. Since it cannot connect, in then attempts to
create an ephemeral connection to the IMDS using DHCP. It is able to
obtain a DHCP lease, but then when it tries to connect to the IMDS,
the call just hangs. The call has no timeout, so this results in an
instance that cannot be logged into even via the serial console
because cloud-init is blocking the rest of boot. A simple cloud-init
workaround is to add something along the lines of `timeout=2` to
https://github.com/canonical/cloud-
init/blob/main/cloudinit/sources/DataSourceOracle.py#L349 . This
allows cloud-init to boot. Looking at the logs, we can see that cloud-
init is unable to connect to the IMDS:
2024-03-05 14:23:54,836 - ephemeral.py[DEBUG]: Received dhcp lease on ens3
for 10.0.0.133/255.255.255.0
2024-03-05 14:23:54,837 - url_helper.py[DEBUG]: [0/3] open
'http://169.254.169.254/opc/v2/instance/' with {'url':
'http://169.254.169.254/opc/v2/instance/', 'stream'
[Touch-packages] [Bug 2056450] [NEW] netinfo_to_netplan: /init: 771: /init: rm: not found
Public bug reported:
The qemu-net autopkgtest shows this error message:
```
/init: 778: /init: rm: not found
```
This comes from the `netinfo_to_netplan` function in
`scripts/functions`:
```
netinfo_to_netplan() {
[...]
rm -Rf "$tmpd"
}
```
The `rm` command is only available if busybox is used.
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2056450
Title:
netinfo_to_netplan: /init: 771: /init: rm: not found
Status in initramfs-tools package in Ubuntu:
New
Bug description:
The qemu-net autopkgtest shows this error message:
```
/init: 778: /init: rm: not found
```
This comes from the `netinfo_to_netplan` function in
`scripts/functions`:
```
netinfo_to_netplan() {
[...]
rm -Rf "$tmpd"
}
```
The `rm` command is only available if busybox is used.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056450/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055718] Re: timezone changed unexpectedly from EST to America/Adak or America/Indiana/Indianapolis
** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2055718 Title: timezone changed unexpectedly from EST to America/Adak or America/Indiana/Indianapolis Status in tzdata package in Ubuntu: Triaged Bug description: A user reported this regression on https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739: UPDATE: I don't think it's a regression anymore, see comment #5 """ Hello. After automatic upgrade of tzdata from 2023c-0ubuntu0.22.04.2 to 2024a-0ubuntu0.22.04 the previously set EST time zone was automatically changed to "America/Adak" or "America/Indiana/Indianapolis" on all our servers (50+). Look like a bug in tzdata configure script. """ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2055718/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2036302] Re: apparmor 4.0.0~alpha2-0ubuntu3 ships same file as liblxc-common
** Tags removed: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/2036302 Title: apparmor 4.0.0~alpha2-0ubuntu3 ships same file as liblxc-common Status in apparmor package in Ubuntu: Fix Released Status in lxc package in Ubuntu: Fix Released Bug description: When running apt-get distupgrade I saw this message: Preparing to unpack .../apparmor_4.0.0~alpha2-0ubuntu3_amd64.deb ... Unpacking apparmor (4.0.0~alpha2-0ubuntu3) over (4.0.0~alpha2-0ubuntu2) ... dpkg: error processing archive /var/cache/apt/archives/apparmor_4.0.0~alpha2-0ubuntu3_amd64.deb (--unpack): trying to overwrite '/etc/apparmor.d/usr.bin.lxc-start', which is also in package liblxc-common 1:5.0.1-0ubuntu6 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) The problem could be overcome with: sudo apt-get install liblxc-common --reinstall which resulted in output Preparing to unpack .../liblxc-common_1%3a5.0.1-0ubuntu6_amd64.deb ... Unpacking liblxc-common (1:5.0.1-0ubuntu6) over (1:5.0.1-0ubuntu6) ... I have seen the same type of problem before with other packages. I would have expected apt-get to correctly sequence all necessary actions on its own. These are related events in my apt history: Start-Date: 2022-10-30 05:33:09 Commandline: apt-get install lxc Requested-By: ubuntu (1000) Install: liblxc-common:amd64 (1:5.0.0~git2209-g5a7b9ce67-0ubuntu3, automatic) Start-Date: 2023-01-28 11:06:34 Commandline: apt-get dist-upgrade Requested-By: ubuntu (1000) Upgrade: liblxc-common:amd64 (1:5.0.0~git2209-g5a7b9ce67-0ubuntu3, 1:5.0.1-0ubuntu6) ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: apt 2.7.3 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sat Sep 16 11:12:36 2023 InstallationDate: Installed on 2021-07-01 (807 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2036302/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade
** Tags removed: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in Cinnamon: New Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in ubuntu-release-upgrader source package in Jammy: Fix Released Status in ubuntu-release-upgrader source package in Lunar: Fix Released Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: Fix Released Bug description: [ Impact ] * On Ubuntu Mate with the Lunar series, when running ubuntu-release-upgrader, the displayed font of running applications (including the upgrader) becomes very corrupted. * This is not just a display problem, it is also a functional one. The release upgrader will have text corrupted to the point where a dialog asks a decision, and displays two buttons, but the text is unreadable and one has to guess which button is the one that carries out their desired action. * In the early parts of the upgrader tool, users are told in bold: "To prevent data loss close all open applications and documents." This is just before the "Start Upgrade" button is available. But they may not do so. Many applications may have a corrupted font. * To address this, an additional environment variable is being passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the critical criteria for making the Mate version of the fix work. * Also in the change are * an update to tests * from pre-build.sh * an update of the mirrors.cfg, adding and removing several mirrors * a refresh of the po files [ Test Plan ] * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64 * as user, run "update-manager -d" * monitor the "Distribution Upgrade" screen. During the "Installing the upgrades" step (and mind that this step will be long), observe the text of the "Distribution Upgrade" screen and verify that the font does not corrupt. * Repeat the above for Ubuntu Desktop [ Where problems could occur ] * We are changing, at release time, ubuntu-release upgrader. If we are careless, we could regress upgrades for a wider group of users than just Ubuntu Mate. That said, it is believed that passing the additional XDG_CURRENT_DESKTOP variable is relatively low risk. [ Other Info ] * TBD --- Original description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
** Changed in: initramfs-tools (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
Status in initramfs-tools package in Ubuntu:
Fix Committed
Status in open-iscsi package in Ubuntu:
Invalid
Bug description:
we have a bad interaction between initramfs-tools and open-iscsi,
resulting in the boot interface not being configured.
when the iscsi has a static address, the script `local-top/iscsi` from
open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi
interface. The existence of this file makes configure_networking()
skip configuring the BOOTIF later due to this code in
`scripts/functions`:
for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do
if [ -e "$x" ]; then
IP=done
break
fi
done
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981385] Re: initrd lacks modules to mount boot image from http boot
BTW, could you come up with a test case that we could include in the
initramfs-tools to avoid such kind of regressions in the future?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1981385
Title:
initrd lacks modules to mount boot image from http boot
Status in initramfs-tools package in Ubuntu:
Fix Committed
Status in initramfs-tools source package in Jammy:
Fix Released
Bug description:
[ Impact ]
* If you use UEFI http boot to boot an image (rather than an EFI
executable) and get all the way to a normal userspace, you can
access the boot image as /dev/pmem0. But this is not accessible in
the initrd; presumably some modules are missing.
* This is desirable because then you can just feed an installer ISO to
a machine via http boot and the installer just works as normal
* Add support for physical pmem devices, and simulation thereof with
the memmap kernel command line parameter
* The initrd is larger
[ Test Plan ]
* unpack an initrd on a Jammy system with the generic kernel
metapackage with unmkinitramfs
* observe that the directories kernel/drivers/{nvdimm,dax,acpi/nfit}
are not present
* install the updated initramfs-tools packages from proposed
* again unpack an initrd on a Jammy system with the generic kernel
metapackage with unmkinitramfs
* observe that the directories kernel/drivers/{nvdimm,dax,acpi/nfit}
are present now
* reboot to confirm that the system still boots
* modify /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT to contain a
memmap entry - memmap=1G!4G seems to work on many systems over 4G of
RAM, or do `dmesg | grep BIOS-e820` to observe the memory regions
and select a usable one.
* update-grub and reboot again
* a /dev/pmem device should now be present on the system
[ Where problems could occur ]
* The growth of the files in /boot will accelerate issues for users
who have a dedicated boot partition that is not large enough
[ Other Info ]
* Details on the memmap kernel command line parameter:
https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt
* PMEM simulation with memmap:
https://docs.pmem.io/persistent-memory/getting-started-guide/creating-development-environments/linux-environments/linux-memmap
[ Original Bug Description ]
If you use UEFI http boot to boot an image (rather than an EFI
executable) and get all the way to a normal userspace, you can access
the boot image as /dev/pmem0. But this is not accessible in the
initrd; presumably some modules are missing. Dimitri added some
modules that are clearly going to be necessary (kernel/drivers/nvdimm)
in 0.140ubuntu14 and I added kernel/drivers/dax too in local
experiments but this appears not to be enough to get it to appear.
This is desirable because then you can just feed an installer ISO to a
machine via http boot and the installer just works as normal (the
speed and, uh, quality, of the implementation of HTTP in a given
machine's firmware may mean this isn't always the best option but it
would be nice if it worked in case someone's machine actually does
this well).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1981385/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056194] Re: Networking broken in early boot on Oracle Native instances
** Changed in: initramfs-tools (Ubuntu)
Status: New => Triaged
** Summary changed:
- Networking broken in early boot on Oracle Native instances
+ Networking broken in early boot on Oracle Native instances due to MTU settings
** Changed in: initramfs-tools (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2056194
Title:
Networking broken in early boot on Oracle Native instances due to MTU
settings
Status in cloud-images:
New
Status in cloud-init package in Ubuntu:
New
Status in initramfs-tools package in Ubuntu:
Fix Committed
Bug description:
BACKGROUND:
cloud-init-local.service runs before networking has started. On non-
Oracle platforms, before networking has come up, cloud-init will
create an ephemeral connection to the cloud's IMDS using DHCP to
retrieve instance metadata. On Oracle, this normally isn't necessary
as we boot with connectivity to the IMDS out of the box. This can be
seen in the following Jammy instance using an SR-IOV NIC:
2024-03-05 14:09:05,351 - url_helper.py[DEBUG]: [0/1] open
'http://169.254.169.254/opc/v2/instance/' with {'url':
'http://169.254.169.254/opc/v2/instance/', 'stream': False, 'allow_redirects':
True, 'method': 'GET', 'timeout': 5.0, 'headers': {'User-Agent'
: 'Cloud-Init/23.3.3-0ubuntu0~22.04.1', 'Authorization': 'Bearer Oracle'}}
configuration
2024-03-05 14:09:05,362 - url_helper.py[DEBUG]: Read from
http://169.254.169.254/opc/v2/instance/ (200, 2663b) after 1 attempts
2024-03-05 14:09:05,362 - ephemeral.py[DEBUG]: Skip ephemeral DHCP setup,
instance has connectivity to {'url': 'http://169.254.169.254/opc/v2/instance/',
'headers': {'Authorization': 'Bearer Oracle'}, 'timeout': 5}
2024-03-05 14:09:05,362 - url_helper.py[DEBUG]: [0/3] open
'http://169.254.169.254/opc/v2/instance/' with {'url':
'http://169.254.169.254/opc/v2/instance/', 'stream': False, 'allow_redirects':
True, 'method': 'GET', 'headers': {'User-Agent': 'Cloud-Init/23
.3.3-0ubuntu0~22.04.1', 'Authorization': 'Bearer Oracle'}} configuration
2024-03-05 14:09:05,368 - url_helper.py[DEBUG]: Read from
http://169.254.169.254/opc/v2/instance/ (200, 2663b) after 1 attempts
Notice the "Skip ephemeral DHCP setup, instance has connectivity".
This means that cloud-init has determined that it already has
connectivity and doesn't need to do any additional setup to retrieve
data from the IMDS.
We can also see the same behavior on a Noble paravirtualized instance:
2024-03-01 20:51:33,482 - url_helper.py[DEBUG]: [0/1] open
'http://169.254.169.254/opc/v2/instance/' with {'url':
'http://169.254.169.254/opc/v2/instance/', 'stream': False, 'allow_redirects':
True, 'method': 'GET', 'timeout': 5.0, 'headers': {'User-Agent':
'Cloud-Init/24.1~7g54599148-0ubuntu1', 'Authorization': 'Bearer Oracle'}}
configuration
2024-03-01 20:51:33,488 - url_helper.py[DEBUG]: Read from
http://169.254.169.254/opc/v2/instance/ (200, 3067b) after 1 attempts
2024-03-01 20:51:33,488 - ephemeral.py[DEBUG]: Skip ephemeral DHCP setup,
instance has connectivity to {'url': 'http://169.254.169.254/opc/v2/instance/',
'headers': {'Authorization': 'Bearer Oracle'}, 'timeout': 5}
2024-03-01 20:51:33,489 - url_helper.py[DEBUG]: [0/3] open
'http://169.254.169.254/opc/v2/instance/' with {'url':
'http://169.254.169.254/opc/v2/instance/', 'stream': False, 'allow_redirects':
True, 'method': 'GET', 'headers': {'User-Agent':
'Cloud-Init/24.1~7g54599148-0ubuntu1', 'Authorization': 'Bearer Oracle'}}
configuration
2024-03-01 20:51:33,500 - url_helper.py[DEBUG]: Read from
http://169.254.169.254/opc/v2/instance/ (200, 3067b) after 1 attempts
2024-03-01 20:51:33,501 - util.py[DEBUG]: Writing to
/run/cloud-init/cloud-id-oracle - wb: [644] 7 bytes
PROBLEM:
On a Noble instance using Hardware-assisted (SR-IOV) networking, this
is not working. cloud-init-local.service no longer has immediate
connectivity to the IMDS. Since it cannot connect, in then attempts to
create an ephemeral connection to the IMDS using DHCP. It is able to
obtain a DHCP lease, but then when it tries to connect to the IMDS,
the call just hangs. The call has no timeout, so this results in an
instance that cannot be logged into even via the serial console
because cloud-init is blocking the rest of boot. A simple cloud-init
workaround is to add something along the lines of `timeout=2` to
https://github.com/canonical/cloud-
init/blob/main/cloudinit/sources/DataSourceOracle.py#L349 . This
allows cloud-init to boot. Looking at the logs, we can see that cloud-
init is unable to connect to the IMDS:
2024-03-05 14:23:54,836 - ephemeral.py[DEBUG]: Received dhcp lease on ens3
for 10.0.0.133/255.255.255.0
2024-03-05 14:23:54,837 - url_
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
** Also affects: initramfs-tools (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: open-iscsi (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
Status in initramfs-tools package in Ubuntu:
Fix Committed
Status in open-iscsi package in Ubuntu:
Invalid
Status in initramfs-tools source package in Jammy:
New
Status in open-iscsi source package in Jammy:
New
Bug description:
we have a bad interaction between initramfs-tools and open-iscsi,
resulting in the boot interface not being configured.
when the iscsi has a static address, the script `local-top/iscsi` from
open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi
interface. The existence of this file makes configure_networking()
skip configuring the BOOTIF later due to this code in
`scripts/functions`:
for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do
if [ -e "$x" ]; then
IP=done
break
fi
done
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2057605] Re: update-initramfs fails: /usr/share/initramfs-tools/hooks/fsck failed with return 1
Thank you for taking the time to report this bug and helping to make Ubuntu better and for providing the correct logs to further troubleshoot the issue. Things went south after `ldd /sbin/fsck.ext4` leading to `/lib/libgcwrap.so`. Can you provide the output of the `ldd /sbin/fsck.ext4` command? On a clean focal chroot the output of the command looks like this: ``` $ ldd /sbin/fsck.ext4 linux-vdso.so.1 (0x7ffd483c4000) libext2fs.so.2 => /lib/x86_64-linux-gnu/libext2fs.so.2 (0x776e7776c000) libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2 (0x776e77765000) libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1 (0x776e7770e000) libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x776e77705000) libe2p.so.2 => /lib/x86_64-linux-gnu/libe2p.so.2 (0x776e776fa000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x776e77508000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x776e774e3000) /lib64/ld-linux-x86-64.so.2 (0x776e77828000) ``` ** Changed in: initramfs-tools (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2057605 Title: update-initramfs fails: /usr/share/initramfs-tools/hooks/fsck failed with return 1 Status in initramfs-tools package in Ubuntu: Incomplete Bug description: lsb_release -rd Description: Ubuntu 20.04.6 LTS Release: 20.04 initramfs-tools: Installed: 0.136ubuntu6.7 Candidate: 0.136ubuntu6.7 Version table: *** 0.136ubuntu6.7 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.136ubuntu6 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu focal/main amd64 Packages sudo apt-get install linux-image-5.4.0-173-generic Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: linux-modules-5.4.0-173-generic Suggested packages: fdutils linux-doc | linux-source-5.4.0 linux-tools linux-headers-5.4.0-173-generic The following NEW packages will be installed: linux-image-5.4.0-173-generic linux-modules-5.4.0-173-generic 0 upgraded, 2 newly installed, 0 to remove and 2 not upgraded. Need to get 25.5 MB of archives. After this operation, 92.5 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://nova.clouds.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-modules-5.4.0-173-generic amd64 5.4.0-173.191 [15.0 MB] Get:2 http://nova.clouds.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-image-5.4.0-173-generic amd64 5.4.0-173.191 [10.5 MB] Fetched 25.5 MB in 2s (12.1 MB/s) Selecting previously unselected package linux-modules-5.4.0-173-generic. (Reading database ... 77620 files and directories currently installed.) Preparing to unpack .../linux-modules-5.4.0-173-generic_5.4.0-173.191_amd64.deb ... Unpacking linux-modules-5.4.0-173-generic (5.4.0-173.191) ... Selecting previously unselected package linux-image-5.4.0-173-generic. Preparing to unpack .../linux-image-5.4.0-173-generic_5.4.0-173.191_amd64.deb ... Unpacking linux-image-5.4.0-173-generic (5.4.0-173.191) ... Setting up linux-modules-5.4.0-173-generic (5.4.0-173.191) ... Setting up linux-image-5.4.0-173-generic (5.4.0-173.191) ... I: /boot/vmlinuz is now a symlink to vmlinuz-5.4.0-173-generic I: /boot/initrd.img is now a symlink to initrd.img-5.4.0-173-generic Processing triggers for linux-image-5.4.0-173-generic (5.4.0-173.191) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.4.0-173-generic + PREREQ= + prereqs + echo + exit 0 + PREREQ= + [ ! -x /sbin/fsck ] + . /usr/share/initramfs-tools/scripts/functions + . /usr/share/initramfs-tools/hook-functions + + sort get_fsck_types + get_fsck_type_fstab / root + uniq + _read_fstab_entry / + echo MNT_FSNAME= + echo MNT_DIR= + echo MNT_TYPE= + [ -f /etc/fstab ] + read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK + [ / = / ] + [ -n ] + echo MNT_FSNAME=UUID="d4148b00-3426-4e12-a89c-1eab09c29b72" + echo MNT_DIR=/ + echo MNT_TYPE=ext4 + echo MNT_PASS=0 + break 2 + eval MNT_FSNAME= MNT_DIR= MNT_TYPE= MNT_FSNAME=UUID="d4148b00-3426-4e12-a89c-1eab09c29b72" MNT_DIR=/ MNT_TYPE=ext4 MNT_PASS=0 + MNT_FSNAME= + MNT_DIR= + MNT_TYPE= + MNT_FSNAME=UUID=d4148b00-3426-4e12-a89c-1eab09c29b72 + MNT_DIR=/ + MNT_TYPE=ext4 + MNT_PASS=0 + [ / = / ] + [ / = / ] + resolve_device UUID=d4148b00-3426-4e12-a89c-1eab09c29b72 + DEV=UUID=d4148b00-3426-4e12-a89c-1eab09c29b72 + local orig=UUID=d4148b00-3426-4e12-a89c-1eab09c29b72 + blkid -l -t UUID=d4
[Touch-packages] [Bug 2025369] Re: Left over systemd-udevd processes from initramfs
** Description changed: Running the qemu-net autopkgtest from initramfs-tools on architectures like armhf shows that there are sometimes remaining systemd-udevd after exiting the initramfs. `ps -ww aux` shows: ``` /lib/systemd/systemd-udevd --daemon --resolve-names=never ``` Example run: https://autopkgtest.ubuntu.com/results/autopkgtest-mantic- bdrung-ppa/mantic/armhf/i/initramfs-tools/20230629_015244_c7bd1@/log.gz - Distribution: Ubuntu 23.10 + Distribution: Ubuntu 23.10 and 24.04 (as of 2024-03-13) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2025369 Title: Left over systemd-udevd processes from initramfs Status in systemd package in Ubuntu: New Bug description: Running the qemu-net autopkgtest from initramfs-tools on architectures like armhf shows that there are sometimes remaining systemd-udevd after exiting the initramfs. `ps -ww aux` shows: ``` /lib/systemd/systemd-udevd --daemon --resolve-names=never ``` Example run: https://autopkgtest.ubuntu.com/results/autopkgtest- mantic-bdrung-ppa/mantic/armhf/i/initramfs- tools/20230629_015244_c7bd1@/log.gz Distribution: Ubuntu 23.10 and 24.04 (as of 2024-03-13) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2025369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2057605] Re: update-initramfs fails: /usr/share/initramfs-tools/hooks/fsck failed with return 1
*** This bug is a duplicate of bug 1641230 *** https://bugs.launchpad.net/bugs/1641230 /lib/libgcwrap.so should not be in the output. I found the identical bug #1641230. The root cause from the investigation there was a crypto-miner malware. See the bug discussion there (especially comment 15). ** This bug has been marked a duplicate of bug 1641230 package linux-image-4.4.0-43-generic 4.4.0-43.63 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 due to /usr/share/initramfs-tools/hooks/fsck failed with return 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2057605 Title: update-initramfs fails: /usr/share/initramfs-tools/hooks/fsck failed with return 1 Status in initramfs-tools package in Ubuntu: Incomplete Bug description: lsb_release -rd Description: Ubuntu 20.04.6 LTS Release: 20.04 initramfs-tools: Installed: 0.136ubuntu6.7 Candidate: 0.136ubuntu6.7 Version table: *** 0.136ubuntu6.7 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.136ubuntu6 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu focal/main amd64 Packages sudo apt-get install linux-image-5.4.0-173-generic Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: linux-modules-5.4.0-173-generic Suggested packages: fdutils linux-doc | linux-source-5.4.0 linux-tools linux-headers-5.4.0-173-generic The following NEW packages will be installed: linux-image-5.4.0-173-generic linux-modules-5.4.0-173-generic 0 upgraded, 2 newly installed, 0 to remove and 2 not upgraded. Need to get 25.5 MB of archives. After this operation, 92.5 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://nova.clouds.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-modules-5.4.0-173-generic amd64 5.4.0-173.191 [15.0 MB] Get:2 http://nova.clouds.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-image-5.4.0-173-generic amd64 5.4.0-173.191 [10.5 MB] Fetched 25.5 MB in 2s (12.1 MB/s) Selecting previously unselected package linux-modules-5.4.0-173-generic. (Reading database ... 77620 files and directories currently installed.) Preparing to unpack .../linux-modules-5.4.0-173-generic_5.4.0-173.191_amd64.deb ... Unpacking linux-modules-5.4.0-173-generic (5.4.0-173.191) ... Selecting previously unselected package linux-image-5.4.0-173-generic. Preparing to unpack .../linux-image-5.4.0-173-generic_5.4.0-173.191_amd64.deb ... Unpacking linux-image-5.4.0-173-generic (5.4.0-173.191) ... Setting up linux-modules-5.4.0-173-generic (5.4.0-173.191) ... Setting up linux-image-5.4.0-173-generic (5.4.0-173.191) ... I: /boot/vmlinuz is now a symlink to vmlinuz-5.4.0-173-generic I: /boot/initrd.img is now a symlink to initrd.img-5.4.0-173-generic Processing triggers for linux-image-5.4.0-173-generic (5.4.0-173.191) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.4.0-173-generic + PREREQ= + prereqs + echo + exit 0 + PREREQ= + [ ! -x /sbin/fsck ] + . /usr/share/initramfs-tools/scripts/functions + . /usr/share/initramfs-tools/hook-functions + + sort get_fsck_types + get_fsck_type_fstab / root + uniq + _read_fstab_entry / + echo MNT_FSNAME= + echo MNT_DIR= + echo MNT_TYPE= + [ -f /etc/fstab ] + read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK + [ / = / ] + [ -n ] + echo MNT_FSNAME=UUID="d4148b00-3426-4e12-a89c-1eab09c29b72" + echo MNT_DIR=/ + echo MNT_TYPE=ext4 + echo MNT_PASS=0 + break 2 + eval MNT_FSNAME= MNT_DIR= MNT_TYPE= MNT_FSNAME=UUID="d4148b00-3426-4e12-a89c-1eab09c29b72" MNT_DIR=/ MNT_TYPE=ext4 MNT_PASS=0 + MNT_FSNAME= + MNT_DIR= + MNT_TYPE= + MNT_FSNAME=UUID=d4148b00-3426-4e12-a89c-1eab09c29b72 + MNT_DIR=/ + MNT_TYPE=ext4 + MNT_PASS=0 + [ / = / ] + [ / = / ] + resolve_device UUID=d4148b00-3426-4e12-a89c-1eab09c29b72 + DEV=UUID=d4148b00-3426-4e12-a89c-1eab09c29b72 + local orig=UUID=d4148b00-3426-4e12-a89c-1eab09c29b72 + blkid -l -t UUID=d4148b00-3426-4e12-a89c-1eab09c29b72 -o device + DEV=/dev/md127 + [ -e /dev/md127 ] + echo /dev/md127 + MNT_FSNAME=/dev/md127 + get_fstype /dev/md127 + local FS FSTYPE + FS=/dev/md127 + blkid -o value -s TYPE /dev/md127 + FSTYPE=ext4 + echo ext4 + return 0 + get_fsck_type_fstab /usr /usr + _read_fstab_entry /usr + echo MNT_FSNAME= + echo MNT_DIR= + echo MNT_TYPE= + [ -f /etc/fstab ] + read -r MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK + [ / = /usr ] + MNT_DIR= + read -r MNT_FSNAME MNT_DIR MNT_TYPE M
[Touch-packages] [Bug 1641230] Re: /usr/share/initramfs-tools/hooks/fsck failed with return 1 due to /lib/libgcwrap.so in ldd output caused by crypto-miner malware
** Summary changed: - package linux-image-4.4.0-43-generic 4.4.0-43.63 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 due to /usr/share/initramfs-tools/hooks/fsck failed with return 1 + /usr/share/initramfs-tools/hooks/fsck failed with return 1 due to /lib/libgcwrap.so in ldd output caused by crypto-miner malware -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1641230 Title: /usr/share/initramfs-tools/hooks/fsck failed with return 1 due to /lib/libgcwrap.so in ldd output caused by crypto-miner malware Status in e2fsprogs package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Bug description: Do you want to continue? [Y/n] y (Reading database ... 254369 files and directories currently installed.) Removing linux-image-extra-4.4.0-43-generic (4.4.0-43.63) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-43-generic /boot/vmlinuz-4.4.0-43-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-43-generic /boot/vmlinuz-4.4.0-43-generic Error! Your kernel headers for kernel 4.4.0-43-generic cannot be found. Please install the linux-headers-4.4.0-43-generic package, or use the --kernelsourcedir option to tell DKMS where it's located run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-43-generic /boot/vmlinuz-4.4.0-43-generic update-initramfs: Generating /boot/initrd.img-4.4.0-43-generic E: /usr/share/initramfs-tools/hooks/fsck failed with return 1. update-initramfs: failed for /boot/initrd.img-4.4.0-43-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-extra-4.4.0-43-generic (--remove): subprocess installed post-removal script returned error exit status 1 Removing linux-image-extra-4.4.0-47-generic (4.4.0-47.68) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-47-generic /boot/vmlinuz-4.4.0-47-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-47-generic /boot/vmlinuz-4.4.0-47-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-47-generic /boot/vmlinuz-4.4.0-47-generic update-initramfs: Generating /boot/initrd.img-4.4.0-47-generic E: /usr/share/initramfs-tools/hooks/fsck failed with return 1. update-initramfs: failed for /boot/initrd.img-4.4.0-47-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-extra-4.4.0-47-generic (--remove): subprocess installed post-removal script returned error exit status 1 Errors were encountered while processing: linux-image-extra-4.4.0-43-generic linux-image-extra-4.4.0-47-generic E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-43-generic 4.4.0-43.63 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pezhman1535 F pulseaudio Date: Fri Nov 11 21:03:09 2016 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=e8c76af0-04d5-4831-a401-a0911630111c InstallationDate: Installed on 2016-08-27 (76 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. S300CA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=72d332d4-9180-442f-a032-8c1b612566ec ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-image-4.4.0-43-generic 4.4.0-43.63 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S300CA.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: S300CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS300CA.302:bd01/22/2013:svnASUSTeKCOMPUTERINC.:pnS300CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnS300CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: S300CA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications abo
[Touch-packages] [Bug 2017786] Re: update script in ubuntu-meta not handling germinate or specified versions
I see nothing in this bug that needs sponsoring. Unsubscribing ~ubuntu- sponsors. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2017786 Title: update script in ubuntu-meta not handling germinate or specified versions Status in edubuntu-meta package in Ubuntu: Won't Fix Status in kubuntu-meta package in Ubuntu: Fix Released Status in lubuntu-meta package in Ubuntu: New Status in ubuntu-budgie-meta package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-unity-meta package in Ubuntu: New Status in ubuntucinnamon-meta package in Ubuntu: New Status in ubuntukylin-meta package in Ubuntu: New Status in ubuntustudio-meta package in Ubuntu: Won't Fix Status in xubuntu-meta package in Ubuntu: New Bug description: update script handled debootstrap and devscripts, does not handle germinate. also doesn't handle potential specified versions in the package directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edubuntu-meta/+bug/2017786/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058003] Re: Keine Freigabe
Normalerweise landen gelöschte Dateien im Papierkorb. Hast du geprüft, ob diese Dateien noch im Papierkorb liegen? Erst nach dem Löschen aus dem Papierkorb wird der Platz auf der Festplatte frei. ** Changed in: tzdata (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2058003 Title: Keine Freigabe Status in tzdata package in Ubuntu: Incomplete Bug description: Wenn ich eine grosse Datei in Thunar oder Nautilus lösche wird es auf die Partition nicht um den Anteil gelöscht. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2058003/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869655] Re: Boot animations start too late to be useful
** Changed in: initramfs-tools (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1869655 Title: Boot animations start too late to be useful Status in Plymouth: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Fix Committed Status in plymouth package in Ubuntu: In Progress Bug description: Boot animations start too late to be useful Modern systems spend all their boot time (a couple of seconds) decompressing the kernel. During that time the user only sees the static BIOS logo (ACPI BGRT). Then when Plymouth can finally start animating, the startup process is already finished and there's virtually no time left to show any useful animations. This could be fixed in: grub: By adding a splash under the BIOS logo to show some progress _before_ a Linux kernel is even started and/or plymouth: By preferencing legacy framebuffer devices (like EFI) over DRM, if we find those are available a few seconds sooner. That would also fix bug 1868240 completely, and bug 1836858 mostly as the flicker moves to when the login screen starts. To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/1869655/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
** Changed in: initramfs-tools (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in plymouth package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058242] [NEW] Demote isc-dhcp to universe
Public bug reported: Following the replacement of dhclient by dhcpcd as new DHCP client tool, it is now time to demote isc-dhcp-client. After demoting isc-dhcp-server (bug # 2045577) the complete isc-dhcp can be demoted. ``` $ reverse-depends -c main,restricted isc-dhcp-client $ reverse-depends -c main,restricted -b isc-dhcp-client ``` ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/2058242 Title: Demote isc-dhcp to universe Status in isc-dhcp package in Ubuntu: New Bug description: Following the replacement of dhclient by dhcpcd as new DHCP client tool, it is now time to demote isc-dhcp-client. After demoting isc- dhcp-server (bug # 2045577) the complete isc-dhcp can be demoted. ``` $ reverse-depends -c main,restricted isc-dhcp-client $ reverse-depends -c main,restricted -b isc-dhcp-client ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/2058242/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
Looking at the remaining "add drm modules (only if MODULES=dep)" section: This logic should moved to hooks/framebuffer as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in plymouth package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058249] Re: US symlinks missing in /usr/share/zoneinfo
Yes, this is an intentional change. All backward compatibility symlinks were moved to the tzdata-legacy package. Please install this package for such use cases. ** Changed in: tzdata (Ubuntu) Status: New => Invalid ** Summary changed: - US symlinks missing in /usr/share/zoneinfo + US symlinks missing in /usr/share/zoneinfo -> now in tzdata-legacy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2058249 Title: US symlinks missing in /usr/share/zoneinfo -> now in tzdata-legacy Status in tzdata package in Ubuntu: Invalid Bug description: On 22.04 Jammy with tzdata version 2024a-0ubuntu0.22.04 installed, we have `/usr/share/zoneinfo/US/*` symlinks. On 23.10 Mantic with tzdata version 2024a-0ubuntu0.23.10, we do not. Is this an intentional removal? I don't follow the IANA mailing lists, but I had thought/assumed that "Country/Region" symlinks were being maintained for backward compatibility. Many tools I use reference multiple timezones (regardless of the system TZ), so it is necessary to have them available. As a temporary workaround, we can make the symlinks manually. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2058249/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
Attached the uploaded diff for jammy. Besides the few lines changed in
scripts/functions I backported the improvements of the autopkgtest to
increase the test coverage and to test on all architectures. See
https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/initramfs-
tools/+git/initramfs-tools/+ref/ubuntu/jammy for the individual commits
for details. I tested the autopkgtest changes in my PPA.
** Description changed:
+ [ Impact ]
+
+ * MAAS cannot PXE-boot a machine that has iSCSI disks
+
+ * Focal is the default Ubuntu distribution deployed by MAAS, so we should
+back-port this to ensure it works out-of-the-box.
+
+ [ Test Plan ]
+
+ * reproducing this issue requires a machine with iSCSI disks (Cisco UCS
Manager
+ in the original report), and a MAAS controller (3.4 or better)
+
+ * the issue can be observed by simply enlisting the machine in MAAS. It will
+ fail to boot due to the missing BOOTIF configuration.
+
+ [ Where problems could occur ]
+
+ * the problematic code was an attempt to fix LP#2037202, so we should watch
out
+ for regressions.
+
+ [ Original report ]
+
we have a bad interaction between initramfs-tools and open-iscsi,
resulting in the boot interface not being configured.
when the iscsi has a static address, the script `local-top/iscsi` from
open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi interface.
The existence of this file makes configure_networking() skip configuring
the BOOTIF later due to this code in `scripts/functions`:
- for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do
- if [ -e "$x" ]; then
- IP=done
- break
- fi
- done
+ for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do
+ if [ -e "$x" ]; then
+ IP=done
+ break
+ fi
+ done
** Patch added: "initramfs-tools_0.140ubuntu13.5.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+attachment/5756863/+files/initramfs-tools_0.140ubuntu13.5.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
Status in initramfs-tools package in Ubuntu:
Fix Committed
Status in open-iscsi package in Ubuntu:
Invalid
Status in initramfs-tools source package in Jammy:
New
Status in open-iscsi source package in Jammy:
New
Bug description:
[ Impact ]
* MAAS cannot PXE-boot a machine that has iSCSI disks
* Focal is the default Ubuntu distribution deployed by MAAS, so we should
back-port this to ensure it works out-of-the-box.
[ Test Plan ]
* reproducing this issue requires a machine with iSCSI disks (Cisco UCS
Manager
in the original report), and a MAAS controller (3.4 or better)
* the issue can be observed by simply enlisting the machine in MAAS. It will
fail to boot due to the missing BOOTIF configuration.
[ Where problems could occur ]
* the problematic code was an attempt to fix LP#2037202, so we should watch
out
for regressions.
[ Original report ]
we have a bad interaction between initramfs-tools and open-iscsi,
resulting in the boot interface not being configured.
when the iscsi has a static address, the script `local-top/iscsi` from
open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi
interface. The existence of this file makes configure_networking()
skip configuring the BOOTIF later due to this code in
`scripts/functions`:
for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do
if [ -e "$x" ]; then
IP=done
break
fi
done
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058249] Re: US symlinks missing in /usr/share/zoneinfo -> now in tzdata-legacy
In Ubuntu 24.04 (noble) we have /usr/share/doc/tzdata/NEWS.Debian.gz: tzdata (2023d-1) unstable; urgency=medium From 2023c-8 on the tzdata package ships only timezones that follow the current rules of geographical region (continent or ocean) and city name. All legacy timezone symlinks (old or merged timezones mentioned in the upstream backward file) were moved to tzdata-legacy. This includes the US/* timezones. Please install tzdata-legacy in case you need the legacy timezones or to restore the previous behavior. This might be needed in case the system provides timezone-aware data over the network (e. g. SQL databases). -- Benjamin Drung Tue, 02 Jan 2024 14:17:33 +0100 The debian changelog contains for 2023c-8: * Ship only timezones in tzdata that follow the current rules of geographical region (continent or ocean) and city name. Move all legacy timezone symlinks (that are upgraded during package update) to tzdata-legacy. This includes dropping the special handling for US/* timezones. (Closes: #1040997) Improvements to the documentation are welcome. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2058249 Title: US symlinks missing in /usr/share/zoneinfo -> now in tzdata-legacy Status in tzdata package in Ubuntu: Invalid Bug description: On 22.04 Jammy with tzdata version 2024a-0ubuntu0.22.04 installed, we have `/usr/share/zoneinfo/US/*` symlinks. On 23.10 Mantic with tzdata version 2024a-0ubuntu0.23.10, we do not. Is this an intentional removal? I don't follow the IANA mailing lists, but I had thought/assumed that "Country/Region" symlinks were being maintained for backward compatibility. Many tools I use reference multiple timezones (regardless of the system TZ), so it is necessary to have them available. As a temporary workaround, we can make the symlinks manually. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2058249/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
** Also affects: initramfs-tools (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: open-iscsi (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
Status in initramfs-tools package in Ubuntu:
Fix Committed
Status in open-iscsi package in Ubuntu:
Invalid
Status in initramfs-tools source package in Focal:
New
Status in open-iscsi source package in Focal:
New
Status in initramfs-tools source package in Jammy:
New
Status in open-iscsi source package in Jammy:
New
Bug description:
[ Impact ]
* MAAS cannot PXE-boot a machine that has iSCSI disks
* Focal is the default Ubuntu distribution deployed by MAAS, so we should
back-port this to ensure it works out-of-the-box.
[ Test Plan ]
* reproducing this issue requires a machine with iSCSI disks (Cisco UCS
Manager
in the original report), and a MAAS controller (3.4 or better)
* the issue can be observed by simply enlisting the machine in MAAS. It will
fail to boot due to the missing BOOTIF configuration.
[ Where problems could occur ]
* the problematic code was an attempt to fix LP#2037202, so we should watch
out
for regressions.
[ Original report ]
we have a bad interaction between initramfs-tools and open-iscsi,
resulting in the boot interface not being configured.
when the iscsi has a static address, the script `local-top/iscsi` from
open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi
interface. The existence of this file makes configure_networking()
skip configuring the BOOTIF later due to this code in
`scripts/functions`:
for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do
if [ -e "$x" ]; then
IP=done
break
fi
done
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058313] Re: whoopsie-upload-all (TypeError) /usr/share/apport/whoopsie-upload-all@220 → main → collect_info → process_report → add_gdb_info → gdb_command
** Description changed: + ``` + Traceback (most recent call last): + File "/usr/share/apport/whoopsie-upload-all", line 220, in + main() + File "/usr/share/apport/whoopsie-upload-all", line 202, in main + stamps = collect_info() + ^^ + File "/usr/share/apport/whoopsie-upload-all", line 150, in collect_info + res = process_report(r) + ^ + File "/usr/share/apport/whoopsie-upload-all", line 102, in process_report + r.add_gdb_info() + File "/usr/lib/python3/dist-packages/apport/report.py", line 793, in add_gdb_info + gdb_cmd, environ = self.gdb_command(rootdir, gdb_sandbox) +^^ + File "/usr/lib/python3/dist-packages/apport/report.py", line 1716, in gdb_command + core = self['CoreDump'][0] +^^^ + TypeError: 'CompressedValue' object is not subscriptable + ``` + The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.28.0-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/def1584660098f405d12c36422a9561aa02aa911 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2058313 Title: whoopsie-upload-all (TypeError) /usr/share/apport/whoopsie-upload- all@220 → main → collect_info → process_report → add_gdb_info → gdb_command Status in apport package in Ubuntu: New Bug description: ``` Traceback (most recent call last): File "/usr/share/apport/whoopsie-upload-all", line 220, in main() File "/usr/share/apport/whoopsie-upload-all", line 202, in main stamps = collect_info() ^^ File "/usr/share/apport/whoopsie-upload-all", line 150, in collect_info res = process_report(r) ^ File "/usr/share/apport/whoopsie-upload-all", line 102, in process_report r.add_gdb_info() File "/usr/lib/python3/dist-packages/apport/report.py", line 793, in add_gdb_info gdb_cmd, environ = self.gdb_command(rootdir, gdb_sandbox) ^^ File "/usr/lib/python3/dist-packages/apport/report.py", line 1716, in gdb_command core = self['CoreDump'][0] ^^^ TypeError: 'CompressedValue' object is not subscriptable ``` The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.28.0-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/def1584660098f405d12c36422a9561aa02aa911 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2058313/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
Daniel, please review and comment https://code.launchpad.net/~bdrung/ubuntu/+source/initramfs- tools/+git/initramfs-tools/+merge/462691 (see the description for the two possible implementations) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in plymouth package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
Updated jammy patch to include the increased timeout on arm64/armhf from
the upcoming 0.142ubuntu23 release.
** Patch added: "initramfs-tools_0.140ubuntu13.5_v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+attachment/5757173/+files/initramfs-tools_0.140ubuntu13.5_v2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
Status in initramfs-tools package in Ubuntu:
Fix Committed
Status in open-iscsi package in Ubuntu:
Invalid
Status in initramfs-tools source package in Focal:
New
Status in open-iscsi source package in Focal:
New
Status in initramfs-tools source package in Jammy:
New
Status in open-iscsi source package in Jammy:
New
Bug description:
[ Impact ]
* MAAS cannot PXE-boot a machine that has iSCSI disks
* Focal is the default Ubuntu distribution deployed by MAAS, so we should
back-port this to ensure it works out-of-the-box.
[ Test Plan ]
* reproducing this issue requires a machine with iSCSI disks (Cisco UCS
Manager
in the original report), and a MAAS controller (3.4 or better)
* the issue can be observed by simply enlisting the machine in MAAS. It will
fail to boot due to the missing BOOTIF configuration.
[ Where problems could occur ]
* the problematic code was an attempt to fix LP#2037202, so we should watch
out
for regressions.
[ Original report ]
we have a bad interaction between initramfs-tools and open-iscsi,
resulting in the boot interface not being configured.
when the iscsi has a static address, the script `local-top/iscsi` from
open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi
interface. The existence of this file makes configure_networking()
skip configuring the BOOTIF later due to this code in
`scripts/functions`:
for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do
if [ -e "$x" ]; then
IP=done
break
fi
done
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058380] [NEW] apport crashed with FileNotFoundError in iter_compressed(): [Errno 2] No such file or directory: '/var/lib/systemd/coredump/core.tracker-extract.1000.92c6d53b71364
Public bug reported: Ubuntu 24.04 (noble) VM. ``` Traceback (most recent call last): File "/usr/share/apport/apport", line 1244, in sys.exit(main(sys.argv[1:])) ^^ File "/usr/share/apport/apport", line 761, in main return process_crash_from_systemd_coredump(options.systemd_coredump_instance) ^^ File "/usr/share/apport/apport", line 1240, in process_crash_from_systemd_coredump return process_crash(report, real_user, report_owner) ^^ File "/usr/share/apport/apport", line 1146, in process_crash info.write(reportfile) File "/usr/lib/python3/dist-packages/problem_report.py", line 548, in write self._write_binary_item_compressed_and_encoded(file, k) File "/usr/lib/python3/dist-packages/problem_report.py", line 722, in _write_binary_item_compressed_and_encoded self._write_binary_item_base64_encoded( File "/usr/lib/python3/dist-packages/problem_report.py", line 629, in _write_binary_item_base64_encoded for chunk in chunks: File "/usr/lib/python3/dist-packages/problem_report.py", line 649, in _generate_compressed_chunks yield from value.iter_compressed() File "/usr/lib/python3/dist-packages/problem_report.py", line 194, in iter_compressed with open(self.filename, "rb") as compressed_file: ^ FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/systemd/coredump/core.tracker-extract.1000.92c6d53b71364e3286fd6011f3dad5e7.4441.171084529900.zst' ``` ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: apport 2.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-19.19-generic 6.8.0 Uname: Linux 6.8.0-19-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CrashReports: 640:1000:1000:31075:2024-03-19 11:48:24.843744754 +0100:2024-03-19 11:48:25.843744754 +0100:/var/crash/_usr_share_apport_apport.0.crash Date: Tue Mar 19 11:48:23 2024 ExecutablePath: /usr/share/apport/apport InstallationDate: Installed on 2023-09-19 (182 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) InterpreterPath: /usr/bin/python3.12 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport --from-systemd-coredump 0-4553-0 ProcEnviron: Error: [Errno 13] Permission denied: 'environ' Python3Details: /usr/bin/python3.12, Python 3.12.2, python3-minimal, 3.12.1-0ubuntu2 PythonArgs: ['/usr/share/apport/apport', '--from-systemd-coredump', '0-4553-0'] PythonDetails: N/A SourcePackage: apport Title: apport crashed with FileNotFoundError in iter_compressed(): [Errno 2] No such file or directory: '/var/lib/systemd/coredump/core.tracker-extract.1000.92c6d53b71364e3286fd6011f3dad5e7.4441.171084529900.zst' UpgradeStatus: Upgraded to noble on 2024-01-12 (67 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sudo users ** Affects: apport (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-crash noble wayland-session ** Description changed: Ubuntu 24.04 (noble) VM. + + ``` + Traceback (most recent call last): + File "/usr/share/apport/apport", line 1244, in + sys.exit(main(sys.argv[1:])) + ^^ + File "/usr/share/apport/apport", line 761, in main + return process_crash_from_systemd_coredump(options.systemd_coredump_instance) + ^^ + File "/usr/share/apport/apport", line 1240, in process_crash_from_systemd_coredump + return process_crash(report, real_user, report_owner) +^^ + File "/usr/share/apport/apport", line 1146, in process_crash + info.write(reportfile) + File "/usr/lib/python3/dist-packages/problem_report.py", line 548, in write + self._write_binary_item_compressed_and_encoded(file, k) + File "/usr/lib/python3/dist-packages/problem_report.py", line 722, in _write_binary_item_compressed_and_encoded + self._write_binary_item_base64_encoded( + File "/usr/lib/python3/dist-packages/problem_report.py", line 629, in _write_binary_item_base64_encoded + for chunk in chunks: + File "/usr/lib/python3/dist-packages/problem_report.py", line 649, in _generate_compressed_chunks + yield from value.iter_compressed() + File "/usr/lib/python3/dist-packages/problem_report.py", line 194, in iter_compressed + with open(self.filename, "rb") as compressed_file: + ^ + FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/systemd/coredump/core.tracker-extract.1000.92c6d53b71364e3286fd6011f3dad5e7.4441.171084529900.zst' + ``` ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: apport 2.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-19.19-generic 6
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
And here is the diff for focal (which I also tested in my PPA).
** Patch added: "initramfs-tools_0.136ubuntu6.8.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+attachment/5757181/+files/initramfs-tools_0.136ubuntu6.8.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
Status in initramfs-tools package in Ubuntu:
Fix Committed
Status in open-iscsi package in Ubuntu:
Invalid
Status in initramfs-tools source package in Focal:
New
Status in open-iscsi source package in Focal:
New
Status in initramfs-tools source package in Jammy:
New
Status in open-iscsi source package in Jammy:
New
Bug description:
[ Impact ]
* MAAS cannot PXE-boot a machine that has iSCSI disks
* Focal is the default Ubuntu distribution deployed by MAAS, so we should
back-port this to ensure it works out-of-the-box.
[ Test Plan ]
* reproducing this issue requires a machine with iSCSI disks (Cisco UCS
Manager
in the original report), and a MAAS controller (3.4 or better)
* the issue can be observed by simply enlisting the machine in MAAS. It will
fail to boot due to the missing BOOTIF configuration.
[ Where problems could occur ]
* the problematic code was an attempt to fix LP#2037202, so we should watch
out
for regressions.
[ Original report ]
we have a bad interaction between initramfs-tools and open-iscsi,
resulting in the boot interface not being configured.
when the iscsi has a static address, the script `local-top/iscsi` from
open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi
interface. The existence of this file makes configure_networking()
skip configuring the BOOTIF later due to this code in
`scripts/functions`:
for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do
if [ -e "$x" ]; then
IP=done
break
fi
done
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058380] Re: apport crashed with FileNotFoundError in iter_compressed(): [Errno 2] No such file or directory: '/var/lib/systemd/coredump/core.tracker-extract.1000.92c6d53b71364e3
``` $ ls -l /var/lib/systemd/coredump insgesamt 444 -rw-r-+ 1 root root 447430 M\U19 11:48 core.tracker-extract.1000.92c6d53b71364e3286fd6011f3dad5e7.4887.171084530100.zst ``` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2058380 Title: apport crashed with FileNotFoundError in iter_compressed(): [Errno 2] No such file or directory: '/var/lib/systemd/coredump/core.tracker- extract.1000.92c6d53b71364e3286fd6011f3dad5e7.4441.171084529900.zst' Status in apport package in Ubuntu: New Bug description: Ubuntu 24.04 (noble) VM. ``` Traceback (most recent call last): File "/usr/share/apport/apport", line 1244, in sys.exit(main(sys.argv[1:])) ^^ File "/usr/share/apport/apport", line 761, in main return process_crash_from_systemd_coredump(options.systemd_coredump_instance) ^^ File "/usr/share/apport/apport", line 1240, in process_crash_from_systemd_coredump return process_crash(report, real_user, report_owner) ^^ File "/usr/share/apport/apport", line 1146, in process_crash info.write(reportfile) File "/usr/lib/python3/dist-packages/problem_report.py", line 548, in write self._write_binary_item_compressed_and_encoded(file, k) File "/usr/lib/python3/dist-packages/problem_report.py", line 722, in _write_binary_item_compressed_and_encoded self._write_binary_item_base64_encoded( File "/usr/lib/python3/dist-packages/problem_report.py", line 629, in _write_binary_item_base64_encoded for chunk in chunks: File "/usr/lib/python3/dist-packages/problem_report.py", line 649, in _generate_compressed_chunks yield from value.iter_compressed() File "/usr/lib/python3/dist-packages/problem_report.py", line 194, in iter_compressed with open(self.filename, "rb") as compressed_file: ^ FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/systemd/coredump/core.tracker-extract.1000.92c6d53b71364e3286fd6011f3dad5e7.4441.171084529900.zst' ``` ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: apport 2.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-19.19-generic 6.8.0 Uname: Linux 6.8.0-19-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CrashReports: 640:1000:1000:31075:2024-03-19 11:48:24.843744754 +0100:2024-03-19 11:48:25.843744754 +0100:/var/crash/_usr_share_apport_apport.0.crash Date: Tue Mar 19 11:48:23 2024 ExecutablePath: /usr/share/apport/apport InstallationDate: Installed on 2023-09-19 (182 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) InterpreterPath: /usr/bin/python3.12 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport --from-systemd-coredump 0-4553-0 ProcEnviron: Error: [Errno 13] Permission denied: 'environ' Python3Details: /usr/bin/python3.12, Python 3.12.2, python3-minimal, 3.12.1-0ubuntu2 PythonArgs: ['/usr/share/apport/apport', '--from-systemd-coredump', '0-4553-0'] PythonDetails: N/A SourcePackage: apport Title: apport crashed with FileNotFoundError in iter_compressed(): [Errno 2] No such file or directory: '/var/lib/systemd/coredump/core.tracker-extract.1000.92c6d53b71364e3286fd6011f3dad5e7.4441.171084529900.zst' UpgradeStatus: Upgraded to noble on 2024-01-12 (67 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2058380/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058628] Re: initramfs-tools dhcpcd timeout
Thank you for taking the time to report this bug and helping to make
Ubuntu better. I addressed this in initramfs-tools 0.142ubuntu21 (which
is still in noble-proposed):
* configure_networking:
- Increase minimum timeout to 30 seconds
** Changed in: initramfs-tools (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2058628
Title:
initramfs-tools dhcpcd timeout
Status in initramfs-tools package in Ubuntu:
Fix Committed
Bug description:
Hi,
We found an issue in `initramfs-tools-core` (noble,now 0.142ubuntu20
all) related to this change :
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2024164
(dhclient replaced by dhcpcd).
dhclient was faster to give an IP. In the `initramfs-tools-core`
scripts, in **/usr/share/initramfs-tools/scripts/functions**, the
ROUNDTTT iterations at _2, 3, 4 or even 6 seconds_ fail. This delays
obtaining an IPv4 by at least 20 seconds.
```
# support ip options see linux sources
# Documentation/filesystems/nfs/nfsroot.txt
# Documentation/frv/booting.txt
for ROUNDTTT in 2 3 4 6 9 16 25 36 64 100; do
local iter_entry_time iter_exit_time
iter_entry_time=$(time_elapsed)
if [ -z "${DEVICE}" ]; then
_set_available_devices_to_up
fi
case ${IP} in
none|done|off)
# Do nothing
IP="done"
;;
""|on|any|dhcp|bootp|both)
dhcpcd -1 -t $ROUNDTTT -4 ${DEVICE:+"${DEVICE}"}
;;
*)
ipconfig -t ${ROUNDTTT} -d "$IP"
```
dhcpcd takes at least 5/6 seconds to give an ipv4 because of the arp
probbing to check that the ip is not already in use.
**Possible Fixes**: `dhcpcd --noarp` prevents waiting, otherwise
redistribute the ROUNDTTT iterations by deleting the iterations at 2 3
4 or even 6 seconds.
NB: this problem probably only concerns obtaining an IP in IPv4, I
have not checked if the problem also arises in IPv6.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2058628/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
Sponsored plymouth 24.004.60-1ubuntu6 after dropping the complete drm modules code and correcting the changelog entries. Unsubscribing ~ubuntu-sponsors. ** Patch added: "plymouth_24.004.60-1ubuntu6_sponsored.debdiff" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1970069/+attachment/5757922/+files/plymouth_24.004.60-1ubuntu6_sponsored.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in plymouth package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
** Changed in: plymouth (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in plymouth package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
https://salsa.debian.org/ubuntu-dev- team/plymouth/-/commit/bd9d0119fdbeb3b30c8d3caafdb8a31b23c188c4 does not reflect the removal of the complete drm section. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in plymouth package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2059976] Re: unmkinitramfs is very slow on initrd from ubuntu 23.10+, solution proposed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Speed improvements are welcome. Please submit those
changes (preferred in the smallest possible chunks).
Maybe we should rewrite splitinitramfs (or the complete script) in C.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2059976
Title:
unmkinitramfs is very slow on initrd from ubuntu 23.10+, solution
proposed
Status in initramfs-tools package in Ubuntu:
New
Bug description:
Since 23.10 the initrd consists of 4 embedded cpio:
- amd microcode
- intel microcode
- firmware + kernel modules
- rest (compressed)
Previously it was:
- amd microcode
- intel microcode
- rest (compressed)
There is no archive size header for cpio, so unmkinitramfs has to
parse headers of each entry in uncompressed archives.
> time unmkinitramfs 23.04/{initrd,unpack}
real0m3.625s
user0m1.595s
sys 0m3.467s
> time unmkinitramfs 23.10/{initrd,unpack}
real0m15.982s
user0m20.174s
sys 0m6.995s
> for dir in 23.04/unpack/early*; do printf '%-20s %s\n' "$dir" "$(find
"$dir" | wc -l)"; done
23.04/unpack/early 5
23.04/unpack/early2 6
> for dir in 23.10/unpack/early*; do printf '%-20s %s\n' "$dir" "$(find
"$dir" | wc -l)"; done
23.10/unpack/early 5
23.10/unpack/early2 6
23.10/unpack/early3 2874
Here https://github.com/slowpeek/unmkinitramfs-turbo I've made it a lot
faster with two changes:
- bash instead of sh for bash's "read -N"
- xxd dump of initrd instead of raw binary data
I wonder, if the developers are interested in accepting my improvements into
the code base?
> time unmkinitramfs-classic-turbo 23.10/{initrd,unpack}
real0m2.209s
user0m2.161s
sys 0m1.341s
> time unmkinitramfs-turbo 23.10/{initrd,unpack}
early .. +
early2 .. +
early3 .. +
main .. +
real0m1.973s
user0m2.094s
sys 0m1.244s
All tools in the repo, even the classic one, feature -s/--scan option. With
it, the tools only dump offset + size for embedded archives, nothing is
unpacked. It can be used to measure parsing speed.
In the repo there are three tools:
- unmkinitramfs-classic: the original tool
- unmkinitramfs-classic-turbo: the improved tool with minimal changes
- unmkinitramfs-turbo: the improved tool with many changes to my tastes,
extra dependency on "file" and some additional features (-ss option,
decompression with 7za)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2059976/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055718] Re: timezone changed unexpectedly from EST to America/Adak or America/Indiana/Indianapolis
Fix committed: https://salsa.debian.org/glibc- team/tzdata/-/commit/7cef9e552df97611cd7f097c867f21138cbfa7ba -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2055718 Title: timezone changed unexpectedly from EST to America/Adak or America/Indiana/Indianapolis Status in tzdata package in Ubuntu: Triaged Bug description: A user reported this regression on https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739: UPDATE: I don't think it's a regression anymore, see comment #5 """ Hello. After automatic upgrade of tzdata from 2023c-0ubuntu0.22.04.2 to 2024a-0ubuntu0.22.04 the previously set EST time zone was automatically changed to "America/Adak" or "America/Indiana/Indianapolis" on all our servers (50+). Look like a bug in tzdata configure script. """ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2055718/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055718] Re: timezone changed unexpectedly from EST to America/Adak or America/Indiana/Indianapolis
** Also affects: tzdata (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: tzdata (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: tzdata (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2055718 Title: timezone changed unexpectedly from EST to America/Adak or America/Indiana/Indianapolis Status in tzdata package in Ubuntu: Triaged Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Mantic: New Bug description: A user reported this regression on https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739: UPDATE: I don't think it's a regression anymore, see comment #5 """ Hello. After automatic upgrade of tzdata from 2023c-0ubuntu0.22.04.2 to 2024a-0ubuntu0.22.04 the previously set EST time zone was automatically changed to "America/Adak" or "America/Indiana/Indianapolis" on all our servers (50+). Look like a bug in tzdata configure script. """ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2055718/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054902] Re: apport test error: /bin/bash not found
Proposed fix: https://github.com/canonical/apport/pull/308
** Changed in: apport
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2054902
Title:
apport test error: /bin/bash not found
Status in Apport:
In Progress
Status in apport package in Ubuntu:
New
Bug description:
This looks like fallout from the completion of usrmerge.
https://autopkgtest.ubuntu.com/packages/apport
=== FAILURES
===
367s ___ T.test_get_file_package
367s
367s self =
367s
367s def test_get_file_package(self):
367s """get_file_package() on installed files."""
367s > self.assertEqual(impl.get_file_package("/bin/bash"), "bash")
367s E AssertionError: None != 'bash'
367s
367s tests/integration/test_packaging_apt_dpkg.py:158: AssertionError
367s ___ T.test_get_files
___
367s
367s self =
367s
367s def test_get_files(self):
367s """get_files()."""
367s self.assertRaises(ValueError, impl.get_files, "nonexisting")
367s > self.assertIn("/bin/bash", impl.get_files("bash"))
367s E AssertionError: '/bin/bash' not found in ['/.', '/etc',
'/etc/bash.bashrc', '/etc/skel', '/etc/skel/.bash_logout', '/etc/skel/.bashrc',
'/etc/skel/.profile', '/usr', '/usr/bin', '/usr/bin/bash', '/usr/bin/bashbug',
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2054902/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052794] Re: 2.79.1 test issue on s390x
This test has been fixed upstream: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3920 and therefore fixed in 2.80.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2052794 Title: 2.79.1 test issue on s390x Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: In Progress Bug description: One of the newly added tests in the 2.79 serie is failing on s390x. The issue is being discussed upstream on https://gitlab.gnome.org/GNOME/glib/-/issues/3252 , the test is new and is currently buggy. Upstream/Debian/Ubuntu already disabled similar tests in 2.79.1 but that one as not noticed to fail because it's skipped during build so is only showing now in the installed- tests result and in autopkgtest. (And the package is in Debian/experimental where it didn't get tested by the Debian CI) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/2052794/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2059739] Re: initramfs-tools 0.142ubuntu23 copies host /etc/passwd into initramfs
Thank you for taking the time to report this bug and contributing to Ubuntu. The dhcpcd user is created by dhcpcd-base. So the user should exist. Please test the attached patch that only copies the dhcpcd user into the initramfs. ** Patch added: "0001-Copy-only-dhcpcd-user-into-initramfs-etc-passwd.patch" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2059739/+attachment/5761741/+files/0001-Copy-only-dhcpcd-user-into-initramfs-etc-passwd.patch ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Medium ** Changed in: initramfs-tools (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2059739 Title: initramfs-tools 0.142ubuntu23 copies host /etc/passwd into initramfs Status in initramfs-tools package in Ubuntu: In Progress Bug description: Recent changes to the dhcpd hook shipped with dhcpdinitramfs-tools 0.142ubuntu23 (noble-dev) copy the host /etc/passwd into the initramfs-image: https://git.launchpad.net/ubuntu/+source/initramfs-tools/commit/hooks/dhcpcd?h=applied/ubuntu/noble&id=73c865b9d234087d977d7baa20852639746567fd This has multiple problems: * The passwd file is copied without checking if the dhcpcd user actually exists (which is created by dhcpcd package, but only dhcpcd-base is installed via dependencies) * The change breaks dropbear-initramfs because the passwd file contains a root user with a non existing home directory * leaking user information into initramfs (which may or may not be a problem on fully encrypted systems) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2059739/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055718] Re: timezone changed unexpectedly from EST to America/Adak or America/Indiana/Indianapolis
Here is the debdiff for jammy. debian/test_timezone_conversions found even more inconsistencies in jammy: ERROR: Following 4 timezones cannot be selected, but are not converted: America/Fort_Wayne America/Indianapolis America/Knox_IN America/Louisville ERROR: Following 3 timezones are conversion targets, but are not available: Asia/Riyadh87 Asia/Riyadh88 Asia/Riyadh89 ERROR: Following 4 timezones are conversion targets, but are not selectable: America/Indianapolis Asia/Riyadh87 Asia/Riyadh88 Asia/Riyadh89 ERROR: Following 1 timezones are converted, but they do not match their symlink targets: US/Indiana-Starke ** Patch added: "tzdata_2024a-0ubuntu0.22.04.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2055718/+attachment/5761748/+files/tzdata_2024a-0ubuntu0.22.04.1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2055718 Title: timezone changed unexpectedly from EST to America/Adak or America/Indiana/Indianapolis Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Mantic: New Bug description: A user reported this regression on https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739: UPDATE: I don't think it's a regression anymore, see comment #5 """ Hello. After automatic upgrade of tzdata from 2023c-0ubuntu0.22.04.2 to 2024a-0ubuntu0.22.04 the previously set EST time zone was automatically changed to "America/Adak" or "America/Indiana/Indianapolis" on all our servers (50+). Look like a bug in tzdata configure script. """ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2055718/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055718] Re: timezone changed unexpectedly from EST to America/Adak or America/Indiana/Indianapolis
The debdiff for focal is similar to the debdiff for jammy. Only debian/test_timezone_conversions needed some modification to work with the older Python version. ** Patch added: "tzdata_2024a-0ubuntu0.20.04.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2055718/+attachment/5761753/+files/tzdata_2024a-0ubuntu0.20.04.1.debdiff ** Description changed: + [ Impact ] + + On every tzdata package upgrade the configured timezone might be updated + to an incorrect one. + + I enhanced debian/test_timezone_conversions to detect those + inconsistencies and fixed everything that was found by this check. The + SRUs contain a backport of the script from noble. + + [ Test Plan ] + + debian/test_timezone_conversions is enhanced to check the timezone + conversions for consistency to prevent such kind of issues in the + future. debian/test_timezone_conversions is run during built and as + autopkgtest. + + In addition, manual check can be done. The following test should stay at + `EST` (and not update to `America/Adak`): + + ``` + ln -sf /usr/share/zoneinfo/EST /etc/localtime + dpkg-reconfigure --frontend noninteractive tzdata + ls -alh /etc/localtime + ``` + + `US/East-Indiana` should be updated to `America/Indiana/Indianapolis` + and not to `America/Adak`: + + ``` + ln -sf /usr/share/zoneinfo/US/East-Indiana /etc/localtime + dpkg-reconfigure --frontend noninteractive tzdata + ``` + + `America/Louisville` should be updated to `America/Kentucky/Louisville` + and not to `America/Adak`: + + ``` + ln -sf /usr/share/zoneinfo/America/Louisville /etc/localtime + dpkg-reconfigure --frontend noninteractive tzdata + ``` + + [ Other Info ] + + The autopkgtest for chrony is flaky on jammy and newer (see bug + #2002910). + + [ Regression potential ] + + The patch ziguard.awk-Move-link-to-link-feature-from-vanguard-to- + ma.patch moves the link to link feature from vanguard to main dataform + to produce correct symlinks. This results in symlinks that can point to + symlinks. The zic from glibc that we use can handle that, but there + might be other parsers that read /usr/share/zoneinfo/tzdata.zi directly + and could fail to handle symlinks to symlinks. + + [ Original report ] + A user reported this regression on https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739: UPDATE: I don't think it's a regression anymore, see comment #5 """ Hello. After automatic upgrade of tzdata from 2023c-0ubuntu0.22.04.2 to 2024a-0ubuntu0.22.04 the previously set EST time zone was automatically changed to "America/Adak" or "America/Indiana/Indianapolis" on all our servers (50+). Look like a bug in tzdata configure script. """ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2055718 Title: timezone changed unexpectedly from EST to America/Adak or America/Indiana/Indianapolis Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Mantic: New Bug description: [ Impact ] On every tzdata package upgrade the configured timezone might be updated to an incorrect one. I enhanced debian/test_timezone_conversions to detect those inconsistencies and fixed everything that was found by this check. The SRUs contain a backport of the script from noble. [ Test Plan ] debian/test_timezone_conversions is enhanced to check the timezone conversions for consistency to prevent such kind of issues in the future. debian/test_timezone_conversions is run during built and as autopkgtest. In addition, manual check can be done. The following test should stay at `EST` (and not update to `America/Adak`): ``` ln -sf /usr/share/zoneinfo/EST /etc/localtime dpkg-reconfigure --frontend noninteractive tzdata ls -alh /etc/localtime ``` `US/East-Indiana` should be updated to `America/Indiana/Indianapolis` and not to `America/Adak`: ``` ln -sf /usr/share/zoneinfo/US/East-Indiana /etc/localtime dpkg-reconfigure --frontend noninteractive tzdata ``` `America/Louisville` should be updated to `America/Kentucky/Louisville` and not to `America/Adak`: ``` ln -sf /usr/share/zoneinfo/America/Louisville /etc/localtime dpkg-reconfigure --frontend noninteractive tzdata ``` [ Other Info ] The autopkgtest for chrony is flaky on jammy and newer (see bug #2002910). [ Regression potential ] The patch ziguard.awk-Move-link-to-link-feature-from-vanguard-to- ma.patch moves the link to link feature from vanguard to main dataform to produce correct symlinks. This results in symlinks that can point to symlinks. The zic from glibc that we use can handle that, but there might be other parsers that read /usr/share/zoneinfo/tzdata.zi directly and could fail to handle symlinks to symlinks. [ Original report
[Touch-packages] [Bug 2055718] Re: timezone changed unexpectedly from EST to America/Adak or America/Indiana/Indianapolis
Debdiff for mantic. ** Changed in: tzdata (Ubuntu) Status: Triaged => Fix Committed ** Patch added: "tzdata_2024a-0ubuntu0.23.10.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2055718/+attachment/5761746/+files/tzdata_2024a-0ubuntu0.23.10.1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2055718 Title: timezone changed unexpectedly from EST to America/Adak or America/Indiana/Indianapolis Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Mantic: New Bug description: A user reported this regression on https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739: UPDATE: I don't think it's a regression anymore, see comment #5 """ Hello. After automatic upgrade of tzdata from 2023c-0ubuntu0.22.04.2 to 2024a-0ubuntu0.22.04 the previously set EST time zone was automatically changed to "America/Adak" or "America/Indiana/Indianapolis" on all our servers (50+). Look like a bug in tzdata configure script. """ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2055718/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054902] Re: apport test error: /bin/bash not found
https://github.com/canonical/apport/pull/308 got merged.
** Changed in: apport
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2054902
Title:
apport test error: /bin/bash not found
Status in Apport:
Fix Committed
Status in apport package in Ubuntu:
New
Bug description:
This looks like fallout from the completion of usrmerge.
https://autopkgtest.ubuntu.com/packages/apport
=== FAILURES
===
367s ___ T.test_get_file_package
367s
367s self =
367s
367s def test_get_file_package(self):
367s """get_file_package() on installed files."""
367s > self.assertEqual(impl.get_file_package("/bin/bash"), "bash")
367s E AssertionError: None != 'bash'
367s
367s tests/integration/test_packaging_apt_dpkg.py:158: AssertionError
367s ___ T.test_get_files
___
367s
367s self =
367s
367s def test_get_files(self):
367s """get_files()."""
367s self.assertRaises(ValueError, impl.get_files, "nonexisting")
367s > self.assertIn("/bin/bash", impl.get_files("bash"))
367s E AssertionError: '/bin/bash' not found in ['/.', '/etc',
'/etc/bash.bashrc', '/etc/skel', '/etc/skel/.bash_logout', '/etc/skel/.bashrc',
'/etc/skel/.profile', '/usr', '/usr/bin', '/usr/bin/bash', '/usr/bin/bashbug',
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2054902/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058242] Re: Demote isc-dhcp to universe
Uploaded avahi 0.8-13ubuntu6 to demote isc-dhcp-client from Recommends to Suggests ** Changed in: avahi (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/2058242 Title: Demote isc-dhcp to universe Status in avahi package in Ubuntu: Fix Committed Bug description: Following the replacement of dhclient by dhcpcd as new DHCP client tool, it is now time to demote isc-dhcp-client. After demoting isc- dhcp-server (bug # 2045577) the complete isc-dhcp can be demoted. ``` $ reverse-depends -c main,restricted isc-dhcp-client $ reverse-depends -c main,restricted -b isc-dhcp-client ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/2058242/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 772024] Re: tzdata update keeps changing my timezone
** Changed in: tzdata (Ubuntu Kinetic) Status: New => Won't Fix ** No longer affects: tzdata (Ubuntu Kinetic) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/772024 Title: tzdata update keeps changing my timezone Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata package in Debian: Fix Released Bug description: [ Impact ] Users can select some time zones in debconf that the tzdata debconf script will replace on the next run. See "Original report" for more explanation. Either those time zones should not be selectable in debconf or they should not be replaced. [ Test Plan ] Select US/Central as time zone and run dpkg-reconfigure: ``` sudo ln -sf /usr/share/zoneinfo/US/Central /etc/localtime echo "US/Central" | sudo tee /etc/timezone sudo dpkg-reconfigure -fnoninteractive tzdata ``` The output of dpkg-reconfigure should say that the current default time zone is still US/Central. Besides this manual test, test_timezone_conversions is backported to check that there are no timezones which can be selected, but will be converted. [ Where problems could occur ] Besides added tests, the debconf part of tzdata is touched and could cause issues. The change does not touch the actual timezones. [ Original report ] Other than the fact that Chicago, Illinois is in US Central Timezone, I have no relationship to Chicago. I am not in Chicago. I do not want to be in Chicago. I am in the Central Timezone. I am physically closer to other cities mentioned in tzdata. Selecting America/Chicago versus US/Central is not easier for me nor is it more intuitive. I understand that the upstream tzdata package goes a long way in documenting all of the weirdness associated with timezones and different localities' treatment of timezones and daylight "savings" time. However, from an end-user perspective, the distribution should place no special importance or preference on one timezone specification or another. Likewise, if a user chooses a timezone, the system should never change it. To reproduce the issue: # Manually select US/Central me@ubuntu:~$ sudo dpkg-reconfigure tzdata [sudo] password for me: Current default time zone: 'US/Central' Local time is now: Wed Apr 27 16:05:02 CDT 2011. Universal Time is now: Wed Apr 27 21:05:02 UTC 2011. # Validation that selection was accepted me@ubuntu:~$ cat /etc/timezone US/Central me@ubuntu:~$ md5sum /etc/localtime /usr/share/zoneinfo/US/Central 6540624294b1193e22ed7a15692f2de7 /etc/localtime 6540624294b1193e22ed7a15692f2de7 /usr/share/zoneinfo/US/Central me@ubuntu:~$ debconf-show tzdata debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied tzdata/Zones/Australia: * tzdata/Zones/US: Central tzdata/Zones/Asia: * tzdata/Zones/Etc: UTC tzdata/Zones/SystemV: tzdata/Zones/Arctic: tzdata/Zones/Pacific: tzdata/Zones/Antarctica: tzdata/Zones/Europe: tzdata/Zones/Africa: * tzdata/Zones/America: Chicago * tzdata/Areas: US tzdata/Zones/Atlantic: tzdata/Zones/Indian: # Force the package to reinstall me@ubuntu:~$ aptitude reinstall tzdata The following packages will be REINSTALLED: tzdata 0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/658 kB of archives. After unpacking 0 B will be used. Preconfiguring packages ... (Reading database ... 168356 files and directories currently installed.) Preparing to replace tzdata 2011g-0ubuntu0.11.04 (using .../tzdata_2011g-0ubuntu0.11.04_all.deb) ... Unpacking replacement tzdata ... Setting up tzdata (2011g-0ubuntu0.11.04) ... Current default time zone: 'America/Chicago' Local time is now: Wed Apr 27 16:05:22 CDT 2011. Universal Time is now: Wed Apr 27 21:05:22 UTC 2011. Run 'dpkg-reconfigure tzdata' if you wish to change it. # Now previous indicators are reset to America/Chicago instead of US/Central ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: tzdata 2011g-0ubuntu0.11.04 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Wed Apr 27 15:54:33 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) PackageArchitecture: all ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 LANGUAGE=en_US:en SourcePackage: tzdata UpgradeStatus: Upgraded to natty on 2011-04-10 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/772024/+subscriptions -- Mailing lis
[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
clevis/18-1ubuntu1 ran into a timeout. I retried the test.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
Status in initramfs-tools package in Ubuntu:
Fix Released
Status in open-iscsi package in Ubuntu:
Invalid
Status in initramfs-tools source package in Focal:
Fix Committed
Status in open-iscsi source package in Focal:
New
Status in initramfs-tools source package in Jammy:
Fix Committed
Status in open-iscsi source package in Jammy:
New
Bug description:
[ Impact ]
* MAAS cannot PXE-boot a machine that has iSCSI disks
* Focal is the default Ubuntu distribution deployed by MAAS, so we should
back-port this to ensure it works out-of-the-box.
[ Test Plan ]
* reproducing this issue requires a machine with iSCSI disks (Cisco UCS
Manager
in the original report), and a MAAS controller (3.4 or better)
* the issue can be observed by simply enlisting the machine in MAAS. It will
fail to boot due to the missing BOOTIF configuration.
[ Where problems could occur ]
* the problematic code was an attempt to fix LP#2037202, so we should watch
out
for regressions.
[ Original report ]
we have a bad interaction between initramfs-tools and open-iscsi,
resulting in the boot interface not being configured.
when the iscsi has a static address, the script `local-top/iscsi` from
open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi
interface. The existence of this file makes configure_networking()
skip configuring the BOOTIF later due to this code in
`scripts/functions`:
for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do
if [ -e "$x" ]; then
IP=done
break
fi
done
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058628] Re: initramfs-tools dhcpcd timeout
initramfs-tools 0.142ubuntu23 landed in noble.
** Changed in: initramfs-tools (Ubuntu)
Status: Fix Committed => Confirmed
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2058628
Title:
initramfs-tools dhcpcd timeout
Status in initramfs-tools package in Ubuntu:
Fix Released
Bug description:
Hi,
We found an issue in `initramfs-tools-core` (noble,now 0.142ubuntu20
all) related to this change :
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2024164
(dhclient replaced by dhcpcd).
dhclient was faster to give an IP. In the `initramfs-tools-core`
scripts, in **/usr/share/initramfs-tools/scripts/functions**, the
ROUNDTTT iterations at _2, 3, 4 or even 6 seconds_ fail. This delays
obtaining an IPv4 by at least 20 seconds.
```
# support ip options see linux sources
# Documentation/filesystems/nfs/nfsroot.txt
# Documentation/frv/booting.txt
for ROUNDTTT in 2 3 4 6 9 16 25 36 64 100; do
local iter_entry_time iter_exit_time
iter_entry_time=$(time_elapsed)
if [ -z "${DEVICE}" ]; then
_set_available_devices_to_up
fi
case ${IP} in
none|done|off)
# Do nothing
IP="done"
;;
""|on|any|dhcp|bootp|both)
dhcpcd -1 -t $ROUNDTTT -4 ${DEVICE:+"${DEVICE}"}
;;
*)
ipconfig -t ${ROUNDTTT} -d "$IP"
```
dhcpcd takes at least 5/6 seconds to give an ipv4 because of the arp
probbing to check that the ip is not already in use.
**Possible Fixes**: `dhcpcd --noarp` prevents waiting, otherwise
redistribute the ROUNDTTT iterations by deleting the iterations at 2 3
4 or even 6 seconds.
NB: this problem probably only concerns obtaining an IP in IPv4, I
have not checked if the problem also arises in IPv6.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2058628/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2060358] Re: [FFe] Please add German (Noted) layout
Here is the debdiff. I tested this change and the layout on noble (via https://launchpad.net/~bdrung/+archive/ubuntu/staging). This feature should have a low regression risk since it just add a new keyboard layout. This layout is added to the "exotic" list. ** Summary changed: - Please add German (Noted) layout + [FFe] Please add German (Noted) layout ** Patch added: "xkeyboard-config_2.41-2ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/2060358/+attachment/5761852/+files/xkeyboard-config_2.41-2ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/2060358 Title: [FFe] Please add German (Noted) layout Status in xkeyboard-config package in Ubuntu: New Bug description: Please add the newest layout of the German Neo keyboard layout family. Noted is a layout designed to make typing as comfortable and efficient as possible in both German and English. It was developed with the help of a layout optimizer, which is based on the metrics and concepts of ArneBab's optimizer and adapts and extends them. I switched from Neo 2 via Mine to Noted and I like to see this variant to be available out of the box in Ubuntu. Sources: * https://neo-layout.org/Layouts/noted/ * https://dariogoetz.github.io/noted-layout/ Forwarded upstream: https://gitlab.freedesktop.org/xkeyboard- config/xkeyboard-config/-/merge_requests/681 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/2060358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2060010] Re: apport-bug fails for libglapi-mesa (= 24.0.3-1ubuntu3)
This could be a fallout of the xz rebuild. Do you have packages on your system that cannot be found in any repository any more? What does `apt policy libglapi-mesa` say? ** Changed in: apport (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2060010 Title: apport-bug fails for libglapi-mesa (= 24.0.3-1ubuntu3) Status in apport package in Ubuntu: Incomplete Bug description: Running apport-bug for libglapi-mesa (= 24.0.3-1ubuntu3) results in a message: The problem cannot be reported: 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. apt-get update && apt-get dist-upgrade does not resolve the problem. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: apport 2.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-20.20-generic 6.8.1 Uname: Linux 6.8.0-20-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Apr 2 09:35:33 2024 InstallationDate: Installed on 2021-07-01 (1006 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2060010/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
