[Touch-packages] [Bug 2086560] [NEW] lvm2 missing lvresize_fs_helper

[Dan Christian]

Public bug reported:

Ubuntu 24.10 running live from USB
I'm trying to resize some partitions so I can upgrade (because /boot needs more 
room)

lvresize fails with:
/usr/libexec/lvresize_fs_helper: execvp failed: No such file or directory

This appears to be that lvm2 bug 124 has not been fixed in the shipped
version.  https://github.com/lvmteam/lvm2/issues/124


Log:
root@kubuntu:/home/kubuntu# lvresize --verbose --resizefs -L 922G 
/dev/kubuntu-vg/root 
  File system ext4 found on kubuntu-vg/root. 
  File system size (922.58 GiB) is larger than the requested size (922.00 GiB). 
  File system reduce is required using resize2fs. 
  File system fsck will be run before reduce. 
  Reducing file system ext4 to 922.00 GiB (989989961728 bytes) on 
kubuntu-vg/root... 
  Executing: /usr/libexec/lvresize_fs_helper --fsreduce --fstype ext4 --lvpath 
/dev/kubuntu-vg/root --newsizebytes 989989961728 -
-fsck 
  /usr/libexec/lvresize_fs_helper: execvp failed: No such file or directory 
  /usr/libexec/lvresize_fs_helper failed: 2 
  Failed to reduce file system with lvresize_fs_helper. 

root@kubuntu:/home/kubuntu# lvresize --version 
  LVM version: 2.03.22(2) (2023-08-02) 
  Library version: 1.02.196 (2023-08-02) 
  Driver version:  4.48.0 
  Configuration:   ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=${prefix}/include --mandir=${prefix}/share/man
 --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules --libdir=
${prefix}/lib/x86_64-linux-gnu --runstatedir=/run --disable-maintainer-mode 
--disable-dependency-tracking --prefix=/usr --exec-pr
efix=/usr --with-usrlibdir=/usr/lib/x86_64-linux-gnu --with-optimisation=-O2 
--with-cache=internal --with-device-uid=0 --with-dev
ice-gid=6 --with-device-mode=0660 --with-default-pid-dir=/run 
--with-default-run-dir=/run/lvm --with-default-locking-dir=/run/loc
k/lvm --with-thin=internal --with-thin-check=/usr/sbin/thin_check 
--with-thin-dump=/usr/sbin/thin_dump --with-thin-repair=/usr/sb
in/thin_repair --enable-applib --enable-blkid_wiping --enable-cmdlib 
--enable-dmeventd --enable-editline --enable-lvmlockd-dlm --
enable-lvmlockd-sanlock --enable-lvmpolld --enable-notify-dbus 
--enable-pkgconfig --enable-udev_rules --enable-udev_sync --enable
-write_install --disable-readline 

root@kubuntu:/home/kubuntu# uname -a 
Linux kubuntu 6.11.0-8-generic #8-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 16 
13:41:20 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux 

root@kubuntu:/home/kubuntu# cat /etc/issue 
Ubuntu 24.10 \n \l

** Affects: lvm2 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/2086560

Title:
  lvm2 missing lvresize_fs_helper

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Ubuntu 24.10 running live from USB
  I'm trying to resize some partitions so I can upgrade (because /boot needs 
more room)

  lvresize fails with:
  /usr/libexec/lvresize_fs_helper: execvp failed: No such file or directory

  This appears to be that lvm2 bug 124 has not been fixed in the shipped
  version.  https://github.com/lvmteam/lvm2/issues/124

  
  Log:
  root@kubuntu:/home/kubuntu# lvresize --verbose --resizefs -L 922G 
/dev/kubuntu-vg/root 
File system ext4 found on kubuntu-vg/root. 
File system size (922.58 GiB) is larger than the requested size (922.00 
GiB). 
File system reduce is required using resize2fs. 
File system fsck will be run before reduce. 
Reducing file system ext4 to 922.00 GiB (989989961728 bytes) on 
kubuntu-vg/root... 
Executing: /usr/libexec/lvresize_fs_helper --fsreduce --fstype ext4 
--lvpath /dev/kubuntu-vg/root --newsizebytes 989989961728 -
  -fsck 
/usr/libexec/lvresize_fs_helper: execvp failed: No such file or directory 
/usr/libexec/lvresize_fs_helper failed: 2 
Failed to reduce file system with lvresize_fs_helper. 

  root@kubuntu:/home/kubuntu# lvresize --version 
LVM version: 2.03.22(2) (2023-08-02) 
Library version: 1.02.196 (2023-08-02) 
Driver version:  4.48.0 
Configuration:   ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=${prefix}/include --mandir=${prefix}/share/man
   --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules --libdir=
  ${prefix}/lib/x86_64-linux-gnu --runstatedir=/run --disable-maintainer-mode 
--disable-dependency-tracking --prefix=/usr --exec-pr
  efix=/usr --with-usrlibdir=/usr/lib/x86_64-linux-gnu --with-optimisation=-O2 
--with-cache=internal --with-device-uid=0 --with-dev
  ice-gid=6 --with-device-mode=0660 --with-default-pid-dir=/run 
--with-default-run-dir=/run/lvm --with-default-locking-dir=/run/loc
  k/lvm --with-thin=internal --with-thin-check=/usr/sbin/thin_check 
--with-thin-dump=/usr/sbin/thin_dump --with-thin-repair=/usr/sb
  in/thin_

[Touch-packages] [Bug 2084089] Re: ZFS with disk encryption missing cryptoswap: new oracular installs and release upgrades

[Dan Bungert]

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

[Dan Bungert]

** 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

[Dan Bungert]

** 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

[Dan Bungert]

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

[Dan Bungert]

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

[Dan Bungert]

** 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

[Dan Bungert]

** 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

[Dan Bungert]

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

[Dan Bungert]

>  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

[Dan Bungert]

** 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

[Dan Bungert]

@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

[Dan Bungert]

** 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

[Dan Bungert]

** 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

[Dan Bungert]

** 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

[Dan Bungert]

** 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

[Dan Bungert]

** 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

[Dan Bungert]

** 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

[Dan Bungert]

** 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

[Dan Bungert]

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

[Dan Bungert]

** 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

[Dan Bungert]

** 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

[Dan Bungert]

** 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

[Dan Bungert]

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

[Dan Bungert]

** 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

[Dan Bungert]

** 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

[Dan Bungert]

** 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

[Dan Bungert]

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

[Dan Bungert]

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 2054859] [NEW] VNC connection issues with 22.04

[Dan Towle]

Public bug reported:

I have several computers running 20.04 and a couple running 22.04. VNC
was great on 20.04. I could connect using remina or real vnc no problem.
on the 22.04 machines though, I cannot connect reliably at all. If the
server montitor is in sleep, the server rejects the connection. On some
machines I can connect once, but then not again until I restart the vnc
server.

The issue is the same using rdp or vnc.

I have searched on this, but couldn't find any information that was
helpful.

Thanks. Loving Ubuntu (35 year mac user)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 23 18:33:28 2024
DistUpgraded: 2022-09-04 14:22:00,091 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. 2nd Generation Core Processor Family Integrated 
Graphics Controller [106b:00e6]
InstallationDate: Installed on 2021-12-13 (803 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Apple Inc. Macmini5,1
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic 
root=UUID=3c9a744c-c73a-44bc-95a9-149b6bbc399a ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to jammy on 2022-09-04 (537 days ago)
dmi.bios.date: 04/09/2018
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MM51.88Z.0080.B00.1804091930
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-8ED6AF5B48C039E1
dmi.board.vendor: Apple Inc.
dmi.board.version: Macmini5,1
dmi.chassis.type: 16
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-8ED6AF5B48C039E1
dmi.modalias: 
dmi:bvnAppleInc.:bvrMM51.88Z.0080.B00.1804091930:bd04/09/2018:br0.1:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1:skuSystemSKU#:
dmi.product.family: Macmini
dmi.product.name: Macmini5,1
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2054859

Title:
  VNC connection issues with 22.04

Status in xorg package in Ubuntu:
  New

Bug description:
  I have several computers running 20.04 and a couple running 22.04. VNC
  was great on 20.04. I could connect using remina or real vnc no
  problem. on the 22.04 machines though, I cannot connect reliably at
  all. If the server montitor is in sleep, the server rejects the
  connection. On some machines I can connect once, but then not again
  until I restart the vnc server.

  The issue is the same using rdp or vnc.

  I have searched on this, but couldn't find any information that was
  helpful.

  Thanks. Loving Ubuntu (35 year mac user)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 23 18:33:28 2024
  DistUpgraded: 2022-09-04 14:22:00,091 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09)

[Touch-packages] [Bug 2052982] Re: regression in debconf-copydb when writing to stdout

[Dan Bungert]

** 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

[Dan Bungert]

** 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

[Dan Bungert]

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

[Dan Bungert]

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

[Dan Bungert]

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

[Dan Bungert]

** 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

[Dan Bungert]

** 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

[Dan Bungert]

** 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

[Dan Bungert]

** 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

[Dan Bungert]

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 1969365] Re: focal: backport kexec fallback patch

[Dan Watkins]

In the VM created in my above comment, I enabled proposed, installed the
new systemd and rebooted.  After that, I re-ran:

cd /boot
sudo kexec -l vmlinuz --initrd initrd.img --append 
'BOOT_IMAGE=/boot/vmlinuz-5.4.0-167-generic root=LABEL=cloudimg-rootfs ro 
console=tty1 console=ttyS0'
sudo reboot

And observed the following in the console:

[  OK  ] Reached target Final Step.
 Starting Reboot via kexec...
[  102.782246] systemd-udevd[369]: anon_vma(937:udisks2.service): Worker [960] 
did not accept message, killing the worker: Connection refused
[  102.784224] systemd-udevd[369]: anon_vma(937:udisks2.service): Worker [963] 
did not accept message, killing the worker: Connection refused
[  102.786398] systemd-udevd[369]: anon_vma(937:udisks2.service): Worker [966] 
did not accept message, killing the worker: Connection refused
[  102.788390] systemd-udevd[369]: anon_vma(937:udisks2.service): Worker [968] 
did not accept message, killing the worker: Connection refused
[  102.789954] systemd-udevd[369]: anon_vma(937:udisks2.service): Worker [962] 
did not accept message, killing the worker: Connection refused
[  102.791562] systemd-udevd[369]: anon_vma(937:udisks2.service): Worker [961] 
did not accept message, killing the worker: Connection refused
[  102.793198] systemd-udevd[369]: anon_vma(937:udisks2.service): Worker [964] 
did not accept message, killing the worker: Connection refused
[  102.794669] systemd-udevd[369]: anon_vma(937:udisks2.service): Worker [967] 
did not accept message, killing the worker: Connection refused
[  102.796841] systemd-udevd[369]: anon_vma(937:udisks2.service): Worker [965] 
did not accept message, killing the worker: Connection refused
[  102.904092] kexec_core: Starting new kernel
[0.00] Linux version 5.4.0-167-generic (buildd@lcy02-amd64-010) (gcc 
version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.2)) #184-Ubuntu SMP Tue Oct 31 
09:21:49 UTC 2023 (Ubuntu 5.4.0-167.184-generic 5.4.252)

So I can confirm that the new systemd addresses this bug.

** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

-- 
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/1969365

Title:
  focal: backport kexec fallback patch

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  It would be great if focal's systemd could have
  
https://github.com/systemd/systemd/commit/71180f8e57f8fbb55978b00a13990c79093ff7b3
  backported to it.

  [Impact]

  We have observed that kexec'ing to another kernel will fail as the
  drive containing the `kexec` binary has been unmounted by the time
  systemd attempts to do so, indicated in the console:

   Starting Reboot via kexec...
  [  163.960938] shutdown[1]: (sd-kexec) failed with exit status 1.
  [  163.963463] reboot: Restarting system

  [Test Plan]

  1) Launch a 20.04 instance
  2) `apt-get install kexec-tools`
  3) In `/boot`, filling in whatever  needed in your environment:

  kexec -l vmlinuz --initrd initrd.img --append ''

  4) `reboot`

  (I have reproduced this in a single-disk VM, so I assume it reproduces
  ~everywhere: if not, `apt-get remove kexec-tools` before the `reboot`
  could be used to emulate the unmounting.)

  [Where problems could occur]

  Users could inadvertently be relying on the current behaviour: if they
  have configured their systems to kexec, they currently will be
  rebooting normally, and this patch would cause them to start actually
  kexec'ing.

  [Other info]

  We're currently maintaining a systemd tree with only this patch added
  to focal's tree: this patch has received a bunch of testing from us in
  focal.

  This patch landed in v246, so it's already present in supported
  releases later than focal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1969365/+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 1969365] Re: focal: backport kexec fallback patch

[Dan Watkins]

Apologies, I completely missed your comment, Nick!  I was just able to
reproduce this using uvtool.

To launch the VM (and monitor the console output):

uvt-simplestreams-libvirt sync release=focal arch=amd64
uvt-kvm create firsttest release=focal
virsh console firsttest

Then, within the instance via `uvt-kvm ssh firsttest`:

sudo apt update
sudo apt install kexec-tools
sudo reboot  # I wanted to check `virsh console` was getting output

After reboot and reconnecting:

cd /boot
sudo kexec -l vmlinuz --initrd initrd.img --append 
'BOOT_IMAGE=/boot/vmlinuz-5.4.0-167-generic root=LABEL=cloudimg-rootfs ro 
console=tty1 console=ttyS0'
sudo reboot

I then observed the following in `virsh console`'s output (note the
"Unmount All Filesystems", which is what I think is causing the
problem):

[  OK  ] Reached target Unmount All Filesystems.
 Stopping Monitoring of LVM…meventd or progress polling...
 Stopping Device-Mapper Multipath Device Controller...
[  OK  ] Stopped Create Static Device Nodes in /dev.
[  OK  ] Stopped Create System Users.
[  OK  ] Stopped Remount Root and Kernel File Systems.
[  OK  ] Stopped File System Check on Root Device.
[  OK  ] Stopped Device-Mapper Multipath Device Controller.
[  OK  ] Stopped Monitoring of LVM2… dmeventd or progress polling.
[  OK  ] Reached target Shutdown.
[  OK  ] Reached target Final Step.
 Starting Reboot via kexec...
[   53.030829] systemd-udevd[372]: proc_inode_cache(1258:kexec.service): Worker 
[960] did not accept message, killing the worker: Connection refused
[   53.032915] systemd-udevd[372]: proc_inode_cache(1258:kexec.service): Worker 
[954] did not accept message, killing the worker: Connection refused
[   53.034697] systemd-udevd[372]: proc_inode_cache(1258:kexec.service): Worker 
[953] did not accept message, killing the worker: Connection refused
[   53.036756] systemd-udevd[372]: proc_inode_cache(1258:kexec.service): Worker 
[955] did not accept message, killing the worker: Connection refused
[   53.039144] systemd-udevd[372]: proc_inode_cache(1258:kexec.service): Worker 
[956] did not accept message, killing the worker: Connection refused
[   53.041049] systemd-udevd[372]: proc_inode_cache(1258:kexec.service): Worker 
[958] did not accept message, killing the worker: Connection refused
[   53.042673] systemd-udevd[372]: proc_inode_cache(1258:kexec.service): Worker 
[961] did not accept message, killing the worker: Connection refused
[   53.123845] shutdown[1]: (sd-kexec) failed with exit status 1.
[   53.138542] reboot: Restarting system
[0.00] Linux version 5.4.0-167-generic (buildd@lcy02-amd64-010) (gcc 
version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.2)) #184-Ubuntu SMP Tue Oct 31 
09:21:49 UTC 2023 (Ubuntu 5.4.0-167.184-generic 5.4.252)

(I initially tried to re-reproduce using an Incus VM (and so a community
image rather than a cloud-images one) and could not do so.  Executing
the above `kexec` command produced "ima: impossible to appraise a kernel
image without a file descriptor; try using kexec_file_load syscall." in
the console.  Adding `-s`/`--kexec-file-syscall` to the kexec command
caused it to exit zero, and the VM did then successfully kexec on
`reboot`.)

-- 
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/1969365

Title:
  focal: backport kexec fallback patch

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  It would be great if focal's systemd could have
  
https://github.com/systemd/systemd/commit/71180f8e57f8fbb55978b00a13990c79093ff7b3
  backported to it.

  [Impact]

  We have observed that kexec'ing to another kernel will fail as the
  drive containing the `kexec` binary has been unmounted by the time
  systemd attempts to do so, indicated in the console:

   Starting Reboot via kexec...
  [  163.960938] shutdown[1]: (sd-kexec) failed with exit status 1.
  [  163.963463] reboot: Restarting system

  [Test Plan]

  1) Launch a 20.04 instance
  2) `apt-get install kexec-tools`
  3) In `/boot`, filling in whatever  needed in your environment:

  kexec -l vmlinuz --initrd initrd.img --append ''

  4) `reboot`

  (I have reproduced this in a single-disk VM, so I assume it reproduces
  ~everywhere: if not, `apt-get remove kexec-tools` before the `reboot`
  could be used to emulate the unmounting.)

  [Where problems could occur]

  Users could inadvertently be relying on the current behaviour: if they
  have configured their systems to kexec, they currently will be
  rebooting normally, and this patch would cause them to start actually
  kexec'ing.

  [Other info]

  We're currently maintaining a systemd tree with only this patch added
  to focal's tree: this patch has received a bunch of testing from us in
  focal.

  This patch landed in v246, so it's already present in supported
  releases later than 

[Touch-packages] [Bug 2003756] Re: Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142."

[Dan MacDonald]

This bug also affects installing proftpd under 22.04.

apt install proftpd
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'proftpd-core' instead of 'proftpd'
proftpd-core is already the newest version (1.3.7c+dfsg-1build1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
[master d41b86764d] saving uncommitted changes in /etc prior to apt run
 Author: cseadmin 
 1 file changed, 1 insertion(+), 1 deletion(-)
Setting up proftpd-core (1.3.7c+dfsg-1build1) ...
usermod: no changes
Synchronizing state of proftpd.service with SysV service script with 
/lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable proftpd
Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 142.
dpkg: error processing package proftpd-core (--configure):
 installed proftpd-core package post-installation script subprocess returned 
error exit status 1
Errors were encountered while processing:
 proftpd-core
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/2003756

Title:
  Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute
  systemctl:  at /usr/bin/deb-systemd-invoke line 142."

Status in init-system-helpers package in Ubuntu:
  Confirmed
Status in krb5 package in Ubuntu:
  Confirmed

Bug description:
  I have a fresh install of Ubuntu Server 22.04.01 LTS.  After
  installing the server and running all updates, I run the following
  command:

  apt -y install slapd ldap-utils schema2ldif sasl2-bin
  libsasl2-modules-gssapi-mit krb5-kdc-ldap krb5-admin-server krb5-kdc

  This will be installing krb5-kdc 1.19.2-2.

  This is in preparation for setting up an OpenLDAP server, a Kerberos
  server with an LDAP backend, and saslauthd for pass-through
  authentication.  krb5-kdc was auto-selected when running the steps in
  the guide here in my development environment:
  https://ubuntu.com/server/docs/service-kerberos-with-openldap-backend
  When installing that, I get the following in the output:

  Setting up krb5-kdc (1.19.2-2) ...
  Created symlink /etc/systemd/system/multi-user.target.wants/krb5-kdc.service 
→ /lib/systemd/system/krb5-kdc.service.
  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 142.

  I do get the prompts for the realm, kdc, and admin server hostnames,
  and they are reflected in /etc/krb5.conf.  If I then run the
  following:

  dpkg-reconfigure krb5-kdc

  I am prompted for whether I want the package to create the Kerberos
  KDC configuration automatically, and when I say yes, it then repeats
  the following error:

  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 142.

  I cannot find any further debug in the syslog or anything to indicate
  what the root cause is; the list of packages here are all installed
  together on a separate development server where I experimented with
  the configuration I will be deploying here in production so I don't
  think it's incompatible packages in the install list, but I am open to
  feedback on that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/2003756/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

[Dan Simmons]

Other packages that have been tested and found to be impacted by this
bug have been added.

** Also affects: angelfish (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: angelfish (Ubuntu)
   Status: New => Confirmed

** Also affects: privacybrowser (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: privacybrowser (Ubuntu)
   Status: New => Confirmed

** Also affects: notepadqq (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: notepadqq (Ubuntu)
   Status: New => Confirmed

** Also affects: cantor (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: cantor (Ubuntu)
   Status: New => Confirmed

** Also affects: pageedit (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: pageedit (Ubuntu)
   Status: New => Confirmed

** Also affects: rssguard (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: rssguard (Ubuntu)
   Status: New => Confirmed

** Also affects: konqueror (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: konqueror (Ubuntu)
   Status: New => Confirmed

** Also affects: kiwix (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: kiwix (Ubuntu)
   Status: New => Confirmed

** Also affects: kchmviewer (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: kchmviewer (Ubuntu)
   Status: New => Confirmed

** Also affects: goldendict-webengine (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: goldendict-webengine (Ubuntu)
   Status: New => Confirmed

** Also affects: opam (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: opam (Ubuntu)
   Status: New => Confirmed

** Also affects: akregator (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: akregator (Ubuntu)
   Status: New => Confirmed

** Also affects: kalgebra (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: kalgebra (Ubuntu)
   Status: New => Confirmed

** Also affects: qmapshack (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: qmapshack (Ubuntu)
   Status: New => Confirmed

** Also affects: supercollider (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: supercollider (Ubuntu)
   Status: New => Confirmed

** Also affects: tellico (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: tellico (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2046844

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in akregator package in Ubuntu:
  Confirmed
Status in angelfish package in Ubuntu:
  Confirmed
Status in apparmor package in Ubuntu:
  Confirmed
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  Confirmed
Status in devhelp package in Ubuntu:
  Confirmed
Status in digikam package in Ubuntu:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Confirmed
Status in falkon package in Ubuntu:
  Confirmed
Status in freecad package in Ubuntu:
  Confirmed
Status in gnome-packagekit package in Ubuntu:
  Confirmed
Status in goldendict-webengine package in Ubuntu:
  Confirmed
Status in kalgebra package in Ubuntu:
  Confirmed
Status in kchmviewer package in Ubuntu:
  Confirmed
Status in kdeplasma-addons package in Ubuntu:
  Confirmed
Status in kiwix package in Ubuntu:
  Confirmed
Status in konqueror package in Ubuntu:
  Confirmed
Status in kontact package in Ubuntu:
  Confirmed
Status in notepadqq package in Ubuntu:
  Confirmed
Status in opam package in Ubuntu:
  Confirmed
Status in pageedit package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in privacybrowser package in Ubuntu:
  Confirmed
Status in qmapshack package in Ubuntu:
  Confirmed
Status in qutebrowser package in Ubuntu:
  Confirmed
Status in rssguard package in Ubuntu:
  Confirmed
Status in steam package in Ubuntu:
  Confirmed
Status in supercollider package in Ubuntu:
  Confirmed
Status in tellico package in Ubuntu:
  Confirmed

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  Thanks f

[Touch-packages] [Bug 2046389] Re: FTBFS if bash-completion is installed at build time

[Dan Bungert]

** 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

[Dan Bungert]

** 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

[Dan Bungert]

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

[Dan Bungert]

*** 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

[Dan Bungert]

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 2041672] Re: glob in mime/packages/freedesktop.org.xml is matching wrong files

[Dan Gut]

removing

  

  

and

sudo update-mime-database /usr/share/mime

fixes the issue locally until the next update

** Summary changed:

- glob in mime/packages/freedesktop.org.xml is matching wrong files
+  in mime/packages/freedesktop.org.xml is matching wrong files

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shared-mime-info in
Ubuntu.
https://bugs.launchpad.net/bugs/2041672

Title:
   in mime/packages/freedesktop.org.xml is matching wrong files

Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  /usr/share/mime/packages/freedesktop.org.xml
  line 10466 -> value="import Qt" offset="0:3000"
  context:
  







  


  is matching python files using Pyside
  with imports like:

  from PySide2.QtCore import Qt, QSettings, QSize

  considering them 'Qt Markup Language files (text/x-qml)' thus wrecking
  havoc down the line. Maybe just remove this match entry as it seems
  very broad

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/2041672/+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 2041672] [NEW] glob in mime/packages/freedesktop.org.xml is matching wrong files

[Dan Gut]

Public bug reported:

/usr/share/mime/packages/freedesktop.org.xml
line 10466 -> value="import Qt" offset="0:3000"
context:

  
  

  
  

  



is matching python files using Pyside
with imports like:

from PySide2.QtCore import Qt, QSettings, QSize

considering them 'Qt Markup Language files (text/x-qml)' thus wrecking
havoc down the line. Maybe just remove this match entry as it seems very
broad

** Affects: shared-mime-info (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: mime pyside pyside2 pyside6 python qt

** Summary changed:

- glob in mime/packages/freedesktop.org.xml is matching wron files
+ glob in mime/packages/freedesktop.org.xml is matching wrong files

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shared-mime-info in
Ubuntu.
https://bugs.launchpad.net/bugs/2041672

Title:
  glob in mime/packages/freedesktop.org.xml is matching wrong files

Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  /usr/share/mime/packages/freedesktop.org.xml
  line 10466 -> value="import Qt" offset="0:3000"
  context:
  







  


  is matching python files using Pyside
  with imports like:

  from PySide2.QtCore import Qt, QSettings, QSize

  considering them 'Qt Markup Language files (text/x-qml)' thus wrecking
  havoc down the line. Maybe just remove this match entry as it seems
  very broad

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/2041672/+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

[Dan Bungert]

** 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

[Dan Bungert]

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

[Dan Bungert]

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

[Dan Bungert]

** 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

[Dan Bungert]

** 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

[Dan Bungert]

** 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

[Dan Bungert]

** 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

[Dan Bungert]

** 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

[Dan Bungert]

** 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

[Dan Bungert]

** 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

[Dan Bungert]

** 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

[Dan Bungert]

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

[Dan Bungert]

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

[Dan Bungert]

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

[Dan Bungert]

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

[Dan Bungert]

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

[Dan Bungert]

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

[Dan Bungert]

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

[Dan Bungert]

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

[Dan Bungert]

** 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

[Dan Bungert]

** 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

[Dan Bungert]

** 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

[Dan Bungert]

** 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

[Dan Bungert]

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

[Dan Bungert]

** 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 1969365] Re: focal: backport kexec fallback patch

[Dan Watkins]

Thanks Nick, much appreciated!

-- 
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/1969365

Title:
  focal: backport kexec fallback patch

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Triaged

Bug description:
  It would be great if focal's systemd could have
  
https://github.com/systemd/systemd/commit/71180f8e57f8fbb55978b00a13990c79093ff7b3
  backported to it.

  [Impact]

  We have observed that kexec'ing to another kernel will fail as the
  drive containing the `kexec` binary has been unmounted by the time
  systemd attempts to do so, indicated in the console:

   Starting Reboot via kexec...
  [  163.960938] shutdown[1]: (sd-kexec) failed with exit status 1.
  [  163.963463] reboot: Restarting system

  [Test Plan]

  1) Launch a 20.04 instance
  2) `apt-get install kexec-tools`
  3) In `/boot`, filling in whatever  needed in your environment:

  kexec -l vmlinuz --initrd initrd.img --append ''

  4) `reboot`

  (I have reproduced this in a single-disk VM, so I assume it reproduces
  ~everywhere: if not, `apt-get remove kexec-tools` before the `reboot`
  could be used to emulate the unmounting.)

  [Where problems could occur]

  Users could inadvertently be relying on the current behaviour: if they
  have configured their systems to kexec, they currently will be
  rebooting normally, and this patch would cause them to start actually
  kexec'ing.

  [Other info]

  We're currently maintaining a systemd tree with only this patch added
  to focal's tree: this patch has received a bunch of testing from us in
  focal.

  This patch landed in v246, so it's already present in supported
  releases later than focal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1969365/+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 2028056] [NEW] screen rotates automatically by 90° when physical keyboard is disconnected from tablet

[Dan]

Public bug reported:

On my tablet PC, the screen rotates automatically by 90° as soon as I
disconnect the physical keyboard (that came with the tablet)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 18 12:05:00 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus: rtl8821ce/5.5.2.1: added
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation GeminiLake [UHD Graphics 600] [8086:3185] (rev 06) (prog-if 
00 [VGA controller])
   Subsystem: nCipher Security GeminiLake [UHD Graphics 600] [0100:2782]
InstallationDate: Installed on 2023-07-16 (2 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
MachineType: CHUWI Innovation And Technology(ShenZhen)co.,Ltd Hi10 X
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic 
root=UUID=568dc00b-4a6a-41ac-964a-bfd8bda5f161 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/08/2021
dmi.bios.release: 0.5
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V0.5.0_P4S0M2E0F0L8B0T6P0G48A1U0D701
dmi.board.asset.tag: Default string
dmi.board.name: To be filled by O.E.M.
dmi.board.vendor: To be filled by O.E.M.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 30
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV0.5.0_P4S0M2E0F0L8B0T6P0G48A1U0D701:bd05/08/2021:br0.5:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnHi10X:pvrDefaultstring:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrDefaultstring:cvnDefaultstring:ct30:cvrDefaultstring:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Hi10 X
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: Default string
dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy ubuntu wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2028056

Title:
  screen rotates automatically by 90° when physical keyboard is
  disconnected from tablet

Status in xorg package in Ubuntu:
  New

Bug description:
  On my tablet PC, the screen rotates automatically by 90° as soon as I
  disconnect the physical keyboard (that came with the tablet)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 18 12:05:00 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: rtl8821ce/5.5.2.1: added
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation GeminiLake [UHD Graphics 600] [8086:3185] (rev 06) 
(prog-if 00 [VGA controller])
 Subsystem: nCipher Security GeminiLake [UHD Graphics 600] [0100:2782]
  InstallationDate: Installed on 2023-07-16 (2 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  MachineType: CHUWI Innovation And Technology(ShenZhen)co.,Ltd Hi10 X
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic 
root=UUID=568dc00b-4a6a-41ac-964a-bfd8bda5f161 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2021
  dmi.bios.release: 0.5
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V0.5.0_P4S0M2E0F

[Touch-packages] [Bug 1969365] Re: focal: backport kexec fallback patch

[Dan Watkins]

Thanks for the reply, Nick!

I think it's important enough to land because:

* you cannot execute `kexec` correctly on an Ubuntu 20.04 system without this 
patch (it will fall back to performing a full reboot),
* kexec can be used to reduce downtime for critical systems which take a long 
time to reboot (e.g. because they have a lot of hardware to initialise), and
* kexec-tools is in main (and has been since at least trusty) which indicates 
to me that it is expected that kexec will work on Ubuntu

I'd also add that the patch is three lines in a code path which is only
used by people opting into using `kexec`, so the potential downside is
pretty minimal.

(I'll set the bug back to New for now, until you have a chance to
respond.)

** Changed in: systemd (Ubuntu)
   Status: Fix Released => 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/1969365

Title:
  focal: backport kexec fallback patch

Status in systemd package in Ubuntu:
  New

Bug description:
  It would be great if focal's systemd could have
  
https://github.com/systemd/systemd/commit/71180f8e57f8fbb55978b00a13990c79093ff7b3
  backported to it.

  [Impact]

  We have observed that kexec'ing to another kernel will fail as the
  drive containing the `kexec` binary has been unmounted by the time
  systemd attempts to do so, indicated in the console:

   Starting Reboot via kexec...
  [  163.960938] shutdown[1]: (sd-kexec) failed with exit status 1.
  [  163.963463] reboot: Restarting system

  [Test Plan]

  1) Launch a 20.04 instance
  2) `apt-get install kexec-tools`
  3) In `/boot`, filling in whatever  needed in your environment:

  kexec -l vmlinuz --initrd initrd.img --append ''

  4) `reboot`

  (I have reproduced this in a single-disk VM, so I assume it reproduces
  ~everywhere: if not, `apt-get remove kexec-tools` before the `reboot`
  could be used to emulate the unmounting.)

  [Where problems could occur]

  Users could inadvertently be relying on the current behaviour: if they
  have configured their systems to kexec, they currently will be
  rebooting normally, and this patch would cause them to start actually
  kexec'ing.

  [Other info]

  We're currently maintaining a systemd tree with only this patch added
  to focal's tree: this patch has received a bunch of testing from us in
  focal.

  This patch landed in v246, so it's already present in supported
  releases later than focal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1969365/+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

[Dan Bungert]

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

[Dan Bungert]

** 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

[Dan Bungert]

** 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 1950996] Re: Missing all modules for usb nics in initrd which makes PXE boot impossible

[Dan Czuchra]

Hi all, are there any updates to this issue? This has broken our 20.04
builds over iPXE. We're trying to update the initrd and vmlinuz files,
but there's not very good documentation on how to update these files.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1950996

Title:
  Missing all modules for usb nics in initrd which makes PXE boot
  impossible

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Focal:
  Triaged
Status in initramfs-tools source package in Hirsute:
  Won't Fix
Status in initramfs-tools source package in Impish:
  Won't Fix
Status in initramfs-tools source package in Jammy:
  Fix Released
Status in initramfs-tools package in Debian:
  Fix Released

Bug description:
  initrd taken from the live iso for PXE boot does not contain USB NIC
  drivers which makes PXE installation/netboot impossible via usb.

  This is the case on 20.04 server iso (both hwe and normal
  kernel/initrd) and desktop iso.

  "kernel/drivers/net/usb" is empty and needs to be included in the
  initramfs build.

  As most modern thin laptops lack physical rj45 ethernet this is a big
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.6
  ProcVersionSignature: Ubuntu 5.8.0-64.72-generic 5.8.18
  Uname: Linux 5.8.0-64-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 15 16:47:45 2021
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: Upgraded to focal on 2020-05-11 (552 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1950996/+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

[Dan Bungert]

** 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

[Dan Bungert]

** 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

[Dan Bungert]

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

[Dan Bungert]

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

[Dan Bungert]

** 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

[Dan Bungert]

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

[Dan Bungert]

** 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 2020604] Re: After mesa upgrades, Chrome won't show graphics

[Dan Halbert]

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2020604

Title:
  After mesa upgrades, Chrome won't show graphics

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  After today's Ubuntu 22.04 mesa upgrades many of our users reported
  problems viewing graphics when using Google Chrome (Stable).

  The mesa upgrades we installed were:

  [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2

  We documented the problem in AskUbuntu before we realized it was
  probably related to mesa, so wanted to link to that report here:

  https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
  updates-chrome-wont-display-website-graphi

  There is a bypass listed in that article.  Not sure if this is an
  issue with mesa or Chrome or specific machine graphics or an
  interaction between them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2020604/+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 2018538] Re: All PDFs when printed come out mirror image

[Dan Stephans]

This behavior also occurs on 23.04 with an HP CP2025.  Prior to upgrade
printing was great.  After upgrade if nothing is touched all pages are
mirrored.  If the print option is set to mirrored the described behavior
in the original report occurs.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/2018538

Title:
  All PDFs when printed come out mirror image

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Since updating to Ubuntu 23.04.  Whenever I try to print a PDF
  (regardless of application the PDF is open in) it will print the PDF
  in mirror image.

  If I enable printing mirror image in the settings, every other page
  become mirror image as instead. (I'm printing double sided/long edge
  print, so one side is normal and the other side becomes mirror image
  when I do this).

  I'm trying to print to a HP Colour LaserJet CP2025dn

  Note: If I print from my second device when it was running Ubuntu
  22.10 it would print normally, but as soon as I updated it to 23.04,
  it started having the same issue as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  4 20:31:48 2023
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2022-10-22 (194 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (13 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2018538/+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 1991553] Re: can't add a private PPA

[Dan Streetman]

> Instead, `add-apt-repository` should call `getArchiveSubscriptionURL`
(not `getArchiveSubscriptionURLs`)

this doesn't seem to work correctly.

For example:

In [25]: lp.me.getArchiveSubscriptionURLs()
Out[25]: 
['https://ddstreet:x...@private-ppa.launchpadcontent.net/canonical-support-eng/soscleaner-deletedppa/ubuntu',
 
'https://ddstreet:x...@private-ppa.launchpadcontent.net/canonical-support-eng/ddstreet-deletedppa/ubuntu',
 
'https://ddstreet:x...@private-ppa.launchpadcontent.net/jedis/test-deletedppa1/ubuntu',
 
'https://ddstreet:x...@private-ppa.launchpadcontent.net/jedis/test-deletedppa/ubuntu',
 
'https://ddstreet:x...@private-ppa.launchpadcontent.net/canonical-support-eng/sf155616-deletedppa/ubuntu',
 
'https://ddstreet:x...@private-ppa.launchpadcontent.net/canonical-support-eng/sf107001-deletedppa/ubuntu',
 
'https://ddstreet:x...@private-ppa.launchpadcontent.net/canonical-support-eng/sf99522-deletedppa/ubuntu',
 
'https://ddstreet:x...@private-ppa.launchpadcontent.net/canonical-support-eng/sf94878-deletedppa/ubuntu']

In [26]: jedis = lp.people('jedis')

In [28]: testdeletedppa = jedis.getPPAByName(name='test-deletedppa')

In [29]: lp.me.getArchiveSubscriptionURL(archive=testdeletedppa)
Out[29]: 
{'self_link': 'https://api.launchpad.net/devel/~ddstreet',
 'web_link': 'https://launchpad.net/~ddstreet',
 'resource_type_link': 'https://api.launchpad.net/devel/#person',

...and the rest of my personal object (i.e. lp.me) as a python object.

It's the same result when I try with a non-deleted ppa, which doesn't
show up in getArchiveSubscriptionURLs():

In [37]: lteam = lp.people('launch-lite')

In [38]: lppa = lteam.getPPAByName(name='ppa')

In [39]: lp.me.getArchiveSubscriptionURL(archive=lppa)
Out[39]: 
{'self_link': 'https://api.launchpad.net/devel/~ddstreet',
 'web_link': 'https://launchpad.net/~ddstreet',
 'resource_type_link': 'https://api.launchpad.net/devel/#person',
...

Until that bug is fixed (and that bug isn't in software-properties), I
don't think add-apt-repository can be changed to use
getArchiveSubscriptionURL(). Or at least, if this bug only applies to
me, then I can't make the change in software-properties since I wouldn't
be able to test the change...

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1991553

Title:
  can't add a private PPA

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  As per today's discussion in ~is :

  add-apt-repository has a bug when adding a private PPA. Quoting
  ~cjwatson :

  ===
  It asks Launchpad for all your personal archive subscriptions _that have 
tokens_.  But `Person:+archivesubscriptions` also shows subscriptions without 
tokens - the token is generated when you click on Viewt here for the first time.

  Instead, `add-apt-repository` should call `getArchiveSubscriptionURL` (not 
`getArchiveSubscriptionURLs`) for the archive it's interested in.  That 
generates tokens on-demand.  Either it will get an HTTP 401, or it will get a 
URL which it can parse for the username and password.
  ===

  Thanks !

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1991553/+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 1973441] Re: Printing does not work on Ubuntu 22.04 - cups-pki-invalid

[Dan Andreșan]

Same, ubuntu 23.04, Epson ET-8500 printer, old certificate was from
November, deleted it then I was able to print (and a new certificate
appeared).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1973441

Title:
  Printing does not work on Ubuntu 22.04 - cups-pki-invalid

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 22.04 printing did not work. There is cups-pki-
  invalid error and printer goes to paused state.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4
  Uname: Linux 5.17.7-051707-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 15 15:34:47 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2021-10-12 (214 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010)
  Lpstat: device for HP_Color_LaserJet_M552_5F80BF: 
implicitclass://HP_Color_LaserJet_M552_5F80BF/
  MachineType: ASUSTeK COMPUTER INC. ROG Strix G513QY_G513QY
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.17.7-051707-generic 
root=UUID=ff964c9b-ce92-4334-8759-9d785a262c60 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-04-24 (21 days ago)
  dmi.bios.date: 03/29/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: G513QY.318
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G513QY
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 0.81
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513QY.318:bd03/29/2022:br5.19:efr0.81:svnASUSTeKCOMPUTERINC.:pnROGStrixG513QY_G513QY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG513QY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ROG Strix
  dmi.product.name: ROG Strix G513QY_G513QY
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973441/+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 2016281] Re: Xorg freezing entirely for up to 5 seconds after brightness-change via hotkeys

[Dan]

** Attachment added: "brightness.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2016281/+attachment/5663971/+files/brightness.png

** Description changed:

  After each brightness-step change (via using Fn+arrow up-/arrow-down
  keys), system freezes for ~500ms. With my notebook's 10 brightness-
  levels, this often results in total delay from 10x 500ms, = 5 entire
  seconds for the notebook finishing a multi-step brightness-change in
  very very laggy steps, when the user input already stops within 1-2
  seconds.
  
  Also, the brightness update-rate symbology is often freezing entirely
  for up to 5 seconds before indicating that brightness was changed at all
- (see screenshot for symbology)
+ (see screenshot in comment #2 for symbology)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
-  NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.157  Wed Oct 12 09:19:07 
UTC 2022
-  GCC version:
+  NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.157  Wed Oct 12 09:19:07 
UTC 2022
+  GCC version:
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 14 11:17:18 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
-Subsystem: Micro-Star International Co., Ltd. [MSI] 3rd Gen Core processor 
Graphics Controller [1462:10d7]
-  NVIDIA Corporation GK107M [GeForce GTX 660M] [10de:0fd4] (rev a1) (prog-if 
00 [VGA controller])
-Subsystem: Micro-Star International Co., Ltd. [MSI] GK107M [GeForce GTX 
660M] [1462:10d7]
+  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
+    Subsystem: Micro-Star International Co., Ltd. [MSI] 3rd Gen Core processor 
Graphics Controller [1462:10d7]
+  NVIDIA Corporation GK107M [GeForce GTX 660M] [10de:0fd4] (rev a1) (prog-if 
00 [VGA controller])
+    Subsystem: Micro-Star International Co., Ltd. [MSI] GK107M [GeForce GTX 
660M] [1462:10d7]
  InstallationDate: Installed on 2023-03-30 (14 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Micro-Star International Co., Ltd. GE60 0NC\0ND
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic 
root=UUID=c2574575-ad11-44a8-9aa0-69c2e7c72473 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16GAIMS.513
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-16GA
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16GAIMS.513:bd11/08/2012:br4.6:svnMicro-StarInternationalCo.,Ltd.:pnGE600NC\0ND:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GA:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: GE60 0NC\0ND
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2016281

Title:
  Xorg freezing entirely for up to 5 seconds after brightness-change via
  hotkeys

Status in xorg package in Ubuntu:
  New

Bug description:
  After each brightness-step change (via using Fn+arrow up-/arrow-dow

[Touch-packages] [Bug 2016281] [NEW] Xorg freezing entirely for up to 5 seconds after brightness-change via hotkeys

[Dan]

Public bug reported:

After each brightness-step change (via using Fn+arrow up-/arrow-down
keys), system freezes for ~500ms. With my notebook's 10 brightness-
levels, this often results in total delay from 10x 500ms, = 5 entire
seconds for the notebook finishing a multi-step brightness-change in
very very laggy steps, when the user input already stops within 1-2
seconds.

Also, the brightness update-rate symbology is often freezing entirely
for up to 5 seconds before indicating that brightness was changed at all
(see screenshot in comment #2 for symbology)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-38-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.157  Wed Oct 12 09:19:07 
UTC 2022
 GCC version:
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 14 11:17:18 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] 3rd Gen Core processor 
Graphics Controller [1462:10d7]
 NVIDIA Corporation GK107M [GeForce GTX 660M] [10de:0fd4] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GK107M [GeForce GTX 
660M] [1462:10d7]
InstallationDate: Installed on 2023-03-30 (14 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: Micro-Star International Co., Ltd. GE60 0NC\0ND
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic 
root=UUID=c2574575-ad11-44a8-9aa0-69c2e7c72473 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/08/2012
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E16GAIMS.513
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MS-16GA
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16GAIMS.513:bd11/08/2012:br4.6:svnMicro-StarInternationalCo.,Ltd.:pnGE600NC\0ND:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GA:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: GE60 0NC\0ND
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug false-gpu-hang freeze jammy ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2016281

Title:
  Xorg freezing entirely for up to 5 seconds after brightness-change via
  hotkeys

Status in xorg package in Ubuntu:
  New

Bug description:
  After each brightness-step change (via using Fn+arrow up-/arrow-down
  keys), system freezes for ~500ms. With my notebook's 10 brightness-
  levels, this often results in total delay from 10x 500ms, = 5 entire
  seconds for the notebook finishing a multi-step brightness-change in
  very very laggy steps, when the user input already stops within 1-2
  seconds.

  Also, the brightness update-rate symbology is often freezing entirely
  for up to 5 seconds before indicating that brightness was changed at
  all (see screenshot in comment #2 for symbology)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvid

[Touch-packages] [Bug 2015373] Re: massive yellow screen color corruption

[Dan]

The corruption occurs as soon as "try ubuntu" is clicked and seems to be
caused by the "automatic" color-profile being applied ("Automatic -
C24F390", Samsung monitor C24F390). It can temporarily be fixed by
removing the automatic profile and activating "Colorspace sRGB" profile.
A permanent patch would be for the "Try Ubuntu" feature to automatically
select Colorspace sRGB instead of automatic.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2015373

Title:
  massive yellow screen color corruption

Status in xorg package in Ubuntu:
  New

Bug description:
  using the "try ubuntu" feature, this is what the entire experience
  looks like (see the 2nd attached image in comment #2).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.470.2
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  5 15:37:32 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU104 [GeForce RTX 2060] [10de:1e89] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd TU104 [GeForce RTX 2060] 
[1458:402b]
  LiveMediaBuild: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  MachineType: To Be Filled By O.E.M. A320M Pro4 R2.0
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/hostname.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.40
  dmi.board.name: A320M Pro4 R2.0
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.40:bd10/26/2022:br5.17:svnToBeFilledByO.E.M.:pnA320MPro4R2.0:pvrToBeFilledByO.E.M.:rvnASRock:rnA320MPro4R2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: A320M Pro4 R2.0
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2015373/+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 2015373] Re: massive yellow screen color corruption

[Dan]

** Description changed:

  using the "try ubuntu" feature, this is what the entire experience looks
- like (see the 2nd attached screenshot in comment #2).
+ like (see the 2nd attached image in comment #2).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.470.2
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  5 15:37:32 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU104 [GeForce RTX 2060] [10de:1e89] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd TU104 [GeForce RTX 2060] 
[1458:402b]
  LiveMediaBuild: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  MachineType: To Be Filled By O.E.M. A320M Pro4 R2.0
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/hostname.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.40
  dmi.board.name: A320M Pro4 R2.0
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.40:bd10/26/2022:br5.17:svnToBeFilledByO.E.M.:pnA320MPro4R2.0:pvrToBeFilledByO.E.M.:rvnASRock:rnA320MPro4R2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: A320M Pro4 R2.0
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2015373

Title:
  massive yellow screen color corruption

Status in xorg package in Ubuntu:
  New

Bug description:
  using the "try ubuntu" feature, this is what the entire experience
  looks like (see the 2nd attached image in comment #2).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.470.2
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  5 15:37:32 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU104 [GeForce RTX 2060] [10de:1e89] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd TU104 [GeForce RTX 2060] 
[1458:402b]
  LiveMediaBuild: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  MachineType: To Be Filled By O.E.M. A320M Pro4 R2.0
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/hostname.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.40
  dmi.board.name: A320M Pro4 R2.0
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.40:bd10/26/2022:br5.17:svnToBeFilledByO.

[Touch-packages] [Bug 2008952] Re: DNS failure while trying to fetch user-data

[Dan Bungert]

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

[Dan Bungert]

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