[Touch-packages] [Bug 2084089] Re: ZFS with disk encryption missing cryptoswap: new oracular installs and release upgrades
Tagging incoming and systemd - it appears we want an archive fix related to systemd-cryptsetup - what is the next step? ** Tags added: rls-pp-incoming ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: subiquity (Ubuntu) Status: Triaged => 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/2084089 Title: ZFS with disk encryption missing cryptoswap: new oracular installs and release upgrades Status in subiquity package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Bug description: After installing Oracular for the "Install (entire disk with ZFS plus encryption) in Ubuntu Desktop amd64" ISO testing and rebooting the system I noticed that the swap was not activated. I can see this in the systemd journal out 09 19:25:13 danilo-Aspire-ES1-572 systemd[1]: dev-disk-by\x2did-dm\x2duuid\x2dCRYPT\x2dPLAIN\x2ddm_crypt\x2d0.device: Job dev-disk-by\x2did-dm\x2duuid\x2dCRYPT\x2dPLAIN\x2ddm_crypt\x2d0.device/start timed out. out 09 19:25:13 danilo-Aspire-ES1-572 systemd[1]: Timed out waiting for device dev-disk-by\x2did-dm\x2duuid\x2dCRYPT\x2dPLAIN\x2ddm_crypt\x2d0.device - /dev/disk/by-id/dm-uuid-CRYPT-PLAIN-dm_crypt-0. out 09 19:25:13 danilo-Aspire-ES1-572 systemd[1]: Dependency failed for dev-disk-by\x2did-dm\x2duuid\x2dCRYPT\x2dPLAIN\x2ddm_crypt\x2d0.swap - /dev/disk/by-id/dm-uuid-CRYPT-PLAIN-dm_crypt-0. out 09 19:25:13 danilo-Aspire-ES1-572 systemd[1]: Dependency failed for swap.target - Swaps. out 09 19:25:13 danilo-Aspire-ES1-572 systemd[1]: swap.target: Job swap.target/start failed with result 'dependency'. out 09 19:25:13 danilo-Aspire-ES1-572 systemd[1]: dev-disk-by\x2did-dm\x2duuid\x2dCRYPT\x2dPLAIN\x2ddm_crypt\x2d0.swap: Job dev-disk-by\x2did-dm\x2duuid\x2dCRYPT\x2dPLAIN\x2ddm_crypt\x2d0.swap/start failed with result 'dependency'. out 09 19:25:13 danilo-Aspire-ES1-572 systemd[1]: dev-disk-by\x2did-dm\x2duuid\x2dCRYPT\x2dPLAIN\x2ddm_crypt\x2d0.device: Job dev-disk-by\x2did-dm\x2duuid\x2dCRYPT\x2dPLAIN\x2ddm_crypt\x2d0.device/start failed with result 'timeout'. # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS loop0 7:00 4K 1 loop /snap/bare/5 loop1 7:10 74,2M 1 loop /snap/core22/1621 loop2 7:20 11,7M 1 loop /snap/desktop-security-center/32 loop3 7:30 272M 1 loop /snap/firefox/5091 loop4 7:40 10,7M 1 loop /snap/firmware-updater/127 loop5 7:50 505,1M 1 loop /snap/gnome-42-2204/176 loop6 7:60 89,7M 1 loop /snap/gtk-common-themes/1536 loop7 7:7014M 1 loop /snap/prompting-client/51 loop8 7:80 10,7M 1 loop /snap/snap-store/1218 loop9 7:90 564K 1 loop /snap/snapd-desktop-integration/247 loop10 7:10 0 38,8M 1 loop /snap/snapd/21759 loop11 7:11 0 149,9M 1 loop /snap/thunderbird/526 sda8:00 223,6G 0 disk ├─sda1 8:10 1M 0 part ├─sda2 8:20 2G 0 part ├─sda3 8:30 4G 0 part └─sda4 8:40 217,6G 0 part sr0 11:01 1024M 0 rom zd0 230:0020M 0 disk └─keystore-rpool 252:00 4M 0 crypt /run/keystore/rpool # ls -l /dev/mapper/ total 0 crw--- 1 root root 10, 236 out 9 19:23 control lrwxrwxrwx 1 root root 7 out 9 19:23 keystore-rpool -> ../dm-0 # cat /etc/crypttab dm_crypt-0 PARTUUID=e3ce6d46-c340-4d83-b40f-87eeff46c4bc /dev/urandom cipher=aes-cbc-essiv:sha256,initramfs,plain,size=256,swap root@danilo-Aspire-ES1-572:~# # ls -l /dev/disk/by-id/ total 0 lrwxrwxrwx 1 root root 9 out 9 19:23 ata-HL-DT-ST_DVDRAM_GUE1N_KXKG7P34019 -> ../../sr0 lrwxrwxrwx 1 root root 9 out 9 19:23 ata-SanDisk_SSD_PLUS_240_GB_174336804972 -> ../../sda lrwxrwxrwx 1 root root 10 out 9 19:23 ata-SanDisk_SSD_PLUS_240_GB_174336804972-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 out 9 19:23 ata-SanDisk_SSD_PLUS_240_GB_174336804972-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 out 9 19:23 ata-SanDisk_SSD_PLUS_240_GB_174336804972-part3 -> ../../sda3 lrwxrwxrwx 1 root root 10 out 9 19:23 ata-SanDisk_SSD_PLUS_240_GB_174336804972-part4 -> ../../sda4 lrwxrwxrwx 1 root root 10 out 9 19:23 dm-name-keystore-rpool -> ../../dm-0 lrwxrwxrwx 1 root root 10 out 9 19:23 dm-uuid-CRYPT-LUKS2-c09e07539b4c4db39637f9503b6eca56-keystore-rpool -> ../../dm-0 lrwxrwxrwx 1 root root 9 out 9 19:23 wwn-0x50014800 -> ../../sr0 lrwxrwxrwx 1 root root 9 out 9 19:23 wwn-0x5001b448b64d0ef0 -> ../../sda lrwxrwxrwx 1 root root 10 out 9 19:23 wwn-0x5001b448b64d0ef0-part1 -> ../../sda1 lrwxrwxrwx 1 root
[Touch-packages] [Bug 2081684] Re: Things depending on libmount1 complain MOUNT_2_40 not found
** Tags removed: rls-oo-incoming ** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2081684 Title: Things depending on libmount1 complain MOUNT_2_40 not found Status in util-linux package in Ubuntu: New Bug description: I have upgraded to the oracular beta yesterday on my home machine. After upgrading I started to notice errors issued by libgio that MOUNT_2_40 could not be found despite having libmount1 2.40.2 installed as part the upgrade. On reboot I noticed that gdm no longer starts, and networking is broken. Even running nmcli in a tty fails with the same complaint. Loggin in on a tty using username and password still works but the system is broken. I have tried using a live environment and chrooting to reinstall libmount1, util-linux and libglib2.0 and libc6 packages as recommended on the arch forums (only arch users seem to have encountered this before me). The reinstalls were successful but the error message did not go away when I tried to run nmcli or other libgio using programs. Please give this a look since it might break many people's machines trying the beta like I tried to do. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2081684/+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 2078573] Re: I can no longer boot from my Thunderbolt disk
** Tags removed: rls-nn-incoming ** Tags added: foundations-todo ** Changed in: initramfs-tools (Ubuntu) Assignee: (unassigned) => Benjamin Drung (bdrung) -- 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/2078573 Title: I can no longer boot from my Thunderbolt disk Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Won't Fix Bug description: Description: Ubuntu 24.04.1 LTS Release: 24.04 Package:linux-image-6.8.0-41-generic Since the kernel 6.8.0-36 has been updated to a newer version, I can no longer boot from my Thunderbolt disk. Even with the current kernel 6.8.0-41 it does not work. If I boot with the old kernel 6.8.0-36 it still works, but I don't want to work with it forever. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-41-generic 6.8.0-41.41 ProcVersionSignature: Ubuntu 6.8.0-36.36-generic 6.8.4 Uname: Linux 6.8.0-36-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:roman 2357 F pipewire /dev/snd/controlC0: roman 2361 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Aug 31 18:34:27 2024 InstallationDate: Installed on 2024-07-07 (55 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Dell Inc. Latitude 5550 ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-36-generic root=/dev/mapper/cryptvg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-36-generic N/A linux-backports-modules-6.8.0-36-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2024 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.1 dmi.board.name: 0314H2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnDellInc.:bvr1.6.1:bd07/18/2024:br1.6:efr1.5:svnDellInc.:pnLatitude5550:pvr:rvnDellInc.:rn0314H2:rvrA00:cvnDellInc.:ct10:cvr:sku0CB9: dmi.product.family: Latitude dmi.product.name: Latitude 5550 dmi.product.sku: 0CB9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2078573/+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 2003266] Re: 22.04 package lacks GSSAPI support
LGTM, uploading, thank you! ** Changed in: neon27 (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to neon27 in Ubuntu. https://bugs.launchpad.net/bugs/2003266 Title: 22.04 package lacks GSSAPI support Status in neon27 package in Ubuntu: Confirmed Status in neon27 source package in Jammy: Fix Committed Bug description: [ Impact ] * GSSAPI was disabled by accident as a side-effect of packaging a new release. Upstream renamed the environment variable used to setup the feature and the flag was not updated in d/rules. * Users get caught off-guard when updating from 20.04 to 22.04, 24.04 is not affected. [ Test Plan ] * Did not test the binary, confirmed the fix is effective by analyzing the build logs. * I've confirmed that the issue is solved by checking for the presence of the following string in the build logs: checking for krb5-config... /usr/bin/krb5-config.mit Whereas a build with the issue will instead output: checking for krb5-config... none * I believe the fix is non-intrusive enough that no further testing is needed. [ Where problems could occur ] * Enabling a new feature could have a side effect of disabling another mutually-exclusive feature, but I did not identify any. * Enabling a new feature could break a different feature which changes its behavior when this new feature is present, I also did not identify any such case. [ Other Info ] * Upstream bug reports: - https://github.com/notroj/neon/issues/102 - https://github.com/notroj/neon/issues/52 * Upstream breaking change: - https://github.com/notroj/neon/commit/b9b7425de38b35249e689c03c30c8fd8adfae806 * Upstream change to avoid this from happening again: - https://github.com/notroj/neon/commit/4fdcff4a0ccbb0924f7dabcf8d213452aa33ab82 * Launchpad bug: - https://bugs.launchpad.net/ubuntu/+source/neon27/+bug/2003266 [ Original description ] For more information, please see https://github.com/notroj/neon/issues/102. The 22.04 built package of neon lacks GSSAPI support, whereas previous versions (e.g. 18.04) had this support built-in. This appears to be due to a recent-ish change in the build logic for neon, which changes when GSSAPI is compiled in to the library (https://github.com/notroj/neon/commit/b9b7425de38b35249e689c03c30c8fd8adfae806) We were able to get a work around building from source with the following envvar during build-time: KRB5_CONF_TOOL=/usr/bin/krb5-config.mit ./configure. TL;DR: KRB5_CONFIG became KRB5_CONF_TOOL. Version information: $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt show libneon27 Package: libneon27 Version: 0.32.2-1 Priority: optional Section: universe/libs Source: neon27 Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Laszlo Boszormenyi (GCS) Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 233 kB Depends: libc6 (>= 2.33), libssl3 (>= 3.0.0~~alpha1), libxml2 (>= 2.7.4), zlib1g (>= 1:1.1.4) Homepage: https://notroj.github.io/neon/ Download-Size: 102 kB APT-Manual-Installed: no APT-Sources: [corporate Launchpad mirror] Description: HTTP and WebDAV client library To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neon27/+bug/2003266/+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 2059734] Re: Tar fails to extract archives that include folders with certain permissions on armhf
Hi Ghadi, I reviewed this patch today. Thanks for the work on this. > this time I only back ported the fchmodat2 syscall and only for arm, aarch64, and powerpc platforms The upstream patch is applying the value 452 to all arches in syscalls.csv, and that's what's in noble+. Would you help me understand the motivation to deviate from this value for the arches not yet known to be affected, but only in SRU? Is this a trying-to-limit-regressions thing? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/2059734 Title: Tar fails to extract archives that include folders with certain permissions on armhf Status in libseccomp package in Ubuntu: New Status in tar package in Ubuntu: Invalid Status in libseccomp source package in Jammy: In Progress Status in libseccomp source package in Mantic: Won't Fix Status in tar source package in Mantic: Won't Fix Status in libseccomp source package in Noble: Invalid Status in tar source package in Noble: Invalid Bug description: Thank you @loganbussell-msft for the bug report! [Impact] Currently running containers using modern versions of glibc such as the one available in noble on older hosts causes permissions issues inside the container. This is due to newer versions of glibc expecting the fchmodat2 syscall to be available and to return ENOSYS in case it is not. However docker seccomp profile defaults to returning EPERM for all non defined syscalls and writing an entry for fchmodat2 in the docker seccomp profile to return ENOSYS does not work on systems where libseccomp does not have support for fchmodat2. Running armhf noble docker containers on arm64 jammy hosts has been seen to exhibit this behavior and a patch to libseccomp for jammy is required to fix the issue. Other architectures may also be affected by this issue that such as ppc64le as reported by @mark-elvers. I have backported a fix from upstream that adds the missing syscalls to libseccomp and verified it on an ampere arm machine as well as on a raspberry pi 4 [Test Plan] 1- On an ARM 64 machine install the latest version of docker on a jammy host by following the official docker documentation. [https://docs.docker.com/engine/install/ubuntu/] 2- Create an armhf noble docker container: $ docker run --rm -it --platform linux/arm/v7 --entrypoint bash ubuntu.azurecr.io/ubuntu:noble 3- inside the docker container execute the following commands to create a new tar file and then extract it: mkdir /test \ && chmod 775 /test \ && cd /test \ && mkdir 775 \ && chmod 775 775 \ && touch 775/test.txt \ && chmod 644 775/test.txt \ && tar -czvf /test.tar.gz . mkdir -p /test2 \ && tar -tzvf /test.tar.gz \ && tar -oxzf /test.tar.gz -C /test2 4- you will see the following errors: tar: ./775: Cannot change mode to rwxrwxr-x: Operation not permitted tar: Exiting with failure status due to previous errors 5- When libseccomp is patched the command will run with no permission issues [Where problems could occur] * the issue might still occur on other platforms * if using an older version of docker the issue will still occur [Original Description] When running Ubuntu Noble in an arm32 Docker container, on certain hosts (Azure VM CI agents), tar fails to extract certain archives that include folders with specific permissions set. Here's a concise repro. The error occurs in when building the Dockerfile. I can only get this to work on Azure VMs, but can't find out why. ```Dockerfile FROM ubuntu.azurecr.io/ubuntu:noble # Create the problematic archive RUN mkdir /test \ && chmod 775 /test \ && cd /test \ && mkdir 775 \ && chmod 775 775 \ && touch 775/test.txt \ && chmod 644 775/test.txt \ && tar -czvf /test.tar.gz . # Extracting it gives an error RUN mkdir -p /test2 \ && tar -tzvf /test.tar.gz \ && tar -oxzf /test.tar.gz -C /test2 ``` What I expected to happen: The test.tar.gz archive should be successfully extracted to the /test2 directory. What happened instead: Tar throws the following error: ``` tar: ./775: Cannot change mode to rwxrwxr-x: Operation not permitted tar: Exiting with failure status due to previous errors ``` The Ubuntu container is running as root so there shouldn't be any permission errors. Since this is running in a container, I observed this happening on the following kernel: `Linux version 5.15.148.2-2.cm2 (root@CBL-Mariner) (gcc (GCC) 11.2.0, GNU ld (GNU Binutils) 2.37) #1 SMP Fri Feb 23 23:38:33 UTC 2024` As well as `Linux 6.5.0-1017-azure #17~22.04.1-Ubuntu SMP Sat Mar 9 10:04:07 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux` I was not able to reproduce it using Ubuntu 22.04 Jammy (ubuntu.azurecr.io/ubuntu:jammy)
[Touch-packages] [Bug 2077159] Re: i40e interfaces renamed after upgrade from hwe-6.5
** Tags removed: rls-jj-incoming
** Tags added: foundations-todo
--
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/2077159
Title:
i40e interfaces renamed after upgrade from hwe-6.5
Status in netplan.io package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Bug description:
Server running Ubuntu 22.04.4 LTS
Interface names with linux-image-6.5.0-21-generic 6.5.0-21.21~22.04.1:
3: eno1: mtu 9100 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp102s0f0
4: eno5: mtu 1500 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp183s0f0
6: eno2: mtu 1500 qdisc mq master mgmt
state UP mode DEFAULT group default qlen 1000
altname enp102s0f1
7: eno6: mtu 1500 qdisc mq master mgmt
state DOWN mode DEFAULT group default qlen 1000
altname enp183s0f1
8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f2
9: eno7: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f2
10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f3
11: eno8: mtu 1500 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp183s0f3
Interface names with linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3:
3: eno5np0: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f0np0
4: eno1: mtu 9100 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp102s0f0
5: enp101s0f1np1: mtu 9100 qdisc mq state
DOWN mode DEFAULT group default qlen 1000
6: eno2: mtu 1500 qdisc mq master mgmt
state UP mode DEFAULT group default qlen 1000
altname enp102s0f1
7: eno6np1: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f1np1
8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f2
9: eno7np2: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f2np2
10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f3
11: eno8np3: mtu 1500 qdisc noop state DOWN mode
DEFAULT group default qlen 1000
altname enp183s0f3np3
Expected result: Static network configuration via netplan keeps
working after the upgrade.
Actual result: Static network configuration is no longer applied for the
interface that changed their name.
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Aug 16 09:40 seq
crw-rw 1 root audio 116, 33 Aug 16 09:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5json:
{
"result": "skip"
}
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-12-04 (260 days ago)
InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release
amd64 (20230217.1)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Supermicro SYS-5019D-FN8TP
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-21-generic
root=/dev/mapper/system-root ro
ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-m
[Touch-packages] [Bug 2078555] Re: Upgrading from 22.04 to 24.04.01 breaks dnsmasq
** Changed in: dnsmasq (Ubuntu) Status: Confirmed => Triaged ** Changed in: systemd (Ubuntu) Status: Confirmed => Triaged ** Changed in: dnsmasq (Ubuntu) Importance: Undecided => Medium ** Changed in: ubuntu-release-upgrader (Ubuntu) Importance: Undecided => Medium ** Changed in: ubuntu Status: Confirmed => Triaged ** Changed in: ubuntu Importance: Undecided => Medium ** Tags removed: rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2078555 Title: Upgrading from 22.04 to 24.04.01 breaks dnsmasq Status in Ubuntu: Triaged Status in dnsmasq package in Ubuntu: Triaged Status in systemd package in Ubuntu: Triaged Status in ubuntu-release-upgrader package in Ubuntu: Incomplete Bug description: Was running Ubuntu 22.04 as home gateway/firewall with dnsmasq as dns/dhcp server. Previous upgrade from Ubuntu 20.04 to 22.04 had worked without issue. After the upgrade to 24.04.01, systemd-resovled was automatically enabled. The result was that after a reboot, dnsmasq failed to start, as systemd-resolved had already bound to the necessary port. This in turn meant that my entire home network lost connectivity as it was dependant on dnsmasq running to provide both correct dns and dhcp functionality. Ideally, during the upgrade process, a check should be made for if another dns/dhcp service is already enabled, and if so, not enable systemd-resolved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2078555/+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 2073552] Re: Add SoundWire devices to alsa-info reported in ACPI
So if you look at https://merges.ubuntu.com/main.html?query=alsa-
utils&showProposed=true&showMergeNeeded=true&showLongBinaries=true you
can see the state of this - Ubuntu has a delta on the alsa-utils
package, the Ubuntu version is 1.2.11-1ubuntu1 and the Debian version is
1.2.12-1.
Someone would have to analyze this and most likely do the package merge,
or justify why the multiple Ubuntu patches are no longer required and
sync the package to the Debian version instead. Mind that we're past
feature freeze, so attempting to do that needs to be subject to feature
freeze rules.
Alternately, we can patch v1.2.11-1ubuntu1 in Oracular for your scenario
- a merge will still be needed later, but with a patched Oracular
version we are a step closer to meeting SRU expectations. Please read
https://wiki.ubuntu.com/FeatureFreeze and consider if your change needs
an exception request or not.
Unsubscribing sponsors, as there is nothing actionable here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-utils in Ubuntu.
https://bugs.launchpad.net/bugs/2073552
Title:
Add SoundWire devices to alsa-info reported in ACPI
Status in alsa-utils package in Ubuntu:
New
Status in alsa-utils source package in Jammy:
In Progress
Status in alsa-utils source package in Noble:
In Progress
Bug description:
[SRU Justifications]
[Impact]
Modern Intel platforms (RPL, MTL, LNL...etc) connect audio codecs on
Soundwire instead of HDA, but the soundwire devices are not well reflected on
the alsa-info report. In order to meet the increasing demands for SoundWire
debugging, we must enable alsa-info to provide more information about SoundWire.
[Fix]
Backport the upstream commit cc0bcef81389 ("alsa-info.sh: log SoundWire
devices reported in ACPI") of v1.2.12. The Oracular is expected to sync with
v1.2.12 and we may not have to backport to Oracular. The reported information
can reflect which soundwire devices are connected and which soundware link the
device connects to. It's quite sufficient for what driver should be ready and
what tplg/firmware file should be loaded.
[Test Case]
1. Find a machine with (RTK/Cirrus/TI) Soundwire audio device.
2. Install the new alsa-utils debian package
3. Execute `alsa-info` to generate the report
4. Check if the section "ACPI SoundWire Device Status Information" exists in
the output report.
[Where problems could occur]
It's simply an additional soundwire information when ACPI exposed the
soundwire device. The risk for regression is low.
[Other Info]
Verify if the official Oracular starts from version v1.2.12 to determine if
we have to land it on Oracular.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/2073552/+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 2073552] Re: Add SoundWire devices to alsa-info reported in ACPI
> The Oracular is expected to sync with v1.2.12 and we may not have to
backport to Oracular.
What happens if the merge of alsa-utils doesn't occur? Right now we are
in a state where a merge is required, so this isn't going to autosync,
and if the merge doesn't happen in Oracular then users will see
regressions in this behavior.
To satisfy SRU requirements
(https://wiki.ubuntu.com/StableReleaseUpdates#Development_Release_Fixed_First)
I request that this merge be completed first, or at least a backport of
the relevant fix if a merge is unrealistic.
Unsubscribing sponsors for the moment, please resubscribe when ready.
The patches themselves look fine but I'll request dep3 consideration.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-utils in Ubuntu.
https://bugs.launchpad.net/bugs/2073552
Title:
Add SoundWire devices to alsa-info reported in ACPI
Status in alsa-utils package in Ubuntu:
New
Status in alsa-utils source package in Jammy:
In Progress
Status in alsa-utils source package in Noble:
In Progress
Bug description:
[SRU Justifications]
[Impact]
Modern Intel platforms (RPL, MTL, LNL...etc) connect audio codecs on
Soundwire instead of HDA, but the soundwire devices are not well reflected on
the alsa-info report. In order to meet the increasing demands for SoundWire
debugging, we must enable alsa-info to provide more information about SoundWire.
[Fix]
Backport the upstream commit cc0bcef81389 ("alsa-info.sh: log SoundWire
devices reported in ACPI") of v1.2.12. The Oracular is expected to sync with
v1.2.12 and we may not have to backport to Oracular. The reported information
can reflect which soundwire devices are connected and which soundware link the
device connects to. It's quite sufficient for what driver should be ready and
what tplg/firmware file should be loaded.
[Test Case]
1. Find a machine with (RTK/Cirrus/TI) Soundwire audio device.
2. Install the new alsa-utils debian package
3. Execute `alsa-info` to generate the report
4. Check if the section "ACPI SoundWire Device Status Information" exists in
the output report.
[Where problems could occur]
It's simply an additional soundwire information when ACPI exposed the
soundwire device. The risk for regression is low.
[Other Info]
Verify if the official Oracular starts from version v1.2.12 to determine if
we have to land it on Oracular.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/2073552/+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 2073552] Re: Add SoundWire devices to alsa-info reported in ACPI
** Merge proposal linked:
https://code.launchpad.net/~mschiu77/ubuntu/+source/alsa-utils/+git/alsa-utils/+merge/469921
** Merge proposal linked:
https://code.launchpad.net/~mschiu77/ubuntu/+source/alsa-utils/+git/alsa-utils/+merge/469920
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-utils in Ubuntu.
https://bugs.launchpad.net/bugs/2073552
Title:
Add SoundWire devices to alsa-info reported in ACPI
Status in alsa-utils package in Ubuntu:
New
Status in alsa-utils source package in Jammy:
In Progress
Status in alsa-utils source package in Noble:
In Progress
Bug description:
[SRU Justifications]
[Impact]
Modern Intel platforms (RPL, MTL, LNL...etc) connect audio codecs on
Soundwire instead of HDA, but the soundwire devices are not well reflected on
the alsa-info report. In order to meet the increasing demands for SoundWire
debugging, we must enable alsa-info to provide more information about SoundWire.
[Fix]
Backport the upstream commit cc0bcef81389 ("alsa-info.sh: log SoundWire
devices reported in ACPI") of v1.2.12. The Oracular is expected to sync with
v1.2.12 and we may not have to backport to Oracular. The reported information
can reflect which soundwire devices are connected and which soundware link the
device connects to. It's quite sufficient for what driver should be ready and
what tplg/firmware file should be loaded.
[Test Case]
1. Find a machine with (RTK/Cirrus/TI) Soundwire audio device.
2. Install the new alsa-utils debian package
3. Execute `alsa-info` to generate the report
4. Check if the section "ACPI SoundWire Device Status Information" exists in
the output report.
[Where problems could occur]
It's simply an additional soundwire information when ACPI exposed the
soundwire device. The risk for regression is low.
[Other Info]
Verify if the official Oracular starts from version v1.2.12 to determine if
we have to land it on Oracular.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/2073552/+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 2071468] Re: ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not defined
@Nathan Teodosio (nteodosio)
> speech-dispatcher
> +export DEB_BUILD_OS_RELEASE_ID=$(dpkg-buildflags --get
> DEB_BUILD_OS_RELEASE_ID)
This part looks incorrect. Running that command returns an empty string, when
I believe the expected value is "ubuntu". I ended up dealing with this
problem on casper via:
https://git.launchpad.net/casper/commit/?id=ceeae71bbcddf2f3a4a142b6a09a47b46c15880f
See also Ben's suggestion in
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/2071468/comments/23
Unsubscribing sponsors, as this seems to be the only thing on this bug
asking for sponsorship.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to curl in Ubuntu.
https://bugs.launchpad.net/bugs/2071468
Title:
ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not
defined
Status in asymptote package in Ubuntu:
Fix Released
Status in biosig package in Ubuntu:
New
Status in curl package in Ubuntu:
Fix Released
Status in deal.ii package in Ubuntu:
New
Status in doxygen package in Ubuntu:
Fix Released
Status in dpkg package in Ubuntu:
Triaged
Status in gcl27 package in Ubuntu:
New
Status in graphite2 package in Ubuntu:
Fix Released
Status in gsequencer package in Ubuntu:
Fix Released
Status in gsl package in Ubuntu:
New
Status in haskell-devscripts package in Ubuntu:
Fix Released
Status in jose package in Ubuntu:
New
Status in ksmtuned package in Ubuntu:
Fix Released
Status in libreoffice package in Ubuntu:
Fix Released
Status in libtpms package in Ubuntu:
New
Status in mosh package in Ubuntu:
Fix Released
Status in mpich package in Ubuntu:
New
Status in mwrap package in Ubuntu:
Fix Released
Status in proftpd package in Ubuntu:
New
Status in proftpd-dfsg package in Ubuntu:
Fix Released
Status in quantlib package in Ubuntu:
Fix Released
Status in serf package in Ubuntu:
Fix Released
Status in setserial package in Ubuntu:
Fix Released
Status in speech-dispatcher package in Ubuntu:
New
Status in squid package in Ubuntu:
Fix Released
Status in swtpm package in Ubuntu:
Fix Released
Status in texinfo package in Ubuntu:
Triaged
Status in tix package in Ubuntu:
Fix Released
Bug description:
The ELF package note metadata introduced in dpkg 1.22.6ubuntu11
(refined in 1.22.6ubuntu14) can cause this failure:
```
gcc fatal error: environment variable ‘DEB_HOST_ARCH’ not defined
```
This happens when the `-specs=/usr/share/dpkg/elf-package-
metadata.specs` parameter is set but the needed environment variables
are not set. Cases:
1. Only the LDFLAGS is queried from dpkg-buildflags. Affected source
packages builds: python3.12, openjdk-21, cdbs (causing dvbstreamer and
rp-pppoe fail to build)
2. autopkgtests
3. debugging a crash of an application build with the -spec parameter
4. People like to iteratively continue building the software in the
build dir while hacking on the package and then have no environment
variable set.
This approach is too fragile. An alternative approach would be to specify the
`--package-metadata` linker flag directly. The problem with that approach is
that the curly brackets and quotation marks need to be escaped. Example
failure: Building dpkg would add this parameter to the LDFLAGS:
```
-Wl,--package-metadata,{"type":"deb","os":"ubuntu","name":"dpkg","version":"1.22.6ubuntu15","architecture":"amd64"}
```
The following configure script call (non-relevant parameters deleted):
```
$ gcc
-Wl,--package-metadata,{type:deb,os:ubuntu,name:dpkg,version:1.22.6ubuntu15,architecture:amd64}
/usr/bin/ld: cannot find {type:deb: No such file or directory
/usr/bin/ld: cannot find os:ubuntu: No such file or directory
/usr/bin/ld: cannot find name:dpkg: No such file or directory
/usr/bin/ld: cannot find version:1.22.6ubuntu15: No such file or directory
/usr/bin/ld: cannot find architecture:amd64}: No such file or directory
```
Proposed solution: Add support for an `--escaped-package-metadata` parameter
to the linkers that takes an URL encoded (RFC 3986) parameter. Example:
```
-Wl,--encoded-package-metadata,%7B%22type%22:%22deb%22%2C%22os%22:%22ubuntu%22%2C%22name%22:%22dpkg%22%2C%22version%22:%221.22.6ubuntu15%22%2C%22architecture%22:%22amd64%22%7D
```
Solution (see comment #31)
==
dpkg 1.22.11ubuntu1 stops passing the --specs option. It will be
replaced by
- dpkg-buildpackage setting ELF_PACKAGE_METADATA in the environment,
which gets picked up GCC and clang, and added as a linker option.
- the linkers ld.bfd, gold, mold and lld picking up ELF_PACKAGE_METADATA
if they don't see a package-metadata option.
This is committed, and will be uploaded later.
- dpkg-buildflags passing an option --encoded-package-metadata, which
can be safely passed.
This option has to go upstream first into the linkers, so that we
don't have API incom
[Touch-packages] [Bug 2064360] Re: libpam-doc: doc-base reports missing files
** Patch added: "1.5.2-9.1ubuntu3_to_1.5.3-5ubuntu5_libpam-doc.debdiff"
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2064360/+attachment/5773775/+files/1.5.2-9.1ubuntu3_to_1.5.3-5ubuntu5_libpam-doc.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/2064360
Title:
libpam-doc: doc-base reports missing files
Status in pam package in Ubuntu:
Fix Committed
Status in pam source package in Noble:
In Progress
Status in pam package in Debian:
Fix Released
Bug description:
[ Impact ]
* In the pam 1.5.3-1 merge, documents formerly found in libpam-doc
were omitted. Just a few documents remain in a package that
formerly had many in /usr/share/doc/libpam-doc/{html,txt}.
* A debdiff of the dropped files can be found in attachment
1.5.2-9.1ubuntu3_to_1.5.3-5ubuntu5_libpam-doc.debdiff
* The fix takes the form of correcting a build dependency, which
results in the docs being again available.
[ Test Plan ]
* debdiff
* Obtain a copy of the current pam binary packages, perhaps with
`pull-lp-debs libpam-doc 1.5.3-5ubuntu5`
* Obtain a copy of the proposed pam binary packages, perhaps with
`pull-lp-debs libpam-doc 1.5.3-5ubuntu5.1`
* `debdiff libpam-doc_1.5.3-5ubuntu5{,.1}_all.deb`
and verify that the documents are present
* upgrade
* Obtain a mantic test system - I personally used a mantic chroot
* `apt install libpam-doc doc-base`
* Adjust apt sources to change mantic to noble and ensure
noble-proposed is present
* `apt update; apt install libpam-doc/noble-proposed`
* Verify that the "Error in /usr/share/doc-base" messages are no
longer present
[ Where problems could occur ]
* As usual, no SRU has zero risk
* Any change to pam risks problems in user logins failing, so that is
reflected in the regression test plan on LP: #2064350
[ Other Info ]
* None at this time
original description follows:
---
Imported from Debian bug http://bugs.debian.org/1065064:
Package: libpam-doc
Version: 1.5.3-4
Severity: normal
An upgrade reported:
Error in `/usr/share/doc-base/libpam-doc.pam-admin-guide', line 14: all
`Format' sections are invalid.
Error in `/usr/share/doc-base/libpam-doc.pam-applications-guide', line 17:
all `Format' sections are invalid.
Error in `/usr/share/doc-base/libpam-doc.pam-modules-guide', line 14: all
`Format' sections are invalid.
This is true; all of /usr/share/doc/libpam-doc/html/Linux-PAM_SAG.html,
/usr/share/doc/libpam-doc/html/sag-*.html,
/usr/share/doc/libpam-doc/txt/Linux-PAM_SAG.txt.gz,
/usr/share/doc/libpam-doc/html/Linux-PAM_ADG.html,
/usr/share/doc/libpam-doc/html/adg*.html,
/usr/share/doc/libpam-doc/txt/Linux-PAM_ADG.txt.gz,
/usr/share/doc/libpam-doc/html/Linux-PAM_MWG.html,
/usr/share/doc/libpam-doc/html/mwg*.html, and
/usr/share/doc/libpam-doc/txt/Linux-PAM_MWG.txt.gz are listed in those
doc-base files but are in fact missing. I don't know whether this is
intentional (in which case the doc-base registrations should be removed
to match), or an accidental build issue that should be fixed.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.6.0-14-generic (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND,
TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
-- no debconf information
--
Colin Watson (he/him) [cjwat...@debian.org]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2064360/+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 2064360] Re: libpam-doc: doc-base reports missing files
** Description changed:
+ [ Impact ]
+
+ * In the pam 1.5.3-1 merge, documents formerly found in libpam-doc
+were omitted. Just a few documents remain in a package that
+formerly had many in /usr/share/doc/libpam-doc/{html,txt}.
+ * A debdiff of the dropped files can be found in attachment
+1.5.2-9.1ubuntu3_to_1.5.3-5ubuntu5_libpam-doc.debdiff
+ * The fix takes the form of correcting a build dependency, which
+results in the docs being again available.
+
+ [ Test Plan ]
+
+ * debdiff
+* Obtain a copy of the current pam binary packages, perhaps with
+ `pull-lp-debs libpam-doc 1.5.3-5ubuntu5`
+* Obtain a copy of the proposed pam binary packages, perhaps with
+ `pull-lp-debs libpam-doc 1.5.3-5ubuntu5.1`
+* `debdiff libpam-doc_1.5.3-5ubuntu5{,.1}_all.deb`
+ and verify that the documents are present
+ * upgrade
+* Obtain a mantic test system - I personally used a mantic chroot
+* `apt install libpam-doc doc-base`
+* Adjust apt sources to change mantic to noble and ensure
+ noble-proposed is present
+* `apt update; apt install libpam-doc/noble-proposed`
+* Verify that the "Error in /usr/share/doc-base" messages are no
+ longer present
+
+ [ Where problems could occur ]
+
+ * As usual, no SRU has zero risk
+ * Any change to pam risks problems in user logins failing, so that is
+reflected in the regression test plan on LP: #2064350
+
+ [ Other Info ]
+
+ * None at this time
+
+ original description follows:
+ ---
+
Imported from Debian bug http://bugs.debian.org/1065064:
Package: libpam-doc
Version: 1.5.3-4
Severity: normal
An upgrade reported:
- Error in `/usr/share/doc-base/libpam-doc.pam-admin-guide', line 14: all
`Format' sections are invalid.
- Error in `/usr/share/doc-base/libpam-doc.pam-applications-guide', line 17:
all `Format' sections are invalid.
- Error in `/usr/share/doc-base/libpam-doc.pam-modules-guide', line 14: all
`Format' sections are invalid.
+ Error in `/usr/share/doc-base/libpam-doc.pam-admin-guide', line 14: all
`Format' sections are invalid.
+ Error in `/usr/share/doc-base/libpam-doc.pam-applications-guide', line 17:
all `Format' sections are invalid.
+ Error in `/usr/share/doc-base/libpam-doc.pam-modules-guide', line 14: all
`Format' sections are invalid.
This is true; all of /usr/share/doc/libpam-doc/html/Linux-PAM_SAG.html,
/usr/share/doc/libpam-doc/html/sag-*.html,
/usr/share/doc/libpam-doc/txt/Linux-PAM_SAG.txt.gz,
/usr/share/doc/libpam-doc/html/Linux-PAM_ADG.html,
/usr/share/doc/libpam-doc/html/adg*.html,
/usr/share/doc/libpam-doc/txt/Linux-PAM_ADG.txt.gz,
/usr/share/doc/libpam-doc/html/Linux-PAM_MWG.html,
/usr/share/doc/libpam-doc/html/mwg*.html, and
/usr/share/doc/libpam-doc/txt/Linux-PAM_MWG.txt.gz are listed in those
doc-base files but are in fact missing. I don't know whether this is
intentional (in which case the doc-base registrations should be removed
to match), or an accidental build issue that should be fixed.
-- System Information:
Debian Release: trixie/sid
- APT prefers unstable
- APT policy: (500, 'unstable'), (1, 'experimental')
+ APT prefers unstable
+ APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.6.0-14-generic (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND,
TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
-- no debconf information
- --
+ --
Colin Watson (he/him) [cjwat...@debian.org]
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/2064360
Title:
libpam-doc: doc-base reports missing files
Status in pam package in Ubuntu:
In Progress
Status in pam package in Debian:
Fix Released
Bug description:
[ Impact ]
* In the pam 1.5.3-1 merge, documents formerly found in libpam-doc
were omitted. Just a few documents remain in a package that
formerly had many in /usr/share/doc/libpam-doc/{html,txt}.
* A debdiff of the dropped files can be found in attachment
1.5.2-9.1ubuntu3_to_1.5.3-5ubuntu5_libpam-doc.debdiff
* The fix takes the form of correcting a build dependency, which
results in the docs being again available.
[ Test Plan ]
* debdiff
* Obtain a copy of the current pam binary packages, perhaps with
`pull-lp-debs libpam-doc 1.5.3-5ubuntu5`
* Obtain a copy of the proposed pam binary packages, perhaps with
`pull-lp-debs libpam-doc 1.5.3-5ubuntu5.1`
* `debdiff libpam-doc_1.5.3-5ubuntu5{,.1}_all.deb`
and verify that the documents are present
* upgrade
* Obtain a mantic test system - I personally used a mantic chroot
* `apt
[Touch-packages] [Bug 2064360] Re: libpam-doc: doc-base reports missing files
** Attachment added:
"1.5.2-9.1ubuntu3_to_1.5.3-5ubuntu5_libpam-doc.debdiff.notapatch"
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2064360/+attachment/5773776/+files/1.5.2-9.1ubuntu3_to_1.5.3-5ubuntu5_libpam-doc.debdiff.notapatch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/2064360
Title:
libpam-doc: doc-base reports missing files
Status in pam package in Ubuntu:
Fix Committed
Status in pam source package in Noble:
In Progress
Status in pam package in Debian:
Fix Released
Bug description:
[ Impact ]
* In the pam 1.5.3-1 merge, documents formerly found in libpam-doc
were omitted. Just a few documents remain in a package that
formerly had many in /usr/share/doc/libpam-doc/{html,txt}.
* A debdiff of the dropped files can be found in attachment
1.5.2-9.1ubuntu3_to_1.5.3-5ubuntu5_libpam-doc.debdiff
* The fix takes the form of correcting a build dependency, which
results in the docs being again available.
[ Test Plan ]
* debdiff
* Obtain a copy of the current pam binary packages, perhaps with
`pull-lp-debs libpam-doc 1.5.3-5ubuntu5`
* Obtain a copy of the proposed pam binary packages, perhaps with
`pull-lp-debs libpam-doc 1.5.3-5ubuntu5.1`
* `debdiff libpam-doc_1.5.3-5ubuntu5{,.1}_all.deb`
and verify that the documents are present
* upgrade
* Obtain a mantic test system - I personally used a mantic chroot
* `apt install libpam-doc doc-base`
* Adjust apt sources to change mantic to noble and ensure
noble-proposed is present
* `apt update; apt install libpam-doc/noble-proposed`
* Verify that the "Error in /usr/share/doc-base" messages are no
longer present
[ Where problems could occur ]
* As usual, no SRU has zero risk
* Any change to pam risks problems in user logins failing, so that is
reflected in the regression test plan on LP: #2064350
[ Other Info ]
* None at this time
original description follows:
---
Imported from Debian bug http://bugs.debian.org/1065064:
Package: libpam-doc
Version: 1.5.3-4
Severity: normal
An upgrade reported:
Error in `/usr/share/doc-base/libpam-doc.pam-admin-guide', line 14: all
`Format' sections are invalid.
Error in `/usr/share/doc-base/libpam-doc.pam-applications-guide', line 17:
all `Format' sections are invalid.
Error in `/usr/share/doc-base/libpam-doc.pam-modules-guide', line 14: all
`Format' sections are invalid.
This is true; all of /usr/share/doc/libpam-doc/html/Linux-PAM_SAG.html,
/usr/share/doc/libpam-doc/html/sag-*.html,
/usr/share/doc/libpam-doc/txt/Linux-PAM_SAG.txt.gz,
/usr/share/doc/libpam-doc/html/Linux-PAM_ADG.html,
/usr/share/doc/libpam-doc/html/adg*.html,
/usr/share/doc/libpam-doc/txt/Linux-PAM_ADG.txt.gz,
/usr/share/doc/libpam-doc/html/Linux-PAM_MWG.html,
/usr/share/doc/libpam-doc/html/mwg*.html, and
/usr/share/doc/libpam-doc/txt/Linux-PAM_MWG.txt.gz are listed in those
doc-base files but are in fact missing. I don't know whether this is
intentional (in which case the doc-base registrations should be removed
to match), or an accidental build issue that should be fixed.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.6.0-14-generic (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND,
TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
-- no debconf information
--
Colin Watson (he/him) [cjwat...@debian.org]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2064360/+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 2064350] Re: pam_userdb.so is missing
** Description changed: + [ Impact ] + + * In the process of bootstrapping pam for time_t, libdb-dev was +deliberately removed in salsa commit 65621d8 to allow libdb-dev to +undergo time_t transition. + * The result of that is no pam_userdb.so in libpam-modules + * The fix takes the form of correcting a build dependency, which +results in pam_userdb.so being again available. + + [ Test Plan ] + + * regression +* obtain a noble test system - I personally used a noble chroot +* adjust apt sources and ensure noble-proposed is present +* install libpam-modules 1.5.3-5ubuntu5.1 +* login to the test machine with appropriate credentials - the + literal `login` command is useful here + * userdb functionality +* start with the same test machine from the regression test +* install db5.3-util +* modify /etc/pam.d/login to comment out all `auth` lines, and add + this instead + ``` + auth requisite pam_userdb.so db=/etc/dbtest + ``` +* create a textfile named `input` that looks like + ``` + your_username + test_password - different than /etc/shadow + ``` +* `db5.3_load -T -f input -t hash /etc/dbtest.db` +* login to the test machine with your_username and the + test_password - the literal `login` command is useful here + + [ Where problems could occur ] + + * As usual, no SRU has zero risk + * Any change to pam risks problems in user logins failing, so a +basic regression test has been provided + + [ Other Info ] + + * None at this time + + original description follows + --- + The file is missing from libpam-modules. This breaks, for example, existing vsftp configs if it is configured to use pam_userdb.so Log: vsftpd: PAM unable to dlopen(pam_userdb.so): /usr/lib/security/pam_userdb.so: cannot open shared object file: No such file or directory vsftpd: PAM adding faulty module: pam_userdb.so Apparently there was a change which removed this in the past, and it might be the removal has not been undone, while the package has been released nevertheless. http://changelogs.ubuntu.com/changelogs/pool/main/p/pam/pam_1.5.3-5ubuntu5/changelog * For now remove libdb-dev so that libdb-dev can undergo time_t transition. That means this version of pam does not include pam_userdb, which makes pam unsuitable for release. - $ lsb_release -rd No LSB modules are available. Description:Ubuntu 24.04 LTS Release:24.04 $ apt-cache policy libpam-modules libpam-modules: - Installed: 1.5.3-5ubuntu5 - Candidate: 1.5.3-5ubuntu5 - Version table: - *** 1.5.3-5ubuntu5 500 - 500 http://de.archive.ubuntu.com/ubuntu noble/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1.5.3-5ubuntu5 + Candidate: 1.5.3-5ubuntu5 + Version table: + *** 1.5.3-5ubuntu5 500 + 500 http://de.archive.ubuntu.com/ubuntu noble/main amd64 Packages + 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2064350 Title: pam_userdb.so is missing Status in pam package in Ubuntu: In Progress Status in pam source package in Noble: New Status in pam package in Debian: Fix Released Bug description: [ Impact ] * In the process of bootstrapping pam for time_t, libdb-dev was deliberately removed in salsa commit 65621d8 to allow libdb-dev to undergo time_t transition. * The result of that is no pam_userdb.so in libpam-modules * The fix takes the form of correcting a build dependency, which results in pam_userdb.so being again available. [ Test Plan ] * regression * obtain a noble test system - I personally used a noble chroot * adjust apt sources and ensure noble-proposed is present * install libpam-modules 1.5.3-5ubuntu5.1 * login to the test machine with appropriate credentials - the literal `login` command is useful here * userdb functionality * start with the same test machine from the regression test * install db5.3-util * modify /etc/pam.d/login to comment out all `auth` lines, and add this instead ``` auth requisite pam_userdb.so db=/etc/dbtest ``` * create a textfile named `input` that looks like ``` your_username test_password - different than /etc/shadow ``` * `db5.3_load -T -f input -t hash /etc/dbtest.db` * login to the test machine with your_username and the test_password - the literal `login` command is useful here [ Where problems could occur ] * As usual, no SRU has zero risk * Any change to pam risks problems in user logins failing, so a basic regression test has been provided [ Other Info ] * None at this time original description follows --- The file is missing from libpam-modules. This breaks, for example, existing vsftp configs if it is configured t
[Touch-packages] [Bug 2064360] Re: libpam-doc: doc-base reports missing files
** Also affects: pam (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: pam (Ubuntu)
Importance: Undecided => High
** Changed in: pam (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: pam (Ubuntu Noble)
Status: New => In Progress
** Changed in: pam (Ubuntu Noble)
Importance: Undecided => High
** Changed in: pam (Ubuntu Noble)
Assignee: (unassigned) => Dan Bungert (dbungert)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/2064360
Title:
libpam-doc: doc-base reports missing files
Status in pam package in Ubuntu:
Fix Committed
Status in pam source package in Noble:
In Progress
Status in pam package in Debian:
Fix Released
Bug description:
[ Impact ]
* In the pam 1.5.3-1 merge, documents formerly found in libpam-doc
were omitted. Just a few documents remain in a package that
formerly had many in /usr/share/doc/libpam-doc/{html,txt}.
* A debdiff of the dropped files can be found in attachment
1.5.2-9.1ubuntu3_to_1.5.3-5ubuntu5_libpam-doc.debdiff
* The fix takes the form of correcting a build dependency, which
results in the docs being again available.
[ Test Plan ]
* debdiff
* Obtain a copy of the current pam binary packages, perhaps with
`pull-lp-debs libpam-doc 1.5.3-5ubuntu5`
* Obtain a copy of the proposed pam binary packages, perhaps with
`pull-lp-debs libpam-doc 1.5.3-5ubuntu5.1`
* `debdiff libpam-doc_1.5.3-5ubuntu5{,.1}_all.deb`
and verify that the documents are present
* upgrade
* Obtain a mantic test system - I personally used a mantic chroot
* `apt install libpam-doc doc-base`
* Adjust apt sources to change mantic to noble and ensure
noble-proposed is present
* `apt update; apt install libpam-doc/noble-proposed`
* Verify that the "Error in /usr/share/doc-base" messages are no
longer present
[ Where problems could occur ]
* As usual, no SRU has zero risk
* Any change to pam risks problems in user logins failing, so that is
reflected in the regression test plan on LP: #2064350
[ Other Info ]
* None at this time
original description follows:
---
Imported from Debian bug http://bugs.debian.org/1065064:
Package: libpam-doc
Version: 1.5.3-4
Severity: normal
An upgrade reported:
Error in `/usr/share/doc-base/libpam-doc.pam-admin-guide', line 14: all
`Format' sections are invalid.
Error in `/usr/share/doc-base/libpam-doc.pam-applications-guide', line 17:
all `Format' sections are invalid.
Error in `/usr/share/doc-base/libpam-doc.pam-modules-guide', line 14: all
`Format' sections are invalid.
This is true; all of /usr/share/doc/libpam-doc/html/Linux-PAM_SAG.html,
/usr/share/doc/libpam-doc/html/sag-*.html,
/usr/share/doc/libpam-doc/txt/Linux-PAM_SAG.txt.gz,
/usr/share/doc/libpam-doc/html/Linux-PAM_ADG.html,
/usr/share/doc/libpam-doc/html/adg*.html,
/usr/share/doc/libpam-doc/txt/Linux-PAM_ADG.txt.gz,
/usr/share/doc/libpam-doc/html/Linux-PAM_MWG.html,
/usr/share/doc/libpam-doc/html/mwg*.html, and
/usr/share/doc/libpam-doc/txt/Linux-PAM_MWG.txt.gz are listed in those
doc-base files but are in fact missing. I don't know whether this is
intentional (in which case the doc-base registrations should be removed
to match), or an accidental build issue that should be fixed.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.6.0-14-generic (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND,
TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
-- no debconf information
--
Colin Watson (he/him) [cjwat...@debian.org]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2064360/+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 2064350] Re: pam_userdb.so is missing
** Changed in: pam (Ubuntu) Status: In Progress => Fix Committed ** Changed in: pam (Ubuntu Noble) Status: New => In Progress ** Changed in: pam (Ubuntu Noble) Importance: Undecided => High ** Changed in: pam (Ubuntu Noble) Assignee: (unassigned) => Dan Bungert (dbungert) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2064350 Title: pam_userdb.so is missing Status in pam package in Ubuntu: Fix Committed Status in pam source package in Noble: In Progress Status in pam package in Debian: Fix Released Bug description: [ Impact ] * In the process of bootstrapping pam for time_t, libdb-dev was deliberately removed in salsa commit 65621d8 to allow libdb-dev to undergo time_t transition. * The result of that is no pam_userdb.so in libpam-modules * The fix takes the form of correcting a build dependency, which results in pam_userdb.so being again available. [ Test Plan ] * regression * obtain a noble test system - I personally used a noble chroot * adjust apt sources and ensure noble-proposed is present * install libpam-modules 1.5.3-5ubuntu5.1 * login to the test machine with appropriate credentials - the literal `login` command is useful here * userdb functionality * start with the same test machine from the regression test * install db5.3-util * modify /etc/pam.d/login to comment out all `auth` lines, and add this instead ``` auth requisite pam_userdb.so db=/etc/dbtest ``` * create a textfile named `input` that looks like ``` your_username test_password - different than /etc/shadow ``` * `db5.3_load -T -f input -t hash /etc/dbtest.db` * login to the test machine with your_username and the test_password - the literal `login` command is useful here [ Where problems could occur ] * As usual, no SRU has zero risk * Any change to pam risks problems in user logins failing, so a basic regression test has been provided [ Other Info ] * None at this time original description follows --- The file is missing from libpam-modules. This breaks, for example, existing vsftp configs if it is configured to use pam_userdb.so Log: vsftpd: PAM unable to dlopen(pam_userdb.so): /usr/lib/security/pam_userdb.so: cannot open shared object file: No such file or directory vsftpd: PAM adding faulty module: pam_userdb.so Apparently there was a change which removed this in the past, and it might be the removal has not been undone, while the package has been released nevertheless. http://changelogs.ubuntu.com/changelogs/pool/main/p/pam/pam_1.5.3-5ubuntu5/changelog * For now remove libdb-dev so that libdb-dev can undergo time_t transition. That means this version of pam does not include pam_userdb, which makes pam unsuitable for release. $ lsb_release -rd No LSB modules are available. Description:Ubuntu 24.04 LTS Release:24.04 $ apt-cache policy libpam-modules libpam-modules: Installed: 1.5.3-5ubuntu5 Candidate: 1.5.3-5ubuntu5 Version table: *** 1.5.3-5ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2064350/+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 2064360] Re: libpam-doc: doc-base reports missing files
** Changed in: pam (Ubuntu) Status: New => In Progress ** Changed in: pam (Ubuntu) Assignee: (unassigned) => Dan Bungert (dbungert) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2064360 Title: libpam-doc: doc-base reports missing files Status in pam package in Ubuntu: In Progress Status in pam package in Debian: Fix Released Bug description: Imported from Debian bug http://bugs.debian.org/1065064: Package: libpam-doc Version: 1.5.3-4 Severity: normal An upgrade reported: Error in `/usr/share/doc-base/libpam-doc.pam-admin-guide', line 14: all `Format' sections are invalid. Error in `/usr/share/doc-base/libpam-doc.pam-applications-guide', line 17: all `Format' sections are invalid. Error in `/usr/share/doc-base/libpam-doc.pam-modules-guide', line 14: all `Format' sections are invalid. This is true; all of /usr/share/doc/libpam-doc/html/Linux-PAM_SAG.html, /usr/share/doc/libpam-doc/html/sag-*.html, /usr/share/doc/libpam-doc/txt/Linux-PAM_SAG.txt.gz, /usr/share/doc/libpam-doc/html/Linux-PAM_ADG.html, /usr/share/doc/libpam-doc/html/adg*.html, /usr/share/doc/libpam-doc/txt/Linux-PAM_ADG.txt.gz, /usr/share/doc/libpam-doc/html/Linux-PAM_MWG.html, /usr/share/doc/libpam-doc/html/mwg*.html, and /usr/share/doc/libpam-doc/txt/Linux-PAM_MWG.txt.gz are listed in those doc-base files but are in fact missing. I don't know whether this is intentional (in which case the doc-base registrations should be removed to match), or an accidental build issue that should be fixed. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.0-14-generic (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect -- no debconf information -- Colin Watson (he/him) [cjwat...@debian.org] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2064360/+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 2064360] [NEW] libpam-doc: doc-base reports missing files
Public bug reported: Imported from Debian bug http://bugs.debian.org/1065064: Package: libpam-doc Version: 1.5.3-4 Severity: normal An upgrade reported: Error in `/usr/share/doc-base/libpam-doc.pam-admin-guide', line 14: all `Format' sections are invalid. Error in `/usr/share/doc-base/libpam-doc.pam-applications-guide', line 17: all `Format' sections are invalid. Error in `/usr/share/doc-base/libpam-doc.pam-modules-guide', line 14: all `Format' sections are invalid. This is true; all of /usr/share/doc/libpam-doc/html/Linux-PAM_SAG.html, /usr/share/doc/libpam-doc/html/sag-*.html, /usr/share/doc/libpam-doc/txt/Linux-PAM_SAG.txt.gz, /usr/share/doc/libpam-doc/html/Linux-PAM_ADG.html, /usr/share/doc/libpam-doc/html/adg*.html, /usr/share/doc/libpam-doc/txt/Linux-PAM_ADG.txt.gz, /usr/share/doc/libpam-doc/html/Linux-PAM_MWG.html, /usr/share/doc/libpam-doc/html/mwg*.html, and /usr/share/doc/libpam-doc/txt/Linux-PAM_MWG.txt.gz are listed in those doc-base files but are in fact missing. I don't know whether this is intentional (in which case the doc-base registrations should be removed to match), or an accidental build issue that should be fixed. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.0-14-generic (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect -- no debconf information -- Colin Watson (he/him) [cjwat...@debian.org] ** Affects: pam (Ubuntu) Importance: Undecided Status: New ** Affects: pam (Debian) Importance: Unknown Status: Fix Released ** Bug watch added: Debian Bug tracker #1065064 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065064 ** Changed in: pam (Debian) Remote watch: None => Debian Bug tracker #1065064 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2064360 Title: libpam-doc: doc-base reports missing files Status in pam package in Ubuntu: New Status in pam package in Debian: Fix Released Bug description: Imported from Debian bug http://bugs.debian.org/1065064: Package: libpam-doc Version: 1.5.3-4 Severity: normal An upgrade reported: Error in `/usr/share/doc-base/libpam-doc.pam-admin-guide', line 14: all `Format' sections are invalid. Error in `/usr/share/doc-base/libpam-doc.pam-applications-guide', line 17: all `Format' sections are invalid. Error in `/usr/share/doc-base/libpam-doc.pam-modules-guide', line 14: all `Format' sections are invalid. This is true; all of /usr/share/doc/libpam-doc/html/Linux-PAM_SAG.html, /usr/share/doc/libpam-doc/html/sag-*.html, /usr/share/doc/libpam-doc/txt/Linux-PAM_SAG.txt.gz, /usr/share/doc/libpam-doc/html/Linux-PAM_ADG.html, /usr/share/doc/libpam-doc/html/adg*.html, /usr/share/doc/libpam-doc/txt/Linux-PAM_ADG.txt.gz, /usr/share/doc/libpam-doc/html/Linux-PAM_MWG.html, /usr/share/doc/libpam-doc/html/mwg*.html, and /usr/share/doc/libpam-doc/txt/Linux-PAM_MWG.txt.gz are listed in those doc-base files but are in fact missing. I don't know whether this is intentional (in which case the doc-base registrations should be removed to match), or an accidental build issue that should be fixed. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.0-14-generic (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect -- no debconf information -- Colin Watson (he/him) [cjwat...@debian.org] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2064360/+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 2064350] Re: pam_userdb.so is missing
** Bug watch added: Debian Bug tracker #1065088 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065088 ** Also affects: pam (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065088 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2064350 Title: pam_userdb.so is missing Status in pam package in Ubuntu: In Progress Status in pam source package in Noble: New Status in pam package in Debian: Fix Released Bug description: The file is missing from libpam-modules. This breaks, for example, existing vsftp configs if it is configured to use pam_userdb.so Log: vsftpd: PAM unable to dlopen(pam_userdb.so): /usr/lib/security/pam_userdb.so: cannot open shared object file: No such file or directory vsftpd: PAM adding faulty module: pam_userdb.so Apparently there was a change which removed this in the past, and it might be the removal has not been undone, while the package has been released nevertheless. http://changelogs.ubuntu.com/changelogs/pool/main/p/pam/pam_1.5.3-5ubuntu5/changelog * For now remove libdb-dev so that libdb-dev can undergo time_t transition. That means this version of pam does not include pam_userdb, which makes pam unsuitable for release. $ lsb_release -rd No LSB modules are available. Description:Ubuntu 24.04 LTS Release:24.04 $ apt-cache policy libpam-modules libpam-modules: Installed: 1.5.3-5ubuntu5 Candidate: 1.5.3-5ubuntu5 Version table: *** 1.5.3-5ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2064350/+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 2064350] Re: pam_userdb.so is missing
** Also affects: pam (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2064350 Title: pam_userdb.so is missing Status in pam package in Ubuntu: In Progress Status in pam source package in Noble: New Bug description: The file is missing from libpam-modules. This breaks, for example, existing vsftp configs if it is configured to use pam_userdb.so Log: vsftpd: PAM unable to dlopen(pam_userdb.so): /usr/lib/security/pam_userdb.so: cannot open shared object file: No such file or directory vsftpd: PAM adding faulty module: pam_userdb.so Apparently there was a change which removed this in the past, and it might be the removal has not been undone, while the package has been released nevertheless. http://changelogs.ubuntu.com/changelogs/pool/main/p/pam/pam_1.5.3-5ubuntu5/changelog * For now remove libdb-dev so that libdb-dev can undergo time_t transition. That means this version of pam does not include pam_userdb, which makes pam unsuitable for release. $ lsb_release -rd No LSB modules are available. Description:Ubuntu 24.04 LTS Release:24.04 $ apt-cache policy libpam-modules libpam-modules: Installed: 1.5.3-5ubuntu5 Candidate: 1.5.3-5ubuntu5 Version table: *** 1.5.3-5ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2064350/+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 2064350] Re: pam_userdb.so is missing
** Changed in: pam (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2064350 Title: pam_userdb.so is missing Status in pam package in Ubuntu: In Progress Bug description: The file is missing from libpam-modules. This breaks, for example, existing vsftp configs if it is configured to use pam_userdb.so Log: vsftpd: PAM unable to dlopen(pam_userdb.so): /usr/lib/security/pam_userdb.so: cannot open shared object file: No such file or directory vsftpd: PAM adding faulty module: pam_userdb.so Apparently there was a change which removed this in the past, and it might be the removal has not been undone, while the package has been released nevertheless. http://changelogs.ubuntu.com/changelogs/pool/main/p/pam/pam_1.5.3-5ubuntu5/changelog * For now remove libdb-dev so that libdb-dev can undergo time_t transition. That means this version of pam does not include pam_userdb, which makes pam unsuitable for release. $ lsb_release -rd No LSB modules are available. Description:Ubuntu 24.04 LTS Release:24.04 $ apt-cache policy libpam-modules libpam-modules: Installed: 1.5.3-5ubuntu5 Candidate: 1.5.3-5ubuntu5 Version table: *** 1.5.3-5ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2064350/+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 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Per https://irclogs.ubuntu.com/2024/04/20/%23ubuntu-release.html#t18:58
the required kernel is -31, which is currently in proposed
--
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/2058179
Title:
Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Status in Native ZFS for Linux:
Fix Released
Status in systemd package in Ubuntu:
Fix Committed
Status in zfs-linux package in Ubuntu:
Fix Released
Status in systemd source package in Noble:
Fix Committed
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
As per https://github.com/openzfs/zfs/issues/15930
ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
copy_file_range, breaking a multitude of applications.
Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
2.2.2.
One notable issue is when running Root on ZFS: systemd-sysusers will
always fail to create users/groups with the error "Failed to backup
/etc/{group,passwd}: Operation not supported" due to the call to
copy_file_range.
To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+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 2057996] Re: ubuntu-24.04 version: cmd-curthooks/:Fail:Installing packages on target system:efibootmgr, grub-efi-amd64-signed, nvme-cli, nvme-stas, shim-signed
** Changed in: subiquity (Ubuntu)
Status: New => Fix Released
--
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/2057996
Title:
ubuntu-24.04 version: cmd-curthooks/:Fail:Installing packages on
target system:efibootmgr, grub-efi-amd64-signed,nvme-cli,nvme-
stas,shim-signed
Status in subiquity package in Ubuntu:
Fix Released
Status in ubuntu-meta package in Ubuntu:
New
Bug description:
verison：ubuntu 24.04 subiquity version
OS:noble-live-server-amd64-0222.iso
CPU:AMD EPYC 9634 84-Core Processor*1
MEMORY: M321R2GA3BB6-CQKVG*2
ThinkSystem E1.S 5.9mm 7450 PRO 3.84TB Read Intensive NVMe PCIe 4.0 x4 HS SSD
UEFI MODE
lsb_release -rd: Description:Untun Noble Numbat(development branch)
Release: 24.04
What you expected to happen:
Install os on nvme,expected to install succefully.
What happened instead:
Install os on nvme, install always failed.
Before installation, we cleaned up all our nvme disk by dd if=/dev/zero
of=/dev/sda bs=1M count=5
The error log:
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: finish:
cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL: Installing packages on
target system: ['efibootmgr', 'grub-efi-amd64', 'grub-efi-amd64-signed',
'nvme-cli', 'nvme-stas', 'shim-signed']
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: finish:
cmd-install/stage-curthooks/builtin/cmd-curthooks/installing-missing-packages:
FAIL: installing missing packages
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: finish:
cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL: curtin command
curthooks
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: Traceback
(most recent call last):
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/main.py",
line 202, in main
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: ret =
args.func(args)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/curthooks.py",
line 1998, in curthooks
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:
builtin_curthooks(cfg, target, state)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/curthooks.py",
line 1803, in builtin_curthooks
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:
install_missing_packages(cfg, target, osfamily=osfamily)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/curthooks.py",
line 1362, in install_missing_packages
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:
distro.install_packages(to_add, target=target, osfamily=osfamily)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/distro.py", line 472,
in install_packages
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: return
install_cmd('install', args=pkglist, opts=opts, target=target,
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/distro.py", line 254,
in run_apt_command
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: cmd_rv =
apt_install(mode, args, opts=opts, env=env, target=target,
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/distro.py", line 302,
in apt_install
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: cmd_rv =
inchroot.subp(cmd + dl_opts + packages, env=env,
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/util.py", line 791,
in subp
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: return
subp(*args, **kwargs)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/util.py", line 283,
in subp
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: return
_subp(*args, **kwargs)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/util.py", line 147,
in _subp
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: raise
ProcessExecutionError(stdout=out, stderr=err,
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:
curtin.util.ProcessExecutionError: Unexpected error while running command.
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:
[Touch-packages] [Bug 2057996] Re: ubuntu-24.04 version: cmd-curthooks/:Fail:Installing packages on target system:efibootmgr, grub-efi-amd64-signed, nvme-cli, nvme-stas, shim-signed
** Also affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
--
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/2057996
Title:
ubuntu-24.04 version: cmd-curthooks/:Fail:Installing packages on
target system:efibootmgr, grub-efi-amd64-signed,nvme-cli,nvme-
stas,shim-signed
Status in subiquity package in Ubuntu:
New
Status in ubuntu-meta package in Ubuntu:
New
Bug description:
verison：ubuntu 24.04 subiquity version
OS:noble-live-server-amd64-0222.iso
CPU:AMD EPYC 9634 84-Core Processor*1
MEMORY: M321R2GA3BB6-CQKVG*2
ThinkSystem E1.S 5.9mm 7450 PRO 3.84TB Read Intensive NVMe PCIe 4.0 x4 HS SSD
UEFI MODE
lsb_release -rd: Description:Untun Noble Numbat(development branch)
Release: 24.04
What you expected to happen:
Install os on nvme,expected to install succefully.
What happened instead:
Install os on nvme, install always failed.
Before installation, we cleaned up all our nvme disk by dd if=/dev/zero
of=/dev/sda bs=1M count=5
The error log:
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: finish:
cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL: Installing packages on
target system: ['efibootmgr', 'grub-efi-amd64', 'grub-efi-amd64-signed',
'nvme-cli', 'nvme-stas', 'shim-signed']
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: finish:
cmd-install/stage-curthooks/builtin/cmd-curthooks/installing-missing-packages:
FAIL: installing missing packages
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: finish:
cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL: curtin command
curthooks
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: Traceback
(most recent call last):
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/main.py",
line 202, in main
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: ret =
args.func(args)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/curthooks.py",
line 1998, in curthooks
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:
builtin_curthooks(cfg, target, state)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/curthooks.py",
line 1803, in builtin_curthooks
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:
install_missing_packages(cfg, target, osfamily=osfamily)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/curthooks.py",
line 1362, in install_missing_packages
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:
distro.install_packages(to_add, target=target, osfamily=osfamily)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/distro.py", line 472,
in install_packages
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: return
install_cmd('install', args=pkglist, opts=opts, target=target,
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/distro.py", line 254,
in run_apt_command
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: cmd_rv =
apt_install(mode, args, opts=opts, env=env, target=target,
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/distro.py", line 302,
in apt_install
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: cmd_rv =
inchroot.subp(cmd + dl_opts + packages, env=env,
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/util.py", line 791,
in subp
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: return
subp(*args, **kwargs)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/util.py", line 283,
in subp
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: return
_subp(*args, **kwargs)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/util.py", line 147,
in _subp
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: raise
ProcessExecutionError(stdout=out, stderr=err,
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:
curtin.util.ProcessExecutionError: Unexpected error while running command.
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[637
[Touch-packages] [Bug 2055453] Re: FTBFS with -Werror=implicit-function-declaration
** Description changed: As part of time_t work, -Werror=implicit-function-declaration is being - set, but that causes the following FTBFS: + set on armhf, but that causes the following FTBFS on any arch with the + same -Werror=implicit-function-declaration setting: https://launchpadlibrarian.net/716768885/buildlog_ubuntu-noble- armhf.pam_1.5.3-5ubuntu1_BUILDING.txt.gz In file included from obscure.c:42: obscure.c: In function ‘password_check’: support.h:160:9: error: implicit declaration of function ‘pam_overwrite_string’; did you mean ‘_pam_overwrite_n’? [-Werror=implicit-function-declaration] - 160 | pam_overwrite_string(xx); \ - | ^~~~ + 160 | pam_overwrite_string(xx); \ + | ^~~~ obscure.c:151:9: note: in expansion of macro ‘_pam_delete’ - 151 | _pam_delete(newmono); - | ^~~ + 151 | _pam_delete(newmono); + | ^~~ ** Changed in: pam (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2055453 Title: FTBFS with -Werror=implicit-function-declaration Status in pam package in Ubuntu: Fix Committed Bug description: As part of time_t work, -Werror=implicit-function-declaration is being set on armhf, but that causes the following FTBFS on any arch with the same -Werror=implicit-function-declaration setting: https://launchpadlibrarian.net/716768885/buildlog_ubuntu-noble- armhf.pam_1.5.3-5ubuntu1_BUILDING.txt.gz In file included from obscure.c:42: obscure.c: In function ‘password_check’: support.h:160:9: error: implicit declaration of function ‘pam_overwrite_string’; did you mean ‘_pam_overwrite_n’? [-Werror=implicit-function-declaration] 160 | pam_overwrite_string(xx); \ | ^~~~ obscure.c:151:9: note: in expansion of macro ‘_pam_delete’ 151 | _pam_delete(newmono); | ^~~ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2055453/+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 2055453] [NEW] FTBFS with -Werror=implicit-function-declaration
Public bug reported: As part of time_t work, -Werror=implicit-function-declaration is being set, but that causes the following FTBFS: https://launchpadlibrarian.net/716768885/buildlog_ubuntu-noble- armhf.pam_1.5.3-5ubuntu1_BUILDING.txt.gz In file included from obscure.c:42: obscure.c: In function ‘password_check’: support.h:160:9: error: implicit declaration of function ‘pam_overwrite_string’; did you mean ‘_pam_overwrite_n’? [-Werror=implicit-function-declaration] 160 | pam_overwrite_string(xx); \ | ^~~~ obscure.c:151:9: note: in expansion of macro ‘_pam_delete’ 151 | _pam_delete(newmono); | ^~~ ** Affects: pam (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2055453 Title: FTBFS with -Werror=implicit-function-declaration Status in pam package in Ubuntu: New Bug description: As part of time_t work, -Werror=implicit-function-declaration is being set, but that causes the following FTBFS: https://launchpadlibrarian.net/716768885/buildlog_ubuntu-noble- armhf.pam_1.5.3-5ubuntu1_BUILDING.txt.gz In file included from obscure.c:42: obscure.c: In function ‘password_check’: support.h:160:9: error: implicit declaration of function ‘pam_overwrite_string’; did you mean ‘_pam_overwrite_n’? [-Werror=implicit-function-declaration] 160 | pam_overwrite_string(xx); \ | ^~~~ obscure.c:151:9: note: in expansion of macro ‘_pam_delete’ 151 | _pam_delete(newmono); | ^~~ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2055453/+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 2054620] Re: libdm returns wrong error code when dm-verity key cannot be found
With the updated context, I think the proposal looks reasonable and would be comfortable sponsoring the upload. I suggest first waiting for the lvm2 merge to migrate, just to rule out issues on that front. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/2054620 Title: libdm returns wrong error code when dm-verity key cannot be found Status in lvm2 package in Ubuntu: Confirmed Status in lvm2 source package in Noble: Confirmed Bug description: When libcryptsetup tries to activate a signed dm-verity volume, and the key is not in the kernel keyring, libdevicemapper does not return the appropriate ENOKEY, so the failure cannot be distinguished from other generic issues. This is a problem when software like systemd via libcryptsetup try to open a volume, and get an unrecognizable error out of it. With the fix in libdm and libcryptsetup, there is a clear ENOKEY returned when a key is missing and activation fails for that reason. This allows systemd (and other applications) to make the right decision depending on the failure case. Without this, the same generic error is returned in any case. For more details, see: https://gitlab.com/cryptsetup/cryptsetup/-/issues/841 libcryptsetup 2.7.0, now available in debian stable, and systemd v255, shipped in Noble, make use of this error code. This is fixed in the lvm2 version 2.03.23 upstream release. Please consider backporting this patch for Noble. Upstream PR: https://gitlab.com/lvmteam/lvm2/-/merge_requests/3 Upstream commit: 25ef7a7b1a876f491bd361369423d7309358f6c1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054620/+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 2052982] Re: regression in debconf-copydb when writing to stdout
** Bug watch added: Debian Bug tracker #1063817 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063817 ** Also affects: debconf (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063817 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/2052982 Title: regression in debconf-copydb when writing to stdout Status in debconf package in Ubuntu: Fix Committed Status in ubiquity package in Ubuntu: Invalid Status in debconf package in Debian: Unknown Bug description: While debugging a FTBFS in Ubiquity, I observed that the usage of debconf-copydb regressed when using version 1.5.85 of debconf. The previous-in-ubuntu version 1.5.82 of debconf was OK. That invocation looks roughly like: debconf-copydb templatedb pipe --config=Name:pipe --config=Driver:Pipe --config=InFd:none ... Bisecting debconf from there found commit 5db857ade00953496bfdb7edb884296bebc41885: "Avoid two-argument open" Further tracing found the following change to Debconf/DbDriver/Pipe.pm around line 120: - open ($fh, '>-'); + open ($fh, '>', \*STDOUT); An additional symptom of this problem is GLOB files with names that look like: GLOB(0x0123456789ab) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/2052982/+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 2052982] Re: regression in debconf-copydb when writing to stdout
** Changed in: debconf (Ubuntu) Status: New => In Progress ** Changed in: ubiquity (Ubuntu) Status: New => In Progress ** Changed in: ubiquity (Ubuntu) Status: In Progress => Invalid ** Changed in: debconf (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 debconf in Ubuntu. https://bugs.launchpad.net/bugs/2052982 Title: regression in debconf-copydb when writing to stdout Status in debconf package in Ubuntu: Fix Committed Status in ubiquity package in Ubuntu: Invalid Bug description: While debugging a FTBFS in Ubiquity, I observed that the usage of debconf-copydb regressed when using version 1.5.85 of debconf. The previous-in-ubuntu version 1.5.82 of debconf was OK. That invocation looks roughly like: debconf-copydb templatedb pipe --config=Name:pipe --config=Driver:Pipe --config=InFd:none ... Bisecting debconf from there found commit 5db857ade00953496bfdb7edb884296bebc41885: "Avoid two-argument open" Further tracing found the following change to Debconf/DbDriver/Pipe.pm around line 120: - open ($fh, '>-'); + open ($fh, '>', \*STDOUT); An additional symptom of this problem is GLOB files with names that look like: GLOB(0x0123456789ab) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/2052982/+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 2052982] [NEW] regression in debconf-copydb when writing to stdout
Public bug reported: While debugging a FTBFS in Ubiquity, I observed that the usage of debconf-copydb regressed when using version 1.5.85 of debconf. The previous-in-ubuntu version 1.5.82 of debconf was OK. That invocation looks roughly like: debconf-copydb templatedb pipe --config=Name:pipe --config=Driver:Pipe --config=InFd:none ... Bisecting debconf from there found commit 5db857ade00953496bfdb7edb884296bebc41885: "Avoid two-argument open" Further tracing found the following change to Debconf/DbDriver/Pipe.pm around line 120: - open ($fh, '>-'); + open ($fh, '>', \*STDOUT); An additional symptom of this problem is GLOB files with names that look like: GLOB(0x0123456789ab) ** Affects: debconf (Ubuntu) Importance: Undecided Status: New ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Also affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/2052982 Title: regression in debconf-copydb when writing to stdout Status in debconf package in Ubuntu: New Status in ubiquity package in Ubuntu: New Bug description: While debugging a FTBFS in Ubiquity, I observed that the usage of debconf-copydb regressed when using version 1.5.85 of debconf. The previous-in-ubuntu version 1.5.82 of debconf was OK. That invocation looks roughly like: debconf-copydb templatedb pipe --config=Name:pipe --config=Driver:Pipe --config=InFd:none ... Bisecting debconf from there found commit 5db857ade00953496bfdb7edb884296bebc41885: "Avoid two-argument open" Further tracing found the following change to Debconf/DbDriver/Pipe.pm around line 120: - open ($fh, '>-'); + open ($fh, '>', \*STDOUT); An additional symptom of this problem is GLOB files with names that look like: GLOB(0x0123456789ab) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/2052982/+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 2051576] Re: Please merge 1.9.15p5-3 into noble
LGTM, uploading. ** Changed in: sudo (Ubuntu) Status: New => Fix Committed ** Changed in: sudo (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/2051576 Title: Please merge 1.9.15p5-3 into noble Status in sudo package in Ubuntu: Fix Committed Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2051576/+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 2049540] Re: hundreds of differences in module list between initramfs-tools version 0.142ubuntu10 and version 0.142ubuntu11
Hi Ben, > Is there any proof that these modules are needed? It appears we have very different assumptions for how dracut was to be brought on board. Diffstat of 0.142ubuntu1[01].log looks like: 1 file changed, 229 insertions(+), 661 deletions(-) That sounds like a lot of changes, in a LTS. I think we need to flip the mindset here - the status quo of the modules present should be preserved, and the differences should be justified. Do we have supporting evidence that all these changes are appropriate? The risk here is that inadequate testing happens and we get a trickle of bugs like LP: #2042710 that will need to be SRUed. > Using symbol regexes will be more fine-grained than including whole directories. I appreciate that the previous mechanism has certainly acquired some bloat by including whole directories, but now that is the observable shipping behavior and we risk regressing people who depend on that. How can we tell the difference? -- 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/2049540 Title: hundreds of differences in module list between initramfs-tools version 0.142ubuntu10 and version 0.142ubuntu11 Status in initramfs-tools package in Ubuntu: Triaged Status in initramfs-tools source package in Noble: Triaged Bug description: When analyzing the kernel modules present in the current initrd, I have found that there are hundreds of such differences, and that this started with the move to dracut. I believe that the move to dracut was intended to be relatively module neutral - see LP: #2031841 and LP: #2042710 for more details on that. I'm attaching here a test case based on podman, where different versions of the initramfs-tools package are installed, and then the list of modules present in the initrd is analyzed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2049540/+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 2049540] Re: hundreds of differences in module list between initramfs-tools version 0.142ubuntu10 and version 0.142ubuntu11
** Tags added: rls-nn-incoming -- 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/2049540 Title: hundreds of differences in module list between initramfs-tools version 0.142ubuntu10 and version 0.142ubuntu11 Status in initramfs-tools package in Ubuntu: New Bug description: When analyzing the kernel modules present in the current initrd, I have found that there are hundreds of such differences, and that this started with the move to dracut. I believe that the move to dracut was intended to be relatively module neutral - see LP: #2031841 and LP: #2042710 for more details on that. I'm attaching here a test case based on podman, where different versions of the initramfs-tools package are installed, and then the list of modules present in the initrd is analyzed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2049540/+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 2049540] Re: hundreds of differences in module list between initramfs-tools version 0.142ubuntu10 and version 0.142ubuntu11
** Attachment added: "0.142ubuntu11.log" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2049540/+attachment/5740004/+files/0.142ubuntu11.log -- 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/2049540 Title: hundreds of differences in module list between initramfs-tools version 0.142ubuntu10 and version 0.142ubuntu11 Status in initramfs-tools package in Ubuntu: New Bug description: When analyzing the kernel modules present in the current initrd, I have found that there are hundreds of such differences, and that this started with the move to dracut. I believe that the move to dracut was intended to be relatively module neutral - see LP: #2031841 and LP: #2042710 for more details on that. I'm attaching here a test case based on podman, where different versions of the initramfs-tools package are installed, and then the list of modules present in the initrd is analyzed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2049540/+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 2049540] Re: hundreds of differences in module list between initramfs-tools version 0.142ubuntu10 and version 0.142ubuntu11
** Attachment added: "0.142ubuntu19.log" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2049540/+attachment/5740005/+files/0.142ubuntu19.log -- 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/2049540 Title: hundreds of differences in module list between initramfs-tools version 0.142ubuntu10 and version 0.142ubuntu11 Status in initramfs-tools package in Ubuntu: New Bug description: When analyzing the kernel modules present in the current initrd, I have found that there are hundreds of such differences, and that this started with the move to dracut. I believe that the move to dracut was intended to be relatively module neutral - see LP: #2031841 and LP: #2042710 for more details on that. I'm attaching here a test case based on podman, where different versions of the initramfs-tools package are installed, and then the list of modules present in the initrd is analyzed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2049540/+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 2049540] Re: hundreds of differences in module list between initramfs-tools version 0.142ubuntu10 and version 0.142ubuntu11
** Attachment added: "0.142ubuntu10.log" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2049540/+attachment/5740003/+files/0.142ubuntu10.log -- 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/2049540 Title: hundreds of differences in module list between initramfs-tools version 0.142ubuntu10 and version 0.142ubuntu11 Status in initramfs-tools package in Ubuntu: New Bug description: When analyzing the kernel modules present in the current initrd, I have found that there are hundreds of such differences, and that this started with the move to dracut. I believe that the move to dracut was intended to be relatively module neutral - see LP: #2031841 and LP: #2042710 for more details on that. I'm attaching here a test case based on podman, where different versions of the initramfs-tools package are installed, and then the list of modules present in the initrd is analyzed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2049540/+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 2049540] [NEW] hundreds of differences in module list between initramfs-tools version 0.142ubuntu10 and version 0.142ubuntu11
Public bug reported: When analyzing the kernel modules present in the current initrd, I have found that there are hundreds of such differences, and that this started with the move to dracut. I believe that the move to dracut was intended to be relatively module neutral - see LP: #2031841 and LP: #2042710 for more details on that. I'm attaching here a test case based on podman, where different versions of the initramfs-tools package are installed, and then the list of modules present in the initrd is analyzed. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Sample container builder to generate a list of kernel modules" https://bugs.launchpad.net/bugs/2049540/+attachment/5740002/+files/testcase.tar -- 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/2049540 Title: hundreds of differences in module list between initramfs-tools version 0.142ubuntu10 and version 0.142ubuntu11 Status in initramfs-tools package in Ubuntu: New Bug description: When analyzing the kernel modules present in the current initrd, I have found that there are hundreds of such differences, and that this started with the move to dracut. I believe that the move to dracut was intended to be relatively module neutral - see LP: #2031841 and LP: #2042710 for more details on that. I'm attaching here a test case based on podman, where different versions of the initramfs-tools package are installed, and then the list of modules present in the initrd is analyzed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2049540/+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 2046389] Re: FTBFS if bash-completion is installed at build time
** Changed in: p11-kit (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to p11-kit in Ubuntu. https://bugs.launchpad.net/bugs/2046389 Title: FTBFS if bash-completion is installed at build time Status in p11-kit package in Ubuntu: Fix Committed Bug description: p11-kit will FTBFS if bash-completion happens to be installed on the system building p11-kit. The failure is raised by dh_missing: dh_missing dh_missing: warning: usr/share/bash-completion/completions/p11-kit exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/usr/bin/p11-kit") dh_missing: warning: usr/share/bash-completion/completions/trust exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/usr/bin/trust") dh_missing: error: missing files, aborting full sample log: https://launchpadlibrarian.net/702524075/buildlog_ubuntu-noble-amd64.p11-kit_0.25.3-2ubuntu1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/p11-kit/+bug/2046389/+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 2046389] Re: FTBFS if bash-completion is installed at build time
** Changed in: p11-kit (Ubuntu) Assignee: (unassigned) => Dan Bungert (dbungert) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to p11-kit in Ubuntu. https://bugs.launchpad.net/bugs/2046389 Title: FTBFS if bash-completion is installed at build time Status in p11-kit package in Ubuntu: New Bug description: p11-kit will FTBFS if bash-completion happens to be installed on the system building p11-kit. The failure is raised by dh_missing: dh_missing dh_missing: warning: usr/share/bash-completion/completions/p11-kit exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/usr/bin/p11-kit") dh_missing: warning: usr/share/bash-completion/completions/trust exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/usr/bin/trust") dh_missing: error: missing files, aborting full sample log: https://launchpadlibrarian.net/702524075/buildlog_ubuntu-noble-amd64.p11-kit_0.25.3-2ubuntu1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/p11-kit/+bug/2046389/+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 2046389] [NEW] FTBFS if bash-completion is installed at build time
Public bug reported: p11-kit will FTBFS if bash-completion happens to be installed on the system building p11-kit. The failure is raised by dh_missing: dh_missing dh_missing: warning: usr/share/bash-completion/completions/p11-kit exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/usr/bin/p11-kit") dh_missing: warning: usr/share/bash-completion/completions/trust exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/usr/bin/trust") dh_missing: error: missing files, aborting full sample log: https://launchpadlibrarian.net/702524075/buildlog_ubuntu-noble-amd64.p11-kit_0.25.3-2ubuntu1_BUILDING.txt.gz ** Affects: p11-kit (Ubuntu) Importance: Undecided Status: New ** Description changed: p11-kit will FTBFS if bash-completion happens to be installed on the system building p11-kit. The failure is raised by dh_missing: -dh_missing + dh_missing dh_missing: warning: usr/share/bash-completion/completions/p11-kit exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/usr/bin/p11-kit") dh_missing: warning: usr/share/bash-completion/completions/trust exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/usr/bin/trust") dh_missing: error: missing files, aborting + + full sample log: + https://launchpadlibrarian.net/702524075/buildlog_ubuntu-noble-amd64.p11-kit_0.25.3-2ubuntu1_BUILDING.txt.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to p11-kit in Ubuntu. https://bugs.launchpad.net/bugs/2046389 Title: FTBFS if bash-completion is installed at build time Status in p11-kit package in Ubuntu: New Bug description: p11-kit will FTBFS if bash-completion happens to be installed on the system building p11-kit. The failure is raised by dh_missing: dh_missing dh_missing: warning: usr/share/bash-completion/completions/p11-kit exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/usr/bin/p11-kit") dh_missing: warning: usr/share/bash-completion/completions/trust exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/usr/bin/trust") dh_missing: error: missing files, aborting full sample log: https://launchpadlibrarian.net/702524075/buildlog_ubuntu-noble-amd64.p11-kit_0.25.3-2ubuntu1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/p11-kit/+bug/2046389/+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 589496] Re: bash --rcfile does not behave as documented
*** This bug is a duplicate of bug 1097467 *** https://bugs.launchpad.net/bugs/1097467 Merging with LP: #1097467, as documentation fixes are happening there to reflect long-standing upstream desired behavior. ** This bug has been marked a duplicate of bug 1097467 bash does not fulfill --rcfile option properly -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/589496 Title: bash --rcfile does not behave as documented Status in bash package in Ubuntu: Confirmed Status in bash package in Debian: New Bug description: Binary package hint: bash the bash manpage says this about --rcfile --rcfile file Execute commands from file instead of the system wide initial‐ ization file /etc/bash.bashrc and the standard personal initial‐ ization file ~/.bashrc if the shell is interactive (see INVOCA‐ TION below). under INVOCATION it says When an interactive shell that is not a login shell is started, bash reads and executes commands from /etc/bash.bashrc and ~/.bashrc, if these files exist. This may be inhibited by using the --norc option. The --rcfile file option will force bash to read and execute commands from file instead of /etc/bash.bashrc and ~/.bashrc. but when i execute $ bash --rcfile somercfilewhichreallydoesexistandisreadableandall it will still read /etc/bash/bashrc (can be verified by adding --verbose) using lucid with bash 4.1-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/589496/+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 1097467] Re: bash does not fulfill --rcfile option properly
Uploaded ** Changed in: bash (Ubuntu) Assignee: (unassigned) => Dan Bungert (dbungert) ** Changed in: bash (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1097467 Title: bash does not fulfill --rcfile option properly Status in Gnu Bash: New Status in bash package in Ubuntu: Fix Committed Bug description: I am starting a bash shell using $ bash --noprofile --rcfile my-custom-bash-rc-file Due to the --rcflag, the newly started bash should *not* execute commands from /etc/bash.bashrc. That is at least how I interpret `man bash`: --rcfile file Execute commands from file instead of the system wide initialization file /etc/bash.bashrc and the standard personal initial‐ ization file ~/.bashrc if the shell is interactive (see INVOCATION below). However, it seems that the commands in /etc/bash.bashrc are in fact executed. To see/reproduce/diagnose this, on Ubuntu I believe one can just invoke bash like this (as the regular user): $ touch testrc $ env -i bash --noprofile --rcfile testrc The expected result would be that nothing special is printed on the terminal. However, there is an error message, which is printed from /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the invoked shell, which in turn triggers the error. The error message is: > To run a command as administrator (user "root"), use "sudo ". > See "man sudo_root" for details. Another way to see this -- without the "env -i" -- is to add a command to /etc/bash.bashrc, such as echo HELLO THERE To trigger the bug(?), one can then just do $ touch testrc $ bash --noprofile --rcfile testrc The expected result would be that nothing special is shown in the terminal. However, it turns out that the string HELLO THERE is printed. To manage notifications about this bug go to: https://bugs.launchpad.net/gnubash/+bug/1097467/+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 2040481] Re: Cannot install Jammy server on machine using pppoe connection to access internet
** Changed in: ubuntu-meta (Ubuntu Noble) Status: New => Triaged ** Changed in: ubuntu-meta (Ubuntu Noble) Importance: Undecided => Medium -- 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/2040481 Title: Cannot install Jammy server on machine using pppoe connection to access internet Status in ubuntu-meta package in Ubuntu: Triaged Status in ubuntu-meta source package in Noble: Triaged Bug description: I've noticed that the Ubuntu Jammy live server installer iso does not contain the ppp package, so this makes it impossible to install ubuntu on a device which uses pppoe to access the internet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2040481/+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 2039611] Re: [SRU] Fix fcc-unlock script for Lenovo X13s
I'm unsubscribing sponsors for the moment, when you are content with the results on noble please provide a modified debdiff with a SRU-friendly version number for mantic and subscribe sponsors again. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2039611 Title: [SRU] Fix fcc-unlock script for Lenovo X13s Status in modemmanager package in Ubuntu: Fix Committed Status in modemmanager source package in Mantic: New Status in modemmanager source package in Noble: Fix Committed Bug description: [ Impact ] Some of the Lenovo X13s laptop SKUs, based on the Qualcomm Snapdragon 8cx, come with an integrated 4G/5G modem. The modem on the X13s is manufactured by foxconn, and is based on the Qualcomm Snapdragon X55 PCIe modem. Here is the output of mmcli -m 0 on an X13s Hardware |manufacturer: foxconn | model: Qualcomm Snapdragon X55 5G | firmware revision: T99W175.F0.6.0.0.6.OG.005 | 045 1 [Feb 03 2023 10:00:00] All Linux kernel drivers are upstream to support this data modem, and included in the Ubuntu kernel for mantic. The support for this modem is also merged in modemmanager, including the fcc-unlock script for this modem model (https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/ac06052b97cc02e60ae1ed7a551727b3c14d6a22). We are however missing the symlink for the specific PCIe ID link reported on the X13s for this modem, which is shown by lspci as: 0004:01:00.0 Wireless controller [0d40]: Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] [105b:e0c3] This is already fixed upstream with https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/commit/8061bcd9c03c26946b6fa3356313e069203f8838. With the backport of this patch the modem on the X13S can be enabled by laptop users using the fcc-unlock generic guidelines. And mobile broadband is working out of the box. Without it, the modem won't work. [ Test Plan ] Without the ability to FCC unlock this modem model, any attempt to enable/start the modem will fail / stall, as detailed on https://modemmanager.org/docs/modemmanager/fcc-unlock/. With this backport/fix, the Ubuntu Mobile network settings/UI can be used to enabled the modem, unlock the SIM card and connect to the 4G/5G network (assuming the user has a SIM card with an appropriate data plan). [ Where problems could occur ] The patch is fairly isolated change. The purpose of this change is to create an additional symlink in /usr/share/ModemManager/fcc- unlock.available.d/ whose name is the PCIe ID of this specific device. PCIe IDs are documented here: https://cateee.net/lkddb/web- lkddb/MHI_BUS.html. Also links in this folder have no effect on the system, unless the user manually enable the appropriate fcc unlock script, typically by adding a link in /etc/ModemManager/fcc-unlock.d/ to the appropriate modem model script. [ Other Info ] I am working on a debdiff, and will upload shortly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/2039611/+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 2039611] Re: [SRU] Fix fcc-unlock script for Lenovo X13s
Thanks Nicholas. I have adjusted the patch slightly to target noble instead of mantic - noble will need to be first, now. When modemmanager is synced from Debian this patch looks to already be present there, but I thought it interesting to upload this now to facilitate the SRU process. Uploading for noble. ** Changed in: modemmanager (Ubuntu Noble) Assignee: (unassigned) => Dan Bungert (dbungert) ** Changed in: modemmanager (Ubuntu Noble) Status: New => In Progress ** Changed in: modemmanager (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2039611 Title: [SRU] Fix fcc-unlock script for Lenovo X13s Status in modemmanager package in Ubuntu: Fix Committed Status in modemmanager source package in Mantic: New Status in modemmanager source package in Noble: Fix Committed Bug description: [ Impact ] Some of the Lenovo X13s laptop SKUs, based on the Qualcomm Snapdragon 8cx, come with an integrated 4G/5G modem. The modem on the X13s is manufactured by foxconn, and is based on the Qualcomm Snapdragon X55 PCIe modem. Here is the output of mmcli -m 0 on an X13s Hardware |manufacturer: foxconn | model: Qualcomm Snapdragon X55 5G | firmware revision: T99W175.F0.6.0.0.6.OG.005 | 045 1 [Feb 03 2023 10:00:00] All Linux kernel drivers are upstream to support this data modem, and included in the Ubuntu kernel for mantic. The support for this modem is also merged in modemmanager, including the fcc-unlock script for this modem model (https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/ac06052b97cc02e60ae1ed7a551727b3c14d6a22). We are however missing the symlink for the specific PCIe ID link reported on the X13s for this modem, which is shown by lspci as: 0004:01:00.0 Wireless controller [0d40]: Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] [105b:e0c3] This is already fixed upstream with https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/commit/8061bcd9c03c26946b6fa3356313e069203f8838. With the backport of this patch the modem on the X13S can be enabled by laptop users using the fcc-unlock generic guidelines. And mobile broadband is working out of the box. Without it, the modem won't work. [ Test Plan ] Without the ability to FCC unlock this modem model, any attempt to enable/start the modem will fail / stall, as detailed on https://modemmanager.org/docs/modemmanager/fcc-unlock/. With this backport/fix, the Ubuntu Mobile network settings/UI can be used to enabled the modem, unlock the SIM card and connect to the 4G/5G network (assuming the user has a SIM card with an appropriate data plan). [ Where problems could occur ] The patch is fairly isolated change. The purpose of this change is to create an additional symlink in /usr/share/ModemManager/fcc- unlock.available.d/ whose name is the PCIe ID of this specific device. PCIe IDs are documented here: https://cateee.net/lkddb/web- lkddb/MHI_BUS.html. Also links in this folder have no effect on the system, unless the user manually enable the appropriate fcc unlock script, typically by adding a link in /etc/ModemManager/fcc-unlock.d/ to the appropriate modem model script. [ Other Info ] I am working on a debdiff, and will upload shortly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/2039611/+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 2039611] Re: [SRU] Fix fcc-unlock script for Lenovo X13s
** Also affects: modemmanager (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: modemmanager (Ubuntu Mantic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2039611 Title: [SRU] Fix fcc-unlock script for Lenovo X13s Status in modemmanager package in Ubuntu: New Status in modemmanager source package in Mantic: New Status in modemmanager source package in Noble: New Bug description: [ Impact ] Some of the Lenovo X13s laptop SKUs, based on the Qualcomm Snapdragon 8cx, come with an integrated 4G/5G modem. The modem on the X13s is manufactured by foxconn, and is based on the Qualcomm Snapdragon X55 PCIe modem. Here is the output of mmcli -m 0 on an X13s Hardware |manufacturer: foxconn | model: Qualcomm Snapdragon X55 5G | firmware revision: T99W175.F0.6.0.0.6.OG.005 | 045 1 [Feb 03 2023 10:00:00] All Linux kernel drivers are upstream to support this data modem, and included in the Ubuntu kernel for mantic. The support for this modem is also merged in modemmanager, including the fcc-unlock script for this modem model (https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/ac06052b97cc02e60ae1ed7a551727b3c14d6a22). We are however missing the symlink for the specific PCIe ID link reported on the X13s for this modem, which is shown by lspci as: 0004:01:00.0 Wireless controller [0d40]: Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] [105b:e0c3] This is already fixed upstream with https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/commit/8061bcd9c03c26946b6fa3356313e069203f8838. With the backport of this patch the modem on the X13S can be enabled by laptop users using the fcc-unlock generic guidelines. And mobile broadband is working out of the box. Without it, the modem won't work. [ Test Plan ] Without the ability to FCC unlock this modem model, any attempt to enable/start the modem will fail / stall, as detailed on https://modemmanager.org/docs/modemmanager/fcc-unlock/. With this backport/fix, the Ubuntu Mobile network settings/UI can be used to enabled the modem, unlock the SIM card and connect to the 4G/5G network (assuming the user has a SIM card with an appropriate data plan). [ Where problems could occur ] The patch is fairly isolated change. The purpose of this change is to create an additional symlink in /usr/share/ModemManager/fcc- unlock.available.d/ whose name is the PCIe ID of this specific device. PCIe IDs are documented here: https://cateee.net/lkddb/web- lkddb/MHI_BUS.html. Also links in this folder have no effect on the system, unless the user manually enable the appropriate fcc unlock script, typically by adding a link in /etc/ModemManager/fcc-unlock.d/ to the appropriate modem model script. [ Other Info ] I am working on a debdiff, and will upload shortly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/2039611/+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
** Description changed: [ 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 of the mirrors.cfg, adding and removing 2 mirrors -* rev the POT-Creation-Date of the po files -* an update to tests + * 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 -- 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 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-meta source package in Lunar: New Status in ubuntu-release-upgrader source package in Lunar: In Progress 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 "Sta
[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade
** Description changed: [ 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 of the mirrors.cfg, adding and removing 2 mirrors +* rev the POT-Creation-Date of the po files +* an update to tests + [ 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. + 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 -- 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 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-meta source package in Lunar: New Status in ubuntu-release-upgrader source package in Lunar: In Progress 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
[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade
** Description changed: [ 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. + critical criteria for making the Mate version of the fix work. [ 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. - - * We are proposing to move this package update to Ubuntu Lunar as - fast as possible. The risk is high here that we, in the rush, - create new problems. + 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 -- 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 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-meta source package in Lunar: New Status in ubuntu-release-upgrader source package in Lunar: In Progress 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 fon
[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade
** Description changed: [ 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. + * 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. + * 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. + * 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_SESSION_TYPE, as this is the critical -criteria for making the Mate version of the fix work. + * 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. [ Test Plan ] - * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64 + * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64 - * as user, run "update-manager -d" + * 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. + * 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 + * 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. + * 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. - * We are proposing to move this package update to Ubuntu Lunar as -fast as possible. The risk is high here that we, in the rush, -create new problems. + * We are proposing to move this package update to Ubuntu Lunar as + fast as possible. The risk is high here that we, in the rush, + create new problems. [ Other Info ] - * TBD + * 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-0
[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade
** Description changed: [ 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_SESSION_TYPE, as this is the critical +criteria for making the Mate version of the fix work. [ 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. * We are proposing to move this package update to Ubuntu Lunar as fast as possible. The risk is high here that we, in the rush, create new problems. [ 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 -- 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 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-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_SESSION_TYPE, as this is the critical criteria for making the Mate version of the fix work. [ Test Plan ] * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64 * as user, run "update-manager -d" * monit
[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade
** Description changed: + [ 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. + + [ 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. + + * We are proposing to move this package update to Ubuntu Lunar as +fast as possible. The risk is high here that we, in the rush, +create new problems. + + [ 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 + + mtime.conffile..etc.update-manager.meta-release: + 2021-05-27T16:30:16.970490 -- 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 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-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_SESSION_TYPE, as this is the critical criteria for making the Mate version of the fix work. [ 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 b
[Touch-packages] [Bug 2037202] Re: Mantic/23.10: PXE boot tries to initialize DHCP before network link is up
** Merge proposal linked: https://code.launchpad.net/~mwhudson/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/452586 -- 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/2037202 Title: Mantic/23.10: PXE boot tries to initialize DHCP before network link is up Status in initramfs-tools package in Ubuntu: New Bug description: I'm not sure whether this is the correct package for this bug, please reassign if not. I'm booting the Ubuntu Mantic/23.10 desktop beta image via PXE in order to perform an unattended installation. The kernel command line looks like that: iso/casper/vmlinuz --- ip=dhcp netboot=nfs nfsroot=192.168.1.1:/export/ubuntu autoinstall ds=nocloud\;s= This has worked perfectly before. However, in 23.10, the kernel tries to intialize DHCP before a network link is up. I can see a few instances of messages like the following: dhcpcd-10.0.2 starting dev: loaded udev no interfaces have a carrier exiting due to oneshot dhcpcd exited Then, the kernel tries to mount NFS, even though neither an IP address nor even a link is available: connect: Network is unreachable NFS over TCP not available from 192.168.1.1 This is repeated for a while. In between, a message tells that now the link is up: [10.0002805] e1000e :00:19.0 enp0s25: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx The NFS messages repeat for a while, until the system gives up and I'm dropped into a busybox prompt. Executing dhcpcd now correctly gets IP addresses, but I don't know how to continue the boot from there. The problem occurs on most physical machines that I tried, but not in VMs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2037202/+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 2037569] Re: udev issues with mantic beta
Seb reviewed and +1ed on IRC. Uploaded. ** Changed in: udisks2 (Ubuntu) Assignee: (unassigned) => Dan Bungert (dbungert) ** Changed in: udisks2 (Ubuntu) Status: Confirmed => 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/2037569 Title: udev issues with mantic beta Status in Ubuntu on IBM z Systems: Confirmed Status in libblockdev package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Status in udisks2 package in Ubuntu: Fix Committed Bug description: While installing mantic beta (on s390x, LPAR and z/VM - but this might not be architecture specific) I faced issues with udev. In my installation I've updated the installer to "edge/lp-2009141" (subiquity 22.02.2+git1762.1b1ee6f4 5164). During my installations I first noticed bad response times in case of dealing with devices (like enabling new devices with chzdev). chzdev is used during the installation, hence the installation procedure is also affected by this. (I mainly notice this issue in case of DASD ECKD disk enablements.) But even after after a successful (but due to this issue less snappier) installation, means after the post-install reboot, in the installed system I can find several udev related processes, like: 69448 root 20 0 31280 11944 2560 S 39.2 0.0 2:51.67 (udev-worker) 509 root 20 0 31276 13812 4600 S 20.6 0.0 2:07.76 systemd-udevd 893 root 20 0 469016 13544 10496 R 17.3 0.0 1:43.53 udisksd 1 root 20 0 168664 12748 8396 S 16.3 0.0 1:40.47 systemd which is not only unusual, but (as one can see) they consume quite some resources. Even the remote ssh into that system is impacted by this high load. So far I only see this in mantic. I tried 20.04.3 as well as lunar, but both do not seem to be affected by this udev problem. I neither face the bad response on device enablement, nor can see any udev related processes still running after post-install-reboot in the installed system. (Sometimes I could also see a growing log file 'syslog'). I cannot say yet what is causing this, but since I see 'systemd-udevd' as prominent process in top, I'll first of all mark this as affecting systemd-udevd (or systemd). I've attached the outcome of some more investigations I did ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+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 2037569] Re: udev issues with mantic beta
Proposed changes to avoid the event storm ** Patch added: "udisks2-1_2.10.1-1_2.10.1-1ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/2037569/+attachment/5705929/+files/udisks2-1_2.10.1-1_2.10.1-1ubuntu1.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/2037569 Title: udev issues with mantic beta Status in Ubuntu on IBM z Systems: Confirmed Status in libblockdev package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Status in udisks2 package in Ubuntu: Confirmed Bug description: While installing mantic beta (on s390x, LPAR and z/VM - but this might not be architecture specific) I faced issues with udev. In my installation I've updated the installer to "edge/lp-2009141" (subiquity 22.02.2+git1762.1b1ee6f4 5164). During my installations I first noticed bad response times in case of dealing with devices (like enabling new devices with chzdev). chzdev is used during the installation, hence the installation procedure is also affected by this. (I mainly notice this issue in case of DASD ECKD disk enablements.) But even after after a successful (but due to this issue less snappier) installation, means after the post-install reboot, in the installed system I can find several udev related processes, like: 69448 root 20 0 31280 11944 2560 S 39.2 0.0 2:51.67 (udev-worker) 509 root 20 0 31276 13812 4600 S 20.6 0.0 2:07.76 systemd-udevd 893 root 20 0 469016 13544 10496 R 17.3 0.0 1:43.53 udisksd 1 root 20 0 168664 12748 8396 S 16.3 0.0 1:40.47 systemd which is not only unusual, but (as one can see) they consume quite some resources. Even the remote ssh into that system is impacted by this high load. So far I only see this in mantic. I tried 20.04.3 as well as lunar, but both do not seem to be affected by this udev problem. I neither face the bad response on device enablement, nor can see any udev related processes still running after post-install-reboot in the installed system. (Sometimes I could also see a growing log file 'syslog'). I cannot say yet what is causing this, but since I see 'systemd-udevd' as prominent process in top, I'll first of all mark this as affecting systemd-udevd (or systemd). I've attached the outcome of some more investigations I did ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+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 2037569] Re: udev issues with mantic beta
proposal 4. set ID_PART_TABLE_TYPE in the appropriate spot -- 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/2037569 Title: udev issues with mantic beta Status in Ubuntu on IBM z Systems: Confirmed Status in libblockdev package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Status in udisks2 package in Ubuntu: Confirmed Bug description: While installing mantic beta (on s390x, LPAR and z/VM - but this might not be architecture specific) I faced issues with udev. In my installation I've updated the installer to "edge/lp-2009141" (subiquity 22.02.2+git1762.1b1ee6f4 5164). During my installations I first noticed bad response times in case of dealing with devices (like enabling new devices with chzdev). chzdev is used during the installation, hence the installation procedure is also affected by this. (I mainly notice this issue in case of DASD ECKD disk enablements.) But even after after a successful (but due to this issue less snappier) installation, means after the post-install reboot, in the installed system I can find several udev related processes, like: 69448 root 20 0 31280 11944 2560 S 39.2 0.0 2:51.67 (udev-worker) 509 root 20 0 31276 13812 4600 S 20.6 0.0 2:07.76 systemd-udevd 893 root 20 0 469016 13544 10496 R 17.3 0.0 1:43.53 udisksd 1 root 20 0 168664 12748 8396 S 16.3 0.0 1:40.47 systemd which is not only unusual, but (as one can see) they consume quite some resources. Even the remote ssh into that system is impacted by this high load. So far I only see this in mantic. I tried 20.04.3 as well as lunar, but both do not seem to be affected by this udev problem. I neither face the bad response on device enablement, nor can see any udev related processes still running after post-install-reboot in the installed system. (Sometimes I could also see a growing log file 'syslog'). I cannot say yet what is causing this, but since I see 'systemd-udevd' as prominent process in top, I'll first of all mark this as affecting systemd-udevd (or systemd). I've attached the outcome of some more investigations I did ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+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 2037569] Re: udev issues with mantic beta
after exploring udisks2/libblockdev/libfdisk, I have three possible proposals for resolution: 1. hack udisks2 udisks_linux_partition_table_update * calling bd_part_get_disk_spec is always going to be a loop, unless * watches have been inhibited * or calling bd_part_get_disk_spec causes ID_PART_TABLE_TYPE to be set * disable everything under `if (!part_type && num_parts > 0)`, log and bail 2. add read-only API in libblockdev so we open the dev RO in libfdisk 3. add vtoc support to libfdisk + enable the s390 bits in libblockdev only option 1 sounds plausible to me, though, for a Mantic timeframe. -- 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/2037569 Title: udev issues with mantic beta Status in Ubuntu on IBM z Systems: Confirmed Status in libblockdev package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Status in udisks2 package in Ubuntu: Confirmed Bug description: While installing mantic beta (on s390x, LPAR and z/VM - but this might not be architecture specific) I faced issues with udev. In my installation I've updated the installer to "edge/lp-2009141" (subiquity 22.02.2+git1762.1b1ee6f4 5164). During my installations I first noticed bad response times in case of dealing with devices (like enabling new devices with chzdev). chzdev is used during the installation, hence the installation procedure is also affected by this. (I mainly notice this issue in case of DASD ECKD disk enablements.) But even after after a successful (but due to this issue less snappier) installation, means after the post-install reboot, in the installed system I can find several udev related processes, like: 69448 root 20 0 31280 11944 2560 S 39.2 0.0 2:51.67 (udev-worker) 509 root 20 0 31276 13812 4600 S 20.6 0.0 2:07.76 systemd-udevd 893 root 20 0 469016 13544 10496 R 17.3 0.0 1:43.53 udisksd 1 root 20 0 168664 12748 8396 S 16.3 0.0 1:40.47 systemd which is not only unusual, but (as one can see) they consume quite some resources. Even the remote ssh into that system is impacted by this high load. So far I only see this in mantic. I tried 20.04.3 as well as lunar, but both do not seem to be affected by this udev problem. I neither face the bad response on device enablement, nor can see any udev related processes still running after post-install-reboot in the installed system. (Sometimes I could also see a growing log file 'syslog'). I cannot say yet what is causing this, but since I see 'systemd-udevd' as prominent process in top, I'll first of all mark this as affecting systemd-udevd (or systemd). I've attached the outcome of some more investigations I did ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+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 2037569] Re: udev issues with mantic beta
Marking invalid in systemd, other than long-standing udev rules being involved I'm not sure this will be fixed in systemd. Exploring if libblockdev with the s390 plugin enabled helps. ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid ** Also affects: libblockdev (Ubuntu) Importance: Undecided Status: New -- 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/2037569 Title: udev issues with mantic beta Status in Ubuntu on IBM z Systems: Confirmed Status in libblockdev package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Status in udisks2 package in Ubuntu: Confirmed Bug description: While installing mantic beta (on s390x, LPAR and z/VM - but this might not be architecture specific) I faced issues with udev. In my installation I've updated the installer to "edge/lp-2009141" (subiquity 22.02.2+git1762.1b1ee6f4 5164). During my installations I first noticed bad response times in case of dealing with devices (like enabling new devices with chzdev). chzdev is used during the installation, hence the installation procedure is also affected by this. (I mainly notice this issue in case of DASD ECKD disk enablements.) But even after after a successful (but due to this issue less snappier) installation, means after the post-install reboot, in the installed system I can find several udev related processes, like: 69448 root 20 0 31280 11944 2560 S 39.2 0.0 2:51.67 (udev-worker) 509 root 20 0 31276 13812 4600 S 20.6 0.0 2:07.76 systemd-udevd 893 root 20 0 469016 13544 10496 R 17.3 0.0 1:43.53 udisksd 1 root 20 0 168664 12748 8396 S 16.3 0.0 1:40.47 systemd which is not only unusual, but (as one can see) they consume quite some resources. Even the remote ssh into that system is impacted by this high load. So far I only see this in mantic. I tried 20.04.3 as well as lunar, but both do not seem to be affected by this udev problem. I neither face the bad response on device enablement, nor can see any udev related processes still running after post-install-reboot in the installed system. (Sometimes I could also see a growing log file 'syslog'). I cannot say yet what is causing this, but since I see 'systemd-udevd' as prominent process in top, I'll first of all mark this as affecting systemd-udevd (or systemd). I've attached the outcome of some more investigations I did ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+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 2037569] Re: udev issues with mantic beta
In function udisks_linux_partition_table_update if num_parts > 0, no ID_PART_TABLE_TYPE is present, and bd_part_get_disk_spec fails to get the disk information including part_type, this function will fail. Also, because libblockdev uses libfdisk in a manner that opens the disk RW, that causes another udev event and that will cause udisks_linux_partition_table_update to be called again. -- 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/2037569 Title: udev issues with mantic beta Status in Ubuntu on IBM z Systems: Confirmed Status in systemd package in Ubuntu: Confirmed Status in udisks2 package in Ubuntu: Confirmed Bug description: While installing mantic beta (on s390x, LPAR and z/VM - but this might not be architecture specific) I faced issues with udev. In my installation I've updated the installer to "edge/lp-2009141" (subiquity 22.02.2+git1762.1b1ee6f4 5164). During my installations I first noticed bad response times in case of dealing with devices (like enabling new devices with chzdev). chzdev is used during the installation, hence the installation procedure is also affected by this. (I mainly notice this issue in case of DASD ECKD disk enablements.) But even after after a successful (but due to this issue less snappier) installation, means after the post-install reboot, in the installed system I can find several udev related processes, like: 69448 root 20 0 31280 11944 2560 S 39.2 0.0 2:51.67 (udev-worker) 509 root 20 0 31276 13812 4600 S 20.6 0.0 2:07.76 systemd-udevd 893 root 20 0 469016 13544 10496 R 17.3 0.0 1:43.53 udisksd 1 root 20 0 168664 12748 8396 S 16.3 0.0 1:40.47 systemd which is not only unusual, but (as one can see) they consume quite some resources. Even the remote ssh into that system is impacted by this high load. So far I only see this in mantic. I tried 20.04.3 as well as lunar, but both do not seem to be affected by this udev problem. I neither face the bad response on device enablement, nor can see any udev related processes still running after post-install-reboot in the installed system. (Sometimes I could also see a growing log file 'syslog'). I cannot say yet what is causing this, but since I see 'systemd-udevd' as prominent process in top, I'll first of all mark this as affecting systemd-udevd (or systemd). I've attached the outcome of some more investigations I did ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+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 2037425] Re: ubuntu-server pulls in ZFS userspace
seed MP merged, dput of ubuntu-meta done. ** Changed in: ubuntu-meta (Ubuntu Mantic) Status: In Progress => Fix Committed -- 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/2037425 Title: ubuntu-server pulls in ZFS userspace Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Mantic: Fix Released Bug description: ubuntu-server in Mantic pulls in zfs userspace packages and systemd services are automatically enabled, which means zfs kernel modules are automatically loaded at boot, for everybody. On Raspberry Pi, this results in +5MB of additional memory consumption which is not acceptable, especially not on 512MB devices. Culprit: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=36c17dbdbfd13f1b386aa86d065a8a9d34c48a35 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2037425/+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 2037569] Re: udev issues with mantic beta
Spent some time analyzing this. Frank loaned me a test system. The test system in the "idle" state is enough to see the issue, with a persistent load of 3+ when nothing is happening except event loop spin. The test system is using a dasd as the disk that it is running from. With some udev tracing, one can see an apparent loop, with udisks2 opening /dev/dasda, which triggers an inotify, which triggers udev rules, which trigger udisks2 again, or something similar to this flow. Workarounds include: * adding a nowatch rule 'ACTION=="add|change", KERNEL=="dasd*", OPTIONS:="nowatch"' * systemctl stop udisks2 I've begun exploring udev changes for udisks2 to ignore dasd. -- 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/2037569 Title: udev issues with mantic beta Status in Ubuntu on IBM z Systems: New Status in systemd package in Ubuntu: Confirmed Status in udisks2 package in Ubuntu: Confirmed Bug description: While installing mantic beta (on s390x, LPAR and z/VM - but this might not be architecture specific) I faced issues with udev. In my installation I've updated the installer to "edge/lp-2009141" (subiquity 22.02.2+git1762.1b1ee6f4 5164). During my installations I first noticed bad response times in case of dealing with devices (like enabling new devices with chzdev). chzdev is used during the installation, hence the installation procedure is also affected by this. (I mainly notice this issue in case of DASD ECKD disk enablements.) But even after after a successful (but due to this issue less snappier) installation, means after the post-install reboot, in the installed system I can find several udev related processes, like: 69448 root 20 0 31280 11944 2560 S 39.2 0.0 2:51.67 (udev-worker) 509 root 20 0 31276 13812 4600 S 20.6 0.0 2:07.76 systemd-udevd 893 root 20 0 469016 13544 10496 R 17.3 0.0 1:43.53 udisksd 1 root 20 0 168664 12748 8396 S 16.3 0.0 1:40.47 systemd which is not only unusual, but (as one can see) they consume quite some resources. Even the remote ssh into that system is impacted by this high load. So far I only see this in mantic. I tried 20.04.3 as well as lunar, but both do not seem to be affected by this udev problem. I neither face the bad response on device enablement, nor can see any udev related processes still running after post-install-reboot in the installed system. (Sometimes I could also see a growing log file 'syslog'). I cannot say yet what is causing this, but since I see 'systemd-udevd' as prominent process in top, I'll first of all mark this as affecting systemd-udevd (or systemd). I've attached the outcome of some more investigations I did ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+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 2037569] Re: udev issues with mantic beta
** Also affects: udisks2 (Ubuntu) Importance: Undecided Status: New ** Changed in: udisks2 (Ubuntu) Status: New => Confirmed -- 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/2037569 Title: udev issues with mantic beta Status in Ubuntu on IBM z Systems: New Status in systemd package in Ubuntu: Confirmed Status in udisks2 package in Ubuntu: Confirmed Bug description: While installing mantic beta (on s390x, LPAR and z/VM - but this might not be architecture specific) I faced issues with udev. In my installation I've updated the installer to "edge/lp-2009141" (subiquity 22.02.2+git1762.1b1ee6f4 5164). During my installations I first noticed bad response times in case of dealing with devices (like enabling new devices with chzdev). chzdev is used during the installation, hence the installation procedure is also affected by this. (I mainly notice this issue in case of DASD ECKD disk enablements.) But even after after a successful (but due to this issue less snappier) installation, means after the post-install reboot, in the installed system I can find several udev related processes, like: 69448 root 20 0 31280 11944 2560 S 39.2 0.0 2:51.67 (udev-worker) 509 root 20 0 31276 13812 4600 S 20.6 0.0 2:07.76 systemd-udevd 893 root 20 0 469016 13544 10496 R 17.3 0.0 1:43.53 udisksd 1 root 20 0 168664 12748 8396 S 16.3 0.0 1:40.47 systemd which is not only unusual, but (as one can see) they consume quite some resources. Even the remote ssh into that system is impacted by this high load. So far I only see this in mantic. I tried 20.04.3 as well as lunar, but both do not seem to be affected by this udev problem. I neither face the bad response on device enablement, nor can see any udev related processes still running after post-install-reboot in the installed system. (Sometimes I could also see a growing log file 'syslog'). I cannot say yet what is causing this, but since I see 'systemd-udevd' as prominent process in top, I'll first of all mark this as affecting systemd-udevd (or systemd). I've attached the outcome of some more investigations I did ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+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 2037569] Re: udev issues with mantic beta
** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/2037569 Title: udev issues with mantic beta Status in Ubuntu on IBM z Systems: New Status in systemd package in Ubuntu: Confirmed Bug description: While installing mantic beta (on s390x, LPAR and z/VM - but this might not be architecture specific) I faced issues with udev. In my installation I've updated the installer to "edge/lp-2009141" (subiquity 22.02.2+git1762.1b1ee6f4 5164). During my installations I first noticed bad response times in case of dealing with devices (like enabling new devices with chzdev). chzdev is used during the installation, hence the installation procedure is also affected by this. (I mainly notice this issue in case of DASD ECKD disk enablements.) But even after after a successful (but due to this issue less snappier) installation, means after the post-install reboot, in the installed system I can find several udev related processes, like: 69448 root 20 0 31280 11944 2560 S 39.2 0.0 2:51.67 (udev-worker) 509 root 20 0 31276 13812 4600 S 20.6 0.0 2:07.76 systemd-udevd 893 root 20 0 469016 13544 10496 R 17.3 0.0 1:43.53 udisksd 1 root 20 0 168664 12748 8396 S 16.3 0.0 1:40.47 systemd which is not only unusual, but (as one can see) they consume quite some resources. Even the remote ssh into that system is impacted by this high load. So far I only see this in mantic. I tried 20.04.3 as well as lunar, but both do not seem to be affected by this udev problem. I neither face the bad response on device enablement, nor can see any udev related processes still running after post-install-reboot in the installed system. (Sometimes I could also see a growing log file 'syslog'). I cannot say yet what is causing this, but since I see 'systemd-udevd' as prominent process in top, I'll first of all mark this as affecting systemd-udevd (or systemd). I've attached the outcome of some more investigations I did ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+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 2037425] Re: ubuntu-server pulls in ZFS userspace
** Merge proposal linked: https://code.launchpad.net/~dbungert/ubuntu-seeds/+git/ubuntu/+merge/452156 -- 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/2037425 Title: ubuntu-server pulls in ZFS userspace Status in ubuntu-meta package in Ubuntu: In Progress Status in ubuntu-meta source package in Mantic: In Progress Bug description: ubuntu-server in Mantic pulls in zfs userspace packages and systemd services are automatically enabled, which means zfs kernel modules are automatically loaded at boot, for everybody. On Raspberry Pi, this results in +5MB of additional memory consumption which is not acceptable, especially not on 512MB devices. Culprit: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=36c17dbdbfd13f1b386aa86d065a8a9d34c48a35 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2037425/+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 2037425] Re: ubuntu-server pulls in ZFS userspace
** Changed in: ubuntu-meta (Ubuntu Mantic) Status: New => In Progress ** Changed in: ubuntu-meta (Ubuntu Mantic) Assignee: (unassigned) => Dan Bungert (dbungert) -- 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/2037425 Title: ubuntu-server pulls in ZFS userspace Status in ubuntu-meta package in Ubuntu: In Progress Status in ubuntu-meta source package in Mantic: In Progress Bug description: ubuntu-server in Mantic pulls in zfs userspace packages and systemd services are automatically enabled, which means zfs kernel modules are automatically loaded at boot, for everybody. On Raspberry Pi, this results in +5MB of additional memory consumption which is not acceptable, especially not on 512MB devices. Culprit: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=36c17dbdbfd13f1b386aa86d065a8a9d34c48a35 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2037425/+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 2035061] Re: uptime -p reports incorrect output after 52 weeks
Hi Robert, thanks for the update to the description. I would like to see two things 1. (Like Paride, I don't have a SRU hat to wear) While this updated description elaborates on what has changed, it doesn't really go into the "what can go wrong" territory. This is an important field for SRU review as we want to consider how problems might manifest, if they are going to. In this case, we've got an upstream patch that has been around for a while. Have there been further upstream changes in this code area since? You can evaluate that to help establish some history. We're changing a calculation. The immediate calculation is improved, but what about similar ones? is `uptime -p` correct now for 51 weeks and 53? Similar things like that are good to consider. 2. It would be good to elaborate on the changelog, on what's going on. I think https://www.debian.org/doc/manuals/developers-reference/best- pkging-practices.html#writing-useful-changelog-entries is a good description of what sort of content is desired. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/2035061 Title: uptime -p reports incorrect output after 52 weeks Status in procps package in Ubuntu: New Status in procps source package in Focal: New Status in procps source package in Jammy: New Bug description: [IMPACT] uptime will provide incorrect data after 52 weeks. This is at least confusing for users utilizing this tool. Issue is already fixed in upstream https://gitlab.com/procps-ng/procps/-/commit/8827c6763f79f77a126968e200b0e402de7cb749. Latest procps releases already include this patch (procps 4.0.3 lunar/mantic) The fix is needed for following set of packages: procps | 2:3.3.17-6ubuntu2 | jammy procps | 2:3.3.16-1ubuntu2 | focal [TEST CASE] UPTIME="31528920 31528800"; mkfifo uptime_fifo; while true; do cat <<<$UPTIME > uptime_fifo; done & sudo mount -obind uptime_fifo /proc/uptime uptime -p Running above commands will result in incorrect uptime output. [REGRESSION POTENTIAL] The patch is already available in upstream, lunar/mantic releases already include is as well. Old behavior will inaccurately print uptime -p for 24h after 31449600 seconds (0 years, 0 weeks). With new patch during that time uptime -p will print "52 weeks". [OTHER] Bug upstream: https://gitlab.com/procps-ng/procps/-/issues/217 Following patch is needed for older releases: https://gitlab.com/procps-ng/procps/-/commit/8827c6763f79f77a126968e200b0e402de7cb749 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/2035061/+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 2034967] Re: cloud-init & cloud-guest-utils are installed on non-cloud installations
** Changed in: subiquity (Ubuntu) Status: New => Won't Fix -- 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/2034967 Title: cloud-init & cloud-guest-utils are installed on non-cloud installations Status in cloud-init package in Ubuntu: Invalid Status in cloud-utils package in Ubuntu: New Status in subiquity package in Ubuntu: Won't Fix Status in ubuntu-meta package in Ubuntu: New Bug description: ~$ apt-cache rdepends --installed cloud-init cloud-init Reverse Depends: cloud-guest-utils ~$ apt-cache rdepends --installed cloud-guest-utils cloud-guest-utils Reverse Depends: |cloud-init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2034967/+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 2026199] Re: Please merge 3.137 into mantic
Uploaded, thanks! ** Changed in: adduser (Ubuntu) Assignee: Mateus Rodrigues de Morais (mateus-morais) => Dan Bungert (dbungert) ** Changed in: adduser (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 adduser in Ubuntu. https://bugs.launchpad.net/bugs/2026199 Title: Please merge 3.137 into mantic Status in adduser package in Ubuntu: Fix Committed Bug description: The upstream version 3.137 should be merged into mantic. The current version is 3.134ubuntu1. * PPA for review: https://launchpad.net/~mateus-morais/+archive/ubuntu/adduser-merge-lp2026199 * Git rebase of Ubuntu delta available at: https://code.launchpad.net/~mateus-morais/ubuntu/+source/adduser/+git/adduser-devel/+ref/ubuntu/devel - To be pushed to ubuntu/devel at https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/adduser/+git/adduser Note: this is a tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/2026199/+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 2002043] Re: Python extension modules get built using wrong compiler flags with python2
** Merge proposal unlinked:
https://code.launchpad.net/~dbungert/ubuntu-sponsoring/+git/ubuntu-sponsoring/+merge/446529
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2002043
Title:
Python extension modules get built using wrong compiler flags with
python2
Status in python2.7 package in Ubuntu:
In Progress
Status in python2.7 source package in Bionic:
Won't Fix
Status in python2.7 source package in Focal:
In Progress
Status in python2.7 source package in Jammy:
In Progress
Status in python2.7 source package in Kinetic:
In Progress
Status in python2.7 source package in Lunar:
Won't Fix
Status in python2.7 source package in Mantic:
Won't Fix
Bug description:
Compiling a Python extension using Python2 (Python 2.7.18) is making
use of wrong compiler flags, hence dropping required optimizations
when required. This is happening only when python2 is installed from
Ubuntu's repositories. By default, Python's distutils module uses
compiler and linker flags used to compile Python itself to be used to
compile extensions.
Steps to reproduce:
1) On Ubuntu 20.04, install python2 using apt package manager.
2) After successful installation, verify the CFLAGS variable from sysconfig
module. On my machine, the output is
Python 2.7.18 (default, Jul 1 2022, 12:27:04)
[GCC 9.4.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_config_var('CFLAGS')
'-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-Wdate-time -D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security '
3) Build a test extension module using python2 and verify the compilation
flags.
python2 setup.py build_ext --inplace
Output from below command is not matching with our expected above CFLAGS.
aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time
-D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-I/usr/include/python2.7 -c testmodule.c -o
build/temp.linux-aarch64-2.7/testmodule.o
On further investigation, it looks like Ubuntu's specific patch applied on
libpython2.7-stdlib package is altering the original upstream implementation of
distutils/sysconfig.py code.
Package - https://packages.ubuntu.com/focal/libpython2.7-stdlib
Patch -
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
Below is the code block which is causing the issue, where the presence of
configure_cflags is modifying cflags. This code is result of ubuntu's patch and
doesn't come directly from upstream python implementation.
File - /usr/lib/python2.7/distutils/sysconfig.py
Part of code block:
elif configure_cflags:
cflags = ' '.join(str(x) for x in (basecflags, configure_cflags,
extra_cflags) if x)
ldshared = ldshared + ' ' + configure_cflags
I don't see problem on Python3 though we have extra code added from patch
there as well. Patch used on python3, is not modifying the cflags completely
and instead appending new flags to cflags.
On python3 (tested on Ubuntu 20.04)
File - /usr/lib/python3.8/distutils/sysconfig.py
Part of code block which doesn't alter cflags completely
elif configure_cflags:
cflags = cflags + ' ' + configure_cflags
ldshared = ldshared + ' ' + configure_cflags
Request to update the python2 patch to behave similar to what is been done on
python3.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/2002043/+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 2002043] Re: Python extension modules get built using wrong compiler flags with python2
** Merge proposal unlinked:
https://code.launchpad.net/~dbungert/ubuntu-sponsoring/+git/ubuntu-sponsoring/+merge/446529
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2002043
Title:
Python extension modules get built using wrong compiler flags with
python2
Status in python2.7 package in Ubuntu:
In Progress
Status in python2.7 source package in Bionic:
Won't Fix
Status in python2.7 source package in Focal:
In Progress
Status in python2.7 source package in Jammy:
In Progress
Status in python2.7 source package in Kinetic:
In Progress
Status in python2.7 source package in Lunar:
Won't Fix
Status in python2.7 source package in Mantic:
Won't Fix
Bug description:
Compiling a Python extension using Python2 (Python 2.7.18) is making
use of wrong compiler flags, hence dropping required optimizations
when required. This is happening only when python2 is installed from
Ubuntu's repositories. By default, Python's distutils module uses
compiler and linker flags used to compile Python itself to be used to
compile extensions.
Steps to reproduce:
1) On Ubuntu 20.04, install python2 using apt package manager.
2) After successful installation, verify the CFLAGS variable from sysconfig
module. On my machine, the output is
Python 2.7.18 (default, Jul 1 2022, 12:27:04)
[GCC 9.4.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_config_var('CFLAGS')
'-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-Wdate-time -D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security '
3) Build a test extension module using python2 and verify the compilation
flags.
python2 setup.py build_ext --inplace
Output from below command is not matching with our expected above CFLAGS.
aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time
-D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-I/usr/include/python2.7 -c testmodule.c -o
build/temp.linux-aarch64-2.7/testmodule.o
On further investigation, it looks like Ubuntu's specific patch applied on
libpython2.7-stdlib package is altering the original upstream implementation of
distutils/sysconfig.py code.
Package - https://packages.ubuntu.com/focal/libpython2.7-stdlib
Patch -
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
Below is the code block which is causing the issue, where the presence of
configure_cflags is modifying cflags. This code is result of ubuntu's patch and
doesn't come directly from upstream python implementation.
File - /usr/lib/python2.7/distutils/sysconfig.py
Part of code block:
elif configure_cflags:
cflags = ' '.join(str(x) for x in (basecflags, configure_cflags,
extra_cflags) if x)
ldshared = ldshared + ' ' + configure_cflags
I don't see problem on Python3 though we have extra code added from patch
there as well. Patch used on python3, is not modifying the cflags completely
and instead appending new flags to cflags.
On python3 (tested on Ubuntu 20.04)
File - /usr/lib/python3.8/distutils/sysconfig.py
Part of code block which doesn't alter cflags completely
elif configure_cflags:
cflags = cflags + ' ' + configure_cflags
ldshared = ldshared + ' ' + configure_cflags
Request to update the python2 patch to behave similar to what is been done on
python3.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/2002043/+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 2026292] Re: conflict on syslog.service when moving between rsyslog and busybox-syslogd
** Changed in: busybox (Ubuntu) Status: New => Won't Fix ** Changed in: rsyslog (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/2026292 Title: conflict on syslog.service when moving between rsyslog and busybox- syslogd Status in busybox package in Ubuntu: Won't Fix Status in rsyslog package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: New Bug description: Suppose a system with systemd 252 and rsyslog installed. Install busybox-syslogd version 1:1.36.1-3ubuntu1, which will cause rsyslog to be removed (but not purged). The install of busybox-syslogd will fail as follows: Failed to preset unit, file "/etc/systemd/system/syslog.service" already exists and is a symlink to "/lib/systemd/system/rsyslog.service". The failure can also be seen in the reverse direction - busybox- syslogd 1:1.36.1-3ubuntu1 installed, then install rsyslog. With systemd 253, we instead see: Removed "/etc/systemd/system/syslog.service". Workarounds: * use systemd 253 when available * purge the existing system-log-daemon before installing the new one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2026292/+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 2026292] Re: conflict on syslog.service when moving between rsyslog and busybox-syslogd
** Attachment added: "syslog-service-conflict" https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2026292/+attachment/5684334/+files/syslog-service-conflict -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/2026292 Title: conflict on syslog.service when moving between rsyslog and busybox- syslogd Status in busybox package in Ubuntu: New Status in rsyslog package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Suppose a system with systemd 252 and rsyslog installed. Install busybox-syslogd version 1:1.36.1-3ubuntu1, which will cause rsyslog to be removed (but not purged). The install of busybox-syslogd will fail as follows: Failed to preset unit, file "/etc/systemd/system/syslog.service" already exists and is a symlink to "/lib/systemd/system/rsyslog.service". The failure can also be seen in the reverse direction - busybox- syslogd 1:1.36.1-3ubuntu1 installed, then install rsyslog. With systemd 253, we instead see: Removed "/etc/systemd/system/syslog.service". Workarounds: * use systemd 253 when available * purge the existing system-log-daemon before installing the new one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2026292/+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 2026292] Re: conflict on syslog.service when moving between rsyslog and busybox-syslogd
This script is a reproducer, assuming it installs the affected busybox- syslogd. Debian sid (systemd 253) passes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/2026292 Title: conflict on syslog.service when moving between rsyslog and busybox- syslogd Status in busybox package in Ubuntu: New Status in rsyslog package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Suppose a system with systemd 252 and rsyslog installed. Install busybox-syslogd version 1:1.36.1-3ubuntu1, which will cause rsyslog to be removed (but not purged). The install of busybox-syslogd will fail as follows: Failed to preset unit, file "/etc/systemd/system/syslog.service" already exists and is a symlink to "/lib/systemd/system/rsyslog.service". The failure can also be seen in the reverse direction - busybox- syslogd 1:1.36.1-3ubuntu1 installed, then install rsyslog. With systemd 253, we instead see: Removed "/etc/systemd/system/syslog.service". Workarounds: * use systemd 253 when available * purge the existing system-log-daemon before installing the new one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2026292/+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 2026292] [NEW] conflict on syslog.service when moving between rsyslog and busybox-syslogd
Public bug reported: Suppose a system with systemd 252 and rsyslog installed. Install busybox-syslogd version 1:1.36.1-3ubuntu1, which will cause rsyslog to be removed (but not purged). The install of busybox-syslogd will fail as follows: Failed to preset unit, file "/etc/systemd/system/syslog.service" already exists and is a symlink to "/lib/systemd/system/rsyslog.service". The failure can also be seen in the reverse direction - busybox-syslogd 1:1.36.1-3ubuntu1 installed, then install rsyslog. With systemd 253, we instead see: Removed "/etc/systemd/system/syslog.service". Workarounds: * use systemd 253 when available * purge the existing system-log-daemon before installing the new one ** Affects: busybox (Ubuntu) Importance: Undecided Status: New ** Affects: rsyslog (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: rsyslog (Ubuntu) Importance: Undecided Status: New ** Also affects: busybox (Ubuntu) Importance: Undecided Status: New -- 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/2026292 Title: conflict on syslog.service when moving between rsyslog and busybox- syslogd Status in busybox package in Ubuntu: New Status in rsyslog package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Suppose a system with systemd 252 and rsyslog installed. Install busybox-syslogd version 1:1.36.1-3ubuntu1, which will cause rsyslog to be removed (but not purged). The install of busybox-syslogd will fail as follows: Failed to preset unit, file "/etc/systemd/system/syslog.service" already exists and is a symlink to "/lib/systemd/system/rsyslog.service". The failure can also be seen in the reverse direction - busybox- syslogd 1:1.36.1-3ubuntu1 installed, then install rsyslog. With systemd 253, we instead see: Removed "/etc/systemd/system/syslog.service". Workarounds: * use systemd 253 when available * purge the existing system-log-daemon before installing the new one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2026292/+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 2008952] Re: DNS failure while trying to fetch user-data
** Changed in: subiquity 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/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: Fix Released Status in netplan: Invalid Status in subiquity: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+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 2019856] Re: Add missing ARM-cores to support Grace-based systems
Uploaded for Mantic, thanks! ** Changed in: util-linux (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2019856 Title: Add missing ARM-cores to support Grace-based systems Status in util-linux package in Ubuntu: Fix Committed Status in util-linux source package in Jammy: In Progress Status in util-linux source package in Kinetic: Won't Fix Status in util-linux source package in Lunar: In Progress Status in util-linux source package in Mantic: Fix Committed Bug description: [Impact] When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't report a model name: Vendor ID: ARM Model: 0 [Fix] Adding the additional arm_part to sys-utils/lscpu-arm.c solves the problem. The commit below adds the specific codes missing from Jammy's version. https://github.com/util-linux/util- linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740 [Test Steps] * Verify whether output of lscpu is correct on new CPUs; eg: Vendor ID: ARM Model name: Neoverse-V2 * Verify whether output of lscpu doesn't change on old CPUs; eg: Vendor ID: ARM Model name: Neoverse-N1 [What Could Go Wrong] The fix only introduces additional model identifiers to match against and print a model name string, thus regression impact should be contained within lscpu and printing cpus model name on ARM systems. Output doesn't change on systems with non-affected CPU models. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+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 2019856] Re: Add missing ARM-cores to support Grace-based systems
** Changed in: util-linux (Ubuntu Mantic) Assignee: Mauricio Faria de Oliveira (mfo) => Dan Bungert (dbungert) ** Changed in: util-linux (Ubuntu Mantic) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2019856 Title: Add missing ARM-cores to support Grace-based systems Status in util-linux package in Ubuntu: In Progress Status in util-linux source package in Jammy: In Progress Status in util-linux source package in Kinetic: Won't Fix Status in util-linux source package in Lunar: In Progress Status in util-linux source package in Mantic: In Progress Bug description: [Impact] When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't report a model name: Vendor ID: ARM Model: 0 [Fix] Adding the additional arm_part to sys-utils/lscpu-arm.c solves the problem. The commit below adds the specific codes missing from Jammy's version. https://github.com/util-linux/util- linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740 [Test Steps] * Verify whether output of lscpu is correct on new CPUs; eg: Vendor ID: ARM Model name: Neoverse-V2 * Verify whether output of lscpu doesn't change on old CPUs; eg: Vendor ID: ARM Model name: Neoverse-N1 [What Could Go Wrong] The fix only introduces additional model identifiers to match against and print a model name string, thus regression impact should be contained within lscpu and printing cpus model name on ARM systems. Output doesn't change on systems with non-affected CPU models. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+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 2008952] Re: DNS failure while trying to fetch user-data
What a mess! I have uploaded the livecd-rootfs change proposed by Chad in #26. Note that there is another problem around jsonschema exposed by this that is in progress. ** Also affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu) Status: New => 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/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: In Progress Status in netplan: Invalid Status in subiquity: New Status in livecd-rootfs package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+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 2011751] Re: openbox crashed with SIGABRT
Thanks, uploaded! ** Changed in: openbox (Ubuntu) Status: Confirmed => Fix Committed -- 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/2011751 Title: openbox crashed with SIGABRT Status in glib2.0 package in Ubuntu: Invalid Status in openbox package in Ubuntu: Fix Committed Bug description: Lubuntu lunar (primary box) on - dell [optiplex] 7050 (i5-6500, 16gb, intel hd530/i915) I experienced a crash yesterday (openbox) but tend to ignore the first crashes... Whilst using the machine again today a crash occurred. This is my primary box, so my setup is pretty consistent - featherpad (restored session) - hexchat (irc) - qterminal (only single tab today; usually many) - firefox (snap, most sites excluding google related) - chromium (snap, used for anything google related) - telegram (snap) - element I was using chromium full screen (trying to read my gmail inbox) when borders around windows disappeared & I lost the capacity to switch between windows; mouse would move, but keyboard appeared mostly dead (it wasn't, more I think windows weren't responding, inc. clicks with mouse though that's likely inconsistent; I could [not] work out how to describe it yesterday, but todays is almost identical). I switched to text terminal (ctrl+alt+f4) & explored; returned to GUI and used - ctrl+alt+t to open new terminal - openbox & session returned to what I expect... ** expected outcome Openbox doesn't crash ** actual outcome all windows lost borders, and i lost ability to switch between windows I appeared to have minimal control (not true, more a fraction of what I expect) ** How to get crash For me, - I used chromium (browser) - make chromium full screen (ie. F11) - click on link/something & right-click to open in new window OPENBOX CRASH. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: openbox 3.6.1-10 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: LXQt Date: Thu Mar 16 09:46:22 2023 ExecutablePath: /usr/bin/openbox ExecutableTimestamp: 1643543619 InstallationDate: Installed on 2023-01-25 (49 days ago) InstallationMedia: Lubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230124) JournalErrors: -- No entries -- ProcCmdline: /usr/bin/openbox ProcCwd: /home/guiverc RebootRequiredPkgs: Error: path contained symlinks. Signal: 6 SourcePackage: openbox StacktraceTop: () at /lib/x86_64-linux-gnu/libobt.so.2 () at /lib/x86_64-linux-gnu/libc.so.6 client_calc_layer () () () at /lib/x86_64-linux-gnu/libobt.so.2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+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 2011751] Re: openbox crashed with SIGABRT
Thanks for the patch, Aaron. I'm able to reproduce this bug using the firefox f11 -> open link in new window, when using the live session of the daily-live lubuntu iso. And the attached patch does seem to help. Overall the patch is what I was hoping to see, but I will request some changes. * The Maintainer field currently reads "Maintainer: Lubuntu Developers". I'd like you to go with the more conventional "Ubuntu Developers" attribution. `seeded-in-ubuntu` says that openbox is also used in Ubuntu Mate, and of course people can use openbox otherwise. The `update-maintainer` script is a convenient way to set this field to the value I'm suggesting (when starting from the original value). * There is a sponsorship process listed on the wiki, I think https://wiki.ubuntu.com/MOTU/Sponsorship/SponsorsQueue is a good summary. This can also help, in the future, find someone to take a look at the patch as doing so means your work show up in the queue. http://reports.qa.ubuntu.com/reports/sponsoring/ Since I'm already looking at this I won't demand the SponsorsQueue bug changes but please keep that in mind for the next one. * I forget where I saw it but I like the convention that the patch has a change number, like it looks like you're on v4 of the patch. So it might have been called glib_crash_bugfix-v4.patch or something. A nice convention for when these keep changing. * One item also mentioned on the wiki is forwarding this patch to Debian. It is likely that the same problem applies there. https://wiki.ubuntu.com/Debian/Bugs talks about this in detail. I will ask that you do this before upload. For this particular bug I'd feel comfortable sharing the patch with Debian without reproducing on Debian, since it's already known to be happening elsewhere. Just say so when forwarding. * A tweak to the changelog would be nice. It isn't necessary to note the update to the maintainer field, that will be the case for most if not all packages with an Ubuntu delta. Also, the first segment about the patch is in my opinion too developer focused. I'd probably start with "Cherry-pick patch from A for crash issue when B + C happens", fill in appropriate details you think might be interesting for someone who might not look at the code. So Maintainer + Debian + Changelog tweaks and I will be happy to upload. -- 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/2011751 Title: openbox crashed with SIGABRT Status in glib2.0 package in Ubuntu: Invalid Status in openbox package in Ubuntu: Confirmed Bug description: Lubuntu lunar (primary box) on - dell [optiplex] 7050 (i5-6500, 16gb, intel hd530/i915) I experienced a crash yesterday (openbox) but tend to ignore the first crashes... Whilst using the machine again today a crash occurred. This is my primary box, so my setup is pretty consistent - featherpad (restored session) - hexchat (irc) - qterminal (only single tab today; usually many) - firefox (snap, most sites excluding google related) - chromium (snap, used for anything google related) - telegram (snap) - element I was using chromium full screen (trying to read my gmail inbox) when borders around windows disappeared & I lost the capacity to switch between windows; mouse would move, but keyboard appeared mostly dead (it wasn't, more I think windows weren't responding, inc. clicks with mouse though that's likely inconsistent; I could [not] work out how to describe it yesterday, but todays is almost identical). I switched to text terminal (ctrl+alt+f4) & explored; returned to GUI and used - ctrl+alt+t to open new terminal - openbox & session returned to what I expect... ** expected outcome Openbox doesn't crash ** actual outcome all windows lost borders, and i lost ability to switch between windows I appeared to have minimal control (not true, more a fraction of what I expect) ** How to get crash For me, - I used chromium (browser) - make chromium full screen (ie. F11) - click on link/something & right-click to open in new window OPENBOX CRASH. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: openbox 3.6.1-10 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: LXQt Date: Thu Mar 16 09:46:22 2023 ExecutablePath: /usr/bin/openbox ExecutableTimestamp: 1643543619 InstallationDate: Installed on 2023-01-25 (49 days ago) InstallationMedia: Lubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230124) JournalErrors: -- No entries -- ProcCmdline: /usr/bin/openbox ProcCwd: /home/guiverc RebootRequiredPkgs: Error: path contained symlinks. Signal: 6 SourcePackage: openbox StacktraceTo
[Touch-packages] [Bug 2011751] Re: openbox crashed with SIGABRT
Partial review of the patch so far. I haven't read much openbox code so take this with a grain of salt. https://bugzilla.icculus.org/show_bug.cgi?id=6669#c9 mentions a concern that itPrev may still be pointing to invalid data. I share this concern. I think some interesting testcases are what happens with lists that have one or two elements, which then are modified by this function. In the single element case, I believe your itPrev now points to the deleted item, and in the two element case, itPrev may be ok but itPrev->prev or itPrev->next are both probably not valid. https://bugzilla.icculus.org/show_bug.cgi?id=6669#c5 mentions a work branch. I suggest tracking that down and considering it. It's presumably this patch https://bugzilla.icculus.org/attachment.cgi?id=3646&action=diff. -- 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/2011751 Title: openbox crashed with SIGABRT Status in glib2.0 package in Ubuntu: Invalid Status in openbox package in Ubuntu: Confirmed Bug description: Lubuntu lunar (primary box) on - dell [optiplex] 7050 (i5-6500, 16gb, intel hd530/i915) I experienced a crash yesterday (openbox) but tend to ignore the first crashes... Whilst using the machine again today a crash occurred. This is my primary box, so my setup is pretty consistent - featherpad (restored session) - hexchat (irc) - qterminal (only single tab today; usually many) - firefox (snap, most sites excluding google related) - chromium (snap, used for anything google related) - telegram (snap) - element I was using chromium full screen (trying to read my gmail inbox) when borders around windows disappeared & I lost the capacity to switch between windows; mouse would move, but keyboard appeared mostly dead (it wasn't, more I think windows weren't responding, inc. clicks with mouse though that's likely inconsistent; I could work out how to describe it yesterday, but todays is almost identical). I switched to text terminal (ctrl+alt+f4) & explored; returned to GUI and used - ctrl+alt+t to open new terminal - openbox & session returned to what I expect... ** expected outcome Openbox doesn't crash ** actual outcome all windows lost borders, and i lost ability to switch between windows I appeared to have minimal control (not true, more a fraction of what I expect) ** How to get crash For me, - I used chromium (browser) - make chromium full screen (ie. F11) - click on something & right-click to open in new window OPENBOX CRASH. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: openbox 3.6.1-10 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: LXQt Date: Thu Mar 16 09:46:22 2023 ExecutablePath: /usr/bin/openbox ExecutableTimestamp: 1643543619 InstallationDate: Installed on 2023-01-25 (49 days ago) InstallationMedia: Lubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230124) JournalErrors: -- No entries -- ProcCmdline: /usr/bin/openbox ProcCwd: /home/guiverc RebootRequiredPkgs: Error: path contained symlinks. Signal: 6 SourcePackage: openbox StacktraceTop: () at /lib/x86_64-linux-gnu/libobt.so.2 () at /lib/x86_64-linux-gnu/libc.so.6 client_calc_layer () () () at /lib/x86_64-linux-gnu/libobt.so.2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+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 1956102] Re: Time for the US is shown in 24h format. It should be 12h with AM/PM
Curtin is not the appropriate place to land fixes or even quirk workarounds for this problem. I would appreciate if you avoided adding uninvolved components to the bug, especially when it has already been pointed out that this is the wrong spot. The linked threads you mention do not appear to me to have an "all but refused" stance. Last I see they are sitting in a "volunteers welcome" state, or dependencies on things that need further work. This sort of change is really best done in a package in the archive, and I'm not hearing appropriate justification for installer quirks. Declining for Subiquity, thanks. ** Changed in: subiquity (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1956102 Title: Time for the US is shown in 24h format. It should be 12h with AM/PM Status in GSettings Desktop Schemas: New Status in curtin package in Ubuntu: Invalid Status in gsettings-desktop-schemas package in Ubuntu: Confirmed Status in subiquity package in Ubuntu: Won't Fix Bug description: Source- https://time.gov/ To manage notifications about this bug go to: https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1956102/+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 1956102] Re: Time for the US is shown in 24h format. It should be 12h with AM/PM
** Changed in: curtin (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1956102 Title: Time for the US is shown in 24h format. It should be 12h with AM/PM Status in GSettings Desktop Schemas: New Status in curtin package in Ubuntu: Invalid Status in gsettings-desktop-schemas package in Ubuntu: Confirmed Status in subiquity package in Ubuntu: Incomplete Bug description: Source- https://time.gov/ To manage notifications about this bug go to: https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1956102/+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 1956102] Re: Time for the US is shown in 24h format. It should be 12h with AM/PM
Curtin (no "a") doesn't manage time settings, so the fix definitely isn't going there. Comment #4 though makes this sound like it needs to be in the image, and isn't installer specific? Or can you clarify what you'd like the installer to do here? ** Changed in: curtain (Ubuntu) Status: New => Invalid ** Changed in: subiquity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1956102 Title: Time for the US is shown in 24h format. It should be 12h with AM/PM Status in GSettings Desktop Schemas: New Status in curtain package in Ubuntu: Invalid Status in gsettings-desktop-schemas package in Ubuntu: Confirmed Status in subiquity package in Ubuntu: Incomplete Bug description: Source- https://time.gov/ To manage notifications about this bug go to: https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1956102/+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 2008952] Re: DNS failure while trying to fetch user-data
I played with a two variation of dropping in some after directives, but obtained similar failing results where the network state was not what cloud-init wanted at the time it started. @Chad - what's your thoughts on some service reordering? -- 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/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: Triaged Status in netplan: Invalid Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+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 2008952] Re: DNS failure while trying to fetch user-data
> So I wonder what is the exact sequence of events for running the Netplan generator (by systemd), installing the 50-cloud-init.yaml file (by cloud-init), installing the 01-network-manager-all.yaml file (by the installer?), executing `netplan apply` (by cloud-init). By the time Subiquity has started, the bad interaction has already taken place. In this nocloud case, cloud-init should have been able to retrieve the user-data and other things, that failed. So at Subiquity start time, we ask for the autoinstall and get an empty answer. An empty answer is quite common - that is what happens in a normal interactive install - so it's not immediately obvious that a misbehavior has taken place. -- 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/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: Triaged Status in netplan: New Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+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 2008952] Re: DNS failure while trying to fetch user-data
So while this bug talks about netboot, I think it isn't necessary to involve that for testing purposes. I suggest simply booting the desktop daily-live with the nocloud kernel command line listed above and seeing how things go. Are the various network tools doing what we expect? Note that gnome-boxes is a convenient tool for running this ISO in a VM, it seems to have a better video driver than what kvm would suggest by default. It's still possible to give it kernel command line with config like: /srv/iso/lunar/vmlinuz /srv/iso/lunar/initrd autoinstall layerfs-path=minimal.standard.live.squashfs ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/ -- 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/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: Triaged Status in netplan: New Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+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 2008952] Re: DNS failure while trying to fetch user-data
** Tags added: rls-ll-incoming -- 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/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: Triaged Status in netplan: New Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+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 2008952] Re: DNS failure while trying to fetch user-data
Looking at the desktop ISOs, while the system is configured with Netplan to use NetworkManager, there seems to be some conflict here where systemd-networkd is trying to interact with the device. Some feedback would be appreciated. The practical result is that early boot cloud- init is not able to fetch data that it should be able to retrieve. ** Also affects: netplan Importance: Undecided Status: New ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: Triaged Status in netplan: New Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+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 2009034] Re: Ubuntu 23.04 Canary subiquity crashed install failed
** Also affects: subiquity (Ubuntu) Importance: Undecided Status: New ** Changed in: openssh (Ubuntu) Status: New => Invalid ** Summary changed: - Ubuntu 23.04 Canary subiquity crashed install failed + subiquity subcommand crash on apt hash mismatch ** Changed in: subiquity (Ubuntu) Status: New => Triaged ** Changed in: subiquity (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2009034 Title: subiquity subcommand crash on apt hash mismatch Status in openssh package in Ubuntu: Invalid Status in subiquity package in Ubuntu: Triaged Bug description: QA Testing daily build 20230302 install failed. Mar 02 06:24:14 ubuntu subiquity_log.3098[12985]: Running command ['mount', '--make-private', '/target/dev'] with allowed return codes [0] (capture=False) Mar 02 06:24:14 ubuntu subiquity_log.3098[12985]: Running command ['umount', '/target/dev'] with allowed return codes [0] (capture=False) Mar 02 06:24:14 ubuntu subiquity_log.3098[12985]: finish: cmd-in-target: FAIL: curtin command in-target ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: openssh-client 1:9.0p1-1ubuntu8 Uname: Linux 5.19.0-21-generic x86_64 Architecture: amd64 Date: Thu Mar 2 12:13:28 2023 ExecutablePath: /usr/bin/ssh-keygen ExecutableTimestamp: 1666713463 ProcCmdline: ssh-keygen -t rsa -b 4096 -N -f /tmp/snapd3272526883/rsa.key -m PEM ProcCwd: / ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) Signal: 7 SourcePackage: openssh UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2009034/+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 2004092] Re: casper fails to add any users because GID 999 is already taken
>> the next casper upload will regress the current version of the fix > What is the rationale for reverting this change? As of yet I think that has't happened. Right now we have 2 caspers * git casper at https://git.launchpad.net/casper, version 1.478, without this proposed fix since the MP was rejected * archive casper, version 1.480, which per https://launchpadlibrarian.net/649860924/casper_1.479_1.480.diff.gz does seem to still have this change I'm only trying to point out that the next time someone uploads directly from what is in "git casper", it will drop this change, so we need a long-term fix. -- 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/2004092 Title: casper fails to add any users because GID 999 is already taken Status in casper package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Status in systemd package in Debian: Unknown Bug description: This bug is due to the latest systemd upload in Ubuntu. systemd- journald now uses GID 999, when casper explicitly sets the live user to that UID and GID. Rather than going through the painstaking task of updating systemd to use a *different* user, let's just update casper to use 1000, which is the first dynamically-allocated user account per Debian Policy[1]. [1] https://www.debian.org/doc/debian-policy/ch-opersys.html#uid-and- gid-classes [ Original Report ] Normally, when one first boots a live ISO, a desktop automatically appears, asking users if they want to try or install Ubuntu (or, in the case of Lubuntu, they are simply dropped into a working desktop with an installation desktop icon available). As of the Lubuntu ISO on January 27, 2023, this has stopped occuring. Plymouth shows the initial boot animation, but the user is then dropped to a solid black screen. No user input is accepted. Attempting to switch to a TTY and sign in fails with the default "lubuntu" username and a blank password (the error "Login incorrect" is displayed). On Ubuntu Desktop, the behavior is even stranger. Rather than being shown a "Try or Install Ubuntu" screen, an initial system setup wizard appears that takes the user through the process of creating a user account. On a live ISO. Only after this wizard is finished does the "Try or Install Ubuntu" screen appear. Attempting to log into a TTY using the default "ubuntu" username and a blank password fails the same way as Lubuntu does, if done before the wizard is finished. However, one can log into a TTY if they finish the wizard and then attempt to log into the TTY using the credentials provided during user account setup. This issue affects at least the Lubuntu ISOs as of January 27, 2023, and the Ubuntu Desktop ISO at least as of January 28, 2023 (it is assumed that the 27th ISO for Ubuntu Desktop is also broken). The ISO from the 26th is most likely unaffected as there is successful testing information for Lubuntu on the 26th, so something likely happened between the 26th and the 27th to cause this breakage. Steps to reproduce: 1. Download the latest Lunar daily ISO of Ubuntu Desktop or Lubuntu. 2. Boot the ISO (hardware is irrelevant - this appears to occur on both physical and virtual hardware). For Lubuntu: 3. Wait until you are dropped to a black, blank screen. 4. Wait a while, then attempt to switch to a TTY and attempt to log in using "lubuntu" as the username and a blank password. The login attempt will be denied. For Ubuntu Desktop: 3. Wait until you are provided with an initial system setup wizard. 4. Switch to a TTY and attempt to log in using "ubuntu" as the username and a blank password. The login attempt will be denied. 5. Switch back to the system setup wizard, and complete it. 6. After completing the wizard, switch to a TTY again and attempt to log in using the credentials provided to the wizard. The login attempt will be successful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/2004092/+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 2004092] Re: casper fails to add any users because GID 999 is already taken
Tagged incoming as while there is a modified casper uploaded, the matching merge proposal was disapproved (https://code.launchpad.net/~tsimonq2/casper/+git/casper/+merge/436490), so the next casper upload will regress the current version of the fix. A longer term solution is needed. ** Tags added: rls-ll-incoming -- 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/2004092 Title: casper fails to add any users because GID 999 is already taken Status in casper package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Status in systemd package in Debian: Unknown Bug description: This bug is due to the latest systemd upload in Ubuntu. systemd- journald now uses GID 999, when casper explicitly sets the live user to that UID and GID. Rather than going through the painstaking task of updating systemd to use a *different* user, let's just update casper to use 1000, which is the first dynamically-allocated user account per Debian Policy[1]. [1] https://www.debian.org/doc/debian-policy/ch-opersys.html#uid-and- gid-classes [ Original Report ] Normally, when one first boots a live ISO, a desktop automatically appears, asking users if they want to try or install Ubuntu (or, in the case of Lubuntu, they are simply dropped into a working desktop with an installation desktop icon available). As of the Lubuntu ISO on January 27, 2023, this has stopped occuring. Plymouth shows the initial boot animation, but the user is then dropped to a solid black screen. No user input is accepted. Attempting to switch to a TTY and sign in fails with the default "lubuntu" username and a blank password (the error "Login incorrect" is displayed). On Ubuntu Desktop, the behavior is even stranger. Rather than being shown a "Try or Install Ubuntu" screen, an initial system setup wizard appears that takes the user through the process of creating a user account. On a live ISO. Only after this wizard is finished does the "Try or Install Ubuntu" screen appear. Attempting to log into a TTY using the default "ubuntu" username and a blank password fails the same way as Lubuntu does, if done before the wizard is finished. However, one can log into a TTY if they finish the wizard and then attempt to log into the TTY using the credentials provided during user account setup. This issue affects at least the Lubuntu ISOs as of January 27, 2023, and the Ubuntu Desktop ISO at least as of January 28, 2023 (it is assumed that the 27th ISO for Ubuntu Desktop is also broken). The ISO from the 26th is most likely unaffected as there is successful testing information for Lubuntu on the 26th, so something likely happened between the 26th and the 27th to cause this breakage. Steps to reproduce: 1. Download the latest Lunar daily ISO of Ubuntu Desktop or Lubuntu. 2. Boot the ISO (hardware is irrelevant - this appears to occur on both physical and virtual hardware). For Lubuntu: 3. Wait until you are dropped to a black, blank screen. 4. Wait a while, then attempt to switch to a TTY and attempt to log in using "lubuntu" as the username and a blank password. The login attempt will be denied. For Ubuntu Desktop: 3. Wait until you are provided with an initial system setup wizard. 4. Switch to a TTY and attempt to log in using "ubuntu" as the username and a blank password. The login attempt will be denied. 5. Switch back to the system setup wizard, and complete it. 6. After completing the wizard, switch to a TTY again and attempt to log in using the credentials provided to the wizard. The login attempt will be successful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/2004092/+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 2004092] Re: casper fails to add any users because GID 999 is already taken
** Merge proposal linked: https://code.launchpad.net/~tsimonq2/casper/+git/casper/+merge/436490 -- 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/2004092 Title: casper fails to add any users because GID 999 is already taken Status in casper package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Status in systemd package in Debian: Unknown Bug description: This bug is due to the latest systemd upload in Ubuntu. systemd- journald now uses GID 999, when casper explicitly sets the live user to that UID and GID. Rather than going through the painstaking task of updating systemd to use a *different* user, let's just update casper to use 1000, which is the first dynamically-allocated user account per Debian Policy[1]. [1] https://www.debian.org/doc/debian-policy/ch-opersys.html#uid-and- gid-classes [ Original Report ] Normally, when one first boots a live ISO, a desktop automatically appears, asking users if they want to try or install Ubuntu (or, in the case of Lubuntu, they are simply dropped into a working desktop with an installation desktop icon available). As of the Lubuntu ISO on January 27, 2023, this has stopped occuring. Plymouth shows the initial boot animation, but the user is then dropped to a solid black screen. No user input is accepted. Attempting to switch to a TTY and sign in fails with the default "lubuntu" username and a blank password (the error "Login incorrect" is displayed). On Ubuntu Desktop, the behavior is even stranger. Rather than being shown a "Try or Install Ubuntu" screen, an initial system setup wizard appears that takes the user through the process of creating a user account. On a live ISO. Only after this wizard is finished does the "Try or Install Ubuntu" screen appear. Attempting to log into a TTY using the default "ubuntu" username and a blank password fails the same way as Lubuntu does, if done before the wizard is finished. However, one can log into a TTY if they finish the wizard and then attempt to log into the TTY using the credentials provided during user account setup. This issue affects at least the Lubuntu ISOs as of January 27, 2023, and the Ubuntu Desktop ISO at least as of January 28, 2023 (it is assumed that the 27th ISO for Ubuntu Desktop is also broken). The ISO from the 26th is most likely unaffected as there is successful testing information for Lubuntu on the 26th, so something likely happened between the 26th and the 27th to cause this breakage. Steps to reproduce: 1. Download the latest Lunar daily ISO of Ubuntu Desktop or Lubuntu. 2. Boot the ISO (hardware is irrelevant - this appears to occur on both physical and virtual hardware). For Lubuntu: 3. Wait until you are dropped to a black, blank screen. 4. Wait a while, then attempt to switch to a TTY and attempt to log in using "lubuntu" as the username and a blank password. The login attempt will be denied. For Ubuntu Desktop: 3. Wait until you are provided with an initial system setup wizard. 4. Switch to a TTY and attempt to log in using "ubuntu" as the username and a blank password. The login attempt will be denied. 5. Switch back to the system setup wizard, and complete it. 6. After completing the wizard, switch to a TTY again and attempt to log in using the credentials provided to the wizard. The login attempt will be successful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/2004092/+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 2002789] Re: Missing 50-ubuntu-logging in sysvinit-utils 3.05-7ubuntu1
I have sponsored this upload. ** Changed in: sysvinit (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 sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/2002789 Title: Missing 50-ubuntu-logging in sysvinit-utils 3.05-7ubuntu1 Status in sysvinit package in Ubuntu: Fix Committed Status in sysvinit package in Debian: New Bug description: The following file used to be provided by the lsb-base package in Ubuntu and it now supposed to be provided by the sysvinit-utils package. * lsb/init-functions.d/50-ubuntu-logging The file is Ubuntu specific but is not included in Ubuntu using a delta from Debian. Instead, the debian source tree includes the file but conditional statements in debian/rules makes it absent from the binary packages in Debian. Sadly, when moving the file from src:lsb to src:sysvinit, the conditional statements are not consistent anymore, resulting in the file being absent from the Ubuntu binary package as well. Affected version: sysvinit-utils 3.05-7ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/2002789/+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 2002789] Re: Missing 50-ubuntu-logging in sysvinit-utils 3.05-7ubuntu1
** Changed in: sysvinit (Ubuntu) Assignee: (unassigned) => Dan Bungert (dbungert) ** Changed in: sysvinit (Ubuntu) Status: New => In Progress ** Changed in: sysvinit (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/2002789 Title: Missing 50-ubuntu-logging in sysvinit-utils 3.05-7ubuntu1 Status in sysvinit package in Ubuntu: In Progress Status in sysvinit package in Debian: New Bug description: The following file used to be provided by the lsb-base package in Ubuntu and it now supposed to be provided by the sysvinit-utils package. * lsb/init-functions.d/50-ubuntu-logging The file is Ubuntu specific but is not included in Ubuntu using a delta from Debian. Instead, the debian source tree includes the file but conditional statements in debian/rules makes it absent from the binary packages in Debian. Sadly, when moving the file from src:lsb to src:sysvinit, the conditional statements are not consistent anymore, resulting in the file being absent from the Ubuntu binary package as well. Affected version: sysvinit-utils 3.05-7ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/2002789/+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 1998787] Re: Please merge unattended-upgrades 2.9.1+nmu2 from Debian unstable.
Sponsored, thanks Dave! ** Changed in: unattended-upgrades (Ubuntu) Assignee: (unassigned) => Dan Bungert (dbungert) ** Changed in: unattended-upgrades (Ubuntu) Status: New => In Progress ** Changed in: unattended-upgrades (Ubuntu) Importance: Undecided => Wishlist ** Changed in: unattended-upgrades (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 unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1998787 Title: Please merge unattended-upgrades 2.9.1+nmu2 from Debian unstable. Status in unattended-upgrades package in Ubuntu: Fix Committed Bug description: Please merge unattended-upgrades 2.9.1+nmu2 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1998787/+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
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
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 Released
Status in initramfs-tools source package in Jammy:
Fix Committed
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 1981385] Re: initrd lacks modules to mount boot image from http boot
I have self-verified the change and it passes my listed test plan.
--
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 Released
Status in initramfs-tools source package in Jammy:
Fix Committed
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 1996619] Re: Setfont error due to deprecated PIO_FONTX ioctl
I am marking this invalid for Subiquity as I believe no changes are needed there. When we rebuild for 22.04.2 this change should be picked up, once that SRU to Jammy is done. ** Changed in: subiquity Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1996619 Title: Setfont error due to deprecated PIO_FONTX ioctl Status in subiquity: Invalid Status in kbd package in Ubuntu: Fix Released Status in kbd source package in Jammy: In Progress Bug description: There is an error message that get thrown in in syslog. There is a suggestion to fix by upgrading the KDB package to version 2.5.1+ or to understand the root cause and troubleshoot as to why it's broken and resolve it there. It is caused by this line in subiquity https://github.com/canonical/subiquity/blob/46f671d14d57a5da6bc3d60b1da6715b43954f0d/bin/subiquity-service#L11 It's due to PIO_FONTX ioctl removed from kernel since 5.12 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ff2047fb755d4415ec3c70ac799889371151796d In 2.4.5 of kbd which provide setfont in user space, they already switched over to use KDFONTOP only. ### REPRODUCER STEPS ### # install libvirt sudo apt install qemu qemu-kvm libvirt-clients libvirt-daemon-system virtinst bridge-utils sudo systemctl enable libvirtd sudo systemctl start libvirtd # check libvirtd process is running virsh virsh list # get iso wget https://releases.ubuntu.com/22.04/ubuntu-22.04.1-live-server-amd64.iso # install vm sudo virt-install --cdrom='./ubuntu-22.04.1-live-server-amd64.iso' --name=setfont-repo --vcpus=2 --memory=2048 --disk size=20 --serial pty --graphics none --boot=uefi --debug # you can either do the full install, the error will be in the /var/log/installer.log file # or on the first page of the installer press Tab-> go to Help, -> Shell and cd /var/log/ grep setfont* syslog # to show error message cd to /snap/subiquity/3698 #execute setfont $SNAP/subiquity.psf # error root@ubuntu-server:/snap/subiquity/3698# setfont $SNAP/subiquity.psf setfont: ERROR kdfontop.c:266 put_font_piofontx: ioctl(PIO_FONTX): 512,8x16: failed: Inappropriate ioctl for device # grep grep setfont* syslog Nov 14 18:22:11 ubuntu-server console-setup.sh[1107]: setfont: ERROR kdfontop.c:266 put_font_piofontx: ioctl(PIO_FONTX): 512,8x16: failed: Inappropriate ioctl for device Nov 14 18:22:29 ubuntu-server subiquity.subiquity-service[1878]: setfont: ERROR kdfontop.c:266 put_font_piofontx: ioctl(PIO_FONTX): 512,8x16: failed: Inappropriate ioctl for device To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1996619/+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
