date:20220208

Given the bug doesn't occur for upgrades, maybe this change is relevant:

https://launchpad.net/ubuntu/+source/ubiquity/22.04.6

(the working image has 22.04.4)

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

Title:
  Ubuntu Jammy Desktop fails to boot after install

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Jammy Desktop fails to boot after install

  Testing Ubuntu Jammy Desktop daily ISO - 2022-02-07

  This also affects Ubuntu Jammy Canary desktop - tested daily ISO
  2022-02-07

  After installing the OS and selecting reboot the system reboot fails -

  The vendors logo appears with the Ubuntu logo and fails to boot - I
  have tried this with 2 barebone machines and 1 in VirtualBox - will
  attach syslogs and images in a separate comment.

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


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

[Touch-packages] [Bug 1960226] Re: Ubuntu Jammy Desktop fails to boot after install

I don't think this is a systemd bug. Here's the diff between working and
not working.

** Attachment added: "diff-0203-0205.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1960226/+attachment/5559919/+files/diff-0203-0205.txt

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

Title:
  Ubuntu Jammy Desktop fails to boot after install

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Jammy Desktop fails to boot after install

  Testing Ubuntu Jammy Desktop daily ISO - 2022-02-07

  This also affects Ubuntu Jammy Canary desktop - tested daily ISO
  2022-02-07

  After installing the OS and selecting reboot the system reboot fails -

  The vendors logo appears with the Ubuntu logo and fails to boot - I
  have tried this with 2 barebone machines and 1 in VirtualBox - will
  attach syslogs and images in a separate comment.

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


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

[Touch-packages] [Bug 1960226] Re: Ubuntu Jammy Desktop fails to boot after install

Although this is one of the changes:

https://launchpad.net/ubuntu/+source/ubuntu-meta/1.475

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

Title:
  Ubuntu Jammy Desktop fails to boot after install

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Jammy Desktop fails to boot after install

  Testing Ubuntu Jammy Desktop daily ISO - 2022-02-07

  This also affects Ubuntu Jammy Canary desktop - tested daily ISO
  2022-02-07

  After installing the OS and selecting reboot the system reboot fails -

  The vendors logo appears with the Ubuntu logo and fails to boot - I
  have tried this with 2 barebone machines and 1 in VirtualBox - will
  attach syslogs and images in a separate comment.

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


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

[Touch-packages] [Bug 1960226] Re: Ubuntu Jammy Desktop fails to boot after install

2022-02-02 WORKS
2022-02-03 ?
2022-02-04 ?
2022-02-05 ?
2022-02-06 FAILS
2022-02-07 FAILS
2022-02-08 FAILS

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

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

Title:
  Ubuntu Jammy Desktop fails to boot after install

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Jammy Desktop fails to boot after install

  Testing Ubuntu Jammy Desktop daily ISO - 2022-02-07

  This also affects Ubuntu Jammy Canary desktop - tested daily ISO
  2022-02-07

  After installing the OS and selecting reboot the system reboot fails -

  The vendors logo appears with the Ubuntu logo and fails to boot - I
  have tried this with 2 barebone machines and 1 in VirtualBox - will
  attach syslogs and images in a separate comment.

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


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

[Touch-packages] [Bug 1960226] Re: Ubuntu Jammy Desktop fails to boot after install

2022-02-08 Thread Chris Guiver

I zsync'd the daily & completed 3 installs but did NOT experience this
issue

uEFI - sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)
BIOS - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)

the sony 'thingy' had two installs to it; 
- one using normal uEFI, and
- the other using Secure-uEFI
reports can be found at link provided in Leó's comment #7

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

Title:
  Ubuntu Jammy Desktop fails to boot after install

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Jammy Desktop fails to boot after install

  Testing Ubuntu Jammy Desktop daily ISO - 2022-02-07

  This also affects Ubuntu Jammy Canary desktop - tested daily ISO
  2022-02-07

  After installing the OS and selecting reboot the system reboot fails -

  The vendors logo appears with the Ubuntu logo and fails to boot - I
  have tried this with 2 barebone machines and 1 in VirtualBox - will
  attach syslogs and images in a separate comment.

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


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

[Touch-packages] [Bug 1958594] Re: Boot error: libgcc_s.so.1 must be installed for pthread_exit to work

This bug was fixed in the package initramfs-tools - 0.140ubuntu12

---
initramfs-tools (0.140ubuntu12) jammy; urgency=medium

  * Force copy pthread and libgcc_s libraries via a stub binary.

To avoid circular shared library dependencies between compiler and
libc, libpthreads chooses to dlopen libgcc_s, instead of linking
against it. However, we have no way to parse/know what it
needs. And even when we hardcode to include libgcc_s1, we don't
have a way to know which libgcc_s1 is needed on a given system and
from which path to include it. But there is a hook-function to
copy a binary and all of its shared library dependencies. Thus
create a stub empty executable, with shared linking against
pthreads and gcc_s1 and always include it in the initrd. This way
at initrd creation time, ldd is used to correctly resolve these
shared library dependencies and correctly copy them into the
initrd. This removes hardcoding paths as to where these libraries
must be copied from on the host. LP: #1958594 LP: #1880853

  * For net boot include most of net/usb modules, except niche modems. LP:
#1950996

  * Cherry-pick updated merge request !26 to support xz compressed
firmware. Uncompressed firmware is preffered, with a fallback to use
compressed firmware files. LP: #1942260

  * Cherry-pick updated merge request !51 to decompress compressed kernel
modules for boot speed performance. LP: #1932329

 -- Dimitri John Ledkov   Tue, 08 Feb 2022
20:43:02 +

** Changed in: initramfs-tools (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Boot error: libgcc_s.so.1 must be installed for pthread_exit to work

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Jammy:
  Fix Released

Bug description:
  [Bug description]

  On a jammy installation, which was upgraded from focal, after a full-
  upgrade and a reboot,

  I enter the LUKS password to decrypt the disk. Then I get the
  following error:

  libgcc_s.so.1 must be installed for pthread_exit to work

  After the error is shown, the system asks for the password again
  (which never works, always throwing the same error).

  [Root cause]

  I was able to decrypt the disk with the same password by booting from
  a live usb. Which allowed further investigation.

  The error shown in the LUKS password prompt menu comes from
  https://github.com/bminor/glibc/blob/glibc-2.34/nptl/pthread_exit.c#L31-L32, 
which indeed shows that pthread_exit fails when libgcc_s.so.1 is missing.

  From
  
https://git.launchpad.net/ubuntu/+source/initramfs-tools/tree/hook-functions?h=import/0.140ubuntu10#n260,
  we noticed that libgcc_s.so.1 is only copied if

  1) copy_exec is called for a binary directly linked to libgcc_s.so.1, or
  2) copy_exec is called for a binary linked to libpthread

  The cryptsetup initramfs hook, calls copy_exec for /sbin/cryptsetup,
  which is linked to libargon2.so.1, which is linked to libpthread.so.0.
  This covers case (2) above. As a consequence, libgcc_s.so.1 is copied
  to the initrd image and the error reported here is not seen.

  However, since glibc 2.34, libpthread is shipped within glibc, and the
  binaries are no longer linked to libpthread.so.0. As a consequence, an
  argon2 package built with glibc 2.32 will no longer be linked to
  libpthread.so.0 and libgcc_s.so.1 will no longer be copied to the
  initrd image. Triggering the reported error.

  This can be verified in these two argon2 builds, from the same
  sources, but with different glibc versions:

  
https://launchpad.net/ubuntu/+source/argon2/0~20171227-0.2build21.04.0/+build/21066610
  
https://launchpad.net/ubuntu/+source/argon2/0~20171227-0.2build22/+build/22255217

  Still lvm2 is a seeded package, which Recommends thin-provisioning-
  tools. thin-provisioning-tools ships a initramfs hook that calls
  copy_exec for /usr/sbin/pdata_tools, which is directly linked to
  libgcc_s.so.1. This covers the case (1) above and should suffice to
  ensure the boot process works properly.

  Since thin-provisioning-tools is just a recommends for lvm2, it could
  be removed from the system (and indeed, for some reason, was not
  present in my focal=>jammy installation). In this case, a new kernel
  installation should trigger the reported error.

  [Reproducer]

  - Install jammy with a LUKS encrypted disk
  - remove thin-provisioning-tools
  - perform a full-upgrade (make sure the kernel was upgraded or run 
update-initramfs manually)
  - reboot and verify you can no longer get past the decrypt password prompt 
screen

  [Workaround]

  A workaround for anyone affected would be to install thin-
  provisioning-tools and run update-initramfs.

  [Impact]

  Users upgrading

[Touch-packages] [Bug 1950996] Re: Missing all modules for usb nics in initrd which makes PXE boot impossible

This bug was fixed in the package initramfs-tools - 0.140ubuntu12

---
initramfs-tools (0.140ubuntu12) jammy; urgency=medium

  * Force copy pthread and libgcc_s libraries via a stub binary.

To avoid circular shared library dependencies between compiler and
libc, libpthreads chooses to dlopen libgcc_s, instead of linking
against it. However, we have no way to parse/know what it
needs. And even when we hardcode to include libgcc_s1, we don't
have a way to know which libgcc_s1 is needed on a given system and
from which path to include it. But there is a hook-function to
copy a binary and all of its shared library dependencies. Thus
create a stub empty executable, with shared linking against
pthreads and gcc_s1 and always include it in the initrd. This way
at initrd creation time, ldd is used to correctly resolve these
shared library dependencies and correctly copy them into the
initrd. This removes hardcoding paths as to where these libraries
must be copied from on the host. LP: #1958594 LP: #1880853

  * For net boot include most of net/usb modules, except niche modems. LP:
#1950996

  * Cherry-pick updated merge request !26 to support xz compressed
firmware. Uncompressed firmware is preffered, with a fallback to use
compressed firmware files. LP: #1942260

  * Cherry-pick updated merge request !51 to decompress compressed kernel
modules for boot speed performance. LP: #1932329

 -- Dimitri John Ledkov   Tue, 08 Feb 2022
20:43:02 +

** Changed in: initramfs-tools (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

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

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Focal:
  Confirmed
Status in initramfs-tools source package in Hirsute:
  Confirmed
Status in initramfs-tools source package in Impish:
  Confirmed
Status in initramfs-tools source package in Jammy:
  Fix Released

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

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

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

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

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

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


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

[Touch-packages] [Bug 1578138] Re: 'BadRegion (invalid Region parameter)' causes WM to exit

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

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

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

Title:
  'BadRegion (invalid Region parameter)' causes WM to exit

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Same as https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455916

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed May  4 12:03:42 2016
  DistUpgraded: 2016-04-22 15:24:35,321 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.10, 4.2.0-35-generic, x86_64: installed
   vboxhost, 5.0.10, 4.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / 
R9 280X] [1002:6798] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Tahiti XT [Radeon HD 7970/8970 OEM / R9 
280X] [1043:0442]
  InstallationDate: Installed on 2014-03-29 (766 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash swapaccount=1 nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (11 days ago)
  dmi.bios.date: 07/05/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X79-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd07/05/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnX79-UD3:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed May  4 11:51:49 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2
  xserver.video_driver: radeon

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


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

[Touch-packages] [Bug 1629837] Re: Chrome + hardware acceleration after resume causes unusable system with Nvidia

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

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

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

Title:
  Chrome + hardware acceleration after resume causes unusable system
  with Nvidia

Status in xorg package in Ubuntu:
  Expired

Bug description:
  After resuming from a suspend, the Ubuntu UI lags so much the system is not 
usable. However, this happens only if chrome is running (or is started if not 
already running) and hardware acceleration is enabled in chrome.
  I've tried both GNOME Shell and Unity with the same result. ssh into the host 
works fine while the UI is unusable, showing excessive CPU usage by Xorg, 
gnome-shell and chrome processes.

  I tried disable the NVIDIA drivers to test with nouveau, but then the
  screen will not turn on after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm zfs zunicode zcommon znvpair zavl nvidia_drm 
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  370.28  Thu Sep  1 19:45:04 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Oct  3 12:10:12 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-34-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-38-generic, x86_64: installed
   nvidia-370, 370.28, 4.4.0-38-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c60] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Device [1558:6a04]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10ab:9008 USI Co., Ltd 
   Bus 001 Device 003: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 002: ID 046d:c047 Logitech, Inc. Laser Mouse M-UAL120
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook P65xRP
  ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.4.0-38-generic 
root=ZFS=rpool/ROOT/ubuntu ro boot=zfs bootfs=rpool/ROOT/ubuntu
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.01
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65xRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.01:bd07/18/2016:svnNotebook:pnP65xRP:pvrNotApplicable:rvnNotebook:rnP65xRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: P65xRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Oct  3 11:34:58 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.3

To manage notifications about this bug go to:

[Touch-packages] [Bug 1960383] [NEW] package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2022-02-08 Thread Keita Fuse

Public bug reported:

While installing 21.04

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4
ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Feb  9 13:04:28 2022
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2022-02-03 (5 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: i386
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.1
 apt  2.0.6
SourcePackage: glib2.0
Title: package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package focal i386 need-duplicate-check third-party-packages

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

Title:
  package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to
  install/upgrade: dependency problems - leaving triggers unprocessed

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  While installing 21.04

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4
  ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Feb  9 13:04:28 2022
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2022-02-03 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: i386
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.1
   apt  2.0.6
  SourcePackage: glib2.0
  Title: package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1960383/+subscriptions


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

[Touch-packages] [Bug 1960372] Re: DPMS ignores attempts to DISABLE IT

2022-02-08 Thread Anonymous

If normal user programs are allowed to access dpms then it is a security
issue. Requesting the security team be brought in to help on this.

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

Title:
  DPMS ignores attempts to DISABLE IT

Status in libxcb package in Ubuntu:
  New

Bug description:
  I'm on a fresh installation of Debian, linux image 5.10, with a radeon
  RX580 gpu.

  My computer is not honoring the setting to "never" turn the monitor
  off, in power settings.

  DPMS is still killing the monitor after 10 minutes. It appears bugged.
  I have to manually turn DPMS with a cron job every 5 minutes to make
  sure it "stays off".

  I don't want DPMS. I want my monitor to always stay on ALWAYS FOREVER
  AND EVER NO MATTER WHAT HAPPENS. Why is DPMS fighting me???

  How do I completely disable and REMOVE this bugged program "dpms" from
  my system, safely???

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


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

[Touch-packages] [Bug 1960372] Re: DPMS ignores attempts to DISABLE IT

2022-02-08 Thread Anonymous

One part of this issue seems to be, MAYBE, that VLC is enabling DPMS
somehow. It should not be allowed to do that.

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

Title:
  DPMS ignores attempts to DISABLE IT

Status in libxcb package in Ubuntu:
  New

Bug description:
  I'm on a fresh installation of Debian, linux image 5.10, with a radeon
  RX580 gpu.

  My computer is not honoring the setting to "never" turn the monitor
  off, in power settings.

  DPMS is still killing the monitor after 10 minutes. It appears bugged.
  I have to manually turn DPMS with a cron job every 5 minutes to make
  sure it "stays off".

  I don't want DPMS. I want my monitor to always stay on ALWAYS FOREVER
  AND EVER NO MATTER WHAT HAPPENS. Why is DPMS fighting me???

  How do I completely disable and REMOVE this bugged program "dpms" from
  my system, safely???

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


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

[Touch-packages] [Bug 1960372] [NEW] DPMS ignores attempts to DISABLE IT

2022-02-08 Thread Anonymous

Public bug reported:

I'm on a fresh installation of Debian, linux image 5.10, with a radeon
RX580 gpu.

My computer is not honoring the setting to "never" turn the monitor off,
in power settings.

DPMS is still killing the monitor after 10 minutes. It appears bugged. I
have to manually turn DPMS with a cron job every 5 minutes to make sure
it "stays off".

I don't want DPMS. I want my monitor to always stay on ALWAYS FOREVER
AND EVER NO MATTER WHAT HAPPENS. Why is DPMS fighting me???

How do I completely disable and REMOVE this bugged program "dpms" from
my system, safely???

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

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

Title:
  DPMS ignores attempts to DISABLE IT

Status in libxcb package in Ubuntu:
  New

Bug description:
  I'm on a fresh installation of Debian, linux image 5.10, with a radeon
  RX580 gpu.

  My computer is not honoring the setting to "never" turn the monitor
  off, in power settings.

  DPMS is still killing the monitor after 10 minutes. It appears bugged.
  I have to manually turn DPMS with a cron job every 5 minutes to make
  sure it "stays off".

  I don't want DPMS. I want my monitor to always stay on ALWAYS FOREVER
  AND EVER NO MATTER WHAT HAPPENS. Why is DPMS fighting me???

  How do I completely disable and REMOVE this bugged program "dpms" from
  my system, safely???

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


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

[Touch-packages] [Bug 1958594] Re: Boot error: libgcc_s.so.1 must be installed for pthread_exit to work

To be fair we don't need the empty pthread in the initramfs, we only
need the non-empty dynamically opened libgcc_s, but it shouldn't hurt
either.

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

Title:
Boot error: libgcc_s.so.1 must be installed for pthread_exit to work

Status in initramfs-tools package in Ubuntu:
Fix Committed
Status in initramfs-tools source package in Jammy:
Fix Committed

Bug description:
[Bug description]

On a jammy installation, which was upgraded from focal, after a full-
upgrade and a reboot,

I enter the LUKS password to decrypt the disk. Then I get the
following error:

libgcc_s.so.1 must be installed for pthread_exit to work

After the error is shown, the system asks for the password again
(which never works, always throwing the same error).

[Root cause]

I was able to decrypt the disk with the same password by booting from
a live usb. Which allowed further investigation.

The error shown in the LUKS password prompt menu comes from
https://github.com/bminor/glibc/blob/glibc-2.34/nptl/pthread_exit.c#L31-L32,
which indeed shows that pthread_exit fails when libgcc_s.so.1 is missing.

From

https://git.launchpad.net/ubuntu/+source/initramfs-tools/tree/hook-functions?h=import/0.140ubuntu10#n260,
we noticed that libgcc_s.so.1 is only copied if

1) copy_exec is called for a binary directly linked to libgcc_s.so.1, or
2) copy_exec is called for a binary linked to libpthread

The cryptsetup initramfs hook, calls copy_exec for /sbin/cryptsetup,
which is linked to libargon2.so.1, which is linked to libpthread.so.0.
This covers case (2) above. As a consequence, libgcc_s.so.1 is copied
to the initrd image and the error reported here is not seen.

However, since glibc 2.34, libpthread is shipped within glibc, and the
binaries are no longer linked to libpthread.so.0. As a consequence, an
argon2 package built with glibc 2.32 will no longer be linked to
libpthread.so.0 and libgcc_s.so.1 will no longer be copied to the
initrd image. Triggering the reported error.

This can be verified in these two argon2 builds, from the same
sources, but with different glibc versions:

https://launchpad.net/ubuntu/+source/argon2/0~20171227-0.2build21.04.0/+build/21066610

https://launchpad.net/ubuntu/+source/argon2/0~20171227-0.2build22/+build/22255217

Still lvm2 is a seeded package, which Recommends thin-provisioning-
tools. thin-provisioning-tools ships a initramfs hook that calls
copy_exec for /usr/sbin/pdata_tools, which is directly linked to
libgcc_s.so.1. This covers the case (1) above and should suffice to
ensure the boot process works properly.

Since thin-provisioning-tools is just a recommends for lvm2, it could
be removed from the system (and indeed, for some reason, was not
present in my focal=>jammy installation). In this case, a new kernel
installation should trigger the reported error.

[Reproducer]

- Install jammy with a LUKS encrypted disk
- remove thin-provisioning-tools
- perform a full-upgrade (make sure the kernel was upgraded or run
update-initramfs manually)
- reboot and verify you can no longer get past the decrypt password prompt
screen

[Workaround]

A workaround for anyone affected would be to install thin-
provisioning-tools and run update-initramfs.

[Impact]

Users upgrading from focal to jammy will eventually be locked out of
their systems in case they are using LUKS encryption.

[Additional information]

While this issue is similar to
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1861757,
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950254, and
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950551,
This is a different bug, with a different root cause.

Thanks to sergiodj for the pairing session on the root cause analysis.

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

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

[Touch-packages] [Bug 1960366] Re: skel.bashrc PS1 debian_chroot not dynamic in xterm title

2022-02-08 Thread Ubuntu Foundations Team Bug Bot

The attachment "0001-Properly-escape-PS1-for-xterm-title.patch" seems to
be a patch.  If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  skel.bashrc PS1 debian_chroot not dynamic in xterm title

Status in bash package in Ubuntu:
  New

Bug description:
  
https://git.launchpad.net/~iheino+ub/ubuntu/+source/bash/commit/?h=bugfix/1960366

  Expected:

  debian_chroot part of xterm title should update dynamically; with the
  following PS1 contents by default

  $ set | fgrep PS1 | head -1
  PS1='\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: 
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
 '

  Actual result without patch:

  debian_chroot part of xterm title got evaluated only during bash
  startup, as can be seen in PS1 contents

  $ set | fgrep PS1 | head -1
  PS1='\[\e]0;\u@\h: 
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
 '

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


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

[Touch-packages] [Bug 1950996] Re: Missing all modules for usb nics in initrd which makes PXE boot impossible

** Changed in: initramfs-tools (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

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

Status in initramfs-tools package in Ubuntu:
  Fix Committed
Status in initramfs-tools source package in Focal:
  Confirmed
Status in initramfs-tools source package in Hirsute:
  Confirmed
Status in initramfs-tools source package in Impish:
  Confirmed
Status in initramfs-tools source package in Jammy:
  Fix Committed

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

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

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

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

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

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


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

[Touch-packages] [Bug 1958594] Re: Boot error: libgcc_s.so.1 must be installed for pthread_exit to work

** Changed in: initramfs-tools (Ubuntu Jammy)
   Status: Confirmed => Fix Committed

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

Title:
  Boot error: libgcc_s.so.1 must be installed for pthread_exit to work

Status in initramfs-tools package in Ubuntu:
  Fix Committed
Status in initramfs-tools source package in Jammy:
  Fix Committed

Bug description:
  [Bug description]

  On a jammy installation, which was upgraded from focal, after a full-
  upgrade and a reboot,

  I enter the LUKS password to decrypt the disk. Then I get the
  following error:

  libgcc_s.so.1 must be installed for pthread_exit to work

  After the error is shown, the system asks for the password again
  (which never works, always throwing the same error).

  [Root cause]

  I was able to decrypt the disk with the same password by booting from
  a live usb. Which allowed further investigation.

  The error shown in the LUKS password prompt menu comes from
  https://github.com/bminor/glibc/blob/glibc-2.34/nptl/pthread_exit.c#L31-L32, 
which indeed shows that pthread_exit fails when libgcc_s.so.1 is missing.

  From
  
https://git.launchpad.net/ubuntu/+source/initramfs-tools/tree/hook-functions?h=import/0.140ubuntu10#n260,
  we noticed that libgcc_s.so.1 is only copied if

  1) copy_exec is called for a binary directly linked to libgcc_s.so.1, or
  2) copy_exec is called for a binary linked to libpthread

  The cryptsetup initramfs hook, calls copy_exec for /sbin/cryptsetup,
  which is linked to libargon2.so.1, which is linked to libpthread.so.0.
  This covers case (2) above. As a consequence, libgcc_s.so.1 is copied
  to the initrd image and the error reported here is not seen.

  However, since glibc 2.34, libpthread is shipped within glibc, and the
  binaries are no longer linked to libpthread.so.0. As a consequence, an
  argon2 package built with glibc 2.32 will no longer be linked to
  libpthread.so.0 and libgcc_s.so.1 will no longer be copied to the
  initrd image. Triggering the reported error.

  This can be verified in these two argon2 builds, from the same
  sources, but with different glibc versions:

  
https://launchpad.net/ubuntu/+source/argon2/0~20171227-0.2build21.04.0/+build/21066610
  
https://launchpad.net/ubuntu/+source/argon2/0~20171227-0.2build22/+build/22255217

  Still lvm2 is a seeded package, which Recommends thin-provisioning-
  tools. thin-provisioning-tools ships a initramfs hook that calls
  copy_exec for /usr/sbin/pdata_tools, which is directly linked to
  libgcc_s.so.1. This covers the case (1) above and should suffice to
  ensure the boot process works properly.

  Since thin-provisioning-tools is just a recommends for lvm2, it could
  be removed from the system (and indeed, for some reason, was not
  present in my focal=>jammy installation). In this case, a new kernel
  installation should trigger the reported error.

  [Reproducer]

  - Install jammy with a LUKS encrypted disk
  - remove thin-provisioning-tools
  - perform a full-upgrade (make sure the kernel was upgraded or run 
update-initramfs manually)
  - reboot and verify you can no longer get past the decrypt password prompt 
screen

  [Workaround]

  A workaround for anyone affected would be to install thin-
  provisioning-tools and run update-initramfs.

  [Impact]

  Users upgrading from focal to jammy will eventually be locked out of
  their systems in case they are using LUKS encryption.

  [Additional information]

  While this issue is similar to
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1861757,
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950254, and
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950551,
  This is a different bug, with a different root cause.

  Thanks to sergiodj for the pairing session on the root cause analysis.

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


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

[Touch-packages] [Bug 1959525] Status changed to Confirmed

2022-02-08 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 libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1959525

Title:
  Occasional no display output on 6900XT or if been idle for too long

Status in libdrm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  ## No output at boot
  The dmesg I attached is from when nothing showed at boot.

  Journal output:
  $ journalctl -r --grep amdgpu
  -- Journal begins at Thu 2022-01-27 05:36:17 EST, ends at Sun 2022-01-30 
15:58:40 EST. --
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu: probe of :0c:00.0 failed with 
error -110
  Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu: ttm finalized
  Jan 30 15:50:24 Y4M1-II kernel:  amdgpu_init+0x77/0x1000 [amdgpu]
  Jan 30 15:50:24 Y4M1-II kernel:  amdgpu_pci_probe+0x12a/0x1b0 [amdgpu]
  Jan 30 15:50:24 Y4M1-II kernel:  amdgpu_driver_load_kms.cold+0x46/0x83 
[amdgpu]
  Jan 30 15:50:24 Y4M1-II kernel:  amdgpu_driver_unload_kms+0x43/0x70 [amdgpu]
  Jan 30 15:50:24 Y4M1-II kernel:  amdgpu_device_fini+0xc5/0x1e5 [amdgpu]
  Jan 30 15:50:24 Y4M1-II kernel:  amdgpu_device_ip_fini.isra.0+0x206/0x2cd 
[amdgpu]
  Jan 30 15:50:24 Y4M1-II kernel:  gmc_v10_0_sw_fini+0x33/0x40 [amdgpu]
  Jan 30 15:50:24 Y4M1-II kernel:  amdgpu_bo_fini+0x12/0x50 [amdgpu]
  Jan 30 15:50:24 Y4M1-II kernel:  amdgpu_ttm_fini+0xab/0x100 [amdgpu]
  Jan 30 15:50:24 Y4M1-II kernel:  amdgpu_vram_mgr_fini+0xe8/0x160 [amdgpu]
  Jan 30 15:50:24 Y4M1-II kernel: Modules linked in: hid_generic usbhid hid 
amdgpu(+) iommu_v2 gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper 
crct10dif_pclmul syscopyarea crc32_pclmul sysfillrect ghash_clmulni_intel 
sysimgblt fb_sys_fops cec aesni_intel rc_core crypto_simd cryptd drm nvme ahci 
xhci_pci i2c_piix4 nvme_core igc libahci xhci_pci_renesas wmi
  Jan 30 15:50:24 Y4M1-II kernel: [drm:psp_v11_0_ring_destroy [amdgpu]] *ERROR* 
Fail to stop psp ring
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: amdgpu: 
finishing device.
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Fatal error 
during GPU init
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: 
amdgpu_device_ip_init failed
  Jan 30 15:50:24 Y4M1-II kernel: [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* 
hw_init of IP block  failed -110
  Jan 30 15:50:24 Y4M1-II kernel: [drm:amdgpu_gfx_enable_kcq.cold [amdgpu]] 
*ERROR* KCQ enable failed
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: 
[drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110)
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SMU is 
initialized successfully!
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: use vbios 
provided pptable
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SMU driver if 
version not matched
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: smu driver if 
version = 0x003d, smu fw if version = 0x0040, smu fw version = 
0x003a4700 (58.71.0)
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SECUREDISPLAY: 
securedisplay ta ucode is not available
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Will use PSP to 
load VCN firmware
  Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu: 16368M of GTT memory ready.
  Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu: 16368M of VRAM memory ready
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: AGP: 267894784M 
0x0084 - 0x
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: GART: 512M 
0x - 0x1FFF
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: VRAM: 16368M 
0x0080 - 0x0083FEFF (16368M used)
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SRAM ECC is not 
presented.
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: MEM ECC is not 
presented.
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu: ATOM BIOS: 113-EXT800216-L05
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Fetched VBIOS 
from VFCT
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Trusted Memory 
Zone (TMZ) feature not supported
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: enabling device (0006 -> 
0007)
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: vgaarb: deactivate vga 
console
  Jan 30 15:50:24 Y4M1-II kernel: fb0: switching to amdgpudrmfb from EFI VGA
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu: Topology: Add CPU node
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu: Virtual CRAT table created for CPU
  Jan 30 15:50:24 Y4M1-II kernel: amdgpu: Ignoring ACPI CRAT on non-APU system
  Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu kernel modesetting enabled.
  Jan 30 15:50:24 Y4M1-II kernel: Kernel command line:

[Touch-packages] [Bug 1958594] Re: Boot error: libgcc_s.so.1 must be installed for pthread_exit to work

With above, when testing I now get:

Adding binary /usr/lib/initramfs-tools/bin/gcc_s1-stub
Adding binary /lib/x86_64-linux-gnu/libgcc_s.so.1
Adding binary /lib/x86_64-linux-gnu/libc.so.6
Adding binary-link /usr/lib64/ld-linux-x86-64.so.2
Adding binary /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
Adding binary /lib/x86_64-linux-gnu/libpthread.so.0

which seems alright.

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

Title:
  Boot error: libgcc_s.so.1 must be installed for pthread_exit to work

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in initramfs-tools source package in Jammy:
  Confirmed

Bug description:
  [Bug description]

  On a jammy installation, which was upgraded from focal, after a full-
  upgrade and a reboot,

  I enter the LUKS password to decrypt the disk. Then I get the
  following error:

  libgcc_s.so.1 must be installed for pthread_exit to work

  After the error is shown, the system asks for the password again
  (which never works, always throwing the same error).

  [Root cause]

  I was able to decrypt the disk with the same password by booting from
  a live usb. Which allowed further investigation.

  The error shown in the LUKS password prompt menu comes from
  https://github.com/bminor/glibc/blob/glibc-2.34/nptl/pthread_exit.c#L31-L32, 
which indeed shows that pthread_exit fails when libgcc_s.so.1 is missing.

  From
  
https://git.launchpad.net/ubuntu/+source/initramfs-tools/tree/hook-functions?h=import/0.140ubuntu10#n260,
  we noticed that libgcc_s.so.1 is only copied if

  1) copy_exec is called for a binary directly linked to libgcc_s.so.1, or
  2) copy_exec is called for a binary linked to libpthread

  The cryptsetup initramfs hook, calls copy_exec for /sbin/cryptsetup,
  which is linked to libargon2.so.1, which is linked to libpthread.so.0.
  This covers case (2) above. As a consequence, libgcc_s.so.1 is copied
  to the initrd image and the error reported here is not seen.

  However, since glibc 2.34, libpthread is shipped within glibc, and the
  binaries are no longer linked to libpthread.so.0. As a consequence, an
  argon2 package built with glibc 2.32 will no longer be linked to
  libpthread.so.0 and libgcc_s.so.1 will no longer be copied to the
  initrd image. Triggering the reported error.

  This can be verified in these two argon2 builds, from the same
  sources, but with different glibc versions:

  
https://launchpad.net/ubuntu/+source/argon2/0~20171227-0.2build21.04.0/+build/21066610
  
https://launchpad.net/ubuntu/+source/argon2/0~20171227-0.2build22/+build/22255217

  Still lvm2 is a seeded package, which Recommends thin-provisioning-
  tools. thin-provisioning-tools ships a initramfs hook that calls
  copy_exec for /usr/sbin/pdata_tools, which is directly linked to
  libgcc_s.so.1. This covers the case (1) above and should suffice to
  ensure the boot process works properly.

  Since thin-provisioning-tools is just a recommends for lvm2, it could
  be removed from the system (and indeed, for some reason, was not
  present in my focal=>jammy installation). In this case, a new kernel
  installation should trigger the reported error.

  [Reproducer]

  - Install jammy with a LUKS encrypted disk
  - remove thin-provisioning-tools
  - perform a full-upgrade (make sure the kernel was upgraded or run 
update-initramfs manually)
  - reboot and verify you can no longer get past the decrypt password prompt 
screen

  [Workaround]

  A workaround for anyone affected would be to install thin-
  provisioning-tools and run update-initramfs.

  [Impact]

  Users upgrading from focal to jammy will eventually be locked out of
  their systems in case they are using LUKS encryption.

  [Additional information]

  While this issue is similar to
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1861757,
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950254, and
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950551,
  This is a different bug, with a different root cause.

  Thanks to sergiodj for the pairing session on the root cause analysis.

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


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

[Touch-packages] [Bug 1958594] Re: Boot error: libgcc_s.so.1 must be installed for pthread_exit to work

$ gcc -Wl,--no-as-needed -shared -l:libpthread.so.0 -l:libgcc_s.so.1 -o
bla

$ ldd bla 
linux-vdso.so.1 (0x7ffe0e7e6000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7feeeaa32000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7feeeaa18000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7feeea7f)
/lib64/ld-linux-x86-64.so.2 (0x7feeeaa7f000)


might do it.

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

Title:
  Boot error: libgcc_s.so.1 must be installed for pthread_exit to work

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in initramfs-tools source package in Jammy:
  Confirmed

Bug description:
  [Bug description]

  On a jammy installation, which was upgraded from focal, after a full-
  upgrade and a reboot,

  I enter the LUKS password to decrypt the disk. Then I get the
  following error:

  libgcc_s.so.1 must be installed for pthread_exit to work

  After the error is shown, the system asks for the password again
  (which never works, always throwing the same error).

  [Root cause]

  I was able to decrypt the disk with the same password by booting from
  a live usb. Which allowed further investigation.

  The error shown in the LUKS password prompt menu comes from
  https://github.com/bminor/glibc/blob/glibc-2.34/nptl/pthread_exit.c#L31-L32, 
which indeed shows that pthread_exit fails when libgcc_s.so.1 is missing.

  From
  
https://git.launchpad.net/ubuntu/+source/initramfs-tools/tree/hook-functions?h=import/0.140ubuntu10#n260,
  we noticed that libgcc_s.so.1 is only copied if

  1) copy_exec is called for a binary directly linked to libgcc_s.so.1, or
  2) copy_exec is called for a binary linked to libpthread

  The cryptsetup initramfs hook, calls copy_exec for /sbin/cryptsetup,
  which is linked to libargon2.so.1, which is linked to libpthread.so.0.
  This covers case (2) above. As a consequence, libgcc_s.so.1 is copied
  to the initrd image and the error reported here is not seen.

  However, since glibc 2.34, libpthread is shipped within glibc, and the
  binaries are no longer linked to libpthread.so.0. As a consequence, an
  argon2 package built with glibc 2.32 will no longer be linked to
  libpthread.so.0 and libgcc_s.so.1 will no longer be copied to the
  initrd image. Triggering the reported error.

  This can be verified in these two argon2 builds, from the same
  sources, but with different glibc versions:

  
https://launchpad.net/ubuntu/+source/argon2/0~20171227-0.2build21.04.0/+build/21066610
  
https://launchpad.net/ubuntu/+source/argon2/0~20171227-0.2build22/+build/22255217

  Still lvm2 is a seeded package, which Recommends thin-provisioning-
  tools. thin-provisioning-tools ships a initramfs hook that calls
  copy_exec for /usr/sbin/pdata_tools, which is directly linked to
  libgcc_s.so.1. This covers the case (1) above and should suffice to
  ensure the boot process works properly.

  Since thin-provisioning-tools is just a recommends for lvm2, it could
  be removed from the system (and indeed, for some reason, was not
  present in my focal=>jammy installation). In this case, a new kernel
  installation should trigger the reported error.

  [Reproducer]

  - Install jammy with a LUKS encrypted disk
  - remove thin-provisioning-tools
  - perform a full-upgrade (make sure the kernel was upgraded or run 
update-initramfs manually)
  - reboot and verify you can no longer get past the decrypt password prompt 
screen

  [Workaround]

  A workaround for anyone affected would be to install thin-
  provisioning-tools and run update-initramfs.

  [Impact]

  Users upgrading from focal to jammy will eventually be locked out of
  their systems in case they are using LUKS encryption.

  [Additional information]

  While this issue is similar to
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1861757,
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950254, and
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950551,
  This is a different bug, with a different root cause.

  Thanks to sergiodj for the pairing session on the root cause analysis.

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


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

[Touch-packages] [Bug 1958594] Re: Boot error: libgcc_s.so.1 must be installed for pthread_exit to work

With that branch rebased, and typpos fixed up testing locally does
produce this:

Adding binary /usr/lib/initramfs-tools/bin/gcc_s1-stub
Adding binary /lib/x86_64-linux-gnu/libgcc_s.so.1
Adding binary /lib/x86_64-linux-gnu/libc.so.6
Adding binary-link /usr/lib64/ld-linux-x86-64.so.2
Adding binary /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2


Let me see if i can force linkage with pthreads too.

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

Title:
  Boot error: libgcc_s.so.1 must be installed for pthread_exit to work

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in initramfs-tools source package in Jammy:
  Confirmed

Bug description:
  [Bug description]

  On a jammy installation, which was upgraded from focal, after a full-
  upgrade and a reboot,

  I enter the LUKS password to decrypt the disk. Then I get the
  following error:

  libgcc_s.so.1 must be installed for pthread_exit to work

  After the error is shown, the system asks for the password again
  (which never works, always throwing the same error).

  [Root cause]

  I was able to decrypt the disk with the same password by booting from
  a live usb. Which allowed further investigation.

  The error shown in the LUKS password prompt menu comes from
  https://github.com/bminor/glibc/blob/glibc-2.34/nptl/pthread_exit.c#L31-L32, 
which indeed shows that pthread_exit fails when libgcc_s.so.1 is missing.

  From
  
https://git.launchpad.net/ubuntu/+source/initramfs-tools/tree/hook-functions?h=import/0.140ubuntu10#n260,
  we noticed that libgcc_s.so.1 is only copied if

  1) copy_exec is called for a binary directly linked to libgcc_s.so.1, or
  2) copy_exec is called for a binary linked to libpthread

  The cryptsetup initramfs hook, calls copy_exec for /sbin/cryptsetup,
  which is linked to libargon2.so.1, which is linked to libpthread.so.0.
  This covers case (2) above. As a consequence, libgcc_s.so.1 is copied
  to the initrd image and the error reported here is not seen.

  However, since glibc 2.34, libpthread is shipped within glibc, and the
  binaries are no longer linked to libpthread.so.0. As a consequence, an
  argon2 package built with glibc 2.32 will no longer be linked to
  libpthread.so.0 and libgcc_s.so.1 will no longer be copied to the
  initrd image. Triggering the reported error.

  This can be verified in these two argon2 builds, from the same
  sources, but with different glibc versions:

  
https://launchpad.net/ubuntu/+source/argon2/0~20171227-0.2build21.04.0/+build/21066610
  
https://launchpad.net/ubuntu/+source/argon2/0~20171227-0.2build22/+build/22255217

  Still lvm2 is a seeded package, which Recommends thin-provisioning-
  tools. thin-provisioning-tools ships a initramfs hook that calls
  copy_exec for /usr/sbin/pdata_tools, which is directly linked to
  libgcc_s.so.1. This covers the case (1) above and should suffice to
  ensure the boot process works properly.

  Since thin-provisioning-tools is just a recommends for lvm2, it could
  be removed from the system (and indeed, for some reason, was not
  present in my focal=>jammy installation). In this case, a new kernel
  installation should trigger the reported error.

  [Reproducer]

  - Install jammy with a LUKS encrypted disk
  - remove thin-provisioning-tools
  - perform a full-upgrade (make sure the kernel was upgraded or run 
update-initramfs manually)
  - reboot and verify you can no longer get past the decrypt password prompt 
screen

  [Workaround]

  A workaround for anyone affected would be to install thin-
  provisioning-tools and run update-initramfs.

  [Impact]

  Users upgrading from focal to jammy will eventually be locked out of
  their systems in case they are using LUKS encryption.

  [Additional information]

  While this issue is similar to
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1861757,
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950254, and
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950551,
  This is a different bug, with a different root cause.

  Thanks to sergiodj for the pairing session on the root cause analysis.

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


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

[Touch-packages] [Bug 1960366] Re: skel.bashrc PS1 debian_chroot not dynamic in xterm title

2022-02-08 Thread Tuomas Heino

** Patch added: "0001-Properly-escape-PS1-for-xterm-title.patch"
   
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1960366/+attachment/5559792/+files/0001-Properly-escape-PS1-for-xterm-title.patch

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

Title:
  skel.bashrc PS1 debian_chroot not dynamic in xterm title

Status in bash package in Ubuntu:
  New

Bug description:
  
https://git.launchpad.net/~iheino+ub/ubuntu/+source/bash/commit/?h=bugfix/1960366

  Expected:

  debian_chroot part of xterm title should update dynamically; with the
  following PS1 contents by default

  $ set | fgrep PS1 | head -1
  PS1='\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: 
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
 '

  Actual result without patch:

  debian_chroot part of xterm title got evaluated only during bash
  startup, as can be seen in PS1 contents

  $ set | fgrep PS1 | head -1
  PS1='\[\e]0;\u@\h: 
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
 '

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


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

[Touch-packages] [Bug 1960366] Re: skel.bashrc PS1 debian_chroot not dynamic in xterm title

2022-02-08 Thread Tuomas Heino

Added a patch at
https://git.launchpad.net/~iheino+ub/ubuntu/+source/bash/commit/?h=bugfix/1960366

** Description changed:

- Submitting a patch soon.
+ 
https://git.launchpad.net/~iheino+ub/ubuntu/+source/bash/commit/?h=bugfix/1960366
  
- Without fix:
- $ set|fgrep PS1|head -1
+ Expected:
+ 
+ debian_chroot part of xterm title should update dynamically; with the
+ following PS1 contents by default
+ 
+ $ set | fgrep PS1 | head -1
+ PS1='\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: 
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
 '
+ 
+ Actual result without patch:
+ 
+ debian_chroot part of xterm title got evaluated only during bash
+ startup, as can be seen in PS1 contents
+ 
+ $ set | fgrep PS1 | head -1
  PS1='\[\e]0;\u@\h: 
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
 '
- 
- With quotation fix applied:
- $ set|fgrep PS1|head -1
- PS1='\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: 
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
 '

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

Title:
  skel.bashrc PS1 debian_chroot not dynamic in xterm title

Status in bash package in Ubuntu:
  New

Bug description:
  
https://git.launchpad.net/~iheino+ub/ubuntu/+source/bash/commit/?h=bugfix/1960366

  Expected:

  debian_chroot part of xterm title should update dynamically; with the
  following PS1 contents by default

  $ set | fgrep PS1 | head -1
  PS1='\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: 
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
 '

  Actual result without patch:

  debian_chroot part of xterm title got evaluated only during bash
  startup, as can be seen in PS1 contents

  $ set | fgrep PS1 | head -1
  PS1='\[\e]0;\u@\h: 
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
 '

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


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

[Touch-packages] [Bug 1959085] Re: Ubuntu 21.10 boot stuck in initramfs

2022-02-08 Thread Brian Murray

** Tags added: rls-ii-incoming

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

Title:
  Ubuntu 21.10 boot stuck in initramfs

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I just installed the latest Ubuntu desktop from iso file
  ubuntu-21.10-desktop-amd64.iso inside of VMWare workstation. I chose
  ZFS and native ZFS encryption of the filesystem. The installation went
  fine. Everything worked as expected.

  Then I upgraded the packages to the latest version via the Software
  updater. After reboot I'm stuck in the initramfs prompt. The following
  command fails:

  mount -o zfsutil -t zfs rpool/ROOT/ubuntu_gtw63h /root//

  Permission denied.

  And the system never asks me for the password to unlock the root fs.

  So, I'm guessing that there is something wrong with the new initramfs
  disk: initrd.img-5.13.0-27-generic

  When I reboot and select the previous version in grub:
  initrd.img-5.13.0-27-generic, the system asks for the password and
  boots without a problem.

  Thanks.

  To summarize:

  1. Installed new VM using the Ubuntu iso image. Chose ZFS native encryption. 
Minimal install.
  2. As soon as the system came up, I hit the update/upgrade prompt. Rebooted 
and failed to boot the new version.

  I didn't customize anything or installed anything extra.

  root@ubud01:/var# lsb_release -rd
  Description:  Ubuntu 21.10
  Release:  21.10

  root@ubud01:/var# dpkg -l | grep zfs
  ii  libzfs4linux   2.0.6-1ubuntu2 
amd64OpenZFS filesystem library for Linux
  ii  zfs-initramfs  2.0.6-1ubuntu2 
amd64OpenZFS root filesystem capabilities for Linux - 
initramfs
  ii  zfs-zed2.0.6-1ubuntu2 
amd64OpenZFS Event Daemon
  ii  zfsutils-linux 2.0.6-1ubuntu2 
amd64command-line tools to manage OpenZFS filesystems

  root@ubud01:/var# dpkg -l | grep init
  ii  busybox-initramfs  1:1.30.1-6ubuntu3.1
amd64Standalone shell setup for initramfs
  ii  cryptsetup-initramfs   2:2.3.6-0ubuntu1   
all  disk encryption support - initramfs integration
  ii  gnome-initial-setup40.4-1ubuntu1  
amd64Initial GNOME system setup helper
  ii  init   1.60build1 
amd64metapackage ensuring an init system is installed
  ii  init-system-helpers1.60build1 
all  helper tools for all init systems
  ii  initramfs-tools0.140ubuntu6   
all  generic modular initramfs generator (automation)
  ii  initramfs-tools-bin0.140ubuntu6   
amd64binaries used by initramfs-tools
  ii  initramfs-tools-core   0.140ubuntu6   
all  generic modular initramfs generator (core tools)
  ii  libatopology2:amd641.2.4-1.1ubuntu3.1 
amd64shared library for handling ALSA topology definitions
  ii  libklibc:amd64 2.0.8-6.1ubuntu2   
amd64minimal libc subset for use with initramfs
  ii  lsb-base   11.1.0ubuntu3  
all  Linux Standard Base init script functionality
  ii  ncurses-base   6.2+20201114-2build1   
all  basic terminal type definitions
  ii  sysvinit-utils 2.96-7ubuntu1  
amd64System-V-like utilities
  ii  xinit  1.4.1-0ubuntu3 
amd64X server initialisation tool
  ii  zfs-initramfs  2.0.6-1ubuntu2 
amd64OpenZFS root filesystem capabilities for Linux - 
initramfs

  root@ubud01:/var# zfs list
  NAME   USED  AVAIL REFER  
MOUNTPOINT
  bpool  290M   542M   96K  
/boot
  bpool/BOOT 289M   542M   96K  none
  bpool/BOOT/ubuntu_gtw63h   288M   542M  156M  
/boot
  rpool 6.39G  10.6G  192K  /
  rpool/ROOT5.64G  10.6G  192K  none
  rpool/ROOT/ubuntu_gtw63h

[Touch-packages] [Bug 1960366] [NEW] skel.bashrc PS1 debian_chroot not dynamic in xterm title

2022-02-08 Thread Tuomas Heino

Public bug reported:

Submitting a patch soon.

Without fix:
$ set|fgrep PS1|head -1
PS1='\[\e]0;\u@\h: 
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
 '

With quotation fix applied:
$ set|fgrep PS1|head -1
PS1='\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: 
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
 '

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

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

Title:
  skel.bashrc PS1 debian_chroot not dynamic in xterm title

Status in bash package in Ubuntu:
  New

Bug description:
  Submitting a patch soon.

  Without fix:
  $ set|fgrep PS1|head -1
  PS1='\[\e]0;\u@\h: 
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
 '

  With quotation fix applied:
  $ set|fgrep PS1|head -1
  PS1='\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: 
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
 '

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


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

[Touch-packages] [Bug 1958594] Re: Boot error: libgcc_s.so.1 must be installed for pthread_exit to work

2022-02-08 Thread Sergio Durigan Junior

Dimitri,

I don't know if this will suffice.  With glibc's decision to remove
libpthread, I believe we will need to explicitly copy libpthread.so, at
least temporarily until everything else doesn't explicitly link against
it.

Taking the stub binary your MP is generating as an example (running on
Jammy):

# gcc -Wl,--no-as-needed -shared -pthread -l:libgcc_s.so.1 -o bla
# ldd bla 
linux-vdso.so.1 (0x7ffdba94d000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f581d651000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f581d429000)
/lib64/ld-linux-x86-64.so.2 (0x7f581d678000)

We see that it's not linked against pthread.

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

Title:
  Boot error: libgcc_s.so.1 must be installed for pthread_exit to work

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in initramfs-tools source package in Jammy:
  Confirmed

Bug description:
  [Bug description]

  On a jammy installation, which was upgraded from focal, after a full-
  upgrade and a reboot,

  I enter the LUKS password to decrypt the disk. Then I get the
  following error:

  libgcc_s.so.1 must be installed for pthread_exit to work

  After the error is shown, the system asks for the password again
  (which never works, always throwing the same error).

  [Root cause]

  I was able to decrypt the disk with the same password by booting from
  a live usb. Which allowed further investigation.

  The error shown in the LUKS password prompt menu comes from
  https://github.com/bminor/glibc/blob/glibc-2.34/nptl/pthread_exit.c#L31-L32, 
which indeed shows that pthread_exit fails when libgcc_s.so.1 is missing.

  From
  
https://git.launchpad.net/ubuntu/+source/initramfs-tools/tree/hook-functions?h=import/0.140ubuntu10#n260,
  we noticed that libgcc_s.so.1 is only copied if

  1) copy_exec is called for a binary directly linked to libgcc_s.so.1, or
  2) copy_exec is called for a binary linked to libpthread

  The cryptsetup initramfs hook, calls copy_exec for /sbin/cryptsetup,
  which is linked to libargon2.so.1, which is linked to libpthread.so.0.
  This covers case (2) above. As a consequence, libgcc_s.so.1 is copied
  to the initrd image and the error reported here is not seen.

  However, since glibc 2.34, libpthread is shipped within glibc, and the
  binaries are no longer linked to libpthread.so.0. As a consequence, an
  argon2 package built with glibc 2.32 will no longer be linked to
  libpthread.so.0 and libgcc_s.so.1 will no longer be copied to the
  initrd image. Triggering the reported error.

  This can be verified in these two argon2 builds, from the same
  sources, but with different glibc versions:

  
https://launchpad.net/ubuntu/+source/argon2/0~20171227-0.2build21.04.0/+build/21066610
  
https://launchpad.net/ubuntu/+source/argon2/0~20171227-0.2build22/+build/22255217

  Still lvm2 is a seeded package, which Recommends thin-provisioning-
  tools. thin-provisioning-tools ships a initramfs hook that calls
  copy_exec for /usr/sbin/pdata_tools, which is directly linked to
  libgcc_s.so.1. This covers the case (1) above and should suffice to
  ensure the boot process works properly.

  Since thin-provisioning-tools is just a recommends for lvm2, it could
  be removed from the system (and indeed, for some reason, was not
  present in my focal=>jammy installation). In this case, a new kernel
  installation should trigger the reported error.

  [Reproducer]

  - Install jammy with a LUKS encrypted disk
  - remove thin-provisioning-tools
  - perform a full-upgrade (make sure the kernel was upgraded or run 
update-initramfs manually)
  - reboot and verify you can no longer get past the decrypt password prompt 
screen

  [Workaround]

  A workaround for anyone affected would be to install thin-
  provisioning-tools and run update-initramfs.

  [Impact]

  Users upgrading from focal to jammy will eventually be locked out of
  their systems in case they are using LUKS encryption.

  [Additional information]

  While this issue is similar to
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1861757,
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950254, and
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950551,
  This is a different bug, with a different root cause.

  Thanks to sergiodj for the pairing session on the root cause analysis.

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


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

[Touch-packages] [Bug 1950996] Re: Missing all modules for usb nics in initrd which makes PXE boot impossible

** Changed in: initramfs-tools (Ubuntu Jammy)
   Status: Triaged => In Progress

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

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

Status in initramfs-tools package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Focal:
  Confirmed
Status in initramfs-tools source package in Hirsute:
  Confirmed
Status in initramfs-tools source package in Impish:
  Confirmed
Status in initramfs-tools source package in Jammy:
  In Progress

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

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

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

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

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

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


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

[Touch-packages] [Bug 1958594] Re: Boot error: libgcc_s.so.1 must be installed for pthread_exit to work

We have been bitten by this before. And Last time I did proposed to do
this:

- create a stub binary tha tis linked with pthread and libgcc_s
- copy_exec that into the initramfs

https://code.launchpad.net/~xnox/ubuntu/+source/initramfs-
tools/+git/initramfs-tools/+merge/385243

This ensures that at least one binary wants pthreads and libgcc_s and
those things get copied into the initramfs correctly and always for the
host architecture.

I had to do this with a binary, because precisely like raof says we
never know which architecture we need, and which hw optimized version of
those libraries is needed.

I feel like I should upload the above (rebased on jammy) into jammy to
get this done once and for all. Kind of sad that I didn't do that 2
years ago. Which would have avoided this issue today.

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

Title:
Boot error: libgcc_s.so.1 must be installed for pthread_exit to work

Status in initramfs-tools package in Ubuntu:
Confirmed
Status in initramfs-tools source package in Jammy:
Confirmed

Bug description:
[Bug description]

On a jammy installation, which was upgraded from focal, after a full-
upgrade and a reboot,

I enter the LUKS password to decrypt the disk. Then I get the
following error:

libgcc_s.so.1 must be installed for pthread_exit to work

After the error is shown, the system asks for the password again
(which never works, always throwing the same error).

[Root cause]

I was able to decrypt the disk with the same password by booting from
a live usb. Which allowed further investigation.

From

https://git.launchpad.net/ubuntu/+source/initramfs-tools/tree/hook-functions?h=import/0.140ubuntu10#n260,
we noticed that libgcc_s.so.1 is only copied if

1) copy_exec is called for a binary directly linked to libgcc_s.so.1, or
2) copy_exec is called for a binary linked to libpthread

This can be verified in these two argon2 builds, from the same
sources, but with different glibc versions:

https://launchpad.net/ubuntu/+source/argon2/0~20171227-0.2build21.04.0/+build/21066610

https://launchpad.net/ubuntu/+source/argon2/0~20171227-0.2build22/+build/22255217

[Reproducer]

[Workaround]

A workaround for anyone affected would be to install thin-
provisioning-tools and run update-initramfs.

[Impact]

Users upgrading from focal to jammy will eventually be locked out of
their systems in case they are using LUKS encryption.

[Additional information]

Thanks to sergiodj for the pairing session on the root cause analysis.

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

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

[Touch-packages] [Bug 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}

2022-02-08 Thread Andreas Hasenack

** Changed in: rsync (Ubuntu Bionic)
   Status: New => In Progress

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

Title:
  rsync hangs on select(5, [], [4], [], {60, 0}

Status in rsync:
  Unknown
Status in rsync package in Ubuntu:
  Confirmed
Status in rsync source package in Bionic:
  In Progress
Status in rsync source package in Focal:
  In Progress

Bug description:
  [Impact]

  What the user suffering from this bug experiences is that the big
  amount of informative messages related to the copy process with the
  three spawned processes(sender, receiver and generator)  exhaust the
  I/O buffer and the sync gets stuck, either because there are too many
  files to synchronise and/or because too many detail messages (levels
  of verbose mode) have been requested in the output.

  The fix, that comes from upstream and is applied there since version
  3.2.0., increments the size of the receiver's I/O buffer.

  [Test Plan]
  This test plan is for Focal, but it's the same for Bionic.

  0.Preparing the test environment:

  #Preparing the container
  lxc launch images:ubuntu/focal rsync-iobuffer-focal
  lxc shell rsync-iobuffer-focal
  apt update -y
  apt upgrade -y

  #Installing necessary tools
  apt install rsync

  #Get test cases from comments #16 and #19 on this LP bug: As test case
  #16 covers both aspects (a lot of files and upper verbosity) and test
  #19 uses a huge tarball (120 Mb), I'm removing from this SRU the #19
  scenario  (but, please, feel to reach me it if you consider it
  necessary and I'll provide the steps and bad/good scenarios).

  cd /tmp/

  #16
  Paste the contents of https://pastebin.com/raw/ctzJJGwt:

  #!/bin/bash
  mkdir source_dir
  pushd source_dir
  dd if=/dev/zero of=source bs=600K count=1

  for i in `seq 1 11500`;
  do
  cp -v source file_$i;
  done

  rm source

  for i in `seq 1 10`;
  do
   dd if=/dev/zero of=file_large_$i bs=200M count=1
  done

  popd

  echo "Created 11500 files with size 600K and 10 files with size 200M, try the 
following command:"
  echo "rsync -avvvz --delete source_dir target_dir"

  in a new file script_comment16.sh

  chmod +x script_comment16.sh
  ./script_comment16.sh

  1. Bad cases (without and with using strace):

  # Scenario from comment 16
  $ rsync -avvvz --delete source_dir target_dir
  sending incremental file list
  [sender] make_file(source_dir,*,0)
  send_file_list done
  [sender] pushing local filters for /root/source_dir/
  [sender] make_file(source_dir/file_3048,*,2)
  [sender] make_file(source_dir/file_11358,*,2)
  [sender] make_file(source_dir/file_5914,*,2)
  [sender] make_file(source_dir/file_5880,*,2)
  [sender] make_file(source_dir/file_9318,*,2)
  [sender] make_file(source_dir/file_5539,*,2)
  [...]
  sending file_sum
  false_alarms=0 hash_hits=0 matches=0
  sender finished source_dir/file_10807
  send_files(903, source_dir/file_10808)
  send_files mapped source_dir/file_10808 of size 614400
  calling match_sums source_dir/file_10808
  source_dir/file_10808

  It hangs here, where using strace we can see:

  $ strace rsync -avvvz --delete source_dir target_dir
  source_dir/file_11280
  read(3, 
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 262144) 
= 262144
  read(3, 
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 262144) 
= 262144
  read(3, 
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 90112) = 
90112
  select(6, [5], [4], [5], {tv_sec=60, tv_usec=0}) = 1 (in [5], left 
{tv_sec=59, tv_usec=96})
  read(5, 
"\0\0\0\0\0\0\0\1\0\240\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\240\0\0\0"..., 
1900) = 1900
  select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
  select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
  select(5, [], [4], [], {tv_sec=60, tv_usec=0}

  1. Good cases:

  # Scenario from comment 16

  $ rsync -avvvz --delete source_dir target_dir
  sending incremental file list
  [sender] make_file(source_dir,*,0)
  send_file_list done
  [sender] pushing local filters for /tmp/source_dir/
  [sender] make_file(source_dir/file_3052,*,2)
  [sender] make_file(source_dir/file_1766,*,2)
  [sender] make_file(source_dir/file_10466,*,2)
  [sender] make_file(source_dir/file_9375,*,2)
  [sender] make_file(source_dir/file_7260,*,2)
  [sender] make_file(source_dir/file_5554,*,2)
  [sender] make_file(source_dir/file_5523,*,2)
  [sender] make_file(source_dir/file_1685,*,2)
  [sender] make_file(source_dir/file_7217,*,2)
  [sender] make_file(source_dir/file_10411,*,2)
  [...]
  generate_files finished

  sent 9,555,678 bytes  received 3,599,560 bytes  124,694.20 bytes/sec
  total size is 9,162,752,000  speedup is 696.51

  [Where problems could occur]

  Perhaps the buffer size may not be sufficient for an operation
  involving a very huge amount of data, as reported upstream here (

[Touch-packages] [Bug 1960094] Re: lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal

2022-02-08 Thread Stéphane Graber

** Changed in: lxc (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: lxc (Ubuntu Focal)
   Status: Incomplete => Invalid

** No longer affects: lxc (Ubuntu)

** No longer affects: lxc (Ubuntu Focal)

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

Title:
  lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal

Status in linux package in Ubuntu:
  New
Status in linux source package in Focal:
  New

Bug description:
  There are failures in ubuntu_lxc regression tests on Focal/linux/5.4.0-99.112 
sru cycle 2022.01.03 with the error
  lxc-create: symbol lookup error: lxc-create: undefined symbol: strlcat

  These errors did not appear on previous kernels in the same cycle and
  now have a few tests failing on all architectures and systems as of
  Feb 4th 2022 it seems. Log with details is attached in the comments.

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


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

[Touch-packages] [Bug 1927063] Re: Terminal prompt got strangely replicated when resizing terminal horizontally

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

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

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

Title:
  Terminal prompt got strangely replicated when resizing terminal
  horizontally

Status in bash package in Ubuntu:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in mate-terminal package in Ubuntu:
  Confirmed
Status in readline package in Ubuntu:
  Confirmed
Status in tilix package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu installed
  2. Launch MATE Terminal
  3. Navigate to some folder with long name - `cd 
/usr/share/doc/ayatana-indicator-application`
  4. Resize terminal horizontally

  Expected results:
  * terminal shows the same 
"user@host:/usr/share/doc/ayatana-indicator-application$" with single occurrence

  Actual results:
  * terminal shows multiple occurrencies of 
"user@host:/usr/share/doc/ayatana-indicator-application$"

  (see attached screencast)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: mate-terminal 1.24.1-1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Tue May  4 10:54:59 2021
  InstallationDate: Installed on 2021-04-23 (10 days ago)
  InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
  SourcePackage: mate-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1958904] Update Released

2022-02-08 Thread Brian Murray

The verification of the Stable Release Update for initramfs-tools has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  autopkgtest is failing on jammy with "no space left on device"

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Invalid
Status in initramfs-tools source package in Focal:
  Fix Released
Status in initramfs-tools source package in Impish:
  Fix Released

Bug description:
  [Impact]
  In debian/tests/prep-image we create an image file of 1GB, but recent 
jammy/focal cloud images are (barely) bigger than that, for example the current 
one uncompressed is 1001MB...

  Example of a test failure:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/i/initramfs-tools/20220126_160323_8bcd1@/log.gz

  Maybe we should consider to create image files of 2GB or even bigger,
  considering that we are only going to allocate the space that is
  actually needed, because we create the file using truncate.

  [Test Plan]
  Run autotestpkg tests from initramfs-tools package. The "net" test is the one 
that depends on the image created by 'prep-image'. The testcase should complete 
successfully without the temporary image running out of space.

  [Where problems could occur]
  The creation of a larger image for the tests could fail if the filesystem of 
the test system is low on disk space. However, as mentioned before, as the 
image file is created using 'truncate', only the necessary space needed to 
uncompress the cloudimg will be used on the filesystem. Apart from that, we 
assume that 2GB of free space should be available on every test system used for 
Ubuntu autopkgtest.

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


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

[Touch-packages] [Bug 1958904] Re: autopkgtest is failing on jammy with "no space left on device"

This bug was fixed in the package initramfs-tools - 0.136ubuntu6.7

---
initramfs-tools (0.136ubuntu6.7) focal; urgency=medium

  * Increase image file to 2GB in autopkgtest (LP: #1958904)

 -- Kleber Sacilotto de Souza   Wed, 26 Jan
2022 18:11:24 +0100

** Changed in: initramfs-tools (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  autopkgtest is failing on jammy with "no space left on device"

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Invalid
Status in initramfs-tools source package in Focal:
  Fix Released
Status in initramfs-tools source package in Impish:
  Fix Released

Bug description:
  [Impact]
  In debian/tests/prep-image we create an image file of 1GB, but recent 
jammy/focal cloud images are (barely) bigger than that, for example the current 
one uncompressed is 1001MB...

  Example of a test failure:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/i/initramfs-tools/20220126_160323_8bcd1@/log.gz

  Maybe we should consider to create image files of 2GB or even bigger,
  considering that we are only going to allocate the space that is
  actually needed, because we create the file using truncate.

  [Test Plan]
  Run autotestpkg tests from initramfs-tools package. The "net" test is the one 
that depends on the image created by 'prep-image'. The testcase should complete 
successfully without the temporary image running out of space.

  [Where problems could occur]
  The creation of a larger image for the tests could fail if the filesystem of 
the test system is low on disk space. However, as mentioned before, as the 
image file is created using 'truncate', only the necessary space needed to 
uncompress the cloudimg will be used on the filesystem. Apart from that, we 
assume that 2GB of free space should be available on every test system used for 
Ubuntu autopkgtest.

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


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

[Touch-packages] [Bug 1958904] Re: autopkgtest is failing on jammy with "no space left on device"

This bug was fixed in the package initramfs-tools - 0.140ubuntu6.1

---
initramfs-tools (0.140ubuntu6.1) impish; urgency=medium

  * Increase image file to 2GB in autopkgtest (LP: #1958904)

 -- Kleber Sacilotto de Souza   Wed, 26 Jan
2022 17:03:17 +0100

** Changed in: initramfs-tools (Ubuntu Impish)
   Status: Fix Committed => Fix Released

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

Title:
  autopkgtest is failing on jammy with "no space left on device"

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Invalid
Status in initramfs-tools source package in Focal:
  Fix Released
Status in initramfs-tools source package in Impish:
  Fix Released

Bug description:
  [Impact]
  In debian/tests/prep-image we create an image file of 1GB, but recent 
jammy/focal cloud images are (barely) bigger than that, for example the current 
one uncompressed is 1001MB...

  Example of a test failure:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/i/initramfs-tools/20220126_160323_8bcd1@/log.gz

  Maybe we should consider to create image files of 2GB or even bigger,
  considering that we are only going to allocate the space that is
  actually needed, because we create the file using truncate.

  [Test Plan]
  Run autotestpkg tests from initramfs-tools package. The "net" test is the one 
that depends on the image created by 'prep-image'. The testcase should complete 
successfully without the temporary image running out of space.

  [Where problems could occur]
  The creation of a larger image for the tests could fail if the filesystem of 
the test system is low on disk space. However, as mentioned before, as the 
image file is created using 'truncate', only the necessary space needed to 
uncompress the cloudimg will be used on the filesystem. Apart from that, we 
assume that 2GB of free space should be available on every test system used for 
Ubuntu autopkgtest.

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


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

[Touch-packages] [Bug 1960268] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1960268/+attachment/5559766/+files/ProcCpuinfoMinimal.txt

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

Title:
  SSL handshake failed - VPN SSL broken in 22.04

Status in openssl package in Ubuntu:
  New

Bug description:
  I'm trying to connect with global protect VPN but fails at login with:

  SSL handshake failed
  Failed to load URL https://...
  QtNetwork Error 6

  Another VPN client does work but the rdp connection to a remote server fails 
with:

  transport_connect_tls:freerdp_set_last_error_ex ERRCONNECT_TLS_CONNECT_FAILED
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-03-19 (325 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: openssl 3.0.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Tags:  wayland-session impish
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: Upgraded to impish on 2022-02-04 (3 days ago)
  UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare 
sudo uinput
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-03-19 (325 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: openssl 3.0.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-02-04 (3 days ago)
  UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare 
sudo uinput
  _MarkForUpload: True

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


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

[Touch-packages] [Bug 1960268] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1960268/+attachment/5559767/+files/ProcEnviron.txt

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

Title:
  SSL handshake failed - VPN SSL broken in 22.04

Status in openssl package in Ubuntu:
  New

Bug description:
  I'm trying to connect with global protect VPN but fails at login with:

  SSL handshake failed
  Failed to load URL https://...
  QtNetwork Error 6

  Another VPN client does work but the rdp connection to a remote server fails 
with:

  transport_connect_tls:freerdp_set_last_error_ex ERRCONNECT_TLS_CONNECT_FAILED
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-03-19 (325 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: openssl 3.0.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Tags:  wayland-session impish
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: Upgraded to impish on 2022-02-04 (3 days ago)
  UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare 
sudo uinput
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-03-19 (325 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: openssl 3.0.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-02-04 (3 days ago)
  UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare 
sudo uinput
  _MarkForUpload: True

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


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

[Touch-packages] [Bug 1960268] Re: SSL handshake failed - VPN SSL broken in 22.04

apport information

** Tags added: jammy

** Description changed:

  I'm trying to connect with global protect VPN but fails at login with:
  
  SSL handshake failed
  Failed to load URL https://...
  QtNetwork Error 6
  
  Another VPN client does work but the rdp connection to a remote server fails 
with:

  transport_connect_tls:freerdp_set_last_error_ex ERRCONNECT_TLS_CONNECT_FAILED
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-03-19 (325 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: openssl 3.0.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Tags:  wayland-session impish
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: Upgraded to impish on 2022-02-04 (3 days ago)
  UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare 
sudo uinput
  _MarkForUpload: True
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu76
+ Architecture: amd64
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2021-03-19 (325 days ago)
+ InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
+ Package: openssl 3.0.1-0ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
+ Tags:  wayland-session jammy
+ Uname: Linux 5.15.0-18-generic x86_64
+ UpgradeStatus: Upgraded to jammy on 2022-02-04 (3 days ago)
+ UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare 
sudo uinput
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1960268/+attachment/5559765/+files/Dependencies.txt

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

Title:
  SSL handshake failed - VPN SSL broken in 22.04

Status in openssl package in Ubuntu:
  New

Bug description:
  I'm trying to connect with global protect VPN but fails at login with:

  SSL handshake failed
  Failed to load URL https://...
  QtNetwork Error 6

  Another VPN client does work but the rdp connection to a remote server fails 
with:

  transport_connect_tls:freerdp_set_last_error_ex ERRCONNECT_TLS_CONNECT_FAILED
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-03-19 (325 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: openssl 3.0.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Tags:  wayland-session impish
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: Upgraded to impish on 2022-02-04 (3 days ago)
  UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare 
sudo uinput
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-03-19 (325 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: openssl 3.0.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-02-04 (3 days ago)
  UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare 
sudo uinput
  _MarkForUpload: True

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


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

[Touch-packages] [Bug 1960268] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1960268/+attachment/5559757/+files/ProcCpuinfoMinimal.txt

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

Title:
  SSL handshake failed - VPN SSL broken in 22.04

Status in openssl package in Ubuntu:
  New

Bug description:
  I'm trying to connect with global protect VPN but fails at login with:

  SSL handshake failed
  Failed to load URL https://...
  QtNetwork Error 6

  Another VPN client does work but the rdp connection to a remote server fails 
with:

  transport_connect_tls:freerdp_set_last_error_ex ERRCONNECT_TLS_CONNECT_FAILED
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-03-19 (325 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: openssl 3.0.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Tags:  wayland-session impish
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: Upgraded to impish on 2022-02-04 (3 days ago)
  UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare 
sudo uinput
  _MarkForUpload: True

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


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

[Touch-packages] [Bug 1960268] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1960268/+attachment/5559759/+files/ProcEnviron.txt

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

Title:
  SSL handshake failed - VPN SSL broken in 22.04

Status in openssl package in Ubuntu:
  New

Bug description:
  I'm trying to connect with global protect VPN but fails at login with:

  SSL handshake failed
  Failed to load URL https://...
  QtNetwork Error 6

  Another VPN client does work but the rdp connection to a remote server fails 
with:

  transport_connect_tls:freerdp_set_last_error_ex ERRCONNECT_TLS_CONNECT_FAILED
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-03-19 (325 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: openssl 3.0.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Tags:  wayland-session impish
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: Upgraded to impish on 2022-02-04 (3 days ago)
  UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare 
sudo uinput
  _MarkForUpload: True

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


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

[Touch-packages] [Bug 1960268] Re: SSL handshake failed - VPN SSL broken in 22.04

apport information

** Package changed: qtwebkit-opensource-src (Ubuntu) => openssl (Ubuntu)

** Tags added: apport-collected impish wayland-session

** Description changed:

  I'm trying to connect with global protect VPN but fails at login with:
  
  SSL handshake failed
  Failed to load URL https://...
  QtNetwork Error 6
  
  Another VPN client does work but the rdp connection to a remote server fails 
with:

  transport_connect_tls:freerdp_set_last_error_ex ERRCONNECT_TLS_CONNECT_FAILED
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu76
+ Architecture: amd64
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 21.10
+ InstallationDate: Installed on 2021-03-19 (325 days ago)
+ InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
+ Package: openssl 3.0.1-0ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
+ Tags:  wayland-session impish
+ Uname: Linux 5.15.0-18-generic x86_64
+ UpgradeStatus: Upgraded to impish on 2022-02-04 (3 days ago)
+ UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare 
sudo uinput
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1960268/+attachment/5559756/+files/Dependencies.txt

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

Title:
  SSL handshake failed - VPN SSL broken in 22.04

Status in openssl package in Ubuntu:
  New

Bug description:
  I'm trying to connect with global protect VPN but fails at login with:

  SSL handshake failed
  Failed to load URL https://...
  QtNetwork Error 6

  Another VPN client does work but the rdp connection to a remote server fails 
with:

  transport_connect_tls:freerdp_set_last_error_ex ERRCONNECT_TLS_CONNECT_FAILED
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-03-19 (325 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: openssl 3.0.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Tags:  wayland-session impish
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: Upgraded to impish on 2022-02-04 (3 days ago)
  UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare 
sudo uinput
  _MarkForUpload: True

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


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

[Touch-packages] [Bug 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}

2022-02-08 Thread Miriam España Acebal

** Description changed:

  [Impact]
  
  What the user suffering from this bug experiences is that the big amount
  of informative messages related to the copy process with the three
  spawned processes(sender, receiver and generator)  exhaust the I/O
  buffer and the sync gets stuck, either because there are too many files
  to synchronise and/or because too many detail messages (levels of
  verbose mode) have been requested in the output.
  
  The fix, that comes from upstream and is applied there since version
  3.2.0., increments the size of the receiver's I/O buffer.
  
- 
  [Test Plan]
  This test plan is for Focal, but it's the same for Bionic.
  
  0.Preparing the test environment:
  
  #Preparing the container
  lxc launch images:ubuntu/focal rsync-iobuffer-focal
  lxc shell rsync-iobuffer-focal
  apt update -y
  apt upgrade -y
  
  #Installing necessary tools
- apt install rsync 
+ apt install rsync
  apt install wget
  
- #Get test cases from comments #16 and #19 on this LP bug
+ #Get test cases from comments #16 and #19 on this LP bug: As test case
+ #16 covers both aspects (a lot of files and upper verbosity) and test
+ #19 uses a huge tarball (120 Mb), I'm removing from this SRU the
+ bad/good case for the #19  (but, please feel to check it if you consider
+ it necessary).
  
  cd /tmp/
  
- #19
- wget 
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1528921/+attachment/5211950/+files/html2.tgz
- tar -xvzf /tmp/html2.tgz
- mkdir /tmp/rsynctest
- 
- #16 
+ #16
  Paste the contents of https://pastebin.com/raw/ctzJJGwt:
  
  #!/bin/bash
  mkdir source_dir
  pushd source_dir
  dd if=/dev/zero of=source bs=600K count=1
  
  for i in `seq 1 11500`;
  do
- cp -v source file_$i;
+ cp -v source file_$i;
  done
  
  rm source
  
  for i in `seq 1 10`;
  do
-  dd if=/dev/zero of=file_large_$i bs=200M count=1
+  dd if=/dev/zero of=file_large_$i bs=200M count=1
  done
  
  popd
  
  echo "Created 11500 files with size 600K and 10 files with size 200M, try the 
following command:"
  echo "rsync -avvvz --delete source_dir target_dir"
  
  in a new file script_comment16.sh
-  
- chmod +x script_comment16.sh 
+ 
+ chmod +x script_comment16.sh
  ./script_comment16.sh
  
+ #19 (Skip this if you can't download the tarball - Examples of good/bad were 
removed). 
+ wget 
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1528921/+attachment/5211950/+files/html2.tgz
+ tar -xvzf /tmp/html2.tgz
+ mkdir /tmp/rsynctest
+ 
  
  1. Bad cases (without and with using strace):
- 
- # Scenario from comment 19 
- $ rsync --debug=all -avz /tmp/html2 /tmp/rsynctest/
- (Client) Protocol versions: remote=31, negotiated=31
- sending incremental file list
- [sender] change_dir(/tmp)
- send_files starting
- server_recv(2) starting pid=49029
- get_local_name count=7070 /tmp/rsynctest/
- created directory /tmp/rsynctest
- [Receiver] change_dir(/tmp/rsynctest)
- generator starting pid=49029
- delta-transmission disabled for local transfer or --whole-file
- recv_generator(html2,1)
- recv_generator(html2,2)
- set uid of html2 from 0 to 1000
- set gid of html2 from 0 to 1000
- set modtime of html2 to (1447205118) Wed Nov 11 01:25:18 2015
- [...]
- sender finished /tmp/html2/annotator__raw_8h__incl.md5
- send_files(282, /tmp/html2/annotator__raw_8h__incl.png)
- html2/annotator__raw_8h__incl.png
- 
- It hangs here, where using strace we can see:
- 
- $ strace rsync --debug=all -avz /tmp/html2 /tmp/rsynctest/
- [...]
- read(3, 
"\211PNG\r\n\32\n\0\0\0\rIHDR\0\0\v\4\0\0\2\233\10\6\0\0\0\361\177\254"..., 
262144) = 262144
- select(6, [5], [4], [5], {tv_sec=60, tv_usec=0}) = 2 (in [5], out [4], left 
{tv_sec=59, tv_usec=98})
- read(5, 
"\0\0\0\0\0\0\0\1\0\240\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\240\0\0\0"..., 95) 
= 95
- write(4, 
"K\374\0\7\177\377\207\343\335\345+{W\335{K\371y\211w`Ysl\336B{\312\340}\320\301"...,
 64591) = 64591
- select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 1 (out [4], left {tv_sec=59, 
tv_usec=98})
- write(4, 
"\336\322\0\7\177\377\255\371\367\215v\321-\224\323+\363\261\243\7\211Do\230\256\257O\372\367:\357O"...,
 53986) = 53986
- select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
- select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
- select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
- select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
- select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
- select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
- select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
- select(5, [], [4], [], {tv_sec=60, tv_usec=0}
- 
  
  # Scenario from comment 16
  $ rsync -avvvz --delete source_dir target_dir
  sending incremental file list
  [sender] make_file(source_dir,*,0)
  send_file_list done
  [sender] pushing local filters for /root/source_dir/
  [sender] make_file(source_dir/file_3048,*,2)
  [sender] make_file(source_dir/file_11358,*,2)
  [sender] make_file(source_dir/file_5914,*,2)
  [sender]

[Touch-packages] [Bug 1955997] Re: The airplane hotkey has no function on a HP platform

2022-02-08 Thread Lukas Märdian

Thank you for providing the "safe" patches for the stable series,
implementing an allowlist instead of following the upstream change.

I've updated the wording a bit on the patch to account for a "whitelist"
-> "allowlist" rename, other than that those LGTM!

I've uploaded the package into impish (this is awaiting SRU review):
https://launchpad.net/ubuntu/impish/+queue?queue_state=1

For focal I've staged the changes, as there is more to be added to the next 
focal upload:
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?h=ubuntu-focal=88a859eaddb6c9a611fcbc44edab441aef4c4355

** Changed in: systemd (Ubuntu Impish)
   Status: New => In Progress

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

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

Title:
  The airplane hotkey has no function on a HP platform

Status in OEM Priority Project:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Impish:
  In Progress
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  The airplane hokey doesn't work on HP new generation machines.

  [Test Plan]
  Press airplane hokey.

  Before the patch, nothing happens.
  After the patch, the rfkill works as expected.

  [Where problems could occur]
  In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will 
not work but HP confirmed the new HP generation won't contain the HPQ6001 and 
also each DM still need to deal with multi-rfkill events because upstream 
changes[2].

  ---

  In the last year, HP mentions HP machines need to use hp-wireless
  (HPQ6001) as the rfkill source[1].

  However, HP confirms the HPQ6001 has been retired in the platforms
  since 2022.

  In the platforms after 2022, there are two sources of rkfill events 
(intel-hid, atkbd) and HP only guarantee the intel-hid works.
  Therefore, the upstream already accept the patch[2] to unmask intel-hid and 
mention this big change in the NEWS.

  This change makes the pre-2022 HP platforms meet the regression since they 
have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing 
function key.
  Thus, there is a patch[3] to make sure the GNOME could deal with this case 
smoothly.
  However, the systemd change will still cause other DEs meet the regression 
(xfce, KDE, lxde, etc..).
  Backport systemd change to make HP 2022 platforms work is not the best choice 
on stable version (focal in this case).

  We still need a solution to make airplane key works on 2022 HP platforms 
(intel-hid and atkbd only).
  The potential solution from my mind that is to maintain a whitelist to unmask 
intel-hid in ubuntu-patch in focal, something like:
  ```
  evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookFury16inchG9*:*
   KEYBOARD_KEY_8=wlan # Use hp-wireless instead
  ```
  after "KEYBOARD_KEY_8=unkown".

  [1] https://bugs.launchpad.net/bugs/1883846
  [2] https://github.com/systemd/systemd/pull/20219
  [3] 
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/f4dbcf3d7b0f951fe44b29229206c97b625dbfda

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1955997/+subscriptions


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

[Touch-packages] [Bug 1958710] Re: Merge network-manager 1.34.0-2 (main) from Debian unstable/testing (main)

This bug was fixed in the package network-manager - 1.34.0-2ubuntu3

---
network-manager (1.34.0-2ubuntu3) jammy; urgency=medium

  * d/tests/control: Have nm.py autopkgtest Depend on wpasupplicant

 -- Jeremy Bicha   Mon, 07 Feb 2022 16:40:52
-0500

** Changed in: network-manager (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 network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1958710

Title:
   Merge network-manager 1.34.0-2 (main) from Debian unstable/testing
  (main)

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  There are some differences between versions from Debian and Ubuntu. A
  new version has been released a week ago.

  
  Debian Changelog:

  network-manager (1.34.0-2) unstable; urgency=medium

* Demote wpasupplicant to Recommends.
  There are enough use cases for network-manager not involving Wi-Fi which
  justifies to make this dependency optional. (Closes: #919619, #980218)

   -- Michael Biebl   Tue, 18 Jan 2022 20:59:36 +0100

  network-manager (1.34.0-1) unstable; urgency=medium

* New upstream version 1.34.0
* Rebase patches
* Install nm-priv-helper service
* Update symbols file for libnm0

   -- Michael Biebl   Fri, 14 Jan 2022 00:18:58 +0100

  
  NM ChangeLog:

  =
  NetworkManager-1.34
  Overview of changes since NetworkManager-1.32
  =

  * initrd: wait for both IPv4 and IPv6 with "ip=dhcp,dhcp6".
  * core: better handle sd-resolved errors when resolving hostnames.
  * nmcli: fix import WireGuard profile with DNS domain and address
family disabled.
  * ndisc: send router solicitations before expiry.
  * policy: send earlier the ip configs to the DNS manager.
  * core: support linking with LLD 13.
  * wireguard: importing wg-quick configuration files with nmcli
no longer sets a negative, exclusive "dns-priority". This plays
better with common split DNS setups that use systemd-resolved.
Adjust the "dns-priority" to your liking after import yourself.
  * NetworkManager no longer listens for netlink events for traffic
control objects (qdiscs and filters).
  * core: add internal nm-priv-helper service for separating privileges
and have a way to drop capabilities from NetworkManager daemon.
  * bond: add support for setting queue-id of bond port.
  * dns: support configuring DNS over TLS (DoT) with systemd-resolved.
  * nmtui: add support for WireGuard profiles.
  * nmcli: add aliases `nmcli device up|down` beside connect|disconnect.
  * conscious language: Deprecate 'Device.Slaves' D-Bus property in favor of new
'Device.Ports' property. Depracate 'nm_device_*_get_slaves()' in favor of
'nm_device_get_ports()' in libnm.
  * nmcli: invoking nmcli command without arguments will now show 'default'
instead of null address in route4 or route6 section.

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


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

[Touch-packages] [Bug 1960268] Re: SSL handshake failed - VPN SSL broken in 22.04

** Package changed: ubuntu => qtwebkit-opensource-src (Ubuntu)

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

Title:
  SSL handshake failed - VPN SSL broken in 22.04

Status in qtwebkit-opensource-src package in Ubuntu:
  New

Bug description:
  I'm trying to connect with global protect VPN but fails at login with:

  SSL handshake failed
  Failed to load URL https://...
  QtNetwork Error 6

  Another VPN client does work but the rdp connection to a remote server fails 
with:

  transport_connect_tls:freerdp_set_last_error_ex ERRCONNECT_TLS_CONNECT_FAILED

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1960268/+subscriptions


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

[Touch-packages] [Bug 1960268] [NEW] SSL handshake failed - VPN SSL broken in 22.04

You have been subscribed to a public bug:

I'm trying to connect with global protect VPN but fails at login with:

SSL handshake failed
Failed to load URL https://...
QtNetwork Error 6

Another VPN client does work but the rdp connection to a remote server fails 
with:
  
transport_connect_tls:freerdp_set_last_error_ex ERRCONNECT_TLS_CONNECT_FAILED

** Affects: qtwebkit-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: 22.04 bot-comment
-- 
SSL handshake failed - VPN SSL broken in 22.04
https://bugs.launchpad.net/bugs/1960268
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to qtwebkit-opensource-src 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 1956915] Re: New bugfix release 21.2.6

2022-02-08 Thread UlfZibis

Hi, since 4 weeks the state is "fix released".
But I do not see this with:
sudo apt dist-upgrade

Why?

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

Title:
  New bugfix release 21.2.6

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Committed
Status in mesa source package in Impish:
  Fix Committed

Bug description:
  [Impact]

  This is the last point-release of the 21.2.x-series, we should put it
  in impish so latest bugfixes would get there, and in focal for 20.04.4
  image.

  [Test case]

  Install the updates, test desktop use and some basic games etc on at
  least AMD and Intel hw.

  [Where things could go wrong]

  It's possible that some apps (like games) might regress on some hw,
  but there should not be a big risk for more wider bugs appearing in
  this update, since upstream and vendor (Intel) CI machinery have
  tested these.

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


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

[Touch-packages] [Bug 1960094] Re: lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal

2022-02-08 Thread Francis Ginther

I've retested two released kernels that passed the lxc test last cycle:

* focal/azure 5.4.0-1068.71
* focal/azure-5-11 5.11.0-1028.31~20.04.1

Both tests now show the same testcase failures where they were passing
before. Will start digging into any other changes in the environment.

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

Title:
  lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal

Status in linux package in Ubuntu:
  New
Status in lxc package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  New
Status in lxc source package in Focal:
  Incomplete

Bug description:
  There are failures in ubuntu_lxc regression tests on Focal/linux/5.4.0-99.112 
sru cycle 2022.01.03 with the error
  lxc-create: symbol lookup error: lxc-create: undefined symbol: strlcat

  These errors did not appear on previous kernels in the same cycle and
  now have a few tests failing on all architectures and systems as of
  Feb 4th 2022 it seems. Log with details is attached in the comments.

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


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

[Touch-packages] [Bug 1949553] Re: Backport packages for 20.04.4 HWE stack

2022-02-08 Thread Timo Aaltonen

tested on intel TGL-U, WHL, and AMD Radeon 520 Mobile, everything looks
good

** Description changed:

  [Impact]
  
  These are needed for 20.04.4 images.
  
  [Test case]
  
  Boot a daily image, see that it still has the necessary stack installed
  and working.
  
  [What could go wrong]
  
  libdrm: adds some new api, no changes to old stuff
  
- llvm-13: a new package, no regression potential on it's own
- 
  mesa: a new major release, but we'll pull the final stable release of
  21.2.x series, so there shouldn't be any regressions left at that point
  
  xserver: a new point-release, 1.20.x series is in deep maintenance mode,
  so there should be little chance of breakage

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

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

Title:
  Backport packages for 20.04.4 HWE stack

Status in libdrm package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libdrm source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  Fix Committed
Status in xorg-server source package in Focal:
  Fix Released

Bug description:
  [Impact]

  These are needed for 20.04.4 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  libdrm: adds some new api, no changes to old stuff

  mesa: a new major release, but we'll pull the final stable release of
  21.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release, 1.20.x series is in deep maintenance
  mode, so there should be little chance of breakage

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


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

[Touch-packages] [Bug 1956915] Re: New bugfix release 21.2.6

2022-02-08 Thread Timo Aaltonen

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

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

Title:
  New bugfix release 21.2.6

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Committed
Status in mesa source package in Impish:
  Fix Committed

Bug description:
  [Impact]

  This is the last point-release of the 21.2.x-series, we should put it
  in impish so latest bugfixes would get there, and in focal for 20.04.4
  image.

  [Test case]

  Install the updates, test desktop use and some basic games etc on at
  least AMD and Intel hw.

  [Where things could go wrong]

  It's possible that some apps (like games) might regress on some hw,
  but there should not be a big risk for more wider bugs appearing in
  this update, since upstream and vendor (Intel) CI machinery have
  tested these.

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


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

[Touch-packages] [Bug 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}

2022-02-08 Thread Andreas Hasenack

** Merge proposal linked:
   
https://code.launchpad.net/~mirespace/ubuntu/+source/rsync/+git/rsync/+merge/415244

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

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

Title:
  rsync hangs on select(5, [], [4], [], {60, 0}

Status in rsync:
  Unknown
Status in rsync package in Ubuntu:
  Confirmed
Status in rsync source package in Bionic:
  New
Status in rsync source package in Focal:
  In Progress

Bug description:
  [Impact]

  What the user suffering from this bug experiences is that the big
  amount of informative messages related to the copy process with the
  three spawned processes(sender, receiver and generator)  exhaust the
  I/O buffer and the sync gets stuck, either because there are too many
  files to synchronise and/or because too many detail messages (levels
  of verbose mode) have been requested in the output.

  The fix, that comes from upstream and is applied there since version
  3.2.0., increments the size of the receiver's I/O buffer.

  
  [Test Plan]
  This test plan is for Focal, but it's the same for Bionic.

  0.Preparing the test environment:

  #Preparing the container
  lxc launch images:ubuntu/focal rsync-iobuffer-focal
  lxc shell rsync-iobuffer-focal
  apt update -y
  apt upgrade -y

  #Installing necessary tools
  apt install rsync 
  apt install wget

  #Get test cases from comments #16 and #19 on this LP bug

  cd /tmp/

  #19
  wget 
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1528921/+attachment/5211950/+files/html2.tgz
  tar -xvzf /tmp/html2.tgz
  mkdir /tmp/rsynctest

  #16 
  Paste the contents of https://pastebin.com/raw/ctzJJGwt:

  #!/bin/bash
  mkdir source_dir
  pushd source_dir
  dd if=/dev/zero of=source bs=600K count=1

  for i in `seq 1 11500`;
  do
  cp -v source file_$i;
  done

  rm source

  for i in `seq 1 10`;
  do
   dd if=/dev/zero of=file_large_$i bs=200M count=1
  done

  popd

  echo "Created 11500 files with size 600K and 10 files with size 200M, try the 
following command:"
  echo "rsync -avvvz --delete source_dir target_dir"

  in a new file script_comment16.sh
   
  chmod +x script_comment16.sh 
  ./script_comment16.sh

  
  1. Bad cases (without and with using strace):

  # Scenario from comment 19 
  $ rsync --debug=all -avz /tmp/html2 /tmp/rsynctest/
  (Client) Protocol versions: remote=31, negotiated=31
  sending incremental file list
  [sender] change_dir(/tmp)
  send_files starting
  server_recv(2) starting pid=49029
  get_local_name count=7070 /tmp/rsynctest/
  created directory /tmp/rsynctest
  [Receiver] change_dir(/tmp/rsynctest)
  generator starting pid=49029
  delta-transmission disabled for local transfer or --whole-file
  recv_generator(html2,1)
  recv_generator(html2,2)
  set uid of html2 from 0 to 1000
  set gid of html2 from 0 to 1000
  set modtime of html2 to (1447205118) Wed Nov 11 01:25:18 2015
  [...]
  sender finished /tmp/html2/annotator__raw_8h__incl.md5
  send_files(282, /tmp/html2/annotator__raw_8h__incl.png)
  html2/annotator__raw_8h__incl.png

  It hangs here, where using strace we can see:

  $ strace rsync --debug=all -avz /tmp/html2 /tmp/rsynctest/
  [...]
  read(3, 
"\211PNG\r\n\32\n\0\0\0\rIHDR\0\0\v\4\0\0\2\233\10\6\0\0\0\361\177\254"..., 
262144) = 262144
  select(6, [5], [4], [5], {tv_sec=60, tv_usec=0}) = 2 (in [5], out [4], left 
{tv_sec=59, tv_usec=98})
  read(5, 
"\0\0\0\0\0\0\0\1\0\240\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\240\0\0\0"..., 95) 
= 95
  write(4, 
"K\374\0\7\177\377\207\343\335\345+{W\335{K\371y\211w`Ysl\336B{\312\340}\320\301"...,
 64591) = 64591
  select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 1 (out [4], left {tv_sec=59, 
tv_usec=98})
  write(4, 
"\336\322\0\7\177\377\255\371\367\215v\321-\224\323+\363\261\243\7\211Do\230\256\257O\372\367:\357O"...,
 53986) = 53986
  select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
  select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
  select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
  select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
  select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
  select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
  select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
  select(5, [], [4], [], {tv_sec=60, tv_usec=0}

  
  # Scenario from comment 16
  $ rsync -avvvz --delete source_dir target_dir
  sending incremental file list
  [sender] make_file(source_dir,*,0)
  send_file_list done
  [sender] pushing local filters for /root/source_dir/
  [sender] make_file(source_dir/file_3048,*,2)
  [sender] make_file(source_dir/file_11358,*,2)
  [sender] make_file(source_dir/file_5914,*,2)
  [sender] make_file(source_dir/file_5880,*,2)
  [sender] make_file(source_dir/file_9318,*,2)
  [sender] make_file(source_dir/file_5539,*,2)
  [...]
  sending file_sum

[Touch-packages] [Bug 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}

2022-02-08 Thread Miriam España Acebal

** Description changed:

- In the last few months my home directory backup stopped completing.
- I've been able to reproduce the problem on a single subdirectory
- although I had to add the --debug=all flag to reproduce it on that
- smaller directory.  Specifically, this command never completes:
+ [Impact]
+ 
+ What the user suffering from this bug experiences is that the big amount
+ of informative messages related to the copy process with the three
+ spawned processes(sender, receiver and generator)  exhaust the I/O
+ buffer and the sync gets stuck, either because there are too many files
+ to synchronise and/or because too many detail messages (levels of
+ verbose mode) have been requested in the output.
+ 
+ The fix, that comes from upstream and is applied there since version
+ 3.2.0., increments the size of the receiver's I/O buffer.
+ 
+ 
+ [Test Plan]
+ This test plan is for Focal, but it's the same for Bionic.
+ 
+ 0.Preparing the test environment:
+ 
+ #Preparing the container
+ lxc launch images:ubuntu/focal rsync-iobuffer-focal
+ lxc shell rsync-iobuffer-focal
+ apt update -y
+ apt upgrade -y
+ 
+ #Installing necessary tools
+ apt install rsync 
+ apt install wget
+ 
+ #Get test cases from comments #16 and #19 on this LP bug
+ 
+ cd /tmp/
+ 
+ #19
+ wget 
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1528921/+attachment/5211950/+files/html2.tgz
+ tar -xvzf /tmp/html2.tgz
+ mkdir /tmp/rsynctest
+ 
+ #16 
+ Paste the contents of https://pastebin.com/raw/ctzJJGwt:
+ 
+ #!/bin/bash
+ mkdir source_dir
+ pushd source_dir
+ dd if=/dev/zero of=source bs=600K count=1
+ 
+ for i in `seq 1 11500`;
+ do
+ cp -v source file_$i;
+ done
+ 
+ rm source
+ 
+ for i in `seq 1 10`;
+ do
+  dd if=/dev/zero of=file_large_$i bs=200M count=1
+ done
+ 
+ popd
+ 
+ echo "Created 11500 files with size 600K and 10 files with size 200M, try the 
following command:"
+ echo "rsync -avvvz --delete source_dir target_dir"
+ 
+ in a new file script_comment16.sh
+  
+ chmod +x script_comment16.sh 
+ ./script_comment16.sh
+ 
+ 
+ 1. Bad cases (without and with using strace):
+ 
+ # Scenario from comment 19 
+ $ rsync --debug=all -avz /tmp/html2 /tmp/rsynctest/
+ (Client) Protocol versions: remote=31, negotiated=31
+ sending incremental file list
+ [sender] change_dir(/tmp)
+ send_files starting
+ server_recv(2) starting pid=49029
+ get_local_name count=7070 /tmp/rsynctest/
+ created directory /tmp/rsynctest
+ [Receiver] change_dir(/tmp/rsynctest)
+ generator starting pid=49029
+ delta-transmission disabled for local transfer or --whole-file
+ recv_generator(html2,1)
+ recv_generator(html2,2)
+ set uid of html2 from 0 to 1000
+ set gid of html2 from 0 to 1000
+ set modtime of html2 to (1447205118) Wed Nov 11 01:25:18 2015
+ [...]
+ sender finished /tmp/html2/annotator__raw_8h__incl.md5
+ send_files(282, /tmp/html2/annotator__raw_8h__incl.png)
+ html2/annotator__raw_8h__incl.png
+ 
+ It hangs here, where using strace we can see:
+ 
+ $ strace rsync --debug=all -avz /tmp/html2 /tmp/rsynctest/
+ [...]
+ read(3, 
"\211PNG\r\n\32\n\0\0\0\rIHDR\0\0\v\4\0\0\2\233\10\6\0\0\0\361\177\254"..., 
262144) = 262144
+ select(6, [5], [4], [5], {tv_sec=60, tv_usec=0}) = 2 (in [5], out [4], left 
{tv_sec=59, tv_usec=98})
+ read(5, 
"\0\0\0\0\0\0\0\1\0\240\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\240\0\0\0"..., 95) 
= 95
+ write(4, 
"K\374\0\7\177\377\207\343\335\345+{W\335{K\371y\211w`Ysl\336B{\312\340}\320\301"...,
 64591) = 64591
+ select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 1 (out [4], left {tv_sec=59, 
tv_usec=98})
+ write(4, 
"\336\322\0\7\177\377\255\371\367\215v\321-\224\323+\363\261\243\7\211Do\230\256\257O\372\367:\357O"...,
 53986) = 53986
+ select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
+ select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
+ select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
+ select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
+ select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
+ select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
+ select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
+ select(5, [], [4], [], {tv_sec=60, tv_usec=0}
+ 
+ 
+ # Scenario from comment 16
+ $ rsync -avvvz --delete source_dir target_dir
+ sending incremental file list
+ [sender] make_file(source_dir,*,0)
+ send_file_list done
+ [sender] pushing local filters for /root/source_dir/
+ [sender] make_file(source_dir/file_3048,*,2)
+ [sender] make_file(source_dir/file_11358,*,2)
+ [sender] make_file(source_dir/file_5914,*,2)
+ [sender] make_file(source_dir/file_5880,*,2)
+ [sender] make_file(source_dir/file_9318,*,2)
+ [sender] make_file(source_dir/file_5539,*,2)
+ [...]
+ sending file_sum
+ false_alarms=0 hash_hits=0 matches=0
+ sender finished source_dir/file_10807
+ send_files(903, source_dir/file_10808)
+ send_files mapped source_dir/file_10808 of size 614400
+ calling match_sums source_dir/file_10808
+ source_dir/file_10808
+ 
+ It hangs here, where

[Touch-packages] [Bug 1958242] Re: mesa update freeze/crash screen before login

2022-02-08 Thread Timo Aaltonen

please try the latest stable release from

https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa

then at least we'd know if it's fixed in 21.3.x

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

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

Title:
  mesa update freeze/crash screen before login

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  After updating my laptop after a long trip. It starts to bootm, then
  screen goes black with the mouse pointer hanging over, sddm does not
  start.

  This symptoms I saw them before and were related to mesa libraries. See 
https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1909171 for details on that.
  But the actual problem seems somewhat different this time.

  Furthermore dmesg shows:

  [66.441074] QSGRenderThread[1134]: segfault at 39 ip 7f1ca6c7311b sp 
7f1c98b76630 error 4 in r300_dri.so[7f1ca660b000+10ab000]
  [66.441088] Code: b6 40 2d eb ef 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 31 
f6 e9 95 a2 f9 ff 0f 1f 44 00 00 41 54 48 8d 15 97 b8 b2 00 55 53 <0f> b6 47 39 
48 89 f3 48 63 04 82 48 01 d0 3e ff e0 0f 1f 40 00bd

  r300_dri.so is from the package libgl1-mesa-dri

  I applied the same workaround I did for the previous time that mesa
  was broken: downgrade to previous mesa version.

  I went to Ctrl+Alt-F2, logged in and:
  **
  sudo apt install libglapi-mesa=21.0.3-0ubuntu0.3~20.04.5 
libglx-mesa0=21.0.3-0ubuntu0.3~20.04.5 
libgl1-mesa-dri=21.0.3-0ubuntu0.3~20.04.5 
libegl-mesa0=21.0.3-0ubuntu0.3~20.04.5 libgbm1=21.0.3-0ubuntu0.3~20.04.5

  sudo apt-mark hold libglapi-mesa=21.0.3-0ubuntu0.3~20.04.5 
libglx-mesa0=21.0.3-0ubuntu0.3~20.04.5 
libgl1-mesa-dri=21.0.3-0ubuntu0.3~20.04.5 
libegl-mesa0=21.0.3-0ubuntu0.3~20.04.5 libgbm1=21.0.3-0ubuntu0.3~20.04.5
  ***

  Now everything works fine. Other than the mentioned mesa packages
  everything else is fully updated.

  === In short something got broken again in mesa 21.2.6, downgrading to
  21.0.3 fixes the issue. ===

  Running Lubuntu 20.04
  Kernel:
  5.4.0-94-generic #106-Ubuntu SMP Thu Jan 6 23:58:14 UTC 2022 x86_64 x86_64 
x86_64 GNU/Linux

  lsb_release -rd:
  Description:Ubuntu 20.04.3 LTS
  Release:20.04

  GPU:
  Advanced Micro Devices [AMD/ATI]
  RS482M [Mobility Radeon Xpress 200]
  driver: radeon

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


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

[Touch-packages] [Bug 1951390] Re: update iproute2

2022-02-08 Thread Andrea Righi

Adding also focal, because with the new linux-hwe-5.15 we get the same
failure.

** Summary changed:

- update iproute2 in jammy
+ update iproute2

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

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

Title:
  update iproute2

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Focal:
  New
Status in iproute2 source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Kernel 5.15 requires iproute2 at least v5.14 to properly support IPv6
  In-situ OAM (IOAM6).

  [Test case]

  This lack of support is triggering the following kernel selftest
  failure:

   # selftests: net: ioam6.sh
   # SKIP: iproute2 too old, missing ioam command
   not ok 1 selftests: net: ioam6.sh # exit=1

  [Fix]

  We're still using iproute2 v5.10 in jammy. It'd be nice to update to
  the latest upstream version (v5.15) to properly support this new
  kernel feature (and more).

  [Regression potential]

  We may introduce networking regressions with this change, because we
  are jumping from iproute2 5.10 to 5.15.

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


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

[Touch-packages] [Bug 1960307] [NEW] No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices

2022-02-08 Thread Avamander

Public bug reported:

After the announcements of PulseAudio 15 and Gstreamer 1.20, which both
advertised LDAC and AptX (HD) support, I expected that jammy (22.04)
would support those codecs.

Though in reality it seems that something is missing, gstreamer reports
that those codecs are supported but "pactl [...] list-codec" only lists
sbc (and variants).

Checking here https://packages.ubuntu.com/jammy/pulseaudio-module-
bluetooth it seems that PulseAudio is not built with gstreamer support,
is that the current blocker?

** Affects: gst-plugins-bad1.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

** Also affects: gst-plugins-bad1.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  No gstreamer dependency causes high-fidelity codecs to be missing for
  Bluetooth devices

Status in gst-plugins-bad1.0 package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After the announcements of PulseAudio 15 and Gstreamer 1.20, which
  both advertised LDAC and AptX (HD) support, I expected that jammy
  (22.04) would support those codecs.

  Though in reality it seems that something is missing, gstreamer
  reports that those codecs are supported but "pactl [...] list-codec"
  only lists sbc (and variants).

  Checking here https://packages.ubuntu.com/jammy/pulseaudio-module-
  bluetooth it seems that PulseAudio is not built with gstreamer
  support, is that the current blocker?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1960307/+subscriptions


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

[Touch-packages] [Bug 1960034] Re: systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-29.32

2022-02-08 Thread Kleber Sacilotto de Souza

Confirmed that systemd storage testacase is now successful with
impish:linux 5.13.0-30.33:

amd64 - 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/s/systemd/20220207_183233_91879@/log.gz
arm64 - 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/s/systemd/20220207_164846_df7a7@/log.gz
ppc64el - 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220207_155813_b0af1@/log.gz

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

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

Title:
  systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-29.32

Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Impish:
  Fix Committed
Status in systemd source package in Impish:
  Invalid

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux/5.13.0-29.32 on impish. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/s/systemd/20220204_114518_6b600@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/s/systemd/20220201_135548_7f169@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220201_110103_b02e4@/log.gz

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


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

[Touch-packages] [Bug 1960094] Re: lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal

2022-02-08 Thread Kleber Sacilotto de Souza

Attached is the testcase log from the run with the previous focal:linux
kernel version (5.4.0-97.110).

I believe that it's very unlikely that this issue is caused by a kernel
change. Between versions 5.4.0-97.110 and 5.4.0-99.112 only a few cifs
patches were reverted to fix a regression
(https://launchpad.net/ubuntu/+source/linux/5.4.0-99.112). These patches
were applied to 5.4.0-97.110 and reverted on 5.4.0-99.112. I haven't
looked at the lxc testcases, but cifs changes should unlikely cause lxc
failures.

** Attachment added: 
"sru-generic-metal-akis.amd64-5.4.0-97.110-ubuntu_lxc-log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960094/+attachment/5559658/+files/sru-generic-metal-akis.amd64-5.4.0-97.110-ubuntu_lxc-log.txt

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

Title:
  lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal

Status in linux package in Ubuntu:
  New
Status in lxc package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  New
Status in lxc source package in Focal:
  Incomplete

Bug description:
  There are failures in ubuntu_lxc regression tests on Focal/linux/5.4.0-99.112 
sru cycle 2022.01.03 with the error
  lxc-create: symbol lookup error: lxc-create: undefined symbol: strlcat

  These errors did not appear on previous kernels in the same cycle and
  now have a few tests failing on all architectures and systems as of
  Feb 4th 2022 it seems. Log with details is attached in the comments.

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


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

[Touch-packages] [Bug 1960297] Re: Please merge python-testtools 2.5.0-3 (main) from Debian unstable (main)

Hello,

In version 2.5.0-2ubuntu1, we had a patch fixing a FTBFS issue with Python 3.10 
and declaring the package as Python 3.10 compatible (including updates to 
setup.cfg and to the list of environments for TOX).
 * debian/patches/add-python-3.10-support.patch
This patch was applied from upstream [1]

In 2.5.0-3, Debian fixed the FTBFS as well with a custom patch [2]. This is the 
only change in this version. Although it fixes the FTBFS, it does not declare 
the package as Python 3.10 compatible.
 * debian/patches/fix-testing-test_syntax_error.patch

Syncing from Debian here would definitely be an option. However, it
would mean we have the package marked compatible with Python 3.10 on
impish (version 2.5.0-2-ubuntu1) but not on jammy (version 2.5.0-2) ;
which would not be great...

Therefore, I decided to go for the merge option and keep our patch while
discarding the one from Debian.

I uploaded the result of the merge (basically a no-op) in a PPA. Build log 
available here:
https://launchpad.net/~ogayot/+archive/ubuntu/jammy-proposed/+build/23142775

Please let me know if a sync would be more sensible. I'll be happy to
turn this into a sync request.

Thanks,
Olivier

[1] 
https://github.com/testing-cabal/testtools/commit/ec9bb7ed026566688a14be9d8d5d1e4c506e71c0
[2] 
https://salsa.debian.org/openstack-team/python/python-testtools/-/commit/fbf2d78b6215f81e8eca29a3ea9fb64fa2e2ab32

** Changed in: python-testtools (Ubuntu)
   Status: New => Confirmed

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

Title:
  Please merge python-testtools 2.5.0-3 (main) from Debian unstable
  (main)

Status in python-testtools package in Ubuntu:
  Confirmed

Bug description:
  python-testtools
  Mon Dec 27 21:14:53 2021

  base: 2.5.0-2
  python-testtools_2.5.0-2.dsc
  python-testtools_2.5.0.orig.tar.xz
  python-testtools_2.5.0-2.debian.tar.xz

  ubuntu: 2.5.0-2ubuntu1
  python-testtools_2.5.0-2ubuntu1.dsc
  python-testtools_2.5.0.orig.tar.xz
  python-testtools_2.5.0-2ubuntu1.debian.tar.xz

  base -> ubuntu
  python-testtools_2.5.0-2ubuntu1.patch

  debian: 2.5.0-3
  python-testtools_2.5.0-3.dsc
  python-testtools_2.5.0.orig.tar.xz
  python-testtools_2.5.0-3.debian.tar.xz

  base -> debian
  python-testtools_2.5.0-3.patch

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


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

[Touch-packages] [Bug 1960226] Re: Ubuntu Jammy Desktop fails to boot after install

2022-02-08 Thread Leó Kolbeinsson

Retested Ubuntu Jammy daily ISO 2022-02-08 - again fails to boot to
desktop after install.

http://iso.qa.ubuntu.com/qatracker/milestones/429/builds/244085/testcases/1300/results

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

Title:
  Ubuntu Jammy Desktop fails to boot after install

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Jammy Desktop fails to boot after install

  Testing Ubuntu Jammy Desktop daily ISO - 2022-02-07

  This also affects Ubuntu Jammy Canary desktop - tested daily ISO
  2022-02-07

  After installing the OS and selecting reboot the system reboot fails -

  The vendors logo appears with the Ubuntu logo and fails to boot - I
  have tried this with 2 barebone machines and 1 in VirtualBox - will
  attach syslogs and images in a separate comment.

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


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

[Touch-packages] [Bug 1960297] Re: Please merge python-testtools 2.5.0-3 (main) from Debian unstable (main)

** Patch added: "Patch between 2.5.0-2ubuntu1 and 2.5.0-3ubuntu1"
   
https://bugs.launchpad.net/ubuntu/+source/python-testtools/+bug/1960297/+attachment/5559657/+files/1-2.5.0-2ubuntu1_2.5.0-3ubuntu1.debdiff

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

Title:
  Please merge python-testtools 2.5.0-3 (main) from Debian unstable
  (main)

Status in python-testtools package in Ubuntu:
  New

Bug description:
  python-testtools
  Mon Dec 27 21:14:53 2021

  base: 2.5.0-2
  python-testtools_2.5.0-2.dsc
  python-testtools_2.5.0.orig.tar.xz
  python-testtools_2.5.0-2.debian.tar.xz

  ubuntu: 2.5.0-2ubuntu1
  python-testtools_2.5.0-2ubuntu1.dsc
  python-testtools_2.5.0.orig.tar.xz
  python-testtools_2.5.0-2ubuntu1.debian.tar.xz

  base -> ubuntu
  python-testtools_2.5.0-2ubuntu1.patch

  debian: 2.5.0-3
  python-testtools_2.5.0-3.dsc
  python-testtools_2.5.0.orig.tar.xz
  python-testtools_2.5.0-3.debian.tar.xz

  base -> debian
  python-testtools_2.5.0-3.patch

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


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

[Touch-packages] [Bug 1960297] Re: Please merge python-testtools 2.5.0-3 (main) from Debian unstable (main)

** Patch added: "Patch between 2.5.0-3 and 2.5.0-3ubuntu1"
   
https://bugs.launchpad.net/ubuntu/+source/python-testtools/+bug/1960297/+attachment/5559656/+files/1-2.5.0-3_2.5.0-3ubuntu1.debdiff

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

Title:
  Please merge python-testtools 2.5.0-3 (main) from Debian unstable
  (main)

Status in python-testtools package in Ubuntu:
  New

Bug description:
  python-testtools
  Mon Dec 27 21:14:53 2021

  base: 2.5.0-2
  python-testtools_2.5.0-2.dsc
  python-testtools_2.5.0.orig.tar.xz
  python-testtools_2.5.0-2.debian.tar.xz

  ubuntu: 2.5.0-2ubuntu1
  python-testtools_2.5.0-2ubuntu1.dsc
  python-testtools_2.5.0.orig.tar.xz
  python-testtools_2.5.0-2ubuntu1.debian.tar.xz

  base -> ubuntu
  python-testtools_2.5.0-2ubuntu1.patch

  debian: 2.5.0-3
  python-testtools_2.5.0-3.dsc
  python-testtools_2.5.0.orig.tar.xz
  python-testtools_2.5.0-3.debian.tar.xz

  base -> debian
  python-testtools_2.5.0-3.patch

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


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

[Touch-packages] [Bug 1960297] [NEW] Please merge python-testtools 2.5.0-3 (main) from Debian unstable (main)

Public bug reported:

python-testtools
Mon Dec 27 21:14:53 2021

base: 2.5.0-2
python-testtools_2.5.0-2.dsc
python-testtools_2.5.0.orig.tar.xz
python-testtools_2.5.0-2.debian.tar.xz

ubuntu: 2.5.0-2ubuntu1
python-testtools_2.5.0-2ubuntu1.dsc
python-testtools_2.5.0.orig.tar.xz
python-testtools_2.5.0-2ubuntu1.debian.tar.xz

base -> ubuntu
python-testtools_2.5.0-2ubuntu1.patch

debian: 2.5.0-3
python-testtools_2.5.0-3.dsc
python-testtools_2.5.0.orig.tar.xz
python-testtools_2.5.0-3.debian.tar.xz

base -> debian
python-testtools_2.5.0-3.patch

** Affects: python-testtools (Ubuntu)
 Importance: Undecided
 Assignee: Olivier Gayot (ogayot)
 Status: New


** Tags: fr-2028

** Changed in: python-testtools (Ubuntu)
 Assignee: (unassigned) => Olivier Gayot (ogayot)

** Tags added: fr-2028

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

Title:
  Please merge python-testtools 2.5.0-3 (main) from Debian unstable
  (main)

Status in python-testtools package in Ubuntu:
  New

Bug description:
  python-testtools
  Mon Dec 27 21:14:53 2021

  base: 2.5.0-2
  python-testtools_2.5.0-2.dsc
  python-testtools_2.5.0.orig.tar.xz
  python-testtools_2.5.0-2.debian.tar.xz

  ubuntu: 2.5.0-2ubuntu1
  python-testtools_2.5.0-2ubuntu1.dsc
  python-testtools_2.5.0.orig.tar.xz
  python-testtools_2.5.0-2ubuntu1.debian.tar.xz

  base -> ubuntu
  python-testtools_2.5.0-2ubuntu1.patch

  debian: 2.5.0-3
  python-testtools_2.5.0-3.dsc
  python-testtools_2.5.0.orig.tar.xz
  python-testtools_2.5.0-3.debian.tar.xz

  base -> debian
  python-testtools_2.5.0-3.patch

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


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

[Touch-packages] [Bug 1959015] Re: Switch to new HTTPS-capable domains for PPAs