[Touch-packages] [Bug 1785350] Re: package libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of packag

[Launchpad Bug Tracker]

[Expired for mesa (Ubuntu) because there has been no activity for 60
days.]

** Changed in: mesa (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 failed to
  install/upgrade: trying to overwrite shared '/etc/drirc', which is
  different from other instances of package libgl1-mesa-dri:amd64

Status in mesa package in Ubuntu:
  Expired

Bug description:
  First appeared after system upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.77  Tue Jul 10 18:28:52 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Aug  3 20:32:48 2018
  DistUpgraded: 2018-05-18 02:00:49,256 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.77, 4.15.0-24-generic, x86_64: installed
   nvidia, 390.77, 4.15.0-29-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-24-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-29-generic, x86_64: installed
  DuplicateSignature:
   package:libgl1-mesa-dri:18.0.5-0ubuntu0~18.04.1
   Unpacking libgl1-mesa-dri:amd64 (18.0.5-0ubuntu0~18.04.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-BSmI2b/074-libgl1-mesa-dri_18.0.5-0ubuntu0~18.04.1_amd64.deb
 (--unpack):
trying to overwrite shared '/etc/drirc', which is different from other 
instances of package libgl1-mesa-dri:amd64
  ErrorMessage: trying to overwrite shared '/etc/drirc', which is different 
from other instances of package libgl1-mesa-dri:amd64
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3701]
  InstallationDate: Installed on 2017-03-23 (499 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=54d26cb9-e0f9-41d1-a593-869de12e6c28 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: mesa
  Title: package libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 failed to 
install/upgrade: trying to overwrite shared '/etc/drirc', which is different 
from other instances of package libgl1-mesa-dri:amd64
  UpgradeStatus: Upgraded to bionic on 2018-05-18 (77 days ago)
  dmi.bios.date: 06/27/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1902
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-E
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1902:bd06/27/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-E:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1785350/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More 

[Touch-packages] [Bug 2036467] Re: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs

[Matthew Ruffell]

** Description changed:

  [Impact]
  
  This is a long running bug plaguing cloud-images, where on a rare
  occasion resize2fs would fail and the image would not resize to fit the
  entire disk.
  
  Online resizes would fail due to a superblock checksum mismatch, where
  the superblock in memory differs from what is currently on disk due to
  changes made to the image.
  
+ $ resize2fs /dev/nvme1n1p1
+ resize2fs 1.47.0 (5-Feb-2023)
+ resize2fs: Superblock checksum does not match superblock while trying to open 
/dev/nvme1n1p1
+ Couldn't find valid filesystem superblock.
+ 
  Changing the read of the superblock to Direct I/O solves the issue.
  
  [Testcase]
  
  Start an c5.large instance on AWS, and attach a 60gb gp3 volume for use
  as a scratch disk.
  
  Run the following script, courtesy of Krister Johansen and his team:
  
-#!/usr/bin/bash
-set -euxo pipefail
+    #!/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
+    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
  
  Test packages are available in the following ppa:
  
  https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test
  
  If you install the test packages, the race no longer occurs.
  
  [Where problems could occur]
  
  We are changing how resize2fs reads the superblock from underlying
  disks.
  
  If a regression were to occur, resize2fs could fail to resize offline or
  online volumes. As all cloud-images are online resized during their
  initial boot, this could have a large impact to public and private
  clouds should a regression occur.
  
  [Other info]
  
- Upstream mailing list discussion: 
+ Upstream mailing list discussion:
  https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/
  https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/
  
  This was fixed in the below commit upstream:
  
  commit 43a498e938887956f393b5e45ea6ac79cc5f4b84
  Author: Theodore Ts'o 
  Date: Thu, 15 Jun 2023 00:17:01 -0400
  Subject: resize2fs: use Direct I/O when reading the superblock for
-  online resizes
+  online resizes
  Link: 
https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84
  
  The commit has not been tagged to any release. All supported Ubuntu
  releases require this fix, and need to be published in standard non-ESM
  archives to be picked up in cloud images.

** Changed in: e2fsprogs (Ubuntu Bionic)
   Status: In Progress => Won't Fix

-- 
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:
  Resizing cloud-images occasionally fails due to superblock checksum
  mismatch in resize2fs

Status in cloud-images:
  New
Status in e2fsprogs package in Ubuntu:
  In Progress
Status in e2fsprogs source package in Trusty:
  Won't Fix
Status in e2fsprogs source package in Xenial:
  Won't Fix
Status in e2fsprogs source package in Bionic:
  Won't Fix
Status in e2fsprogs source package in Focal:
  In Progress
Status in e2fsprogs source package in Jammy:
  In Progress
Status in e2fsprogs source package in Lunar:
  In Progress
Status in e2fsprogs source package in Mantic:
  In Progress

Bug description:
  [Impact]

  This is a long running bug plaguing cloud-images, where on a rare
  occasion resize2fs would fail and the image would not resize to fit
  the entire disk.

  Online resizes would fail due to a superblock checksum mismatch, where
  the superblock in memory differs from what is currently on disk due to
  changes made to the image.

  $ resize2fs /dev/nvme1n1p1
  resize2fs 1.47.0 (5-Feb-2023)
  resize2fs: Superblock checksum does not match superblock while trying to open 
/dev/nvme1n1p1
  Couldn't find valid filesystem superblock.

  Changing the read of the superblock to Direct I/O solves the issue.

  [Testcase]

  Start an c5.large instance on AWS, and attach a 60gb gp3 volume for
  use as a 

[Touch-packages] [Bug 2039117] [NEW] Intermittent problem accessing TPM during 22.04 boot

[Tre Klaus]

Public bug reported:

I am using 22.04 and am hitting a bug accessing the TPM during start-up
to decrypt a LUKS encrypted drive (data drive, not system drive).

With a Virtualbox 22.04 VM, the problem only happens with the HWE kernel
and occurs 8 out of 10 times. 2 out of 10 times the system boots
correctly. When using the non HWE kernel it works 10 out of 10 times.

With a physical server, Supermicro X10, the problem does not occur at
all.

My LUKS volume is named drive1. From journalctl -u 
systemd-cryptsetup@drive1.service
Oct 10 07:42:08 tpm2-test systemd-cryptsetup[547]: Failed to unseal HMAC key in 
TPM: tpm:error(2.0): PCR have changed since checked

The problem is discussed here -
https://github.com/systemd/systemd/issues/24906 . This also discusses
that people get different results with different kernels.

I'll not go into too much detail as this problem is already resolved in newer 
versions of systemd. The fix for this problem was merged into Ubuntu's systemd 
252.3-1.
https://git.launchpad.net/ubuntu/+source/systemd/commit/src/shared/tpm2-util.c?h=ubuntu/lunar=28f8a776415a01cacec747d831f057d3f8b9f01b

Can this fix be made available to 22.04 - systemd 249.11?

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

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

Title:
  Intermittent problem accessing TPM during 22.04 boot

Status in systemd package in Ubuntu:
  New

Bug description:
  I am using 22.04 and am hitting a bug accessing the TPM during start-
  up to decrypt a LUKS encrypted drive (data drive, not system drive).

  With a Virtualbox 22.04 VM, the problem only happens with the HWE
  kernel and occurs 8 out of 10 times. 2 out of 10 times the system
  boots correctly. When using the non HWE kernel it works 10 out of 10
  times.

  With a physical server, Supermicro X10, the problem does not occur at
  all.

  My LUKS volume is named drive1. From journalctl -u 
systemd-cryptsetup@drive1.service
  Oct 10 07:42:08 tpm2-test systemd-cryptsetup[547]: Failed to unseal HMAC key 
in TPM: tpm:error(2.0): PCR have changed since checked

  The problem is discussed here -
  https://github.com/systemd/systemd/issues/24906 . This also discusses
  that people get different results with different kernels.

  I'll not go into too much detail as this problem is already resolved in newer 
versions of systemd. The fix for this problem was merged into Ubuntu's systemd 
252.3-1.
  
https://git.launchpad.net/ubuntu/+source/systemd/commit/src/shared/tpm2-util.c?h=ubuntu/lunar=28f8a776415a01cacec747d831f057d3f8b9f01b

  Can this fix be made available to 22.04 - systemd 249.11?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2039117/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2039107] Re: package linux-image-6.5.0-9-generic 6.5.0-9.9 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Erich Eickmeyer]

A second run under the same conditions did just fine, so this was
probably a VM glitch. Marking invalid.

** Changed in: initramfs-tools (Ubuntu)
   Importance: Critical => Undecided

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

** Changed in: initramfs-tools (Ubuntu)
Milestone: ubuntu-23.10 => None

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

Title:
  package linux-image-6.5.0-9-generic 6.5.0-9.9 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  This failure occurred during a test upgrade from a clean install of
  Edubuntu 23.04 to 23.10.

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  erich  1313 F wireplumber
   /dev/snd/seq:erich  1310 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Wed Oct 11 14:17:46 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2023-10-11 (0 days ago)
  InstallationMedia: Edubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 vmwgfxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic 
root=UUID=84103c76-ebaa-4a1f-8ca9-ca298dacd756 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-6.5.0-9-generic 6.5.0-9.9 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to mantic on 2023-10-11 (0 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2039107/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2039107] Re: package linux-image-6.5.0-9-generic 6.5.0-9.9 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2039107

** Tags added: iso-testing

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

Title:
  package linux-image-6.5.0-9-generic 6.5.0-9.9 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  This failure occurred during a test upgrade from a clean install of
  Edubuntu 23.04 to 23.10.

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  erich  1313 F wireplumber
   /dev/snd/seq:erich  1310 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Wed Oct 11 14:17:46 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2023-10-11 (0 days ago)
  InstallationMedia: Edubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 vmwgfxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic 
root=UUID=84103c76-ebaa-4a1f-8ca9-ca298dacd756 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-6.5.0-9-generic 6.5.0-9.9 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to mantic on 2023-10-11 (0 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2039107/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2039107] [NEW] package linux-image-6.5.0-9-generic 6.5.0-9.9 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Erich Eickmeyer]

Public bug reported:

This failure occurred during a test upgrade from a clean install of
Edubuntu 23.04 to 23.10.

ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
Uname: Linux 6.2.0-34-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  erich  1313 F wireplumber
 /dev/snd/seq:erich  1310 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Wed Oct 11 14:17:46 2023
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2023-10-11 (0 days ago)
InstallationMedia: Edubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
IwConfig:
 lono wireless extensions.
 
 enp0s3no wireless extensions.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
 |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 vmwgfxdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic 
root=UUID=84103c76-ebaa-4a1f-8ca9-ca298dacd756 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
RfKill:
 
SourcePackage: initramfs-tools
Title: package linux-image-6.5.0-9-generic 6.5.0-9.9 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
UpgradeStatus: Upgraded to mantic on 2023-10-11 (0 days ago)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

** Affects: initramfs-tools (Ubuntu)
 Importance: Critical
 Status: New


** Tags: amd64 apport-package mantic need-duplicate-check

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

Title:
  package linux-image-6.5.0-9-generic 6.5.0-9.9 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  This failure occurred during a test upgrade from a clean install of
  Edubuntu 23.04 to 23.10.

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  erich  1313 F wireplumber
   /dev/snd/seq:erich  1310 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Wed Oct 11 14:17:46 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2023-10-11 (0 days ago)
  InstallationMedia: Edubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 vmwgfxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic 
root=UUID=84103c76-ebaa-4a1f-8ca9-ca298dacd756 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-6.5.0-9-generic 6.5.0-9.9 failed to 
install/upgrade: 

[Touch-packages] [Bug 2038964] Re: raspi ethernet rename is racy

[Steve Langasek]

** Package changed: ubuntu-settings (Ubuntu) => ubuntu-raspi-settings
(Ubuntu)

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

Title:
  raspi ethernet rename is racy

Status in ubuntu-raspi-settings package in Ubuntu:
  Confirmed

Bug description:
  The renaming of the ethernet interface (controlled by 10-raspi-
  eth0.link in ubuntu-raspi-settings) turns out to be racy.
  Specifically, in the final mantic server images (but not the desktop
  images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any
  other supported board, including the 3B), the interface renames
  several times during boot. By the end, the interface is left in the
  enxMACMACMAC state and the netplan configuration fails to apply.

  Will attach kern.log from an affected platform, and another from an
  unaffected platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-raspi-settings/+bug/2038964/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2039104] [NEW] ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

[Steve Langasek]

Public bug reported:

In response to LP: #2038964 and due to the timing we have forked ubuntu-
raspi-settings into a separate source package.

ubuntu-settings must therefore be updated to drop ubuntu-raspi-settings*
from debian/control as otherwise binary builds of the package will be
rejected by the archive (if the version number is <= 23.10.6) or will
wrongly supersede the fixes that have just been uploaded to mantic (if
the version number is > 23.10.6).

** Affects: ubuntu-settings (Ubuntu)
 Importance: Undecided
 Assignee: Dave Jones (waveform)
 Status: New

** Affects: ubuntu-settings (Ubuntu Mantic)
 Importance: Undecided
 Assignee: Dave Jones (waveform)
 Status: New


** Tags: foundations-todo

** Also affects: ubuntu-settings (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-settings (Ubuntu Mantic)
 Assignee: (unassigned) => Dave Jones (waveform)

** Tags added: foundations-todo

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

Title:
  ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-settings source package in Mantic:
  New

Bug description:
  In response to LP: #2038964 and due to the timing we have forked
  ubuntu-raspi-settings into a separate source package.

  ubuntu-settings must therefore be updated to drop ubuntu-raspi-
  settings* from debian/control as otherwise binary builds of the
  package will be rejected by the archive (if the version number is <=
  23.10.6) or will wrongly supersede the fixes that have just been
  uploaded to mantic (if the version number is > 23.10.6).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2039104/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

[Thadeu Lima de Souza Cascardo]

Testing with that commit reverted, it works. Testing on a 6.5 kernel on
jammy fails. When testing on mantic, it works. When testing on mantic,
on an lxc jammy container, it fails inside the container, with that same
kernel.

So, it looks like systemd-networkd sets up the Local tunnel address as
the IFLA_ADDR, and the Remote tunnel address as the IFLA_BROADCAST
netlink attributes. This is what the validation from commit b0ad3c179059
is trying to validate. Those attributes are supposed to be hardware
addresses, not the tunnel addresses.

This needs to be investigated on the systemd side. As I read the systemd
code from the jammy version, I didn't find where this would be
incorrectly set. It may be necessary to revert this kernel code, fix
systemd, and wait for some time before reintroducing this kernel fix.
That all depends on why exactly systemd is doing this. Depending on the
resulting investigation, we will need to reassess if this can be
reasonably be used to revert that commit upstream. But given newer
systemd does the right thing, it might be hard to do it.

Cascardo.

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

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

** Changed in: linux (Ubuntu Jammy)
   Importance: Undecided => High

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

** Changed in: linux (Ubuntu Jammy)
   Status: Confirmed => Triaged

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Triaged
Status in systemd source package in Jammy:
  New

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: 

[Touch-packages] [Bug 2038964] Re: raspi ethernet rename is racy

[Dave Jones]

Figured out a work-around: ensure the matching state of the rename rule
matches the end-state of the rename rule so the networkd state machine
stops flopping between the two rules. Linked the MP with the required
change; will tag ubuntu-release to see if it's not too late for a re-
spin.

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

Title:
  raspi ethernet rename is racy

Status in ubuntu-settings package in Ubuntu:
  Confirmed

Bug description:
  The renaming of the ethernet interface (controlled by 10-raspi-
  eth0.link in ubuntu-raspi-settings) turns out to be racy.
  Specifically, in the final mantic server images (but not the desktop
  images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any
  other supported board, including the 3B), the interface renames
  several times during boot. By the end, the interface is left in the
  enxMACMACMAC state and the netplan configuration fails to apply.

  Will attach kern.log from an affected platform, and another from an
  unaffected platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2038964] Re: raspi ethernet rename is racy

[Dave Jones]

** Merge proposal linked:
   
https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/453340

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

Title:
  raspi ethernet rename is racy

Status in ubuntu-settings package in Ubuntu:
  Confirmed

Bug description:
  The renaming of the ethernet interface (controlled by 10-raspi-
  eth0.link in ubuntu-raspi-settings) turns out to be racy.
  Specifically, in the final mantic server images (but not the desktop
  images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any
  other supported board, including the 3B), the interface renames
  several times during boot. By the end, the interface is left in the
  enxMACMACMAC state and the netplan configuration fails to apply.

  Will attach kern.log from an affected platform, and another from an
  unaffected platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup

[Andy Ruddock]

I'm using VNC to access a desktop and experiencing just this issue. Using the 
"export DBUS_SESSION_BUS_ADDRESS" allows me to get a firefox window. I can't 
open file load/save dialogs from that session though, so can't import/export 
certificates & websites with file upload pages that use the standard 
file-picker dialog don't work.
 
To be fair though I'm fed up of being told that it's my configuration that must 
be wrong & I should be applying one of many random environment variable 
settings that I may find on the internet. If firefox works in, say, an xfce 
session by default & everything works, but it doesn't work in a similar session 
over VNC then something in the distro configuration is broken - simple as.

I've better things to do than try to apply workarounds to fix broken
systems, so I'll use a distro that works. It seems that the team at
Ubuntu is simply not ready to fully support the myriad ways of using
desktop linux.

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

Title:
  Can't run snaps: .slice/session-1.scope is not a snap cgroup

Status in X2Go:
  New
Status in Xpra Terminal Server:
  New
Status in snapd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete
Status in x2goserver package in Ubuntu:
  Confirmed
Status in snapd package in Debian:
  New
Status in snapd package in Fedora:
  New

Bug description:
  I just upgraded from hirsute to impish using do-release-upgrade. On
  the upgraded system, I can't run either firefox or chromium (both of
  which worked fine under hirsute). Both fail with:

  /user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where
  NNN is my uid

  With firefox, I was able to fix the problem with:

  snap remove --purge firefox
  apt purge firefox
  apt install firefox

  Now firefox works. But I tried the same thing substituting chromium-
  browser for firefox, and it didn't help: chromium fails with the same
  error message.

  I guess there must be something left over from the hirsute version of
  snapd that isn't getting noticed or cleared by the impish version?

  Someone suggested this might be related to bug 1850667, but that bug
  is marked fixed as of a couple months ago, and I just did this upgrade
  today. Also, it doesn't mention the error message I'm seeing.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: snapd 2.53+21.10ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Nov 18 18:12:45 2021
  InstallationDate: Installed on 2020-04-29 (568 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: snapd
  UpgradeStatus: Upgraded to impish on 2021-11-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/x2go/+bug/1951491/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1981103] Re: System with DNS server in /etc/network/interfaces has bogus systemd-resolved config after upgrade to 22.04

[Heitor Alves de Siqueira]

** Description changed:

+ [ Impact ]
+ ifupdown configurations will stop having a working DNS server on upgrade
+ 
+ [ Test Plan ]
+ Upgrading from an Ubuntu 18.04 or earlier release, bounce a network interface 
with configured DNS server:
+ 
+ root@pangaea-pm:~# ifdown ens13; ifup ens13
+ /etc/network/if-down.d/resolved: 12: mystatedir: not found
+ /etc/network/if-up.d/resolved: 12: mystatedir: not found
+ /etc/network/if-up.d/resolved: 71: DNS: not found
+ /etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13: 
DNS=134.102.20.20 134.102.200.14: not found
+ /etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13: 
DOMAINS=marum.de: not found
+ Failed to parse DNS server address: DNS
+ Failed to set DNS configuration: Invalid argument
+ 
+ This should result in no errors, and in a valid network configuration with 
working DNS resolution.
+ It's likely that existing netplan configuration needs to be removed and 
migrated to classic ifupdown scripts before running the test above.
+ 
+ [ Where problems could occur ]
+ Although we're only fixing the resolved scripts, more complex network setups 
might see regressions in DNS resolution for some cases. We should pay special 
attention to bridges or virtual interfaces that have been configured through 
ifupdown, as well as validate the other scripts under /etc/network/if-up.d/
+ 
+ [ Other Info ]
  Description:Ubuntu 22.04 LTS
  Release:22.04
  
  ifupdown:
-   Installed: 0.8.36+nmu1ubuntu3
-   Candidate: 0.8.36+nmu1ubuntu3
-   Version table:
-  *** 0.8.36+nmu1ubuntu3 500
- 500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 0.8.36+nmu1ubuntu3
+   Candidate: 0.8.36+nmu1ubuntu3
+   Version table:
+  *** 0.8.36+nmu1ubuntu3 500
+ 500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
+ 100 /var/lib/dpkg/status
  
  After upgrading a server with classic ifupdown configuration after
  reboot the machine had no valid dns servers anymore.
  
  The problem is that the state file created by ifupdown using
  /etc/network/if-up.d/resolved looks like this:
  
  root@pangaea-pm:~# cat /run/network/ifupdown-inet-ens13
  "DNS"="134.102.20.20 134.102.200.14"
  "DOMAINS"="marum.de"
  
  The script later sources this file and causes the following errors, easy
  to see when you execute this:
  
  root@pangaea-pm:~# ifdown ens13; ifup ens13
  /etc/network/if-down.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 71: DNS: not found
  /etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13: 
DNS=134.102.20.20 134.102.200.14: not found
  /etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13: 
DOMAINS=marum.de: not found
  Failed to parse DNS server address: DNS
  Failed to set DNS configuration: Invalid argument
  
  This happened to me on three different servers, so this is a serious bug
  and should be fixed before 22.04 upgrades are allowed for everybody.
  Most servers provided by data centers like Hetzner (Germany) are
  configure like that. After a do-release-upgrade you have no working DNS
  anymore, unless you disable systemd-resolved. I don't want to use
  netplan, so changing to this is no option.
  
  The fix is easy - remove the quotes in the script on the left side
  "$DNS" => $DNS; same for DOMAINS:
  
- if  [ -n "$NEW_DNS" ]; then
- cat <"$mystatedir/ifupdown-${ADDRFAM}-$interface"
+ if  [ -n "$NEW_DNS" ]; then
+ cat <"$mystatedir/ifupdown-${ADDRFAM}-$interface"
  $DNS="$NEW_DNS"
  EOF
- if  [ -n "$NEW_DOMAINS" ]; then
- cat <>"$mystatedir/ifupdown-${ADDRFAM}-$interface"
+ if  [ -n "$NEW_DOMAINS" ]; then
+ cat <>"$mystatedir/ifupdown-${ADDRFAM}-$interface"
  $DOMAINS="$NEW_DOMAINS"
  EOF
- fi
- fi
+ fi
+ fi

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

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

** Also affects: ifupdown (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Changed in: ifupdown (Ubuntu Focal)
 Assignee: (unassigned) => Heitor Alves de Siqueira (halves)

** Changed in: ifupdown (Ubuntu Jammy)
 Assignee: (unassigned) => Heitor Alves de Siqueira (halves)

** Changed in: ifupdown (Ubuntu Lunar)
 Assignee: (unassigned) => Heitor Alves de Siqueira (halves)

** Changed in: ifupdown (Ubuntu Focal)
   Status: New => In Progress

** Changed in: ifupdown (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: ifupdown (Ubuntu Lunar)
   Status: New => In Progress

** Changed in: ifupdown (Ubuntu Focal)
   Importance: Undecided => Low

** Changed in: ifupdown (Ubuntu Lunar)
   Importance: Undecided => Critical

** Changed in: ifupdown (Ubuntu Jammy)
   Importance: Undecided => Low

** Changed in: ifupdown (Ubuntu 

[Touch-packages] [Bug 2038964] Re: raspi ethernet rename is racy

[Dave Jones]

There does seem to be something unusual going on with the lan78xx re-
initializing (or restarting?) part way through the boot sequence,
causing another round of renaming to kick off (and then everything
fails). Bizarre.

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

Title:
  raspi ethernet rename is racy

Status in ubuntu-settings package in Ubuntu:
  Confirmed

Bug description:
  The renaming of the ethernet interface (controlled by 10-raspi-
  eth0.link in ubuntu-raspi-settings) turns out to be racy.
  Specifically, in the final mantic server images (but not the desktop
  images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any
  other supported board, including the 3B), the interface renames
  several times during boot. By the end, the interface is left in the
  enxMACMACMAC state and the netplan configuration fails to apply.

  Will attach kern.log from an affected platform, and another from an
  unaffected platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-release-upgrader - 1:23.10.10

---
ubuntu-release-upgrader (1:23.10.10) mantic; urgency=medium

  * Fix failing autopkgtest due to PEP8 line to long issue.
  * Run pre-build.sh: updating po files, mirrors, and demotions.

ubuntu-release-upgrader (1:23.10.9) mantic; urgency=medium

  [ Tim Andersson ]
  * fix: stop TypeError traceback in DistUpgradeQuirks:_set_generic_font
(LP: #2038900)

  [ Brian Murray ]
  * Run pre-build.sh: updating po files, mirrors, and demotions.

  [ Gunnar Hjalmarsson ]
  * Temporary font for Ubuntu MATE (LP: #2034986)

 -- Brian Murray   Wed, 11 Oct 2023 04:48:13 -0700

** Changed in: ubuntu-release-upgrader (Ubuntu Mantic)
   Status: Fix Committed => Fix Released

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

Title:
  some text became unreadable during a distribution upgrade

Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Released

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/2034986/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Jeremy Bícha]

** Changed in: ubuntu-release-upgrader (Ubuntu Mantic)
   Status: In Progress => Fix Committed

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

Title:
  some text became unreadable during a distribution upgrade

Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Committed
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Committed

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/2034986/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2030784] Re: Backport Intel's AVX512 patches on openssl 3.0

[Bun K Tan]

Hi @schopin,

Recommended way to test the relevant code paths would be to use OpenSSL’s 
Capability Bits Environment variable.  Notes below:
 
 
Ubuntu - OpenSSL OPENSSL_ia32cap Environment Variable
OpenSSL Environment variable processor feature bit disable combos for testing. 
https://www.openssl.org/docs/manmaster/man3/OPENSSL_ia32cap.html
 
 
* AES-GCM Relevant Feature Disable
 
   Disable VAES-NI
   $ export OPENSSL_ia32cap=:~0x200
 
   Disable VPCLMULQDQ
   $ export OPENSSL_ia32cap=:~0x400
 
   Disable AES-NI
   $ export OPENSSL_ia32cap=~0x200
 
   Disable AESNI + VAESNI
   $ export OPENSSL_ia32cap=~0x200:~0x200
 
 
* RSA 2K/3K/4K Sign Relevant Feature Disable
 
   Disable AVX512F
   $ export OPENSSL_ia32cap=:~0x1
 
   Disable AVX512VL
   $ export OPENSSL_ia32cap=:~0x8000
 
   Disable AVX512DQ
   $ export OPENSSL_ia32cap=:~0x2
 
   Disable AVX512IFMA
   $ export OPENSSL_ia32cap=:~0x20
 
 
* Unset any previous caps
$ unset OPENSSL_ia32cap
 
 
Examples:
   * AES-128-GCM | AES-256-GCM
  - Baseline - Requires VAES and VPCMULQDQ features present on ICX or newer 
platform.  This should be the most performant flow.
$ taskset -c 0 openssl speed -evp aes-128-gcm

  - Individual VAES Disabled and VPCLMULQDQ Disabled should fallback to AVX 
AESNI flow and should have equivalent performance
$ OPENSSL_ia32cap=:~0x200 taskset -c 0 openssl speed -evp 
aes-128-gcm
$ OPENSSL_ia32cap=:~0x400 taskset -c 0 openssl speed -evp 
aes-128-gcm

  - AESNI and VAESNI Disabled should fallback to 'C code' performance
$ OPENSSL_ia32cap=~0x200:~0x200 taskset -c 0 
openssl speed -evp aes-128-gcm
 
   * RSA 2K/3K/4K Sign Performance
  - Baseline - Requires AVX512F, AVX512VL, AVX512DQ, and AVX512IFMA 
features on ICX or newer platform. This should be the most performant flow.
$ taskset -c 0 openssl speed rsa2048 rsa3072 rsa4096

  - Individual  AVX512F, AVX512VL, and AVX512IFMA features should yield 
equivalent performance.  This flow will use the ADOX/ADCX/MULX RSA flow.
$ OPENSSL_ia32cap=:~0x1 taskset -c 0 openssl speed rsa2048 rsa3072 
rsa4096
$ OPENSSL_ia32cap=:~0x8000 taskset -c 0 openssl speed rsa2048 
rsa3072 rsa4096
$ OPENSSL_ia32cap=:~0x2 taskset -c 0 openssl speed rsa2048 rsa3072 
rsa4096
$ OPENSSL_ia32cap=:~0x20 taskset -c 0 openssl speed rsa2048 rsa3072 
rsa4096

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

Title:
  Backport Intel's AVX512 patches on openssl 3.0

Status in openssl package in Ubuntu:
  Fix Released

Bug description:
  https://github.com/openssl/openssl/pull/14908

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

  These should provide a nice performance bonus on recent CPUs, and the
  patches are fairly self-contained.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2030784/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-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] Re: Requesting Ubuntu package manager to release openssh updates to focal and jammy

[Prashanth Suvarna]

Hi Mitchell,

That's fair. In that case, would it be possible to backport the patch to
the current version of OpenSSH available on Jammy and focal?

https://www.openssl.org/source/ states that 3.1 is the latest stable
version of OpenSSL. We would like to be on the latest stable version and
benefit from the all the fixes that are in 3.1 and not in 3.0. The

Since Ubuntu doesn't yet provide a 3.1 version, we're forced to build the 3.1 
from source and install it. 
Unfortunately, due to the bug in OpenSSH, we aren't able to even evaluate 
OpenSSL 3.1.

-- 
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:
  Incomplete

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 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

@Ethan: MATE is about to be fixed. Once ubuntu-release-upgrader
1:23.10.10 has made it to mantic-release, you shouldn't be able to
reproduce that. Let us know otherwise.

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

Title:
  some text became unreadable during a distribution upgrade

Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  In Progress

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/2034986/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Ethan Hutchison]

just attaching a screen shot

** Attachment added: "upgrade.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2034986/+attachment/5708659/+files/upgrade.png

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

Title:
  some text became unreadable during a distribution upgrade

Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  In Progress

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/2034986/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2034986

** Tags added: iso-testing

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

Title:
  some text became unreadable during a distribution upgrade

Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  In Progress

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/2034986/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2038964] Re: raspi ethernet rename is racy

[Juerg Haefliger]

FWIW, this works correctly with a 6.2 lunar kernel and mantic userspace.

** Attachment added: "udev-6-2-3b+.log"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+attachment/5708655/+files/udev-6-2-3b+.log

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

Title:
  raspi ethernet rename is racy

Status in ubuntu-settings package in Ubuntu:
  Confirmed

Bug description:
  The renaming of the ethernet interface (controlled by 10-raspi-
  eth0.link in ubuntu-raspi-settings) turns out to be racy.
  Specifically, in the final mantic server images (but not the desktop
  images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any
  other supported board, including the 3B), the interface renames
  several times during boot. By the end, the interface is left in the
  enxMACMACMAC state and the netplan configuration fails to apply.

  Will attach kern.log from an affected platform, and another from an
  unaffected platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2038811] Re: /usr/sbin/NetworkManager:6:g_assertion_message:g_assertion_message_expr:_internal_write_connection:nms_keyfile_writer_connection:nms_keyfile_plugin_update_connection

[Lukas Märdian]

Reproducer:
nmcli con add type wifi ifname wlan0 ssid asdasd wifi-sec.key-mgmt wpa-eap 
802-1x.eap leap 802-1x.identity username 802-1x.password 


The crash (SIGABRT) happens in NetworkManager's Netplan integration patch, 
because of running into a "nm_assert_not_reached()" call. This could easily be 
avoided by muting that assert and just logging the error and returning FALSE 
(as is already done below the assert):

https://git.launchpad.net/ubuntu/+source/network-
manager/tree/debian/patches/netplan/0002-netplan-make-use-of-libnetplan-
for-YAML-backend.patch#n319

This would not fix the root-cause, though, which is located in
libnetplan: When creating or updating a NetworkManager connection
profile that uses a 802.1x eap authentication method unknown to Netplan
(such as "leap" or "pwd"), the Netplan keyfile parser is getting
confused and generates a broken keyfile config for NetworkManager.

https://github.com/canonical/netplan/blob/main/src/parse-nm.c#L383

This is triggered when manually adding/modifying a corresponding NM
connection profile (through the NM GUI, nmcli, NM DBus, ...) or
automatically, when migrating a corresponding profile through
NetworkManager's "Netplan everywhere" migration as part of the .postinst
maintainer script. In the latter case the crash is handled gracefully,
NetworkManager is restarted and the broken keyfile is restored from a
backup.

https://git.launchpad.net/ubuntu/+source/network-
manager/tree/debian/network-manager.postinst#n67


This can be fixed by supporting all of NetworkManager's 802.1x eap 
authentication methods in Netplan or by making Netplan's passthrough logic 
detect such cases and handle them as a fallback.


Kudos to @danilogondolfo for the investigation and the proposed patch:
https://github.com/canonical/netplan/pull/415

** Changed in: netplan.io (Ubuntu)
   Importance: Undecided => High

** Changed in: network-manager (Ubuntu)
   Importance: High => Medium

** Changed in: network-manager (Ubuntu)
   Status: New => Triaged

** Changed in: netplan.io (Ubuntu)
   Status: New => Triaged

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

Title:
  
/usr/sbin/NetworkManager:6:g_assertion_message:g_assertion_message_expr:_internal_write_connection:nms_keyfile_writer_connection:nms_keyfile_plugin_update_connection

Status in netplan.io package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
network-manager.  This problem was most recently seen with package version 
1.44.2-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/0185fff02c2976262de9f862e539829420f9c737 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2038811/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2038964] Re: raspi ethernet rename is racy

[Juerg Haefliger]

udev debug log from a 3B

** Attachment added: "udev-3b.log"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+attachment/5708641/+files/udev-3b.log

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

Title:
  raspi ethernet rename is racy

Status in ubuntu-settings package in Ubuntu:
  Confirmed

Bug description:
  The renaming of the ethernet interface (controlled by 10-raspi-
  eth0.link in ubuntu-raspi-settings) turns out to be racy.
  Specifically, in the final mantic server images (but not the desktop
  images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any
  other supported board, including the 3B), the interface renames
  several times during boot. By the end, the interface is left in the
  enxMACMACMAC state and the netplan configuration fails to apply.

  Will attach kern.log from an affected platform, and another from an
  unaffected platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2038964] Re: raspi ethernet rename is racy

[Juerg Haefliger]

udev debug log from a 3B+

** Attachment added: "udev-3b+.log"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+attachment/5708640/+files/udev-3b+.log

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

Title:
  raspi ethernet rename is racy

Status in ubuntu-settings package in Ubuntu:
  Confirmed

Bug description:
  The renaming of the ethernet interface (controlled by 10-raspi-
  eth0.link in ubuntu-raspi-settings) turns out to be racy.
  Specifically, in the final mantic server images (but not the desktop
  images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any
  other supported board, including the 3B), the interface renames
  several times during boot. By the end, the interface is left in the
  enxMACMACMAC state and the netplan configuration fails to apply.

  Will attach kern.log from an affected platform, and another from an
  unaffected platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2038964] Re: raspi ethernet rename is racy

[Dave Jones]

** Changed in: ubuntu-settings (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-settings (Ubuntu)
   Status: New => Confirmed

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

Title:
  raspi ethernet rename is racy

Status in ubuntu-settings package in Ubuntu:
  Confirmed

Bug description:
  The renaming of the ethernet interface (controlled by 10-raspi-
  eth0.link in ubuntu-raspi-settings) turns out to be racy.
  Specifically, in the final mantic server images (but not the desktop
  images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any
  other supported board, including the 3B), the interface renames
  several times during boot. By the end, the interface is left in the
  enxMACMACMAC state and the netplan configuration fails to apply.

  Will attach kern.log from an affected platform, and another from an
  unaffected platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2038909] Re: X13s desktop image is missing qcom power management tools

[Dimitri John Ledkov]

** Changed in: ubuntu-cdimage
   Status: New => Fix Committed

** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-meta (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-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2038909

Title:
  X13s desktop image is missing qcom power management tools

Status in Ubuntu CD Images:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  X13s desktop image is missing qcom power management tools

  specifically protection-domain-mapper and qrtr-tools

  which potentially need MIR

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/2038909/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2038903] Re: X13s didn't run flashkernel as part of the install

[Dimitri John Ledkov]

** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  X13s didn't run flashkernel as part of the install

Status in Ubuntu CD Images:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  X13s didn't run flashkernel as part of the install

  hence dtb was not preset in /boot/ and thus installed system is
  incorrect.

  either we need to splice dtb into vmlinuz (which we can with sd-boot
  stub + zimg + devicetree) or make flashkernel run

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/2038903/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2038998] Re: Screen artifacts/UI oddities on Wayland following Steam/Proton session

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  Screen artifacts/UI oddities on Wayland following Steam/Proton session

Status in xorg package in Ubuntu:
  New

Bug description:
  Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
  Ryzen 7 PRO 5850U
  with Radeon (RX Vega 8?) integrated graphics
  16 GB RAM

  Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
  2023 from a daily-live/current .iso generated on October 4, 2023.

  Wayland
  Kernel 6.5.0-9-generic

  * * * * *

  Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
  day, was going through setting up and testing the usual programs.

  Installed Steam through apt from the 'mantic' repositories. Installed
  Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
  compatible titles.

  Screen corruption (white and grey streaks) present in-game when GNOME
  UI elements appeared on-screen (e.g., volume, brightness, and keyboard
  backlight indicators) and omnipresent after closing either game.

  Artifacts remain on screen until log-out or reboot. Artifacts were not
  present beforehand.

  Artifacts only appeared in Wayland session; not X11/Xorg.

  I previously had been running the same games on Ubuntu 22.04 LTS
  (GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
  computer without issue (kernel 6.2).

  * * * * *

  Please see subsequent posts for video/images.

  Happy to provide any other information as needed. Thanks!

  * * * * *

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 11 01:17:43 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon 
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] 
[17aa:509b]
  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-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET54W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21A00068US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.24
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21A00068US
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2038998/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2038998] [NEW] Screen artifacts/UI oddities on Wayland following Steam/Proton session

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
Ryzen 7 PRO 5850U
with Radeon (RX Vega 8?) integrated graphics
16 GB RAM

Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
2023 from a daily-live/current .iso generated on October 4, 2023.

Wayland
Kernel 6.5.0-9-generic

* * * * *

Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
day, was going through setting up and testing the usual programs.

Installed Steam through apt from the 'mantic' repositories. Installed
Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two compatible
titles.

Screen corruption (white and grey streaks) present in-game when GNOME UI
elements appeared on-screen (e.g., volume, brightness, and keyboard
backlight indicators) and omnipresent after closing either game.

Artifacts remain on screen until log-out or reboot. Artifacts were not
present beforehand.

Artifacts only appeared in Wayland session; not X11/Xorg.

I previously had been running the same games on Ubuntu 22.04 LTS (GNOME,
Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this computer
without issue (kernel 6.2).

* * * * *

Please see subsequent posts for video/images.

Happy to provide any other information as needed. Thanks!

* * * * *

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 11 01:17:43 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon 
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] 
[17aa:509b]
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-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2023
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET54W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A00068US
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A00068US
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
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 corruption mantic ubuntu wayland-session
-- 
Screen artifacts/UI oddities on Wayland following Steam/Proton session
https://bugs.launchpad.net/bugs/2038998
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg 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