date:20231005

@rpocase please check internally I believe we have multiple azure & Aws
affected customers as per previous Salesforce escalations.

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

Title:
  superblock checksum mismatch in resize2fs

Status in cloud-images:
  New
Status in e2fsprogs package in Ubuntu:
  Confirmed
Status in e2fsprogs source package in Focal:
  New
Status in e2fsprogs source package in Jammy:
  New
Status in e2fsprogs source package in Mantic:
  Confirmed

Bug description:
  Hi,
  We run ext4 on EBS volumes on EC2.  During provisioning, cloud-init will 
occasionally report that resize2fs has failed due to a superblock checksum 
mismatch.  We debugged this internally, and were able to come up with the 
following reproducer:

 #!/usr/bin/bash
 set -euxo pipefail

 while true
 do
 parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s
 sleep .5
 mkfs.ext4 /dev/nvme1n1p1
 mount -t ext4 /dev/nvme1n1p1 /mnt
 stress-ng --temp-path /mnt -D 4 &
 STRESS_PID=$!
 sleep 1
 growpart /dev/nvme1n1 1
 resize2fs /dev/nvme1n1p1
 kill $STRESS_PID
 wait $STRESS_PID
 umount /mnt
 wipefs -a /dev/nvme1n1p1
 wipefs -a /dev/nvme1n1
 done

  (This was on a 60gb gp3 volume attached to a c5.4xlarge)

  We were able to find a fix that works and get the patch accepted
  upstream.  The short explanation is that by switching the superblock
  read to direct io, we no longer see the problem.

  The patch is available here, but hasn't been published in a released
  version of e2fsprogs:

  
https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84

  A longer thread with the maintainer is available here:

  https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/

  This bug report is to request that Ubuntu backport this patch to the
  versions of e2fsprogs that are in releases that are available in
  images on AWS, preferably Focal and Jammy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2036467/+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 2038590] [NEW] Wget --rejected-log=file never logs anything

2023-10-05 Thread Charles Evans

Public bug reported:

Wget jammy 1.21.2-2ubuntu1
404 errors etc. are not written to log file
File is never created.

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

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

Title:
  Wget --rejected-log=file  never logs anything

Status in wget package in Ubuntu:
  New

Bug description:
  Wget jammy 1.21.2-2ubuntu1
  404 errors etc. are not written to log file
  File is never created.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wget/+bug/2038590/+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 2038580] [NEW] Brightness adjustments are not working.

2023-10-05 Thread Karthikeyan

Public bug reported:

 Brightness doesn't change. The slide for brightness doesn't change the
level of brightness.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-34-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct  5 17:55:28 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 NVIDIA Corporation TU117M [10de:1f99] (rev ff) (prog-if ff)
 Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c7) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo Renoir [17aa:3a45]
InstallationDate: Installed on 2023-08-04 (62 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
MachineType: LENOVO 82EY
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic 
root=UUID=f8eb5f8e-6d3d-40ca-93b4-00ac9e7df7a9 ro quiet splash 
acpi_backlight=vendor acpi_osi=linux vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/14/2022
dmi.bios.release: 1.18
dmi.bios.vendor: LENOVO
dmi.bios.version: FCCN18WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0Q55724 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad Gaming 3 15ARH05
dmi.ec.firmware.release: 1.18
dmi.modalias: 
dmi:bvnLENOVO:bvrFCCN18WW:bd04/14/2022:br1.18:efr1.18:svnLENOVO:pn82EY:pvrIdeaPadGaming315ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrIdeaPadGaming315ARH05:skuLENOVO_MT_82EY_BU_idea_FM_IdeaPadGaming315ARH05:
dmi.product.family: IdeaPad Gaming 3 15ARH05
dmi.product.name: 82EY
dmi.product.sku: LENOVO_MT_82EY_BU_idea_FM_IdeaPad Gaming 3 15ARH05
dmi.product.version: IdeaPad Gaming 3 15ARH05
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
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/2038580

Title:
  Brightness adjustments are not working.

Status in xorg package in Ubuntu:
  New

Bug description:
   Brightness doesn't change. The slide for brightness doesn't change
  the level of brightness.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  5 17:55:28 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   NVIDIA Corporation TU117M [10de:1f99] (rev ff) (prog-if ff)
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c7) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Renoir [17aa:3a45]
  InstallationDate: Installed on 2023-08-04 (62 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  MachineType: LENOVO 82EY
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic 
root=UUID=f8eb5f8e-6d3d-40ca-93b4-00ac9e7df7a9 ro quiet splash 
acpi_backlight=vendor acpi_osi=linux vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2022
  dmi.bios.release: 1.18
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FCCN18WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55724 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10

[Touch-packages] [Bug 2038567] Re: Mantic 6.5.0-7 kernel causes regression in LXD container usage

2023-10-05 Thread John Johansen

Oct 05 21:25:27 novel-ram kernel: audit: type=1400
audit(1696541127.240:6185): apparmor="DENIED" operation="ptrace"
class="ptrace" profile="lxd-current-iguana_"
pid=12702 comm="systemctl" requested_mask="read" denied_mask="read"
peer="lxd-current-iguana_//"

indicates 1ea37b26d720 UBUNTU: SAUCE: apparmor4.0.0 [73/76]: userns -
allow restricting unprivileged change_profile

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

Title:
  Mantic 6.5.0-7 kernel causes regression in LXD container usage

Status in Release Notes for Ubuntu:
  New
Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in lxd package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  Following upgrade to 6.5.0-7 kernel in mantic cloud images we are
  seeing a regression in our cloud image tests. The test runs the
  following:

  ```
  lxd init --auto --storage-backend dir
  lxc launch ubuntu-daily:mantic mantic
  lxc info mantic
  lxc exec mantic -- cloud-init status --wait
  ```

  The `lxc exec mantic -- cloud-init status --wait` times out after 240s
  and will fail our test as a result.

  I have been able to replicate in a local VM

  ```
  wget 
http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img 
  wget --output-document=launch-qcow2-image-qemu.sh 
https://gist.githubusercontent.com/philroche/14c241c086a5730481e24178b654268f/raw/7af95cd4dfc8e1d0600e6118803d2c866765714e/gistfile1.txt
 
  chmod +x launch-qcow2-image-qemu.sh 

  ./launch-qcow2-image-qemu.sh --password passw0rd --image 
./mantic-server-cloudimg-amd64.img 
  cat < "./reproducer.sh"
  #!/bin/bash -eux
  lxd init --auto --storage-backend dir
  lxc launch ubuntu-daily:mantic mantic
  lxc info mantic
  lxc exec mantic -- cloud-init status --wait
  EOF
  chmod +x ./reproducer.sh
  sshpass -p passw0rd scp -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -P  ./reproducer.sh ubuntu@127.0.0.1:~/
  sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -p  ubuntu@127.0.0.1 sudo apt-get update
  sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -p  ubuntu@127.0.0.1 sudo apt-get upgrade 
--assume-yes
  sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -p  ubuntu@127.0.0.1 ./reproducer.sh
  ```

  The issue is not present with the 6.5.0-5 kernel and the issue is
  present regardless of the container launched. I tried the jammy
  container to test this.

  From my test VM

  ```
  ubuntu@cloudimg:~$ uname --all
  Linux cloudimg 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 29 
09:14:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
  ubuntu@cloudimg:~$ uname --kernel-release
  6.5.0-7-generic
  ```

  This is a regression in our test that will block 23.10 cloud image
  release next week.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038567/+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 2038567] Re: Mantic 6.5.0-7 kernel causes regression in LXD container usage

2023-10-05 Thread John Chittum

apd restart...

..
Copy snap "lxd" data

2023-10-05T21:34:56Z ERROR unlinkat
/var/snap/lxd/common/var/lib/lxcfs/proc/cpuinfo: function not
implemented

..
Run install hook of "lxd" snap if present

2023-10-05T21:34:55Z ERROR run hook "install": cannot read mount
namespace identifier of pid 1: Permission denied

# on mantic host
Oct 05 21:34:58 novel-ram kernel: kauditd_printk_skb: 212 callbacks suppressed
Oct 05 21:34:58 novel-ram kernel: audit: type=1400 audit(1696541698.251:8146): 
apparmor="DENIED" operation="ptrace" class="ptrace" 
profile="lxd-current-iguana_" pid=15416 
comm="systemd" requested_mask="read" denied_mask="read" 
peer="lxd-current-iguana_//"
Oct 05 21:34:58 novel-ram kernel: audit: type=1400 audit(1696541698.279:8147): 
apparmor="DENIED" operation="ptrace" class="ptrace" 
profile="lxd-current-iguana_" pid=15478 
comm="systemd-journal" requested_mask="read" denied_mask="read" 
peer="lxd-current-iguana_//"
Oct 05 21:34:58 novel-ram kernel: audit: type=1400 audit(1696541698.279:8148): 
apparmor="DENIED" operation="ptrace" class="ptrace" 
profile="lxd-current-iguana_" pid=15478 
comm="systemd-journal" requested_mask="read" denied_mask="read" 
peer="lxd-current-iguana_//"
Oct 05 21:34:58 novel-ram kernel: audit: type=1400 audit(1696541698.287:8149): 
apparmor="DENIED" operation="signal" class="signal" 
profile="lxd-current-iguana_" pid=16486 comm="snapd" 
requested_mask="send" denied_mask="send" signal=urg 
peer="lxd-current-iguana_//"
Oct 05 21:34:58 novel-ram kernel: audit: type=1400 audit(1696541698.443:8150): 
apparmor="DENIED" operation="ptrace" class="ptrace" 
profile="lxd-current-iguana_" pid=15478 
comm="systemd-journal" requested_mask="read" denied_mask="read" 
peer="lxd-current-iguana_//"
Oct 05 21:34:58 novel-ram kernel: audit: type=1400 audit(1696541698.443:8151): 
apparmor="DENIED" operation="ptrace" class="ptrace" 
profile="lxd-current-iguana_" pid=15478 
comm="systemd-journal" requested_mask="read" denied_mask="read" 
peer="lxd-current-iguana_//"
Oct 05 21:34:58 novel-ram kernel: audit: type=1400 audit(1696541698.467:8152): 
apparmor="DENIED" operation="ptrace" class="ptrace" 
profile="lxd-current-iguana_" pid=16529 
comm="systemctl" requested_mask="read" denied_mask="read" 
peer="lxd-current-iguana_//"
Oct 05 21:34:58 novel-ram kernel: audit: type=1400 audit(1696541698.519:8153): 
apparmor="DENIED" operation="signal" class="signal" 
profile="lxd-current-iguana_" pid=15416 
comm="systemd" requested_mask="send" denied_mask="send" signal=exists 
peer="lxd-current-iguana_//"
Oct 05 21:34:58 novel-ram kernel: audit: type=1400 audit(1696541698.523:8154): 
apparmor="DENIED" operation="ptrace" class="ptrace" 
profile="lxd-current-iguana_" pid=16531 
comm="systemctl" requested_mask="read" denied_mask="read" 
peer="lxd-current-iguana_//"
Oct 05 21:34:58 novel-ram kernel: audit: type=1400 audit(1696541698.527:8155): 
apparmor="DENIED" operation="ptrace" class="ptrace" 
profile="lxd-current-iguana_" pid=16532 
comm="systemctl" requested_mask="read" denied_mask="read" 
peer="lxd-current-iguana_//"
Oct 05 21:35:04 novel-ram kernel: kauditd_printk_skb: 41 callbacks suppressed
Oct 05 21:35:04 novel-ram kernel: audit: type=1400 audit(1696541704.007:8197): 
apparmor="DENIED" operation="signal" class="signal" 
profile="lxd-current-iguana_" pid=16567 comm="snap" 
requested_mask="send" denied_mask="send" signal=urg 
peer="lxd-current-iguana_//"
Oct 05 21:35:11 novel-ram kernel: audit: type=1400 audit(1696541711.031:8198): 
apparmor="DENIED" operation="signal" class="signal" 
profile="lxd-current-iguana_" pid=15677 comm="snap" 
requested_mask="send" denied_mask="send" signal=urg 
peer="lxd-current-iguana_//"
Oct 05 21:35:14 novel-ram kernel: audit: type=1400 audit(1696541714.915:8199): 
apparmor="DENIED" operation="ptrace" class="ptrace" 
profile="l

[Touch-packages] [Bug 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems

** Changed in: util-linux (Ubuntu Mantic)
Milestone: None => ubuntu-23.10

** Also affects: ubuntu-release-notes
   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/2037417

Title:
  mantic images after 20230917 are failing to deploy with failure to
  mount root and kernel filesystems

Status in maas-images:
  New
Status in The Ubuntu-power-systems project:
  Confirmed
Status in Release Notes for Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  New
Status in linux source package in Mantic:
  Incomplete
Status in systemd source package in Mantic:
  Confirmed
Status in util-linux source package in Mantic:
  New

Bug description:
  Mantic arm64 deploys started failing on Sept 18th with:

  [   41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root 
and Kernel File Systems...
   Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File 
Systems...
  [   41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug 
All udev Devices...
   Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev 
Devices...
  [   41.964758] systemd[1]: Started systemd-journald.service - Journal Service.
  [[0;32m  OK  [0m] Started [0;1;39msystemd-journald.service[0m - Journal 
Service.
  [[0;32m  OK  [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages 
File System.
  [[0;32m  OK  [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message 
Queue File System.
  [[0;32m  OK  [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug 
File System.
  [[0;32m  OK  [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace 
File System.
  [[0;32m  OK  [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console 
keyboard layout.
  [[0;32m  OK  [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static 
Device Nodes.
  [[0;32m  OK  [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or 
progress polling.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel 
Module configfs.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel 
Module dm_mod.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel 
Module drm.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel 
Module efi_pstore.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel 
Module fuse.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel 
Module loop.
  [[0;32m  OK  [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load 
Kernel Modules.
  [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and 
Kernel File Systems.
  See 'systemctl status systemd-remount-fs.service' for details.

  After this many other services and cloud-init fails. See the full
  kopter-0918.log. For comparison, a log from the prior day's test is
  also attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas-images/+bug/2037417/+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 2038567] Re: Mantic 6.5.0-7 kernel causes regression in LXD container usage

2023-10-05 Thread John Johansen

apparmor side there are 2 immediate suspects.

1. kernel
0191e8433f76 UBUNTU: SAUCE: apparmor4.0.0: apparmor: Fix regression in mount 
mediation


2. userspace mount work to fix the mount CVE 
https://bugs.launchpad.net/apparmor/+bug/1597017

https://gitlab.com/apparmor/apparmor/-/merge_requests/1054

https://gitlab.com/apparmor/apparmor/-/merge_requests/333


I doubt #2 as this has been in the apparmor userspace in mantic since before FF.

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

Title:
  Mantic 6.5.0-7 kernel causes regression in LXD container usage

Status in Release Notes for Ubuntu:
  New
Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in lxd package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  Following upgrade to 6.5.0-7 kernel in mantic cloud images we are
  seeing a regression in our cloud image tests. The test runs the
  following:

  ```
  lxd init --auto --storage-backend dir
  lxc launch ubuntu-daily:mantic mantic
  lxc info mantic
  lxc exec mantic -- cloud-init status --wait
  ```

  The `lxc exec mantic -- cloud-init status --wait` times out after 240s
  and will fail our test as a result.

  I have been able to replicate in a local VM

  ```
  wget 
http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img 
  wget --output-document=launch-qcow2-image-qemu.sh 
https://gist.githubusercontent.com/philroche/14c241c086a5730481e24178b654268f/raw/7af95cd4dfc8e1d0600e6118803d2c866765714e/gistfile1.txt
 
  chmod +x launch-qcow2-image-qemu.sh 

  ./launch-qcow2-image-qemu.sh --password passw0rd --image 
./mantic-server-cloudimg-amd64.img 
  cat < "./reproducer.sh"
  #!/bin/bash -eux
  lxd init --auto --storage-backend dir
  lxc launch ubuntu-daily:mantic mantic
  lxc info mantic
  lxc exec mantic -- cloud-init status --wait
  EOF
  chmod +x ./reproducer.sh
  sshpass -p passw0rd scp -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -P  ./reproducer.sh ubuntu@127.0.0.1:~/
  sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -p  ubuntu@127.0.0.1 sudo apt-get update
  sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -p  ubuntu@127.0.0.1 sudo apt-get upgrade 
--assume-yes
  sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -p  ubuntu@127.0.0.1 ./reproducer.sh
  ```

  The issue is not present with the 6.5.0-5 kernel and the issue is
  present regardless of the container launched. I tried the jammy
  container to test this.

  From my test VM

  ```
  ubuntu@cloudimg:~$ uname --all
  Linux cloudimg 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 29 
09:14:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
  ubuntu@cloudimg:~$ uname --kernel-release
  6.5.0-7-generic
  ```

  This is a regression in our test that will block 23.10 cloud image
  release next week.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038567/+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 1302932] Re: libpgm fails to recognize eth0

2023-10-05 Thread Bug Watch Updater

** Changed in: openpgm
   Status: Unknown => New

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

Title:
  libpgm fails to recognize eth0

Status in OpenPGM:
  New
Status in libpgm package in Ubuntu:
  New

Bug description:
  Please see https://code.google.com/p/openpgm/issues/detail?id=34

  Since it will be resolved in a future version of libpgm, we need a
  quick fix for now.

  All machines in my company with Ubuntu 14.04 beta installed yield this
  bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openpgm/+bug/1302932/+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 2025176] Re: External hard disk fails to automount in /etc/fstab with message FEATURE_C12

2023-10-05 Thread Pablo

I had built a 23.04 server just to explore the stuff that will be coming
with the next LTS. Shortly afterwards, I had hard drive failures on 2
22.04 LTS systems (both raid1). I decided to use the 23.04 server (also
raid1) for recovery. I created LV's with ext4 fs and copied over the
data from the degraded arrays. I tried to change the 23.04 network to
bridge using the exact procedure that worked flawlessly with 22.04. It
killed networking each time. So I installed 22.04 using the "keep
existing disk layout" method. I did not allow formatting of  the LV's
with data recovered from the degraded raid arrays. Things were looking
good after reboot until I added those volumes to /etc/fstab (with fsck
2nd pass option). On next reboot I discovered this bug. I think it could
be a showstopper for some folks. I now have all that data on volumes
that were reformatted with 22.04 LTS. When 23.10 is released I will
explore it on a VM carefully. I definitely will stick to LTS for backup
storage, nfs, etc. in the future. I think this bug should be assigned an
appropriate importance. I worked around the problem carefully but I can
see how it might cause panic and/or confusion for others and result in
loss of data.

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

Title:
  External hard disk fails to automount in /etc/fstab with message
  FEATURE_C12

Status in e2fsprogs package in Ubuntu:
  Confirmed

Bug description:
  I am having a problem with auto mounting an external 14TB 3.5" hard
  disk on Ubuntu 22.04 (arm64) (arm board). The drive is formatted using
  ext4 however this was done on a amd64 based Ubuntu 23.04 install
  (laptop).

  I tried to automount on the 22.04 install by using /etc/fstab, however
  the system would then fail to boot, entering emergency mode.

  Terminal output:
  [FAILED]: Failed to start File System Check on 
/dev/disk/by-uuuid/xx-xx-xx-xx-xx
  See 'systemctl status "systemd-fsck@dev-disk-by\\xx\\xx\\xx\\xx\\xx'
  [DEPEND] Dependency failed for /mnt/share/external_14tb_drive

  The particular error is:
  /dev/xxx has unsupported feature(s): FEATURE_C12

  /etc/fstab
  UUID=xx-xx-xx-xx-xx /mnt/share/external_14tb_drive ext4 
defaults,noatime,nofail  0   2

  arm board description:Ubuntu 22.04.2 LTS
  Release:  22.04

  apt-cache policy e2fsprogs
  e2fsprogs:
Installed: 1.46.5-2ubuntu1.1
Candidate: 1.46.5-2ubuntu1.1
Version table:
   *** 1.46.5-2ubuntu1.1 500
  500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 
Packages
  500 http://ports.ubuntu.com/ubuntu-ports jammy-security/main arm64 
Packages
  100 /var/lib/dpkg/status
   1.46.5-2ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages

  apt-cache policy util-linux
  util-linux:
    Installed: 2.37.2-4ubuntu3
    Candidate: 2.37.2-4ubuntu3
    Version table:
   *** 2.37.2-4ubuntu3 500
  500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages
  100 /var/lib/dpkg/status

  Laptop description:   Ubuntu 23.04
  Release:  23.04

  apt-cache policy e2fsprogs
  e2fsprogs:
Installed: 1.47.0-1ubuntu1
Candidate: 1.47.0-1ubuntu1
Version table:
   *** 1.47.0-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  100 /var/lib/dpkg/status

  util-linux:
    Installed: 2.38.1-4ubuntu1
    Candidate: 2.38.1-4ubuntu1
    Version table:
   *** 2.38.1-4ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  100 /var/lib/dpkg/status

  The only option I have is to manually mount it after boot which is not
  convenient as it a server board.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: util-linux 2.37.2-4ubuntu3
  Uname: Linux 5.10.110-rockchip-rk3588 aarch64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Tue Jun 27 19:38:40 2023
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2025176/+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 1994165] Re: CMS_final: do not ignore CMS_dataFinal result

Ah, I noticed that this is part of a big SRU that's being completed on
bug #2033422.  Just leaving a comment here for the record.

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

Title:
  CMS_final: do not ignore CMS_dataFinal result

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Jammy:
  In Progress
Status in openssl source package in Kinetic:
  Won't Fix
Status in openssl source package in Lunar:
  Fix Released

Bug description:
  === SRU information ===
  [Meta]
  This bug is part of a series of four bugs for a single SRU.
  The "central" bug with the global information and debdiff is 
http://pad.lv/2033422

  [Impact]
  S/MIME signature can fail silently
  The commit by upstream propagates the return code of some functions rather 
than ignore it.

  [Test plan]
  This issue is not very simple to reproduce because "openssl cms" cannot be 
used to do so. This has to be done with the openssl API instead.
  At least the bug reportere here and the one on openssl's bug tracker have 
confirmed the patch solves the issue. Additionally, the bug reporter here has 
tested the PPA that contains the patche and validated it. Finally, I read 
through the patch attentively.

  [Where problems could occur]
  At this point it is unlikely an error would appear. The openssl bug tracker 
mentions nothing related to this patch which landed more than a year ago. The 
patch is simple and doesn't change the code logic.

  [Patches]
  The patches come directly from upstream and apply cleanly.

  https://github.com/openssl/openssl/pull/18876

  * 
https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-sru-0001-REGRESSION-CMS_final-do-not-ignore-CMS_dataFinal-res.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0
  * 
https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-sru-0002-Handle-SMIME_crlf_copy-return-code.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0

  === Original description ===

  https://github.com/openssl/openssl/pull/18876

  The CMS_dataFinal result is important as signature may fail, however, it
  is ignored while returning success from CMS_final.

  Please add this fix to The openssl 3.0.2 "Jammy Jellyfish (supported)"

  Thanks

  Upstream commit:

  ```
  commit 67c0460b89cc1b0644a1a59af78284dfd8d720af
  Author: Alon Bar-Lev 
  Date:   Tue Jul 26 15:17:06 2022 +0300

  Handle SMIME_crlf_copy return code

  Currently the SMIME_crlf_copy result is ignored in all usages. It does
  return failure when memory allocation fails.

  This patch handles the SMIME_crlf_copy return code in all
  occurrences.

  Signed-off-by: Alon Bar-Lev 

  Reviewed-by: Tomas Mraz 
  Reviewed-by: Paul Dale 
  Reviewed-by: Hugo Landau 
  (Merged from https://github.com/openssl/openssl/pull/18876)
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1994165/+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 1990216] Re: backport fix for "OpenSSL 3 cannot decrypt data encrypted with OpenSSL 1.1 with blowfish in OFB or CFB modes" to Jammy

Ah, I noticed that this is part of a big SRU that's being completed on
bug #2033422.  Just leaving a comment here for the record.

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

Title:
  backport fix for "OpenSSL 3 cannot decrypt data encrypted with OpenSSL
  1.1 with blowfish in OFB or CFB modes" to Jammy

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Jammy:
  In Progress
Status in openssl source package in Lunar:
  Fix Released

Bug description:
  === SRU information ===
  [Meta]
  This bug is part of a series of four bugs for a single SRU.
  The "central" bug with the global information and debdiff is 
http://pad.lv/2033422

  [Impact]
  Decryption for Blowfish with OFB and CFB modes fails due to using a key 
shorter than expected by default.
  Encryption will also use a key shorter than expected.
  Exchange of encrypted data from/to Jammy using BF OFB/CFB will therefore lead 
to decryption issues.

  [Test plan]
  On Focal, run the following and copy the output to your clipboard

  for cipher in bf-cbc bf-cfb bf-ecb bf-ofb; do  echo "Test with ${cipher}" 
| openssl enc -${cipher} -k test -pbkdf2 -out "pouet.${cipher}"; done
  tar c pouet.bf-* | xz | base64 -w 60

  You can also run this on Lunar or Mantic if you add "-provider legacy
  -provider default" to the "openssl enc" invocation.

  On Jammy, run the following and paste your clipboard

  base64 -d | xz -d | tar x
  for cipher in bf-cbc bf-cfb bf-ecb bf-ofb; do openssl enc -d -provider 
legacy -provider default -${cipher} -k test -pbkdf2 -d -in "pouet.${cipher}"; 
done

  Only "Test with bf-cbc" and "Test with bf-ecb" will be properly
  decrypted: the other two will result in garbage on screen.

  Here is the result of the enc + tar + xz + base64 on Focal (works with
  Lunar/Mantic too but you need to added ):

  /Td6WFoAAATm1rRGAgAhARYAAAB0L+Wj4Cf/ARBdADgbyxDlZ/1Xd7bAmZw7
  8pbqQTu5j8StVybo1p1B2ydBc5VcodF6fu0hEp801tvirgSFNMSAHk5HMN/w
  hCgU1BIr/nK51g3A3Lkdv7QNbaUw2ux1AmO/MpCLKLffCB9ElFZH4tuOS5AR
  m9CJMzi6LQOw9wytGKm2IK3Ph7WpU6JQ/3HJilffQwHbFLnukiWGpLNO5v0O
  D/4AJikrU9iemfChT0jXDbIRZ8a8VpVhJqu0u6eYOheVTqmSRiHHpIC/p1VA
  ecFb0mACF/TQhjxcMUWGSGO/mtof+VaLiyg0KB87GKlChfwXTEvgbNuP9hmu
  GL64VhX568Oy9EakSxlcXiIRk14kJKv0MdHQqY1R22wAACzqSr/nzpwqAAGs
  AoBQAACjzq5WscRn+wIABFla

  Here is the same but from Jammy if you want to test encryption on
  Jammy and decryption on Lunar/Mantic:

  /Td6WFoAAATm1rRGAgAhARYAAAB0L+Wj4Cf/ARFdADgbyxDlZ/1Xd7bAmZw7
  8pbqQTu5j8StVybo1p1B2ydBc1zK4HR2g3CiLJet+R++nZy/gph6RscQ6hI3
  HySjdDOFRfjIVttiNK3DvRsZb37r8SXkj/JCYWicZGjWPZxVE3OAZhEed5qe
  jrFv871QAbm4jVGD4oIc4cOb5V/xDN7KWgwEzpWQy6+tcfPm3KLPQvULx56N
  2qQf60hP//p5EXS3RpCitUsrGUoYzTynjOUIRy2yCmgZDh62RmchUshyWePa
  k0nEYlDbl5/dSHXbWEWESqW+QDj136MZRwQRY+QC4MvLXg2Bo8H+Dl/xvNDF
  /5J4layZdFlh76lWOtFRVoIbX6JtpAP34g4zx1422GSNAABRzyqPdCqX
  1AABrQKAUAAABh3ynbHEZ/sCAARZWg==

  The contents are expected to be different due to the use of
  randomness. Don't try to compare the base64 outputs: I'm only using
  them to ease testing across containers.

  [Where problems could occur]
  This patch makes openssl match the documented default (see "man openssl-enc" 
and search for "Blowfish" for instance) and fixes decryption from an up-to-date 
Jammy to pretty much everything else, but it also create an issue for data 
encrypted on Jammy without this patch and Jammy with this patch.

  There are two possible cases: encrypted data being streamed across
  this boundary or data at rest being transferred or read later.

  Streaming is probably not an issue in practice because it's rather the
  current situation that has been an issue and it's easy to remedy by
  updating everything (which is relatively few machines since that's
  only Jammy and not any other OS or distribution).

  Data at rest is more annoying since updating Jammy will make it
  impossible to read the data again without updates to other pieces of
  software. That sounds like a really bad thing and it kind of is but at
  the same, the benefits are much larger than the issues. Indeed, there
  is already an incompatibility at the moment between Jammy and
  everything else and the more time passes by, the more such problematic
  files can be created. Luckily very few people are using blowfish
  nowadays and it's not even enabled by default anymore in openssl.
  Moreover the software update to work around the issue should be a
  single API call which is documented in the upstream bug report (
  https://github.com/openssl/openssl/issues/18359 ). Finally, I have
  warned the two projects that I am aware are impacted; this is made
  easier by the fact that they encountered the initial incompatibility.

  [Patches]
  The patches come directly from upstream and apply

[Touch-packages] [Bug 2036467] Re: superblock checksum mismatch in resize2fs

2023-10-05 Thread Robby Pocase

@Krister additionally, can you clarify "occasionally"? It's clearly
frequently enough to prioritize upstreaming a fix. Knowing frequency
could aide in priority internally.

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

Title:
  superblock checksum mismatch in resize2fs

Status in cloud-images:
  New
Status in e2fsprogs package in Ubuntu:
  Confirmed
Status in e2fsprogs source package in Focal:
  New
Status in e2fsprogs source package in Jammy:
  New
Status in e2fsprogs source package in Mantic:
  Confirmed

Bug description:
  Hi,
  We run ext4 on EBS volumes on EC2.  During provisioning, cloud-init will 
occasionally report that resize2fs has failed due to a superblock checksum 
mismatch.  We debugged this internally, and were able to come up with the 
following reproducer:

 #!/usr/bin/bash
 set -euxo pipefail

 while true
 do
 parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s
 sleep .5
 mkfs.ext4 /dev/nvme1n1p1
 mount -t ext4 /dev/nvme1n1p1 /mnt
 stress-ng --temp-path /mnt -D 4 &
 STRESS_PID=$!
 sleep 1
 growpart /dev/nvme1n1 1
 resize2fs /dev/nvme1n1p1
 kill $STRESS_PID
 wait $STRESS_PID
 umount /mnt
 wipefs -a /dev/nvme1n1p1
 wipefs -a /dev/nvme1n1
 done

  (This was on a 60gb gp3 volume attached to a c5.4xlarge)

  We were able to find a fix that works and get the patch accepted
  upstream.  The short explanation is that by switching the superblock
  read to direct io, we no longer see the problem.

  The patch is available here, but hasn't been published in a released
  version of e2fsprogs:

  
https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84

  A longer thread with the maintainer is available here:

  https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/

  This bug report is to request that Ubuntu backport this patch to the
  versions of e2fsprogs that are in releases that are available in
  images on AWS, preferably Focal and Jammy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2036467/+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 2033422] Re: openssl: backport to jammy "clear method store / query cache confusion"

Thanks for the contribution, Adrien.

I find the naming scheme you chose for the patches a bit confusing. For
example, you're using the prefix "jammy-sru-0001-" on several patches
that are actually not strictly related. You also don't mention any
patch explicitly in the d/changelog entry, which forces the reader to
open d/p/series and look at the comments there. Moreover, the patches
are missing DEP-3 headers (which, in this case, would be very useful
when trying to understand the context when looking at a single patch).

Could you please address the concerns above before we proceed with the
upload?

Thanks.

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

Title:
openssl: backport to jammy "clear method store / query cache
confusion"

Status in openssl package in Ubuntu:
New
Status in openssl source package in Jammy:
In Progress
Status in openssl source package in Lunar:
Fix Released

Bug description:
=== SRU information ===
[Meta]
This bug is part of a series of four bugs for a single SRU.
This ( #2033422 ) is the "central" bug with the global information and
debdiff.

This SRU addresses four issues with Jammy's openssl version:
- http://pad.lv/1990216: Blowfish OFB/CFB decryption
- http://pad.lv/1994165: ignored SMIME signature errors
- http://pad.lv/2023545: imbca engine dumps core
- http://pad.lv/2033422: very high CPU usage for concurrent TLS connections

The SRU information has been added to the four bug reports and I am
attaching the debdiff here only for all four.

All the patches have been included in subsequent openssl 3.0.x
releases which in turn have been included in subsequent Ubuntu
releases. There has been no report of issues when updating to these
Ubuntu releases.

I have rebuilt the openssl versions and used abi-compliance-checker to
compare the ABIs of the libraries in jammy and the one for the SRU.
Both matched completely (FYI, mantic's matched completely too).

The patch related to blowfish presents an annoying situation: jammy's openssl
creates incompatible files and cannot read other files but fixing it will lead
to files created on jammy so far to become unreadable. Fortunately, blowfish is
long-deprecated and applications can be improved to handle this situation if
the need arises in practice.
This is stated in the SRU information in the bug and in d/changelog.
The current situation in Jammy could be a security issue but due to the
aforementioned deprecation, the low usage of blowfish and the fact that
upstream didn't consider this worthy of a security notice, we (this includes
the security team) chose not to pursue that path either.

I have also pushed the code to git (without any attempt to make it
git-ubuntu friendly).

https://code.launchpad.net/~adrien-n/ubuntu/+source/openssl/+git/openssl/+ref/jammy-
sru

I asked Brian Murray about phasing speed and he concurs a slow roll-out is
probably better for openssl. There is a small uncertainty because a security
update could come before the phasing is over, effectively fast-forwarding the
SRU. Still, unless there is already a current pre-advisory, this is probably
better than a 10% phasing which is over after only a couple days anyway.
NB: at the moment openssl doesn't phase slowly so this needs to be
implemented.

[Impact]
Severely degraded performance for concurrent operations compared to openssl
1.1. The performance is so degraded that some workloads fail due to timeouts or
insufficient resources (noone magically has 5 times more machines). As a
consequence, a number of people use openssl 1.1 instead and do not get security
updates.

[Test plan]
Rafael Lopez has shared a simple benchmarks in http://pad.lv/2009544 with
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2009544/+attachment/5690224/+files/main.py
.
Using this, I get the following numbers on my laptop:

3.0.2:
real 2m5.567s
user 4m3.948s
sys 2m0.233s

this SRU:
real 0m23.966s
user 2m35.687s
sys 0m1.920s

As can be easily seen, the speed-up is massive: system time is divided
by 60 and overall wall clock time is roughly five times lower.

In http://pad.lv/2009544 , Rafael also shared his performance numbers
and they are relatable to these. He used slightly different versions
(upstreams rather than patched with cherry-picks) but at least one of
the version used does not include other performance change. He also
used different hardware and this performance issue seems to depend on
the number of CPUs available but also obtained a performance several
times better. Results on a given machine vary also very little across
runs (less than 2% variation on runs of size 10). They are also very
similar on a Raspberry Pi 4 (8GB).

The benchmark uses https://www.google.com/humans.txt

[Touch-packages] [Bug 2031340] Re: slic3r-prusa autopkgtest flaky

2023-10-05 Thread Vladimir Petko

I have added a build watch script to output to the terminal, but s390x still 
failed:
https://launchpad.net/~vpa1977/+archive/ubuntu/plusone/+sourcepub/15186846/+listing-archive-extra
Looks like one of the tests is getting stuck, I will try to debug it.

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

Title:
  slic3r-prusa autopkgtest flaky

Status in fontconfig package in Ubuntu:
  Fix Released
Status in gmp package in Ubuntu:
  Fix Released
Status in nlopt package in Ubuntu:
  Fix Released
Status in slic3r-prusa package in Ubuntu:
  New

Bug description:
  autopkgtest was added to slic3r-prusa as late as last April. They have
  never let version 2.6.0 of slic3r-prusa migrate to Debian testing, and
  seemingly need more work. slic3r-prusa 2.6.0+dfsg-2 was uploaded to
  unstable on July 27 but hasn't migrated to testing yet due to failing
  autopkgtest.

  In Ubuntu the flaky tests currently prevent fontconfig and nlopt (in
  addition to slic3r-prusa itself) from migrating to mantic-release.
  Probably some kind of hint is motivated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2031340/+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 2038567] Re: Mantic 6.5.0-7 kernel causes regression in LXD container usage

Current suspects are out of date apparmor features in livecd-rootfs
pending https://launchpad.net/ubuntu/+source/livecd-rootfs/23.10.55

kernel, apparmor, snapd, lxd, snapd again having fits about all of them
because of:

..
Make snap "snapd" (20092) available to the system

2023-10-05T19:04:57Z INFO Requested daemon restart (snapd snap).

..
Copy snap "lxd" data

2023-10-05T19:04:56Z ERROR unlinkat
/var/snap/lxd/common/var/lib/lxcfs/proc/cpuinfo: function not
implemented

..
Run install hook of "lxd" snap if present

2023-10-05T19:04:55Z ERROR run hook "install": cannot read mount
namespace identifier of pid 1: Permission denied


and also because of:

Oct 05 19:21:39 mantic-con-priv systemd[1]: snapd.service: Got notification 
message from PID 2560, but reception only permitted for main PID 2338
Oct 05 19:21:39 mantic-con-priv snapd[2338]: taskrunner.go:299: [change 7 
"Setup snap \"snapd\" (20092) security profiles" task] failed: cannot reload 
udev rules: exit status 1
Oct 05 19:21:39 mantic-con-priv snapd[2338]: udev output:
Oct 05 19:21:39 mantic-con-priv snapd[2338]: Failed to send reload request: No 
such file or directory
Oct 05 19:21:39 mantic-con-priv systemd[1]: snap-snapd-20092.mount: Deactivated 
successfully.
Oct 05 19:21:39 mantic-con-priv systemd[1]: snap-snapd-20092.mount: Unit 
process 2559 (snapfuse) remains running after unit stopped.
Oct 05 19:21:39 mantic-con-priv systemd[1]: Reloading requested from client PID 
2565 (unit snapd.service)...
Oct 05 19:21:39 mantic-con-priv systemd[1]: Reloading...
Oct 05 19:21:39 mantic-con-priv (sd-gens)[2568]: Read-only bind remount failed, 
ignoring: Permission denied


and because of:

Oct 05 19:20:58 cloudimg kernel: audit: type=1400
audit(1696533658.780:276): apparmor="DENIED" operation="mount"
class="mount" info="failed type match" error=-13 profile="lxd-dominant-
goldfish_" name="/snap/" pid=1940 comm="(sd-
gens)" flags="ro, remount, bind"

but could be util-linux too

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

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

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

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

Title:
  Mantic 6.5.0-7 kernel causes regression in LXD container usage

Status in Release Notes for Ubuntu:
  New
Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in lxd package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  Following upgrade to 6.5.0-7 kernel in mantic cloud images we are
  seeing a regression in our cloud image tests. The test runs the
  following:

  ```
  lxd init --auto --storage-backend dir
  lxc launch ubuntu-daily:mantic mantic
  lxc info mantic
  lxc exec mantic -- cloud-init status --wait
  ```

  The `lxc exec mantic -- cloud-init status --wait` times out after 240s
  and will fail our test as a result.

  I have been able to replicate in a local VM

  ```
  wget 
http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img 
  wget --output-document=launch-qcow2-image-qemu.sh 
https://gist.githubusercontent.com/philroche/14c241c086a5730481e24178b654268f/raw/7af95cd4dfc8e1d0600e6118803d2c866765714e/gistfile1.txt
 
  chmod +x launch-qcow2-image-qemu.sh 

  ./launch-qcow2-image-qemu.sh --password passw0rd --image 
./mantic-server-cloudimg-amd64.img 
  cat < "./reproducer.sh"
  #!/bin/bash -eux
  lxd init --auto --storage-backend dir
  lxc launch ubuntu-daily:mantic mantic
  lxc info mantic
  lxc exec mantic -- cloud-init status --wait
  EOF
  chmod +x ./reproducer.sh
  sshpass -p passw0rd scp -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -P  ./reproducer.sh ubuntu@127.0.0.1:~/
  sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -p  ubuntu@127.0.0.1 sudo apt-get update
  sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -p  ubuntu@127.0.0.1 sudo apt-get upgrade 
--assume-yes
  sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -p  ubuntu@127.0.0.1 ./reproducer.sh
  ```

  The issue is not present with the 6.5.0-5 kernel and the issue is
  present regardless of the container launched. I tried the jammy
  container to test this.

  From my test VM

  ```
  ubuntu@cloudimg:~$ uname --all
  Linu

[Touch-packages] [Bug 1994165] Re: CMS_final: do not ignore CMS_dataFinal result

Hello,

ubuntu-sponsors is subscribed to this bug but I couldn't find anything
actionable. I'm unsubscribing ubuntu-sponsors; feel free to subscribe it
again if there's anything that needs sponsoring. Thanks.

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

Title:
  CMS_final: do not ignore CMS_dataFinal result

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Jammy:
  In Progress
Status in openssl source package in Kinetic:
  Won't Fix
Status in openssl source package in Lunar:
  Fix Released

Bug description:
  === SRU information ===
  [Meta]
  This bug is part of a series of four bugs for a single SRU.
  The "central" bug with the global information and debdiff is 
http://pad.lv/2033422

  [Impact]
  S/MIME signature can fail silently
  The commit by upstream propagates the return code of some functions rather 
than ignore it.

  [Test plan]
  This issue is not very simple to reproduce because "openssl cms" cannot be 
used to do so. This has to be done with the openssl API instead.
  At least the bug reportere here and the one on openssl's bug tracker have 
confirmed the patch solves the issue. Additionally, the bug reporter here has 
tested the PPA that contains the patche and validated it. Finally, I read 
through the patch attentively.

  [Where problems could occur]
  At this point it is unlikely an error would appear. The openssl bug tracker 
mentions nothing related to this patch which landed more than a year ago. The 
patch is simple and doesn't change the code logic.

  [Patches]
  The patches come directly from upstream and apply cleanly.

  https://github.com/openssl/openssl/pull/18876

  * 
https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-sru-0001-REGRESSION-CMS_final-do-not-ignore-CMS_dataFinal-res.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0
  * 
https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-sru-0002-Handle-SMIME_crlf_copy-return-code.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0

  === Original description ===

  https://github.com/openssl/openssl/pull/18876

  The CMS_dataFinal result is important as signature may fail, however, it
  is ignored while returning success from CMS_final.

  Please add this fix to The openssl 3.0.2 "Jammy Jellyfish (supported)"

  Thanks

  Upstream commit:

  ```
  commit 67c0460b89cc1b0644a1a59af78284dfd8d720af
  Author: Alon Bar-Lev 
  Date:   Tue Jul 26 15:17:06 2022 +0300

  Handle SMIME_crlf_copy return code

  Currently the SMIME_crlf_copy result is ignored in all usages. It does
  return failure when memory allocation fails.

  This patch handles the SMIME_crlf_copy return code in all
  occurrences.

  Signed-off-by: Alon Bar-Lev 

  Reviewed-by: Tomas Mraz 
  Reviewed-by: Paul Dale 
  Reviewed-by: Hugo Landau 
  (Merged from https://github.com/openssl/openssl/pull/18876)
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1994165/+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 1990216] Re: backport fix for "OpenSSL 3 cannot decrypt data encrypted with OpenSSL 1.1 with blowfish in OFB or CFB modes" to Jammy

Hello,

ubuntu-sponsors is subscribed to this bug but I couldn't find anything
actionable.  I'm unsubscribing ubuntu-sponsors; feel free to subscribe
it again if there's anything that needs sponsoring.  Thanks.

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

Title:
  backport fix for "OpenSSL 3 cannot decrypt data encrypted with OpenSSL
  1.1 with blowfish in OFB or CFB modes" to Jammy

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Jammy:
  In Progress
Status in openssl source package in Lunar:
  Fix Released

Bug description:
  === SRU information ===
  [Meta]
  This bug is part of a series of four bugs for a single SRU.
  The "central" bug with the global information and debdiff is 
http://pad.lv/2033422

  [Impact]
  Decryption for Blowfish with OFB and CFB modes fails due to using a key 
shorter than expected by default.
  Encryption will also use a key shorter than expected.
  Exchange of encrypted data from/to Jammy using BF OFB/CFB will therefore lead 
to decryption issues.

  [Test plan]
  On Focal, run the following and copy the output to your clipboard

  for cipher in bf-cbc bf-cfb bf-ecb bf-ofb; do  echo "Test with ${cipher}" 
| openssl enc -${cipher} -k test -pbkdf2 -out "pouet.${cipher}"; done
  tar c pouet.bf-* | xz | base64 -w 60

  You can also run this on Lunar or Mantic if you add "-provider legacy
  -provider default" to the "openssl enc" invocation.

  On Jammy, run the following and paste your clipboard

  base64 -d | xz -d | tar x
  for cipher in bf-cbc bf-cfb bf-ecb bf-ofb; do openssl enc -d -provider 
legacy -provider default -${cipher} -k test -pbkdf2 -d -in "pouet.${cipher}"; 
done

  Only "Test with bf-cbc" and "Test with bf-ecb" will be properly
  decrypted: the other two will result in garbage on screen.

  Here is the result of the enc + tar + xz + base64 on Focal (works with
  Lunar/Mantic too but you need to added ):

  /Td6WFoAAATm1rRGAgAhARYAAAB0L+Wj4Cf/ARBdADgbyxDlZ/1Xd7bAmZw7
  8pbqQTu5j8StVybo1p1B2ydBc5VcodF6fu0hEp801tvirgSFNMSAHk5HMN/w
  hCgU1BIr/nK51g3A3Lkdv7QNbaUw2ux1AmO/MpCLKLffCB9ElFZH4tuOS5AR
  m9CJMzi6LQOw9wytGKm2IK3Ph7WpU6JQ/3HJilffQwHbFLnukiWGpLNO5v0O
  D/4AJikrU9iemfChT0jXDbIRZ8a8VpVhJqu0u6eYOheVTqmSRiHHpIC/p1VA
  ecFb0mACF/TQhjxcMUWGSGO/mtof+VaLiyg0KB87GKlChfwXTEvgbNuP9hmu
  GL64VhX568Oy9EakSxlcXiIRk14kJKv0MdHQqY1R22wAACzqSr/nzpwqAAGs
  AoBQAACjzq5WscRn+wIABFla

  Here is the same but from Jammy if you want to test encryption on
  Jammy and decryption on Lunar/Mantic:

  /Td6WFoAAATm1rRGAgAhARYAAAB0L+Wj4Cf/ARFdADgbyxDlZ/1Xd7bAmZw7
  8pbqQTu5j8StVybo1p1B2ydBc1zK4HR2g3CiLJet+R++nZy/gph6RscQ6hI3
  HySjdDOFRfjIVttiNK3DvRsZb37r8SXkj/JCYWicZGjWPZxVE3OAZhEed5qe
  jrFv871QAbm4jVGD4oIc4cOb5V/xDN7KWgwEzpWQy6+tcfPm3KLPQvULx56N
  2qQf60hP//p5EXS3RpCitUsrGUoYzTynjOUIRy2yCmgZDh62RmchUshyWePa
  k0nEYlDbl5/dSHXbWEWESqW+QDj136MZRwQRY+QC4MvLXg2Bo8H+Dl/xvNDF
  /5J4layZdFlh76lWOtFRVoIbX6JtpAP34g4zx1422GSNAABRzyqPdCqX
  1AABrQKAUAAABh3ynbHEZ/sCAARZWg==

  The contents are expected to be different due to the use of
  randomness. Don't try to compare the base64 outputs: I'm only using
  them to ease testing across containers.

  [Where problems could occur]
  This patch makes openssl match the documented default (see "man openssl-enc" 
and search for "Blowfish" for instance) and fixes decryption from an up-to-date 
Jammy to pretty much everything else, but it also create an issue for data 
encrypted on Jammy without this patch and Jammy with this patch.

  There are two possible cases: encrypted data being streamed across
  this boundary or data at rest being transferred or read later.

  Streaming is probably not an issue in practice because it's rather the
  current situation that has been an issue and it's easy to remedy by
  updating everything (which is relatively few machines since that's
  only Jammy and not any other OS or distribution).

  Data at rest is more annoying since updating Jammy will make it
  impossible to read the data again without updates to other pieces of
  software. That sounds like a really bad thing and it kind of is but at
  the same, the benefits are much larger than the issues. Indeed, there
  is already an incompatibility at the moment between Jammy and
  everything else and the more time passes by, the more such problematic
  files can be created. Luckily very few people are using blowfish
  nowadays and it's not even enabled by default anymore in openssl.
  Moreover the software update to work around the issue should be a
  single API call which is documented in the upstream bug report (
  https://github.com/openssl/openssl/issues/18359 ). Finally, I have
  warned the two projects that I am aware are impacted; this is made
  easier by the fact that they encountered the initial

[Touch-packages] [Bug 2036467] Re: superblock checksum mismatch in resize2fs

@Krister If you are interested in driving the process to get the patch
landed, you can follow the procedure at

https://packaging.ubuntu.com/html/fixing-a-bug.html

And

https://wiki.ubuntu.com/StableReleaseUpdates

To prepare updates for all releases. Feel free to ask for help on IRC.

If not, no worries, we'll get to it, I tagged it foundations-todo for
the team to do! But if you want to gain experience in packaging this is
a good place to start!

** Also affects: e2fsprogs (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: e2fsprogs (Ubuntu Mantic)
   Importance: Undecided
   Status: Confirmed

** Also affects: e2fsprogs (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Tags removed: rls-mm-incoming
** Tags added: foundations-todo

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

Title:
  superblock checksum mismatch in resize2fs

Status in cloud-images:
  New
Status in e2fsprogs package in Ubuntu:
  Confirmed
Status in e2fsprogs source package in Focal:
  New
Status in e2fsprogs source package in Jammy:
  New
Status in e2fsprogs source package in Mantic:
  Confirmed

Bug description:
  Hi,
  We run ext4 on EBS volumes on EC2.  During provisioning, cloud-init will 
occasionally report that resize2fs has failed due to a superblock checksum 
mismatch.  We debugged this internally, and were able to come up with the 
following reproducer:

 #!/usr/bin/bash
 set -euxo pipefail

 while true
 do
 parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s
 sleep .5
 mkfs.ext4 /dev/nvme1n1p1
 mount -t ext4 /dev/nvme1n1p1 /mnt
 stress-ng --temp-path /mnt -D 4 &
 STRESS_PID=$!
 sleep 1
 growpart /dev/nvme1n1 1
 resize2fs /dev/nvme1n1p1
 kill $STRESS_PID
 wait $STRESS_PID
 umount /mnt
 wipefs -a /dev/nvme1n1p1
 wipefs -a /dev/nvme1n1
 done

  (This was on a 60gb gp3 volume attached to a c5.4xlarge)

  We were able to find a fix that works and get the patch accepted
  upstream.  The short explanation is that by switching the superblock
  read to direct io, we no longer see the problem.

  The patch is available here, but hasn't been published in a released
  version of e2fsprogs:

  
https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84

  A longer thread with the maintainer is available here:

  https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/

  This bug report is to request that Ubuntu backport this patch to the
  versions of e2fsprogs that are in releases that are available in
  images on AWS, preferably Focal and Jammy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2036467/+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 2037205] Re: setuptools: FTBFS in mantic

This bug was fixed in the package setuptools - 68.1.2-2

---
setuptools (68.1.2-2) unstable; urgency=medium

  * Don't run dh_auto_clean, just remove the .pybuild directory manually.
dh-python would remove the egg-info dir during the dh_auto_clean call.
Closes: #1052540, #1052783. LP: #2037205.

 -- Matthias Klose   Wed, 04 Oct 2023 10:28:14 +0200

** Changed in: setuptools (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  setuptools: FTBFS in mantic

Status in dh-python package in Ubuntu:
  New
Status in setuptools package in Ubuntu:
  Fix Released
Status in dh-python package in Debian:
  New
Status in setuptools package in Debian:
  New

Bug description:
  As seen in the mantic test rebuild [1], setuptools 68.1.2-1 currently
  FTBFS:

  
  Traceback (most recent call last):
File "/<>/setuptools/config/setupcfg.py", line 284, in 
__setitem__
  current_value = getattr(target_obj, option_name)
  
  AttributeError: 'MinimalDistribution' object has no attribute 'entry_points'

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/<>/setup.py", line 92, in 
  dist = setuptools.setup(**setup_params)
 
File "/<>/setuptools/__init__.py", line 106, in setup
  _install_setup_requires(attrs)
File "/<>/setuptools/__init__.py", line 77, in 
_install_setup_requires
  dist.parse_config_files(ignore_option_errors=True)
File "/<>/setuptools/dist.py", line 895, in parse_config_files
  setupcfg.parse_configuration(
File "/<>/setuptools/config/setupcfg.py", line 177, in 
parse_configuration
  options.parse()
File "/<>/setuptools/config/setupcfg.py", line 500, in parse
  section_parser_method(section_options)
File "/<>/setuptools/config/setupcfg.py", line 727, in 
parse_section_entry_points
  self['entry_points'] = parsed
  
File "/<>/setuptools/config/setupcfg.py", line 286, in 
__setitem__
  raise KeyError(option_name)
  KeyError: 'entry_points'
  E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1: 
python3.11 setup.py clean 

  
  [1] 
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20230830-mantic-mantic.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/2037205/+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 2038561] [NEW] Requesting Ubuntu package manager to release openssh updates to focal and jammy

2023-10-05 Thread Prashanth Suvarna

Public bug reported:

We're are unable to test OpenSSL 3.1 versions on Ubuntu 22.04 and 20.04
machines because the machine gets bricked and loses SSH after
installation of OpenSSL 3.1.2.

This is because SSHD gets restarted when OpenSSL 3.1 gets installed. But
it fails to come up and we lose SSH access to the box.

Debug logging on SSHD shows the below error when it tries to start : 
OpenSSL version mismatch. Built against 3020, you have 30100020

After researching in online forums, it appears that this is an OpenSSH bug and 
it's been fixed in version 9.4p1 and 9.5p1 via this fix : 
https://github.com/openssh/openssh-portable/commit/b7afd8a4ecaca8afd3179b55e9db79c0ff210237

However, it appears that only 8.9p1 version of openssh-client and
openssh-server are available in Ubuntu packages.

Requesting you to please release openssh versions 9.4p1 or 9.5p1 on
Jammy and Focal which will help us move past this bug and start testing
OpenSSL 3.1 for our use cases.


Additional information about our environment:
$ lsb_release -rd
Description:Ubuntu 22.04.3 LTS
Release:22.04

$ apt-cache policy openssh-server
openssh-server:
  Installed: 1:8.9p1-3ubuntu0.4
  Candidate: 1:8.9p1-3ubuntu0.4
  Version table:
 *** 1:8.9p1-3ubuntu0.4 500
500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu jammy-updates/main 
amd64 Packages
100 /var/lib/dpkg/status
 1:8.9p1-3ubuntu0.3 500
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
 1:8.9p1-3 500
500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 
Packages

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

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

Title:
  Requesting Ubuntu package manager to release openssh updates to focal
  and jammy

Status in openssh package in Ubuntu:
  New

Bug description:
  We're are unable to test OpenSSL 3.1 versions on Ubuntu 22.04 and
  20.04 machines because the machine gets bricked and loses SSH after
  installation of OpenSSL 3.1.2.

  This is because SSHD gets restarted when OpenSSL 3.1 gets installed.
  But it fails to come up and we lose SSH access to the box.

  Debug logging on SSHD shows the below error when it tries to start : 
  OpenSSL version mismatch. Built against 3020, you have 30100020

  After researching in online forums, it appears that this is an OpenSSH bug 
and it's been fixed in version 9.4p1 and 9.5p1 via this fix : 
  
https://github.com/openssh/openssh-portable/commit/b7afd8a4ecaca8afd3179b55e9db79c0ff210237

  However, it appears that only 8.9p1 version of openssh-client and
  openssh-server are available in Ubuntu packages.

  Requesting you to please release openssh versions 9.4p1 or 9.5p1 on
  Jammy and Focal which will help us move past this bug and start
  testing OpenSSL 3.1 for our use cases.

  
  Additional information about our environment:
  $ lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  $ apt-cache policy openssh-server
  openssh-server:
Installed: 1:8.9p1-3ubuntu0.4
Candidate: 1:8.9p1-3ubuntu0.4
Version table:
   *** 1:8.9p1-3ubuntu0.4 500
  500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu jammy-updates/main 
amd64 Packages
  100 /var/lib/dpkg/status
   1:8.9p1-3ubuntu0.3 500
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   1:8.9p1-3 500
  500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 
Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2038561/+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 2036467] Re: superblock checksum mismatch in resize2fs

@foundations & EDM can we have this backported all the way to trusty?
Xenial for sure.

** Tags added: rls-mm-incoming

** Information type changed from Public to Public Security

** Also affects: cloud-images
   Importance: Undecided
   Status: New

** Changed in: cloud-images
   Importance: Undecided => Critical

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

Title:
  superblock checksum mismatch in resize2fs

Status in cloud-images:
  New
Status in e2fsprogs package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  We run ext4 on EBS volumes on EC2.  During provisioning, cloud-init will 
occasionally report that resize2fs has failed due to a superblock checksum 
mismatch.  We debugged this internally, and were able to come up with the 
following reproducer:

 #!/usr/bin/bash
 set -euxo pipefail

 while true
 do
 parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s
 sleep .5
 mkfs.ext4 /dev/nvme1n1p1
 mount -t ext4 /dev/nvme1n1p1 /mnt
 stress-ng --temp-path /mnt -D 4 &
 STRESS_PID=$!
 sleep 1
 growpart /dev/nvme1n1 1
 resize2fs /dev/nvme1n1p1
 kill $STRESS_PID
 wait $STRESS_PID
 umount /mnt
 wipefs -a /dev/nvme1n1p1
 wipefs -a /dev/nvme1n1
 done

  (This was on a 60gb gp3 volume attached to a c5.4xlarge)

  We were able to find a fix that works and get the patch accepted
  upstream.  The short explanation is that by switching the superblock
  read to direct io, we no longer see the problem.

  The patch is available here, but hasn't been published in a released
  version of e2fsprogs:

  
https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84

  A longer thread with the maintainer is available here:

  https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/

  This bug report is to request that Ubuntu backport this patch to the
  versions of e2fsprogs that are in releases that are available in
  images on AWS, preferably Focal and Jammy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2036467/+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 2018457] Re: [SRU] Enable support for Bobcat Cloud Archive

2023-10-05 Thread Corey Bryant

Hey Thiago! Still working through the release of bobcat on our end,
hopefully it will be available officially soon. I've just updated the
wiki.

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

Title:
   [SRU] Enable support for Bobcat Cloud Archive

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Jammy:
  Fix Released
Status in software-properties source package in Mantic:
  Fix Released

Bug description:
  Please add support for:

 cloud-archive:bobcat
 cloud-archive:bobcat-proposed

  This will also need to be SRU'd back to jammy.

  [Impact]
  End users have to manually enable the antelope cloud archive pockets.

  [Test case]
  sudo add-apt-repository cloud-archive:bobcat
  sudo add-apt-repository cloud-archive:bobcat-proposed

  [Regression potential]
  Limited - just a data item addition

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2018457/+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 2038433] Status changed to Confirmed

2023-10-05 Thread Ubuntu Kernel Bot

This change was made by a bot.

** Changed in: linux (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/2038433

Title:
  systemd autopkgtest regression on arm64 and s390x on mantic

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in linux source package in Mantic:
  Confirmed
Status in systemd source package in Mantic:
  New

Bug description:
  tests-in-lxd seems to fail to download the lxd image used for the test (or 
something similar), looking at the log:
  ...
  Publishing instance: Image pack: 85% (5.51MB/s)

  Instance published with fingerprint: 
83b511be44395f2afc7d4d1ee0708cb18834c8b15cb208c9d218964ed8479114
  6845s autopkgtest [09:11:14]: starting date and time: 2023-10-03 09:11:14+
  6845s autopkgtest [09:11:14]: version 5.28ubuntu1
  6845s autopkgtest [09:11:14]: host autopkgtest; command line: 
/usr/bin/autopkgtest -U -B . --test-name=unit-tests -- lxd 
autopkgtest/ubuntu/mantic/arm64
  7063s : failure: (down) ['mktemp', '--directory', '--tmpdir', 
'autopkgtest.XX'] failed (exit status 1, stderr '')
  7063s autopkgtest [09:14:52]: ERROR: testbed failure: unexpected eof from the 
testbed
  7063s autopkgtest [09:14:52]: test tests-in-lxd: ---]
  7064s autopkgtest [09:14:53]: test tests-in-lxd:  - - - - - - - - - - results 
- - - - - - - - - -
  7064s tests-in-lxd FAIL non-zero exit status 1
  2:40 PM
  ...

  This introduces a regression that is blocking the promotion of new
  kernels in Mantic.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: systemd 253.5-1ubuntu6
  ProcVersionSignature: Ubuntu 6.5.0-5.5.1-lowlatency 6.5.0
  Uname: Linux 6.5.0-5-lowlatency x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  4 14:38:15 2023
  InstallationDate: Installed on 2023-09-25 (9 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-lowlatency 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 2.04
  dmi.board.asset.tag: Default string
  dmi.board.name: G1621-02
  dmi.board.vendor: GPD
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.ec.firmware.release: 2.3
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.04:bd09/01/2022:br5.19:efr2.3:svnGPD:pnG1621-02:pvrDefaultstring:rvnGPD:rnG1621-02:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: G1621-02
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: GPD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038433/+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 2018457] Re: [SRU] Enable support for Bobcat Cloud Archive

2023-10-05 Thread Thiago Martins

Hey folks, just curious... Why the
https://wiki.ubuntu.com/OpenStack/CloudArchive page doesn't mention
Bobcat?

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

Title:
   [SRU] Enable support for Bobcat Cloud Archive

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Jammy:
  Fix Released
Status in software-properties source package in Mantic:
  Fix Released

Bug description:
  Please add support for:

 cloud-archive:bobcat
 cloud-archive:bobcat-proposed

  This will also need to be SRU'd back to jammy.

  [Impact]
  End users have to manually enable the antelope cloud archive pockets.

  [Test case]
  sudo add-apt-repository cloud-archive:bobcat
  sudo add-apt-repository cloud-archive:bobcat-proposed

  [Regression potential]
  Limited - just a data item addition

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2018457/+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 2038433] Re: systemd autopkgtest regression on arm64 and s390x on mantic

2023-10-05 Thread Nick Rosbrook

** Also affects: linux (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/2038433

Title:
  systemd autopkgtest regression on arm64 and s390x on mantic

Status in linux package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in linux source package in Mantic:
  New
Status in systemd source package in Mantic:
  New

Bug description:
  tests-in-lxd seems to fail to download the lxd image used for the test (or 
something similar), looking at the log:
  ...
  Publishing instance: Image pack: 85% (5.51MB/s)

  Instance published with fingerprint: 
83b511be44395f2afc7d4d1ee0708cb18834c8b15cb208c9d218964ed8479114
  6845s autopkgtest [09:11:14]: starting date and time: 2023-10-03 09:11:14+
  6845s autopkgtest [09:11:14]: version 5.28ubuntu1
  6845s autopkgtest [09:11:14]: host autopkgtest; command line: 
/usr/bin/autopkgtest -U -B . --test-name=unit-tests -- lxd 
autopkgtest/ubuntu/mantic/arm64
  7063s : failure: (down) ['mktemp', '--directory', '--tmpdir', 
'autopkgtest.XX'] failed (exit status 1, stderr '')
  7063s autopkgtest [09:14:52]: ERROR: testbed failure: unexpected eof from the 
testbed
  7063s autopkgtest [09:14:52]: test tests-in-lxd: ---]
  7064s autopkgtest [09:14:53]: test tests-in-lxd:  - - - - - - - - - - results 
- - - - - - - - - -
  7064s tests-in-lxd FAIL non-zero exit status 1
  2:40 PM
  ...

  This introduces a regression that is blocking the promotion of new
  kernels in Mantic.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: systemd 253.5-1ubuntu6
  ProcVersionSignature: Ubuntu 6.5.0-5.5.1-lowlatency 6.5.0
  Uname: Linux 6.5.0-5-lowlatency x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  4 14:38:15 2023
  InstallationDate: Installed on 2023-09-25 (9 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-lowlatency 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 2.04
  dmi.board.asset.tag: Default string
  dmi.board.name: G1621-02
  dmi.board.vendor: GPD
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.ec.firmware.release: 2.3
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.04:bd09/01/2022:br5.19:efr2.3:svnGPD:pnG1621-02:pvrDefaultstring:rvnGPD:rnG1621-02:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: G1621-02
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: GPD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038433/+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 2038490] Re: Apt and apt-get reporting different lists of packages to be held back/upgraded

It's fine, it's pretty non-obvious that the two differ in some behaviors
and even more so that it's intentional.

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

Title:
  Apt and apt-get reporting different lists of packages to be held
  back/upgraded

Status in apt package in Ubuntu:
  Invalid

Bug description:
  When running apt-get from a script (or command line), I see a
  different list of packages to be held back / upgraded vs when I run
  apt.

  I am running Kubuntu 23.04. The version of apt and apt-get I first noticed 
the problem in is 2.6.0ubuntu0.1
  I also see the problem on my servers running Ubuntu 22.04.3 with apt and 
apt-get version 2.4.10.
  I upgraded my copy on Kubuntu 23.04 to 2.7.6 through the launchpad.net ppa 
deity/sid (actually version 2.7.6+0~202309200852~ubuntu23.04.1) and the problem 
remains.

  I've spent a few hours looking for the correct place to search for
  this being already reported and have reviewed recent commits at
  https://salsa.debian.org/apt-team/apt. I'm hesitant but I do not see
  any other mention of this issue. I have tried deleting my
  /var/cache/apt and running apt update. To duplicate the issue one
  needs to have an Ubuntu version that has not yet received the update
  to linux-headers-6.2.0-34, et al. I attempted to duplicate the issue
  on a fresh install of Ubuntu Desktop 23.04, but discovered that the
  system is upgraded to linux 6.2.0-34 during the install process.
  Please see the output of the apt-get and apt commands below.

  $ apt-get update
  Hit:1 http://ftp.usf.edu/pub/ubuntu lunar InRelease
  Hit:2 http://ftp.usf.edu/pub/ubuntu lunar-updates InRelease   
   
  Hit:3 http://ftp.usf.edu/pub/ubuntu lunar-backports InRelease 
   
  Hit:4 https://dl.winehq.org/wine-builds/ubuntu lunar InRelease
   
  Hit:5 http://ftp.usf.edu/pub/ubuntu lunar-security InRelease  
   
  Hit:6 http://packages.microsoft.com/repos/code stable InRelease   
   
  Hit:7 https://repo.steampowered.com/steam stable InRelease
   
  Hit:8 https://pkg.cloudflareclient.com jammy InRelease
   
  Hit:9 https://download.sublimetext.com apt/stable/ InRelease  
   
  Get:10 https://pkgs.tailscale.com/stable/ubuntu jammy InRelease   
   
  Ign:11 https://repo.vivaldi.com/stable/deb stable InRelease   
   
  Hit:12 https://repo.vivaldi.com/stable/deb stable Release 
   
  Hit:13 https://download.virtualbox.org/virtualbox/debian jammy InRelease  
   
  Ign:16 https://download.webmin.com/download/repository sarge InRelease
   
  Hit:17 https://ppa.launchpadcontent.net/cappelikan/ppa/ubuntu lunar InRelease 
 
  Hit:18 https://download.webmin.com/download/repository sarge Release  
   
  Hit:21 https://ppa.launchpadcontent.net/teejee2008/foss/ubuntu lunar 
InRelease   
  Hit:14 https://packagecloud.io/github/git-lfs/ubuntu lunar InRelease  
   
  Hit:15 https://packagecloud.io/eugeny/tabby/ubuntu jammy InRelease
   
  Hit:22 https://ppa.launchpadcontent.net/cubic-wizard/release/ubuntu lunar 
InRelease  
  Hit:23 https://repo.waydro.id bullseye InRelease  
   
  Hit:24 https://ppa.launchpadcontent.net/deity/sid/ubuntu lunar InRelease  
   
  Hit:25 https://ppa.launchpadcontent.net/papirus/papirus/ubuntu lunar InRelease
  Fetched 6,557 B in 3s (2,503 B/s)  
  Reading package lists... Done

  $ apt-get upgrade --assume-no
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  The following packages have been kept back:
grub-efi-amd64-bin grub-efi-amd64-signed linux-generic 
linux-headers-generic linux-image-generic
  The following packages will be upgraded:
code freerdp2-x11 libfreerdp-client2-2

[Touch-packages] [Bug 2036968] Re: Mantic minimized/minimal cloud images do not receive IP address during provisioning; systemd regression with wait-online

** Tags removed: rls-mm-incoming

** Changed in: systemd (Ubuntu)
   Importance: High => Medium

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

Title:
  Mantic minimized/minimal cloud images do not receive IP address during
  provisioning; systemd regression with wait-online

Status in cloud-images:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Following a recent change from linux-kvm kernel to linux-generic
  kernel in the mantic minimized images, there is a reproducable bug
  where a guest VM does not have an IP address assigned as part of
  cloud-init provisioning.

  This is easiest to reproduce when emulating arm64 on amd64 host. The
  bug is a race condition, so there could exist fast enough
  virtualisation on fast enough hardware where this bug is not present
  but in all my testing I have been able to reproduce.

  The latest mantic minimized images from http://cloud-
  images.ubuntu.com/minimal/daily/mantic/ have force initrdless boot and
  no initrd to fallback to.

  This but is not present in the non minimized/base images @
  http://cloud-images.ubuntu.com/mantic/ as these boot with initrd with
  the required drivers present for virtio-net.

  Reproducer

  ```
  wget -O "launch-qcow2-image-qemu-arm64.sh" 
https://people.canonical.com/~philroche/20230921-cloud-images-mantic-fail-to-provision/launch-qcow2-image-qemu-arm64.sh

  chmod +x ./launch-qcow2-image-qemu-arm64.sh
  wget 
https://people.canonical.com/~philroche/20230921-cloud-images-mantic-fail-to-provision/livecd.ubuntu-cpc.img
  ./launch-qcow2-image-qemu-arm64.sh --password passw0rd --image 
./livecd.ubuntu-cpc.img
  ```

  You will then be able to log in with user `ubuntu` and password
  `passw0rd`.

  You can run `ip a` and see that there is a network interface present
  (separate to `lo`) but no IP address has been assigned.

  ```
  ubuntu@cloudimg:~$ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: enp0s1:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff

  ```

  This is because when cloud-init is trying to configure network
  interfaces it doesn't find any so it doesn't configure any. But by the
  time boot is complete the network interface is present but cloud-init
  provisioning has already completed.

  You can verify this by running `sudo cloud-init clean && sudo cloud-
  init init`

  You can then see a successfully configured network interface

  ```
  ubuntu@cloudimg:~$ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: enp0s1:  mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
  link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff
  inet 10.0.2.15/24 metric 100 brd 10.0.2.255 scope global dynamic enp0s1
     valid_lft 86391sec preferred_lft 86391sec
  inet6 fec0::5054:ff:fe12:3456/64 scope site dynamic mngtmpaddr 
noprefixroute
     valid_lft 86393sec preferred_lft 14393sec
  inet6 fe80::5054:ff:fe12:3456/64 scope link
     valid_lft forever preferred_lft forever

  ```

  The bug is also reproducible with amd64 guest on adm64 host on
  older/slower hardware.

  The suggested fixes while debugging this issue are:

  * to include `virtio-net` as a built-in in the mantic generic kernel
  * understand what needs to change in cloud-init so that it can react to late 
additions of network interfaces

  I will file a separate bug against cloud-init to address the race
  condition on emulated guest/older hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2036968/+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 1969709] Re: libreoffice font selection unusably slow

2023-10-05 Thread Sam Townsend

This is still a problem :(

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

Title:
  libreoffice font selection unusably slow

Status in LibreOffice:
  Won't Fix
Status in fontconfig package in Ubuntu:
  Incomplete
Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Trying to scroll through the font list in the menu bar, I experience
  an unacceptable degree of lagging. Just popping up the dropdown list
  takes 7-10 seconds and the system takes the same amount of time to
  respond to perform individidual scrolling gestures. The CPU jumps to
  100% and the whole system becomes unresponsive.

  I have tried deb, snap and even the packages offered on the site of
  the LibreOffice project. They all manifest the same behaviour. The
  only thing that works is disabling font previews. I have downgraded to
  7.2 for now, which appears to be unaffected.

  I have contacted the LibreOffice team and they tell me that this
  should be solved by fontconfig 2.14. Unfortunately, Ubuntu 22.04 is
  shipping 2.13...

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libreoffice-core 1:7.3.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 21 05:01:24 2022
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2022-03-27 (24 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1969709/+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 2038490] Re: Apt and apt-get reporting different lists of packages to be held back/upgraded

2023-10-05 Thread Eric Reinhardt

Thank you. I'd wondered how something seeingly so significant had gone
unnoticed. I apologize for the invalid bug report.

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

Title:
  Apt and apt-get reporting different lists of packages to be held
  back/upgraded

Status in apt package in Ubuntu:
  Invalid

Bug description:
  When running apt-get from a script (or command line), I see a
  different list of packages to be held back / upgraded vs when I run
  apt.

  I am running Kubuntu 23.04. The version of apt and apt-get I first noticed 
the problem in is 2.6.0ubuntu0.1
  I also see the problem on my servers running Ubuntu 22.04.3 with apt and 
apt-get version 2.4.10.
  I upgraded my copy on Kubuntu 23.04 to 2.7.6 through the launchpad.net ppa 
deity/sid (actually version 2.7.6+0~202309200852~ubuntu23.04.1) and the problem 
remains.

  I've spent a few hours looking for the correct place to search for
  this being already reported and have reviewed recent commits at
  https://salsa.debian.org/apt-team/apt. I'm hesitant but I do not see
  any other mention of this issue. I have tried deleting my
  /var/cache/apt and running apt update. To duplicate the issue one
  needs to have an Ubuntu version that has not yet received the update
  to linux-headers-6.2.0-34, et al. I attempted to duplicate the issue
  on a fresh install of Ubuntu Desktop 23.04, but discovered that the
  system is upgraded to linux 6.2.0-34 during the install process.
  Please see the output of the apt-get and apt commands below.

  $ apt-get update
  Hit:1 http://ftp.usf.edu/pub/ubuntu lunar InRelease
  Hit:2 http://ftp.usf.edu/pub/ubuntu lunar-updates InRelease   
   
  Hit:3 http://ftp.usf.edu/pub/ubuntu lunar-backports InRelease 
   
  Hit:4 https://dl.winehq.org/wine-builds/ubuntu lunar InRelease
   
  Hit:5 http://ftp.usf.edu/pub/ubuntu lunar-security InRelease  
   
  Hit:6 http://packages.microsoft.com/repos/code stable InRelease   
   
  Hit:7 https://repo.steampowered.com/steam stable InRelease
   
  Hit:8 https://pkg.cloudflareclient.com jammy InRelease
   
  Hit:9 https://download.sublimetext.com apt/stable/ InRelease  
   
  Get:10 https://pkgs.tailscale.com/stable/ubuntu jammy InRelease   
   
  Ign:11 https://repo.vivaldi.com/stable/deb stable InRelease   
   
  Hit:12 https://repo.vivaldi.com/stable/deb stable Release 
   
  Hit:13 https://download.virtualbox.org/virtualbox/debian jammy InRelease  
   
  Ign:16 https://download.webmin.com/download/repository sarge InRelease
   
  Hit:17 https://ppa.launchpadcontent.net/cappelikan/ppa/ubuntu lunar InRelease 
 
  Hit:18 https://download.webmin.com/download/repository sarge Release  
   
  Hit:21 https://ppa.launchpadcontent.net/teejee2008/foss/ubuntu lunar 
InRelease   
  Hit:14 https://packagecloud.io/github/git-lfs/ubuntu lunar InRelease  
   
  Hit:15 https://packagecloud.io/eugeny/tabby/ubuntu jammy InRelease
   
  Hit:22 https://ppa.launchpadcontent.net/cubic-wizard/release/ubuntu lunar 
InRelease  
  Hit:23 https://repo.waydro.id bullseye InRelease  
   
  Hit:24 https://ppa.launchpadcontent.net/deity/sid/ubuntu lunar InRelease  
   
  Hit:25 https://ppa.launchpadcontent.net/papirus/papirus/ubuntu lunar InRelease
  Fetched 6,557 B in 3s (2,503 B/s)  
  Reading package lists... Done

  $ apt-get upgrade --assume-no
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  The following packages have been kept back:
grub-efi-amd64-bin grub-efi-amd64-signed linux-generic 
linux-headers-generic linux-image-generic
  The following packages will be upgraded:
code freerdp2-x11

[Touch-packages] [Bug 2037497] Re: gnome-shell crashed with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage()

2023-10-05 Thread Tim Holmes-Mitra

** Tags removed: rls-mm-incoming
** Tags added: rls-mm-notfixing

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

Title:
  gnome-shell crashed with SIGSEGV at NULL from end_query() from
  cogl_gl_create_timestamp_query() from
  cogl_onscreen_egl_swap_buffers_with_damage()

Status in Mesa:
  New
Status in Mutter:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Invalid
Status in mesa package in Fedora:
  Confirmed

Bug description:
  crash after update
  wayland session is not accessible anymore

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45.0-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 27 05:52:26 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2023-09-26 (0 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-13.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2037497/+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 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade

2023-10-05 Thread Nick Rosbrook

Dave - yeah that's the expect outcome with this patch.

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

Title:
  systemd wait-online now times out after jammy and lunar upgrade

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Jammy:
  Fix Committed
Status in systemd source package in Lunar:
  Fix Committed

Bug description:
  [NOTE]

  If you are running a desktop system and you see this issue, you should
  run:

  $ systemctl disable --now systemd-networkd.service

  This will disable systemd-networkd and associated units, including
  systemd-networkd-wait-online.service. NetworkManager and systemd-
  networkd should not be running at the same time. On desktop,
  NetworkManager is the default network stack.

  [Impact]

  When all interfaces are "not required for online", e.g. when they are
  marked "optional: true" in netplan, systemd-networkd-wait-online will
  timeout. Or, in other words, systemd-networkd-wait-online will timeout
  even though all interfaces are ignored, hence none of them will ever
  be marked as "ready." Depending on what units depend on network-
  online.target, this can delay boot by 120 seconds (the default timeout
  for systemd-networkd-wait-online).

  [Test Plan]

  1. Create a new LXD container. These instructions assume jammy is the
  release, but the same can be done for lunar.

  $ lxc launch ubuntu-daily:jammy jammy
  $ lxc exec jammy bash

  2. Once in the container, modify the default /etc/netplan/10-lxc.yaml
  so that eth0 is configured with "optional: true":

  $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like
  $ cat /etc/netplan/50-cloud-init.yaml
  network:
    version: 2
    ethernets:
  eth0:
    dhcp4: true
    dhcp-identifier: mac
    optional: true

  3. Re-generate and apply the netplan configuration.

  $ netplan generate
  $ netplan apply

  4. Manually run systemd-networkd-wait-online, and observe that all
  links are ignored, and the command times out:

  $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online 
--timeout=10
  Found link lo(1)
  Found link eth0(19)
  lo: link is ignored
  eth0: link is ignored
  Timeout occurred while waiting for network connectivity.

  [Where problems could occur]

  This patch partially re-instates a patch remove in bug 1982218.
  However, instead of exiting if all links are unmanaged, we exit if all
  links are ignored in manager_configured(). If the patch was wrong, we
  may re-introduce bug 1982218, so as part of this SRU verification,
  that bug should be tested too. Any other regressions would also be
  related to systemd-networkd-wait-online behavior.

  [Original Description]

  On Ubuntu 22.04 desktop system using network-manager and upgrading to
  systemd 249.11-0ubuntu3.10, wait-online now times out which prevents
  logins (GDM, ssh, console) until it does time out. This seems to be
  introduced by the change for
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218.

  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21
  also mentioned the problem on Lunar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+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 2023322] Re: Unable to setup Google Online Accounts with Nvidia drivers

2023-10-05 Thread Bug Watch Updater

** Changed in: webkit2gtk (Debian)
   Status: Confirmed => Fix Released

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

Title:
  Unable to setup Google Online Accounts with Nvidia drivers

Status in Webkit:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-online-accounts package in Ubuntu:
  Triaged
Status in webkit2gtk package in Ubuntu:
  In Progress
Status in yelp package in Ubuntu:
  Triaged
Status in webkit2gtk package in Debian:
  Fix Released

Bug description:
  When I go into Settings > Online Accounts > Google, I get to the
  prompt for email address, once in a while it stops accepting input
  there. But often I can get to the password screen. Once I do, I can't
  type anything or paste anything.

  This is a fresh install of Ubuntu 23.04 and I have installed all
  updates.

  Nothing in /var/crash

  Jun 08 11:15:59 CCW-HAL systemd[3523]: 
vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time.
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell.
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Activating via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 
comm="/usr/bin/gnome-terminal.real" label="unconfined")
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service 
- GNOME Terminal Server...
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Successfully activated service 'org.gnome.Terminal'
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service 
- GNOME Terminal Server.
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 
launched by gnome-terminal-server process 10931.
  Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child 
process exited with code 1
  Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: 
Using cross-namespace EXTERNAL authentication (this will deadlock if server is 
GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation 
gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should 
not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found 
default implementation dconf (DConfSettingsBackend) for 
‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - 
googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - 
exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - 
kerberosGoaBackend: activated kerberos providerGLib-GIO: 
_g_io_module_get_default: Found default implementation gnutls 
(GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was 
dismissed
  Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map 
pid: Could not determine pid namespace: Could not find instance-id in process's 
/.flatpak-info
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened 
for user root(uid=0) by (uid=0)
  Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report 
/etc/cron.hourly)
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed 
for user root
  Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 
55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 
(core 2, socket 0)
  Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 
0x55bd22ad9ab2.
  Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an 
override-redirect window and this is not correct according to the standard, so 
we'll fallback to the first non-override-redirect window 0x3a006dc.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories...
  Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: 
Deactivated successfully.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories.
  Jun 08 11:17:42 CCW-HAL systemd[1]: 
run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated 
successfully.
  Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a029e2 for 0x3a029f0 window override-redirect is an 
override-redirect

[Touch-packages] [Bug 2037022] Re: logrotate systemd timer should run hourly rather than daily

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  logrotate systemd timer should run hourly rather than daily

Status in logrotate package in Ubuntu:
  Confirmed

Bug description:
  Logrotate supports "hourly rotation, however the Ubuntu logrotate
  systemd Timer runs "daily" - so "hourly" logrotate jobs are still only
  run daily.

  Updating /etc/systemd/system/timers.target.wants/logrotate.timer:
  ...
  [Timer]
  OnCalendar=hourly
  ...

  should allow "logrotate hourly" to work as expected.

  See related comment at 
https://github.com/logrotate/logrotate/issues/249#issuecomment-485829363
  "The tricky part is that one needs to change the default cron hook
  (or systemd timer) to make hourly actually work as expected."

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: logrotate 3.21.0-1
  ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Sep 21 22:11:04 2023
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: logrotate
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/2037022/+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 1989124] Re: libunwind-(13/14)-dev conflicts with libunwind-dev

2023-10-05 Thread Nico Burns

This is also affecting https://docs.rs (Rust ecosystem documentation
building) for packages that want to link against libc++. See:
https://github.com/rust-lang/crates-build-env/pull/121

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

Title:
  libunwind-(13/14)-dev conflicts with libunwind-dev

Status in libunwind package in Ubuntu:
  Confirmed
Status in llvm-toolchain-14 package in Ubuntu:
  Confirmed

Bug description:
  Tested on Ubuntu 22.04.

  Since these two packages (libunwind-14 and libunwind-dev) conflict
  with each other, I cannot install some libraries and tools that depend
  on them. For example, I cannot install libc++-14-dev and
  libgstreamer1.0-dev together, and that's really unfortunate.

  I'm not sure which packages should be somehow fixed (if any), so feel
  free to reassign this bug wherever it fits.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1989124/+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 2037641] Re: amdgpu: [gfxhub0] no-retry page fault

2023-10-05 Thread Mario Limonciello

Ok in this case can you please open an upstream mesa bug?

** Changed in: mesa (Ubuntu)
   Status: Fix Released => Triaged

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

Title:
  amdgpu: [gfxhub0] no-retry page fault

Status in linux package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged

Bug description:
  Whenever I use Intellij IDEA, after a couple of minutes the screen
  locks up and pretty much renders the machine unusable. I can still ssh
  to it, but the UI is pretty much gone and doesn't respond to
  Ctrl+Alt+F* keys.

  The setup: the machine is connected to an external monitor via USB-C.
  Running kernel 6.5 on Ubuntu 23.10.

  There's the following in kern.log:

  ```
  2023-09-28T13:58:23.077679+03:00 mavi-ThinkPad-T14s kernel: [  422.206433] 
amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 
vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663)
  2023-09-28T13:58:23.077694+03:00 mavi-ThinkPad-T14s kernel: [  422.206450] 
amdgpu :06:00.0: amdgpu:   in page starting at address 0xb15852923000 
from IH client 0x1b (UTCL2)
  2023-09-28T13:58:23.077695+03:00 mavi-ThinkPad-T14s kernel: [  422.206460] 
amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431
  2023-09-28T13:58:23.077696+03:00 mavi-ThinkPad-T14s kernel: [  422.206466] 
amdgpu :06:00.0: amdgpu:  Faulty UTCL2 client ID: IA (0x2)
  2023-09-28T13:58:23.077698+03:00 mavi-ThinkPad-T14s kernel: [  422.206471] 
amdgpu :06:00.0: amdgpu:  MORE_FAULTS: 0x1
  2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [  422.206476] 
amdgpu :06:00.0: amdgpu:  WALKER_ERROR: 0x0
  2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [  422.206481] 
amdgpu :06:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  2023-09-28T13:58:23.077700+03:00 mavi-ThinkPad-T14s kernel: [  422.206485] 
amdgpu :06:00.0: amdgpu:  MAPPING_ERROR: 0x0
  2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [  422.206490] 
amdgpu :06:00.0: amdgpu:  RW: 0x0
  2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [  422.206497] 
amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 
vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663)
  2023-09-28T13:58:23.077702+03:00 mavi-ThinkPad-T14s kernel: [  422.206506] 
amdgpu :06:00.0: amdgpu:   in page starting at address 0xb07248096000 
from IH client 0x1b (UTCL2)
  2023-09-28T13:58:23.077703+03:00 mavi-ThinkPad-T14s kernel: [  422.206514] 
amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431
  2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [  422.206519] 
amdgpu :06:00.0: amdgpu:  Faulty UTCL2 client ID: IA (0x2)
  2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [  422.206524] 
amdgpu :06:00.0: amdgpu:  MORE_FAULTS: 0x1
  2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [  422.206528] 
amdgpu :06:00.0: amdgpu:  WALKER_ERROR: 0x0
  2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [  422.206533] 
amdgpu :06:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  2023-09-28T13:58:23.077706+03:00 mavi-ThinkPad-T14s kernel: [  422.206538] 
amdgpu :06:00.0: amdgpu:  MAPPING_ERROR: 0x0
  2023-09-28T13:58:23.077707+03:00 mavi-ThinkPad-T14s kernel: [  422.206542] 
amdgpu :06:00.0: amdgpu:  RW: 0x0
  2023-09-28T13:58:23.077708+03:00 mavi-ThinkPad-T14s kernel: [  422.206549] 
amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 
vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663)
  2023-09-28T13:58:23.077709+03:00 mavi-ThinkPad-T14s kernel: [  422.206556] 
amdgpu :06:00.0: amdgpu:   in page starting at address 0xaf8c3d808000 
from IH client 0x1b (UTCL2)
  2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [  422.206564] 
amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431
  2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [  422.206569] 
amdgpu :06:00.0: amdgpu:  Faulty UTCL2 client ID: IA (0x2)
  2023-09-28T13:58:23.077711+03:00 mavi-ThinkPad-T14s kernel: [  422.206574] 
amdgpu :06:00.0: amdgpu:  MORE_FAULTS: 0x1
  2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [  422.206578] 
amdgpu :06:00.0: amdgpu:  WALKER_ERROR: 0x0
  2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [  422.206583] 
amdgpu :06:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  2023-09-28T13:58:23.077713+03:00 mavi-ThinkPad-T14s kernel: [  422.206588] 
amdgpu :06:00.0: amdgpu:  MAPPING_ERROR: 0x0
  2023-09-28T13:58:23.077713+03:00 mavi-ThinkPad-T14s kernel: [  422.206592] 
amdgpu :06:00.0: amdgpu:  RW: 0x0

[Touch-packages] [Bug 2038512] Re: [Mediatek] mt8195-demo: please help to include these MediaTek drivers in initrd.img in CD/DVD release image

ubuntu kernel team does not handle which drivers do or do not get
included in the initrd.

Since this is stuff that affects generic, these should be added by
default for modules=most mode by initramfs-tools.

please contact ubuntu foundations team about this.

** Package changed: linux (Ubuntu) => initramfs-tools (Ubuntu)

** Changed in: initramfs-tools (Ubuntu)
   Status: Incomplete => New

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

Title:
  [Mediatek] mt8195-demo: please help to include these MediaTek drivers
  in initrd.img in CD/DVD release image

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  [Impact]
  Peripheral probe failure for MediaTek boards 'mt8195-demo' and 
'genio-1200-evk'.

  [Kernel version]
  6.2

  [Fix]
  I've used 'dracut' to examing the driver dependencies for boards 
'mt8195-demo' and 'genio-1200-evk'.
  It is able to buot into console and use USB port3. 
  Hope these drivers could help to run installer with USB disk in next daily 
build.

  Note: It won't work with 'update-initramfs -u -k 6.2.0-34-generic' if
  just simply add driver lists in '/etc/modules',
  '/etc/modprobe.d/mediatek.conf' or '/etc/modules-
  load.d/mediatek.conf'. I fixed this issue with 'dracut' and it seems
  this tool will include more common framework drivers into initrd.img.

  [MediaTek relate drivers]
  file: mediatek-drivers-for-mt8195-demo-bringup.txt
  (Not listed in probing sequence)

  i2c-mt65xx
  spi-mt65xx
  reset-ti-syscon
  mt6397
  rtc-mt6397
  mtk-pmic-wrap
  mt6315-regulator
  spmi-mtk-pmif
  mtk_scp_ipi
  mediatek-drm
  mtk-vcodec-dec
  mtk-vcodec-enc
  mtk_jpeg
  mtk-vcodec-common
  mtk-jpeg-enc-hw
  mtk-vpu
  mtk-jpeg-dec-hw
  mtk-cmdq-helper
  mtk-cmdq-helper
  mtk-cmdq-mailbox
  mtk-mdp3
  phy-mtk-mipi-dsi-drv
  btmtk
  leds-mt6360
  tcpci_mt6360
  mt6360_charger
  mt6360-regulator
  mt6360-core
  mt6359-regulator
  mt6360-adc
  snd-soc-mt8195-afe
  snd-soc-mtk-common
  snd-soc-dmic
  dwmac-mediatek
  stmmac-platform
  stmmac
  mtk-rng
  mtk_scp
  mtk_rpmsg
  pwm-mediatek
  pwm-mtk-disp
  nvmem_mtk-efuse
  mtk-sd
  cqhci
  phy-mtk-tphy
  mtu3
  xhci-mtk-hcd
  phy-mtk-pcie
  pcie-mediatek-gen3

  [lsmod log]
  file: lsmod-i1200-demo-kernel-6.2-dracut-initrd.txt

  [Other info]
  effected kernel (6.2-latest)
  ubuntu kernel for lunar, and Mantic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2038512/+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 2038512] [NEW] [Mediatek] mt8195-demo: please help to include these MediaTek drivers in initrd.img in CD/DVD release image

You have been subscribed to a public bug:

[Impact]
Peripheral probe failure for MediaTek boards 'mt8195-demo' and 'genio-1200-evk'.

[Kernel version]
6.2

[Fix]
I've used 'dracut' to examing the driver dependencies for boards 'mt8195-demo' 
and 'genio-1200-evk'.
It is able to buot into console and use USB port3. 
Hope these drivers could help to run installer with USB disk in next daily 
build.

Note: It won't work with 'update-initramfs -u -k 6.2.0-34-generic' if
just simply add driver lists in '/etc/modules',
'/etc/modprobe.d/mediatek.conf' or '/etc/modules-load.d/mediatek.conf'.
I fixed this issue with 'dracut' and it seems this tool will include
more common framework drivers into initrd.img.

[MediaTek relate drivers]
file: mediatek-drivers-for-mt8195-demo-bringup.txt
(Not listed in probing sequence)

i2c-mt65xx
spi-mt65xx
reset-ti-syscon
mt6397
rtc-mt6397
mtk-pmic-wrap
mt6315-regulator
spmi-mtk-pmif
mtk_scp_ipi
mediatek-drm
mtk-vcodec-dec
mtk-vcodec-enc
mtk_jpeg
mtk-vcodec-common
mtk-jpeg-enc-hw
mtk-vpu
mtk-jpeg-dec-hw
mtk-cmdq-helper
mtk-cmdq-helper
mtk-cmdq-mailbox
mtk-mdp3
phy-mtk-mipi-dsi-drv
btmtk
leds-mt6360
tcpci_mt6360
mt6360_charger
mt6360-regulator
mt6360-core
mt6359-regulator
mt6360-adc
snd-soc-mt8195-afe
snd-soc-mtk-common
snd-soc-dmic
dwmac-mediatek
stmmac-platform
stmmac
mtk-rng
mtk_scp
mtk_rpmsg
pwm-mediatek
pwm-mtk-disp
nvmem_mtk-efuse
mtk-sd
cqhci
phy-mtk-tphy
mtu3
xhci-mtk-hcd
phy-mtk-pcie
pcie-mediatek-gen3

[lsmod log]
file: lsmod-i1200-demo-kernel-6.2-dracut-initrd.txt

[Other info]
effected kernel (6.2-latest)
ubuntu kernel for lunar, and Mantic.

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: Incomplete

-- 
[Mediatek] mt8195-demo: please help to include these MediaTek drivers in 
initrd.img in CD/DVD release image
https://bugs.launchpad.net/bugs/2038512
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to initramfs-tools in Ubuntu.

-- 
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 2037604] Re: Backport packages for 22.04.4 HWE stack

2023-10-05 Thread Timo Aaltonen

** Description changed:

  [Impact]
  The graphics HWE stack from kinetic needs to be backported for 22.04.4
  
  directx-headers
  - build-dep of the new Mesa
  
- libdrm
- - build-dep of the new Mesa
- 
- llvm-16
- - new package in jammy
- - build-dep of the new Mesa
- 
  mesa
  - new major release (23.2.x)
  - new HW support, FIXME
  
- spirv-headers
- - needed by s-l-t-16
+ rust-bindgen
  
- spirv-llvm-translator-16
- - needed to bootstrap libclc from llvm
+ rust-clang-sys
  
- spirv-llvm-translator-16
- - needed for the actual libclc-16 after initial bootstrap
  
  [Test case]
  Install the new mesa on various hw, see that everything still works like 
before or better.
  
- 
  [Where things could go wrong]
  This is a major update of Mesa, there could be regressions but we'll backport 
the final stable release of 23.2.x in order to minimize the chance for those.

** Also affects: rust-bindgen (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: rust-clang-sys (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: mesa (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: rust-clang-sys (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: rust-bindgen (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: directx-headers (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: directx-headers (Ubuntu)
   Status: New => Invalid

** Changed in: mesa (Ubuntu)
   Status: New => Invalid

** Changed in: rust-bindgen (Ubuntu)
   Status: New => Invalid

** Changed in: rust-clang-sys (Ubuntu)
   Status: New => Invalid

** Description changed:

  [Impact]
  The graphics HWE stack from kinetic needs to be backported for 22.04.4
  
  directx-headers
  - build-dep of the new Mesa
  
  mesa
  - new major release (23.2.x)
- - new HW support, FIXME
+ - new HW support, Meteor Lake..
  
  rust-bindgen
  
  rust-clang-sys
- 
  
  [Test case]
  Install the new mesa on various hw, see that everything still works like 
before or better.
  
  [Where things could go wrong]
  This is a major update of Mesa, there could be regressions but we'll backport 
the final stable release of 23.2.x in order to minimize the chance for those.

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

Title:
  Backport packages for 22.04.4 HWE stack

Status in directx-headers package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in rust-bindgen package in Ubuntu:
  Invalid
Status in rust-clang-sys package in Ubuntu:
  Invalid
Status in directx-headers source package in Jammy:
  New
Status in mesa source package in Jammy:
  New
Status in rust-bindgen source package in Jammy:
  New
Status in rust-clang-sys source package in Jammy:
  New

Bug description:
  [Impact]
  The graphics HWE stack from kinetic needs to be backported for 22.04.4

  directx-headers
  - build-dep of the new Mesa

  mesa
  - new major release (23.2.x)
  - new HW support, Meteor Lake..

  rust-bindgen

  rust-clang-sys

  [Test case]
  Install the new mesa on various hw, see that everything still works like 
before or better.

  [Where things could go wrong]
  This is a major update of Mesa, there could be regressions but we'll backport 
the final stable release of 23.2.x in order to minimize the chance for those.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+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 2038525] [NEW] Audio not longer coming out of inbuilt speakers after swapping to bluetooth audio

2023-10-05 Thread Paul

Public bug reported:

In built audio was working fine. Connected bluetooth heaphones which
aslo worked fine. On disconnect the audio no longer comes out of
speakers. I have rebooted, checked mute etc.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  paul12tree   2322 F pipewire
  paul12tree   2326 F wireplumber
 /dev/snd/seq:paul12tree   2322 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct  5 10:52:22 2023
InstallationDate: Installed on 2023-09-28 (7 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230919.1)
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 LD_PRELOAD=
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/02/2023
dmi.bios.release: 1.37
dmi.bios.vendor: LENOVO
dmi.bios.version: N3AET72W (1.37 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21CBCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.21
dmi.modalias: 
dmi:bvnLENOVO:bvrN3AET72W(1.37):bd03/02/2023:br1.37:efr1.21:svnLENOVO:pn21CBCTO1WW:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CBCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10:
dmi.product.family: ThinkPad X1 Carbon Gen 10
dmi.product.name: 21CBCTO1WW
dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10
dmi.product.version: ThinkPad X1 Carbon Gen 10
dmi.sys.vendor: LENOVO

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug mantic wayland-session

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

Title:
  Audio not longer coming out of inbuilt speakers after swapping to
  bluetooth audio

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  In built audio was working fine. Connected bluetooth heaphones which
  aslo worked fine. On disconnect the audio no longer comes out of
  speakers. I have rebooted, checked mute etc.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  paul12tree   2322 F pipewire
paul12tree   2326 F wireplumber
   /dev/snd/seq:paul12tree   2322 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  5 10:52:22 2023
  InstallationDate: Installed on 2023-09-28 (7 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230919.1)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   LD_PRELOAD=
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2023
  dmi.bios.release: 1.37
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3AET72W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21CBCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3AET72W(1.37):bd03/02/2023:br1.37:efr1.21:svnLENOVO:pn21CBCTO1WW:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CBCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10:
  dmi.product.family: ThinkPad X1 Carbon Gen 10
  dmi.product.name: 21CBCTO1WW
  dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10
  dmi.product.version: ThinkPad X1 Carbon Gen 10
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2038525/+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 2037642] Re: [FFe] Raspberry Pi 5 support

libcamera is not shipped on the images, and will be SRUed once tested.

** Changed in: pipewire (Ubuntu)
   Status: Triaged => Invalid

** Changed in: libcamera (Ubuntu)
Milestone: None => mantic-updates

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

Title:
  [FFe] Raspberry Pi 5 support

Status in libcamera package in Ubuntu:
  Triaged
Status in linux-meta-raspi package in Ubuntu:
  Fix Released
Status in linux-raspi package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in pipewire package in Ubuntu:
  Invalid
Status in rpi-eeprom package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

   * HWE for Raspberry Pi 5 https://raspberrypi.com/5

  [ Test Plan ]

   * Private builds tested on all existing/supported Raspberry Pi SKUs
  in armhf & arm64 variants

   * No regressions on any existing SKUs

   * Test that Raspberry Pi 5 boards work

  [ Where problems could occur ]

   * Mesa is upgraded, and there are patches to mesa, the raspberry-pi
  specific provider this has been tested but not as extensively.
  Separately there is mesa FFe granted to upgrade to latest release,
  thus these changes piggy-back on top of it.

   * libcamera has new build-depends on new package libpisp for the
  raspberry-pi specific provider which also affects pipewire to provide
  full webcam support.

   * These dependencies, will need to make their way into gnome platform
  snaps to be usable by default in Firefox.

  [ Other Info ]

   * The proposed code changes have been tested in private, prior to
  public announcement

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+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 2036968] Re: Mantic minimized/minimal cloud images do not receive IP address during provisioning; systemd regression with wait-online

This bug was fixed in the package linux - 6.5.0-7.7

---
linux (6.5.0-7.7) mantic; urgency=medium

  * mantic/linux: 6.5.0-7.7 -proposed tracker (LP: #2037611)

  * kexec enable to load/kdump zstd compressed zimg (LP: #2037398)
- [Packaging] Revert arm64 image format to Image.gz

  * Mantic minimized/minimal cloud images do not receive IP address during
provisioning (LP: #2036968)
- [Config] Enable virtio-net as built-in to avoid race

  * Miscellaneous Ubuntu changes
- SAUCE: Add mdev_set_iommu_device() kABI
- [Config] update gcc version in annotations

 -- Andrea Righi   Thu, 28 Sep 2023 10:19:24
+0200

** Changed in: linux (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Mantic minimized/minimal cloud images do not receive IP address during
  provisioning; systemd regression with wait-online

Status in cloud-images:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Following a recent change from linux-kvm kernel to linux-generic
  kernel in the mantic minimized images, there is a reproducable bug
  where a guest VM does not have an IP address assigned as part of
  cloud-init provisioning.

  This is easiest to reproduce when emulating arm64 on amd64 host. The
  bug is a race condition, so there could exist fast enough
  virtualisation on fast enough hardware where this bug is not present
  but in all my testing I have been able to reproduce.

  The latest mantic minimized images from http://cloud-
  images.ubuntu.com/minimal/daily/mantic/ have force initrdless boot and
  no initrd to fallback to.

  This but is not present in the non minimized/base images @
  http://cloud-images.ubuntu.com/mantic/ as these boot with initrd with
  the required drivers present for virtio-net.

  Reproducer

  ```
  wget -O "launch-qcow2-image-qemu-arm64.sh" 
https://people.canonical.com/~philroche/20230921-cloud-images-mantic-fail-to-provision/launch-qcow2-image-qemu-arm64.sh

  chmod +x ./launch-qcow2-image-qemu-arm64.sh
  wget 
https://people.canonical.com/~philroche/20230921-cloud-images-mantic-fail-to-provision/livecd.ubuntu-cpc.img
  ./launch-qcow2-image-qemu-arm64.sh --password passw0rd --image 
./livecd.ubuntu-cpc.img
  ```

  You will then be able to log in with user `ubuntu` and password
  `passw0rd`.

  You can run `ip a` and see that there is a network interface present
  (separate to `lo`) but no IP address has been assigned.

  ```
  ubuntu@cloudimg:~$ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: enp0s1:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff

  ```

  This is because when cloud-init is trying to configure network
  interfaces it doesn't find any so it doesn't configure any. But by the
  time boot is complete the network interface is present but cloud-init
  provisioning has already completed.

  You can verify this by running `sudo cloud-init clean && sudo cloud-
  init init`

  You can then see a successfully configured network interface

  ```
  ubuntu@cloudimg:~$ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: enp0s1:  mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
  link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff
  inet 10.0.2.15/24 metric 100 brd 10.0.2.255 scope global dynamic enp0s1
     valid_lft 86391sec preferred_lft 86391sec
  inet6 fec0::5054:ff:fe12:3456/64 scope site dynamic mngtmpaddr 
noprefixroute
     valid_lft 86393sec preferred_lft 14393sec
  inet6 fe80::5054:ff:fe12:3456/64 scope link
     valid_lft forever preferred_lft forever

  ```

  The bug is also reproducible with amd64 guest on adm64 host on
  older/slower hardware.

  The suggested fixes while debugging this issue are:

  * to include `virtio-net` as a built-in in the mantic generic kernel
  * understand what needs to change in cloud-init so that it can react to late 
additions of network interfaces

  I will file a separate bug against cloud-init to address the race
  condition on emulated guest/older hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2036968/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to :

[Touch-packages] [Bug 2038490] Re: Apt and apt-get reporting different lists of packages to be held back/upgraded