[Touch-packages] [Bug 1958676] Re: error: too early for operation, device not yet seeded or device model not acknowledged Install failed

2023-11-28 Thread Launchpad Bug Tracker
[Expired for launchpad-buildd because there has been no activity for 60
days.]

** Changed in: launchpad-buildd
   Status: Incomplete => Expired

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

Title:
  error: too early for operation, device not yet seeded or device model
  not acknowledged Install failed

Status in launchpad-buildd:
  Expired
Status in init-system-helpers package in Ubuntu:
  Expired
Status in snapd package in Ubuntu:
  Expired
Status in sssd package in Ubuntu:
  Expired
Status in systemd package in Ubuntu:
  Expired

Bug description:
  https://launchpad.net/~ubuntu-core-service/+snap/core22/+build/1650565

  New deb-systemd-invoke added functionality for systemd v250 which
  ubuntu does not have yet. But it also appears to break postinst calls
  to deb-systemd-invoke, at least as seen during snap builds in lxd
  containers operated by launchpad-buildd.

  I wonder if there is a regression in new code, or new systemd, which
  may warrant a revert.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad-buildd/+bug/1958676/+subscriptions


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


[Touch-packages] [Bug 1958676] Re: error: too early for operation, device not yet seeded or device model not acknowledged Install failed

2023-11-28 Thread Launchpad Bug Tracker
[Expired for snapd (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  error: too early for operation, device not yet seeded or device model
  not acknowledged Install failed

Status in launchpad-buildd:
  Expired
Status in init-system-helpers package in Ubuntu:
  Expired
Status in snapd package in Ubuntu:
  Expired
Status in sssd package in Ubuntu:
  Expired
Status in systemd package in Ubuntu:
  Expired

Bug description:
  https://launchpad.net/~ubuntu-core-service/+snap/core22/+build/1650565

  New deb-systemd-invoke added functionality for systemd v250 which
  ubuntu does not have yet. But it also appears to break postinst calls
  to deb-systemd-invoke, at least as seen during snap builds in lxd
  containers operated by launchpad-buildd.

  I wonder if there is a regression in new code, or new systemd, which
  may warrant a revert.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad-buildd/+bug/1958676/+subscriptions


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


[Touch-packages] [Bug 1958676] Re: error: too early for operation, device not yet seeded or device model not acknowledged Install failed

2023-11-28 Thread Launchpad Bug Tracker
[Expired for sssd (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  error: too early for operation, device not yet seeded or device model
  not acknowledged Install failed

Status in launchpad-buildd:
  Expired
Status in init-system-helpers package in Ubuntu:
  Expired
Status in snapd package in Ubuntu:
  Expired
Status in sssd package in Ubuntu:
  Expired
Status in systemd package in Ubuntu:
  Expired

Bug description:
  https://launchpad.net/~ubuntu-core-service/+snap/core22/+build/1650565

  New deb-systemd-invoke added functionality for systemd v250 which
  ubuntu does not have yet. But it also appears to break postinst calls
  to deb-systemd-invoke, at least as seen during snap builds in lxd
  containers operated by launchpad-buildd.

  I wonder if there is a regression in new code, or new systemd, which
  may warrant a revert.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad-buildd/+bug/1958676/+subscriptions


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


[Touch-packages] [Bug 1958676] Re: error: too early for operation, device not yet seeded or device model not acknowledged Install failed

2023-11-28 Thread Launchpad Bug Tracker
[Expired for init-system-helpers (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: init-system-helpers (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  error: too early for operation, device not yet seeded or device model
  not acknowledged Install failed

Status in launchpad-buildd:
  Expired
Status in init-system-helpers package in Ubuntu:
  Expired
Status in snapd package in Ubuntu:
  Expired
Status in sssd package in Ubuntu:
  Expired
Status in systemd package in Ubuntu:
  Expired

Bug description:
  https://launchpad.net/~ubuntu-core-service/+snap/core22/+build/1650565

  New deb-systemd-invoke added functionality for systemd v250 which
  ubuntu does not have yet. But it also appears to break postinst calls
  to deb-systemd-invoke, at least as seen during snap builds in lxd
  containers operated by launchpad-buildd.

  I wonder if there is a regression in new code, or new systemd, which
  may warrant a revert.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad-buildd/+bug/1958676/+subscriptions


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


[Touch-packages] [Bug 1987792] Re: Totem and VLC crash when playing dvd with VAAPI radeon mesa drivers

2023-11-28 Thread Launchpad Bug Tracker
[Expired for mesa (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Totem and VLC crash when playing dvd with VAAPI radeon mesa drivers

Status in mesa package in Ubuntu:
  Expired

Bug description:
  Sony laptop with AMD RV710

  Try to play a DVD with Vaapi mesa drivers installed

  ALl players crash , example with VLC (  Works great without VAAPI )

  libva info: VA-API version 1.14.0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
  libva info: Found init function __vaDriverInit_1_14
  libva info: va_openDriver() returns 0
  [7fd5d8085d50] main generic debug: using glconv module "glconv_vaapi_drm"
  [7fd5d8001610] main vout display debug: using vout display module "gl"
  [7fd5d4039c20] main window debug: resized to 768x576
  [7fd5d8001610] main vout display debug: VoutDisplayEvent 'resize' 768x576
  [7fd5d4028010] main video output debug: original format sz 720x576, of 
(0,0), vsz 720x576, 4cc VAOP, sar 16:15, msk r0x0 g0x0 b0x0
  [7fd5d4029610] main spu text debug: removing module "freetype"
  [7fd5d4072b40] main spu text debug: looking for text renderer module 
matching "any": 2 candidates
  [7fd5d4072b40] freetype spu text debug: Building font databases.
  [5601ed37aed0] qt interface debug: Logical video size: 768x576
  [7fd5d4039c20] main window debug: resized to 768x576
  [7fd5d8001610] main vout display debug: VoutDisplayEvent 'resize' 768x576
  [7fd5d4072b40] freetype spu text debug: Took -23713 microseconds
  [7fd5d4072b40] main spu text debug: using text renderer module "freetype"
  [7fd5d409d080] main generic debug: looking for hw decoder module matching 
"vaapi": 3 candidates
  [7fd5d409d080] main generic debug: using hw decoder module "vaapi"
  [7fd5d004efb0] avcodec decoder: Using Mesa Gallium driver 22.0.5 for AMD 
RV710 (DRM 2.50.0 / 5.15.0-46-generic, LLVM 13.0.1) for hardware decoding
  [mpeg2video @ 0x7fd5d4087d80] Format vaapi_vld chosen by get_format().
  [mpeg2video @ 0x7fd5d4087d80] Format vaapi_vld requires hwaccel 
initialisation.
  [mpeg2video @ 0x7fd5d4087d80] Using deprecated struct vaapi_context in decode.
  [mpeg2video @ 0x7fd5d4087d80] Using user-supplied decoder context: 0x15/0x16.
  [mpeg2video @ 0x7fd5d4087d80] Param buffer (type 0, 40 bytes) is 0x17.
  [mpeg2video @ 0x7fd5d4087d80] Param buffer (type 1, 288 bytes) is 0x18.
  [mpeg2video @ 0x7fd5d4087d80] Slice 0 param buffer (48 bytes) is 0x19.
  [mpeg2video @ 0x7fd5d4087d80] Slice 0 data buffer (176 bytes) is 0x1a.
  [mpeg2video @ 0x7fd5d4087d80] Slice 1 param buffer (48 bytes) is 0x1b.
  [mpeg2video @ 0x7fd5d4087d80] Slice 1 data buffer (175 bytes) is 0x1c.
  [mpeg2video @ 0x7fd5d4087d80] Slice 2 param buffer (48 bytes) is 0x1d.
  [mpeg2video @ 0x7fd5d4087d80] Slice 2 data buffer (175 bytes) is 0x1e.
  [mpeg2video @ 0x7fd5d4087d80] Slice 3 param buffer (48 bytes) is 0x1f.
  [mpeg2video @ 0x7fd5d4087d80] Slice 3 data buffer (175 bytes) is 0x20.
  [mpeg2video @ 0x7fd5d4087d80] Slice 4 param buffer (48 bytes) is 0x21.
  [mpeg2video @ 0x7fd5d4087d80] Slice 4 data buffer (175 bytes) is 0x22.
  [mpeg2video @ 0x7fd5d4087d80] Slice 5 param buffer (48 bytes) is 0x23.
  [mpeg2video @ 0x7fd5d4087d80] Slice 5 data buffer (175 bytes) is 0x24.
  [mpeg2video @ 0x7fd5d4087d80] Slice 6 param buffer (48 bytes) is 0x25.
  [mpeg2video @ 0x7fd5d4087d80] Slice 6 data buffer (175 bytes) is 0x26.
  [mpeg2video @ 0x7fd5d4087d80] Slice 7 param buffer (48 bytes) is 0x27.
  [mpeg2video @ 0x7fd5d4087d80] Slice 7 data buffer (175 bytes) is 0x28.
  [mpeg2video @ 0x7fd5d4087d80] Slice 8 param buffer (48 bytes) is 0x29.
  [mpeg2video @ 0x7fd5d4087d80] Slice 8 data buffer (175 bytes) is 0x2a.
  [mpeg2video @ 0x7fd5d4087d80] Slice 9 param buffer (48 bytes) is 0x2b.
  [mpeg2video @ 0x7fd5d4087d80] Slice 9 data buffer (175 bytes) is 0x2c.
  [mpeg2video @ 0x7fd5d4087d80] Slice 10 param buffer (48 bytes) is 0x2d.
  [mpeg2video @ 0x7fd5d4087d80] Slice 10 data buffer (175 bytes) is 0x2e.
  [mpeg2video @ 0x7fd5d4087d80] Slice 11 param buffer (48 bytes) is 0x2f.
  [mpeg2video @ 0x7fd5d4087d80] Slice 11 data buffer (175 bytes) is 0x30.
  [mpeg2video @ 0x7fd5d4087d80] Slice 12 param buffer (48 bytes) is 0x31.
  [mpeg2video @ 0x7fd5d4087d80] Slice 12 data buffer (175 bytes) is 0x32.
  [mpeg2video @ 0x7fd5d4087d80] Slice 13 param buffer (48 bytes) is 0x33.
  [mpeg2video @ 0x7fd5d4087d80] Slice 13 data buffer (175 bytes) is 0x34.
  [mpeg2video @ 0x7fd5d4087d80] Slice 14 param buffer (48 bytes) is 0x35.
  [mpeg2video @ 0x7fd5d4087d80] Slice 14 data buffer (175 bytes) is 0x36.
  [mpeg2video @ 0x7fd5d4087d80] Slice 15 param buffer (48 bytes) is 0x37.
  [mpeg2video @ 0x7fd5d4087d80] Slice 15 data buffer (571 bytes) is 0

[Touch-packages] [Bug 1958676] Re: error: too early for operation, device not yet seeded or device model not acknowledged Install failed

2023-11-28 Thread Launchpad Bug Tracker
[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  error: too early for operation, device not yet seeded or device model
  not acknowledged Install failed

Status in launchpad-buildd:
  Expired
Status in init-system-helpers package in Ubuntu:
  Expired
Status in snapd package in Ubuntu:
  Expired
Status in sssd package in Ubuntu:
  Expired
Status in systemd package in Ubuntu:
  Expired

Bug description:
  https://launchpad.net/~ubuntu-core-service/+snap/core22/+build/1650565

  New deb-systemd-invoke added functionality for systemd v250 which
  ubuntu does not have yet. But it also appears to break postinst calls
  to deb-systemd-invoke, at least as seen during snap builds in lxd
  containers operated by launchpad-buildd.

  I wonder if there is a regression in new code, or new systemd, which
  may warrant a revert.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad-buildd/+bug/1958676/+subscriptions


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


[Touch-packages] [Bug 2036124] Re: package linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2023-11-28 Thread Launchpad Bug Tracker
[Expired for initramfs-tools (Ubuntu) because there has been no activity
for 60 days.]

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

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

Title:
  package linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Expired

Bug description:
  A crash notification popped up when I was not doing anything so I'm
  not sure what caused it. I hope the automatically-added debug
  information contains something useful.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Sep 11 00:24:38 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2021-10-09 (704 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.10
  SourcePackage: initramfs-tools
  Title: package linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to jammy on 2023-08-23 (22 days ago)

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


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


[Touch-packages] [Bug 2045088] Re: package perl-modules-5.34 5.34.0-3ubuntu1.2 failed to install/upgrade: unable to open '/usr/share/perl/5.34.0/warnings.pm.dpkg-new': Operation not permitted

2023-11-28 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => perl (Ubuntu)

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

Title:
  package perl-modules-5.34 5.34.0-3ubuntu1.2 failed to install/upgrade:
  unable to open '/usr/share/perl/5.34.0/warnings.pm.dpkg-new':
  Operation not permitted

Status in perl package in Ubuntu:
  New

Bug description:
  I was trying to exit Mozilla Thunderbird.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: perl-modules-5.34 5.34.0-3ubuntu1.2
  ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Nov 28 06:27:18 2023
  DpkgTerminalLog:
   Preparing to unpack .../perl-modules-5.34_5.34.0-3ubuntu1.3_all.deb ...
   Unpacking perl-modules-5.34 (5.34.0-3ubuntu1.3) over (5.34.0-3ubuntu1.2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/perl-modules-5.34_5.34.0-3ubuntu1.3_all.deb (--unpack):
unable to open '/usr/share/perl/5.34.0/warnings.pm.dpkg-new': Operation not 
permitted
  DuplicateSignature:
   package:perl-modules-5.34:5.34.0-3ubuntu1.2
   Unpacking perl-modules-5.34 (5.34.0-3ubuntu1.3) over (5.34.0-3ubuntu1.2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/perl-modules-5.34_5.34.0-3ubuntu1.3_all.deb (--unpack):
unable to open '/usr/share/perl/5.34.0/warnings.pm.dpkg-new': Operation not 
permitted
  ErrorMessage: unable to open '/usr/share/perl/5.34.0/warnings.pm.dpkg-new': 
Operation not permitted
  InstallationDate: Installed on 2018-05-17 (2021 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.10
  SourcePackage: perl
  Title: package perl-modules-5.34 5.34.0-3ubuntu1.2 failed to install/upgrade: 
unable to open '/usr/share/perl/5.34.0/warnings.pm.dpkg-new': Operation not 
permitted
  UpgradeStatus: Upgraded to jammy on 2022-08-13 (472 days ago)

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


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


[Touch-packages] [Bug 2044654] Re: No debugging symbols found in libgdk-3.so.0

2023-11-28 Thread Sergio Durigan Junior
I've added ubuntu-debuginfod as an affected project and marked the bug
as Invalid for gtk-3.

BTW, this is a known issue that's being worked on.  Hopefully it should
be resolved in the next days.

Thanks for reporting the bug!

** Also affects: ubuntu-debuginfod
   Importance: Undecided
   Status: New

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Invalid

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

Title:
  No debugging symbols found in libgdk-3.so.0

Status in ubuntu-debuginfod:
  New
Status in gtk+3.0 package in Ubuntu:
  Invalid

Bug description:
  Attach gdb to a running yelp process!

  (gdb) share libgdk
  Reading symbols from /lib/x86_64-linux-gnu/libgdk-3.so.0...
  (No debugging symbols found in /lib/x86_64-linux-gnu/libgdk-3.so.0)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgtk-3-0 3.24.33-1ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-1016.16~22.04.1-azure 6.2.16
  Uname: Linux 6.2.0-1016-azure x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 26 13:11:15 2023
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 2045088] [NEW] package perl-modules-5.34 5.34.0-3ubuntu1.2 failed to install/upgrade: unable to open '/usr/share/perl/5.34.0/warnings.pm.dpkg-new': Operation not permitted

2023-11-28 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I was trying to exit Mozilla Thunderbird.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: perl-modules-5.34 5.34.0-3ubuntu1.2
ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64
Uname: Linux 5.15.0-53-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Tue Nov 28 06:27:18 2023
DpkgTerminalLog:
 Preparing to unpack .../perl-modules-5.34_5.34.0-3ubuntu1.3_all.deb ...
 Unpacking perl-modules-5.34 (5.34.0-3ubuntu1.3) over (5.34.0-3ubuntu1.2) ...
 dpkg: error processing archive 
/var/cache/apt/archives/perl-modules-5.34_5.34.0-3ubuntu1.3_all.deb (--unpack):
  unable to open '/usr/share/perl/5.34.0/warnings.pm.dpkg-new': Operation not 
permitted
DuplicateSignature:
 package:perl-modules-5.34:5.34.0-3ubuntu1.2
 Unpacking perl-modules-5.34 (5.34.0-3ubuntu1.3) over (5.34.0-3ubuntu1.2) ...
 dpkg: error processing archive 
/var/cache/apt/archives/perl-modules-5.34_5.34.0-3ubuntu1.3_all.deb (--unpack):
  unable to open '/usr/share/perl/5.34.0/warnings.pm.dpkg-new': Operation not 
permitted
ErrorMessage: unable to open '/usr/share/perl/5.34.0/warnings.pm.dpkg-new': 
Operation not permitted
InstallationDate: Installed on 2018-05-17 (2021 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
PackageArchitecture: all
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.2
 apt  2.4.10
SourcePackage: perl
Title: package perl-modules-5.34 5.34.0-3ubuntu1.2 failed to install/upgrade: 
unable to open '/usr/share/perl/5.34.0/warnings.pm.dpkg-new': Operation not 
permitted
UpgradeStatus: Upgraded to jammy on 2022-08-13 (472 days ago)

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


** Tags: amd64 apport-package jammy need-duplicate-check
-- 
package perl-modules-5.34 5.34.0-3ubuntu1.2 failed to install/upgrade: unable 
to open '/usr/share/perl/5.34.0/warnings.pm.dpkg-new': Operation not permitted
https://bugs.launchpad.net/bugs/2045088
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to perl 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 2045072] Re: Bug on galaky book2 750xed

2023-11-28 Thread Daniel van Vugt
Thanks for the bug report. Please describe in more detail how and when
the screen becomes dark.

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  Bug on galaky book2 750xed

Status in Ubuntu:
  Incomplete

Bug description:
  I had to set nomode parameter to avoid the screen become dark and then
  change the line of the file /etc/default/grub

  from "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

  to "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_dc=0
  intel_idle.max_cstate=2"

  then add to the file /etc/systemd/logind.conf

  the instructions:

  HandleLidSwitch=ignore
  HandleLidSwitchExternalPower=ignore
  HandleLidSwitchDocked=ignore

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 28 22:00:43 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) 
(prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Alder Lake-UP3 GT2 [Iris Xe 
Graphics] [144d:c1c6]
  InstallationDate: Installed on 2023-11-13 (15 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=it_IT.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=681212a7-b32a-4fbf-a9a1-b51bef0216f7 ro quiet splash i915.enable_dc=0 
intel_idle.max_cstate=2 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2023
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P13CFG.039.230726.HQ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP750XED-KC2IT
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SAMSUNG_SW_REVISION_12345+0.0.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP13CFG.039.230726.HQ:bd07/26/2023:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn750XED:pvrP13CFG:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP750XED-KC2IT:rvrSAMSUNG_SW_REVISION_12345+0.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-ADLP-PCFG:
  dmi.product.family: Galaxy Book2
  dmi.product.name: 750XED
  dmi.product.sku: SCAI-A5A5-A5A5-ADLP-PCFG
  dmi.product.version: P13CFG
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Touch-packages] [Bug 2045027] Re: Regression in poppler bionic - 0.62.0-2ubuntu2.14+esm2

2023-11-28 Thread Nishit Majithia
this issue has been fixed
USN: https://ubuntu.com/security/notices/USN-6508-2

** Changed in: poppler (Ubuntu)
   Status: New => Fix Released

** Changed in: poppler (Ubuntu Bionic)
   Status: New => Fix Released

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

Title:
  Regression in poppler bionic - 0.62.0-2ubuntu2.14+esm2

Status in poppler package in Ubuntu:
  Fix Released
Status in poppler source package in Bionic:
  Fix Released

Bug description:
  The latest version of poppler-utils in bionic esm has a regression
  that produces blank PDF files.

  root@maximum-titmouse:~# apt-cache policy poppler-utils
  poppler-utils:
  Installed: 0.62.0-2ubuntu2.14
  Candidate: 0.62.0-2ubuntu2.14
  Version table:
  *** 0.62.0-2ubuntu2.14 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages
  100 /var/lib/dpkg/status
  0.62.0-2ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  I created a test file with the text "Test test 123", then ran
  `pdfunite in.pdf out.pdf"

  Opening this file in a PDF viewer shows the text "Test test 123".

  Then I attached a Pro token and updated poppler-utils

  root@maximum-titmouse:~# apt-cache policy poppler-utils
  poppler-utils:
  Installed: 0.62.0-2ubuntu2.14+esm2
  Candidate: 0.62.0-2ubuntu2.14+esm2
  Version table:
  *** 0.62.0-2ubuntu2.14+esm2 510
  510 https://esm.ubuntu.com/infra/ubuntu bionic-infra-security/main amd64 
Packages
  100 /var/lib/dpkg/status
  0.62.0-2ubuntu2.14 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages
  0.62.0-2ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  And again ran `pdfunite in.pdf out2.pdf"

  This second file in a PDF viewer is completely blank. It's also
  missing a lot of metadata and is significantly smaller in size when
  checked using "strings"

  root@maximum-titmouse:~# strings out.pdf | wc -l
  186
  root@maximum-titmouse:~# strings out2.pdf | wc -l
  25

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


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


[Touch-packages] [Bug 2045096] [NEW] Error in network definition: Invalid MAC address 'random'

2023-11-28 Thread Rimits
Public bug reported:

netplan dose not understand the 'random' key word in 'Cloned MAC address' set 
by networkmanager.
```
/etc/netplan/90-NM-X.yaml:9:19: Error in network definition: Invalid MAC 
address 'random', must be XX:XX:XX:XX:XX:XX or 
XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX
  macaddress: "random"
  ^
```

netplan Version 0.107-5ubuntu2
network-manager Version 1.44.2-1ubuntu2

** Affects: netplan
 Importance: Undecided
 Status: New

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

** Summary changed:

- Error in network definition: Invalid MAC address 'random
+ Error in network definition: Invalid MAC address 'random'

** Also affects: netplan
   Importance: Undecided
   Status: New

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

Title:
  Error in network definition: Invalid MAC address 'random'

Status in netplan:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  netplan dose not understand the 'random' key word in 'Cloned MAC address' set 
by networkmanager.
  ```
  /etc/netplan/90-NM-X.yaml:9:19: Error in network definition: Invalid MAC 
address 'random', must be XX:XX:XX:XX:XX:XX or 
XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX
macaddress: "random"
^
  ```

  netplan Version 0.107-5ubuntu2
  network-manager Version 1.44.2-1ubuntu2

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


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


[Touch-packages] [Bug 2038998] Re: [amdgpu] Screen corruption, distorted geometry and misplaced triangles

2023-11-28 Thread Daniel van Vugt
The corruption also feels like something is broken with mid command
buffer preemption so please try this kernel parameter:

  amdgpu.mcbp=0

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

Title:
  [amdgpu] Screen corruption, distorted geometry and misplaced triangles

Status in GNOME Shell:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

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

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

  Wayland
  Kernel 6.5.0-9-generic

  * * * * *

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

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

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

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

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

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

  * * * * *

  Please see subsequent posts for video/images.

  Happy to provide any other information as needed. Thanks!

  * * * * *

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2038998/+subscriptions


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


[Touch-packages] [Bug 2038998] Re: [amdgpu] Screen artifacts/UI oddities on Wayland

2023-11-28 Thread Daniel van Vugt
More people, please try comment #16.

Please also ensure you don't have any unsupported extensions installed.
Wobbly Windows comes to mind, but you can remove them all by running:

  cd ~/.local/share/gnome-shell/
  rm -rf extensions

and then log in again.

** Summary changed:

- [amdgpu] Screen artifacts/UI oddities on Wayland
+ [amdgpu] Screen corruption, distorted geometry and misplaced triangles

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

Title:
  [amdgpu] Screen corruption, distorted geometry and misplaced triangles

Status in GNOME Shell:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

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

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

  Wayland
  Kernel 6.5.0-9-generic

  * * * * *

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

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

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

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

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

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

  * * * * *

  Please see subsequent posts for video/images.

  Happy to provide any other information as needed. Thanks!

  * * * * *

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2038998/+subscriptions


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

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

2023-11-28 Thread Launchpad Bug Tracker
This bug was fixed in the package ifupdown - 0.8.36+nmu1ubuntu3.1

---
ifupdown (0.8.36+nmu1ubuntu3.1) jammy; urgency=medium

  [ Uwe Kleine-König ]
  * Fix if-up.d/resolved hook to properly work with nameservers and search
domains (LP: #1981103)

  [ Heinrich Schuchardt ]
  *  Remove invalid lines from resolved integration scripts (LP: #1907878)

 -- Joao Andre Simioni   Mon, 16 Oct 2023
14:41:24 +

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

Title:
  System with DNS server in /etc/network/interfaces has bogus systemd-
  resolved config after  upgrade to 22.04

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Focal:
  Fix Released
Status in ifupdown source package in Jammy:
  Fix Released
Status in ifupdown source package in Lunar:
  Fix Released

Bug description:
  [ Impact ]
  ifupdown configurations will stop having a working DNS server on upgrade

  [ Test Plan ]
  Upgrading from an Ubuntu 18.04 or earlier release, bounce a network interface 
with configured DNS server:

  root@pangaea-pm:~# ifdown ens13; ifup ens13
  /etc/network/if-down.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 71: DNS: not found
  /etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13: 
DNS=134.102.20.20 134.102.200.14: not found
  /etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13: 
DOMAINS=marum.de: not found
  Failed to parse DNS server address: DNS
  Failed to set DNS configuration: Invalid argument

  This should result in no errors, and in a valid network configuration with 
working DNS resolution.
  It's likely that existing netplan configuration needs to be removed and 
migrated to classic ifupdown scripts before running the test above.

  [ Where problems could occur ]
  Although we're only fixing the resolved scripts, more complex network setups 
might see regressions in DNS resolution for some cases. We should pay special 
attention to bridges or virtual interfaces that have been configured through 
ifupdown, as well as validate the other scripts under /etc/network/if-up.d/

  [ Other Info ]
  Description:Ubuntu 22.04 LTS
  Release:22.04

  ifupdown:
    Installed: 0.8.36+nmu1ubuntu3
    Candidate: 0.8.36+nmu1ubuntu3
    Version table:
   *** 0.8.36+nmu1ubuntu3 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status

  After upgrading a server with classic ifupdown configuration after
  reboot the machine had no valid dns servers anymore.

  The problem is that the state file created by ifupdown using
  /etc/network/if-up.d/resolved looks like this:

  root@pangaea-pm:~# cat /run/network/ifupdown-inet-ens13
  "DNS"="134.102.20.20 134.102.200.14"
  "DOMAINS"="marum.de"

  The script later sources this file and causes the following errors,
  easy to see when you execute this:

  root@pangaea-pm:~# ifdown ens13; ifup ens13
  /etc/network/if-down.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 71: DNS: not found
  /etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13: 
DNS=134.102.20.20 134.102.200.14: not found
  /etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13: 
DOMAINS=marum.de: not found
  Failed to parse DNS server address: DNS
  Failed to set DNS configuration: Invalid argument

  This happened to me on three different servers, so this is a serious
  bug and should be fixed before 22.04 upgrades are allowed for
  everybody. Most servers provided by data centers like Hetzner
  (Germany) are configure like that. After a do-release-upgrade you have
  no working DNS anymore, unless you disable systemd-resolved. I don't
  want to use netplan, so changing to this is no option.

  The fix is easy - remove the quotes in the script on the left side
  "$DNS" => $DNS; same for DOMAINS:

  if  [ -n "$NEW_DNS" ]; then
  cat <"$mystatedir/ifupdown-${ADDRFAM}-$interface"
  $DNS="$NEW_DNS"
  EOF
  if  [ -n "$NEW_DOMAINS" ]; then
  cat <>"$mystatedir/ifupdown-${ADDRFAM}-$interface"
  $DOMAINS="$NEW_DOMAINS"
  EOF
  fi
  fi

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


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


[Touch-packages] [Bug 1981103] Update Released

2023-11-28 Thread Brian Murray
The verification of the Stable Release Update for ifupdown 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 ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1981103

Title:
  System with DNS server in /etc/network/interfaces has bogus systemd-
  resolved config after  upgrade to 22.04

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Focal:
  Fix Released
Status in ifupdown source package in Jammy:
  Fix Released
Status in ifupdown source package in Lunar:
  Fix Released

Bug description:
  [ Impact ]
  ifupdown configurations will stop having a working DNS server on upgrade

  [ Test Plan ]
  Upgrading from an Ubuntu 18.04 or earlier release, bounce a network interface 
with configured DNS server:

  root@pangaea-pm:~# ifdown ens13; ifup ens13
  /etc/network/if-down.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 71: DNS: not found
  /etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13: 
DNS=134.102.20.20 134.102.200.14: not found
  /etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13: 
DOMAINS=marum.de: not found
  Failed to parse DNS server address: DNS
  Failed to set DNS configuration: Invalid argument

  This should result in no errors, and in a valid network configuration with 
working DNS resolution.
  It's likely that existing netplan configuration needs to be removed and 
migrated to classic ifupdown scripts before running the test above.

  [ Where problems could occur ]
  Although we're only fixing the resolved scripts, more complex network setups 
might see regressions in DNS resolution for some cases. We should pay special 
attention to bridges or virtual interfaces that have been configured through 
ifupdown, as well as validate the other scripts under /etc/network/if-up.d/

  [ Other Info ]
  Description:Ubuntu 22.04 LTS
  Release:22.04

  ifupdown:
    Installed: 0.8.36+nmu1ubuntu3
    Candidate: 0.8.36+nmu1ubuntu3
    Version table:
   *** 0.8.36+nmu1ubuntu3 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status

  After upgrading a server with classic ifupdown configuration after
  reboot the machine had no valid dns servers anymore.

  The problem is that the state file created by ifupdown using
  /etc/network/if-up.d/resolved looks like this:

  root@pangaea-pm:~# cat /run/network/ifupdown-inet-ens13
  "DNS"="134.102.20.20 134.102.200.14"
  "DOMAINS"="marum.de"

  The script later sources this file and causes the following errors,
  easy to see when you execute this:

  root@pangaea-pm:~# ifdown ens13; ifup ens13
  /etc/network/if-down.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 71: DNS: not found
  /etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13: 
DNS=134.102.20.20 134.102.200.14: not found
  /etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13: 
DOMAINS=marum.de: not found
  Failed to parse DNS server address: DNS
  Failed to set DNS configuration: Invalid argument

  This happened to me on three different servers, so this is a serious
  bug and should be fixed before 22.04 upgrades are allowed for
  everybody. Most servers provided by data centers like Hetzner
  (Germany) are configure like that. After a do-release-upgrade you have
  no working DNS anymore, unless you disable systemd-resolved. I don't
  want to use netplan, so changing to this is no option.

  The fix is easy - remove the quotes in the script on the left side
  "$DNS" => $DNS; same for DOMAINS:

  if  [ -n "$NEW_DNS" ]; then
  cat <"$mystatedir/ifupdown-${ADDRFAM}-$interface"
  $DNS="$NEW_DNS"
  EOF
  if  [ -n "$NEW_DOMAINS" ]; then
  cat <>"$mystatedir/ifupdown-${ADDRFAM}-$interface"
  $DOMAINS="$NEW_DOMAINS"
  EOF
  fi
  fi

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


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


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

2023-11-28 Thread Launchpad Bug Tracker
This bug was fixed in the package ifupdown - 0.8.36+nmu1ubuntu4.1

---
ifupdown (0.8.36+nmu1ubuntu4.1) lunar; urgency=medium

  [ Uwe Kleine-König ]
  * Fix if-up.d/resolved hook to properly work with nameservers and search
domains (LP: #1981103)

 -- Heitor Alves de Siqueira   Mon, 16 Oct 2023
14:34:24 +

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

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

Title:
  System with DNS server in /etc/network/interfaces has bogus systemd-
  resolved config after  upgrade to 22.04

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Focal:
  Fix Released
Status in ifupdown source package in Jammy:
  Fix Released
Status in ifupdown source package in Lunar:
  Fix Released

Bug description:
  [ Impact ]
  ifupdown configurations will stop having a working DNS server on upgrade

  [ Test Plan ]
  Upgrading from an Ubuntu 18.04 or earlier release, bounce a network interface 
with configured DNS server:

  root@pangaea-pm:~# ifdown ens13; ifup ens13
  /etc/network/if-down.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 71: DNS: not found
  /etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13: 
DNS=134.102.20.20 134.102.200.14: not found
  /etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13: 
DOMAINS=marum.de: not found
  Failed to parse DNS server address: DNS
  Failed to set DNS configuration: Invalid argument

  This should result in no errors, and in a valid network configuration with 
working DNS resolution.
  It's likely that existing netplan configuration needs to be removed and 
migrated to classic ifupdown scripts before running the test above.

  [ Where problems could occur ]
  Although we're only fixing the resolved scripts, more complex network setups 
might see regressions in DNS resolution for some cases. We should pay special 
attention to bridges or virtual interfaces that have been configured through 
ifupdown, as well as validate the other scripts under /etc/network/if-up.d/

  [ Other Info ]
  Description:Ubuntu 22.04 LTS
  Release:22.04

  ifupdown:
    Installed: 0.8.36+nmu1ubuntu3
    Candidate: 0.8.36+nmu1ubuntu3
    Version table:
   *** 0.8.36+nmu1ubuntu3 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status

  After upgrading a server with classic ifupdown configuration after
  reboot the machine had no valid dns servers anymore.

  The problem is that the state file created by ifupdown using
  /etc/network/if-up.d/resolved looks like this:

  root@pangaea-pm:~# cat /run/network/ifupdown-inet-ens13
  "DNS"="134.102.20.20 134.102.200.14"
  "DOMAINS"="marum.de"

  The script later sources this file and causes the following errors,
  easy to see when you execute this:

  root@pangaea-pm:~# ifdown ens13; ifup ens13
  /etc/network/if-down.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 71: DNS: not found
  /etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13: 
DNS=134.102.20.20 134.102.200.14: not found
  /etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13: 
DOMAINS=marum.de: not found
  Failed to parse DNS server address: DNS
  Failed to set DNS configuration: Invalid argument

  This happened to me on three different servers, so this is a serious
  bug and should be fixed before 22.04 upgrades are allowed for
  everybody. Most servers provided by data centers like Hetzner
  (Germany) are configure like that. After a do-release-upgrade you have
  no working DNS anymore, unless you disable systemd-resolved. I don't
  want to use netplan, so changing to this is no option.

  The fix is easy - remove the quotes in the script on the left side
  "$DNS" => $DNS; same for DOMAINS:

  if  [ -n "$NEW_DNS" ]; then
  cat <"$mystatedir/ifupdown-${ADDRFAM}-$interface"
  $DNS="$NEW_DNS"
  EOF
  if  [ -n "$NEW_DOMAINS" ]; then
  cat <>"$mystatedir/ifupdown-${ADDRFAM}-$interface"
  $DOMAINS="$NEW_DOMAINS"
  EOF
  fi
  fi

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


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


[Touch-packages] [Bug 1907878] Update Released

2023-11-28 Thread Brian Murray
The verification of the Stable Release Update for ifupdown 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 ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1907878

Title:
  wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]:
  /etc/network/if-up.d/resolved: 12: mystatedir: not found)

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Jammy:
  Fix Released

Bug description:
  Syslog error:

     nm-dispatcher[...]: /etc/network/if-up.d/resolved: 12: mystatedir:
  not found

  I think it's because of this line:

    if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then
    mystatedir statedir ifindex interface <- this 
is interpreted as a 'mystatedir' command and fails

    interface=$IFACE
    if [ ! "$interface" ]; then

  Perhaps the intention was to 'export mystatedir statedir ...'

  SRU for Jammy:

  [ Impact ]

 * /etc/network/if-{up,down}.d/resolved have a mistype:
 
 mystatedir statedir ifindex interface
 
 And when this line is executed, mystatedir is not found (not a valid 
command)
 and it generates an error log in /var/log/syslog and the terminal output. 
 It's not fatal, and the rest of the code gets executed, but it generates 
the
 message.
 
 # ifup ens3
 /etc/network/if-up.d/resolved: 12: mystatedir: not found

 # ifdown ens3
 /etc/network/if-down.d/resolved: 12: mystatedir: not found 
 
 The fix accepted in kinetic is only to remove this line. The same fix can 
be
 applied to Jammy.
 
  [ Test Plan ]

 With the new package installed, remove netplan configuration and add a 
valid
 /etc/network/interfaces file and then use the commands:
 
 # ifdown 
 # ifup 
 
 And confirm the messages are not displayed and the network configuration
 succeeds.
 
  [ Where problems could occur ]

 If mystatedir would be a valid command or function, which is not the case,
 that could break the script.

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


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


[Touch-packages] [Bug 1907878] Re: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found)

2023-11-28 Thread Launchpad Bug Tracker
This bug was fixed in the package ifupdown - 0.8.36+nmu1ubuntu3.1

---
ifupdown (0.8.36+nmu1ubuntu3.1) jammy; urgency=medium

  [ Uwe Kleine-König ]
  * Fix if-up.d/resolved hook to properly work with nameservers and search
domains (LP: #1981103)

  [ Heinrich Schuchardt ]
  *  Remove invalid lines from resolved integration scripts (LP: #1907878)

 -- Joao Andre Simioni   Mon, 16 Oct 2023
14:41:24 +

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

Title:
  wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]:
  /etc/network/if-up.d/resolved: 12: mystatedir: not found)

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Jammy:
  Fix Released

Bug description:
  Syslog error:

     nm-dispatcher[...]: /etc/network/if-up.d/resolved: 12: mystatedir:
  not found

  I think it's because of this line:

    if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then
    mystatedir statedir ifindex interface <- this 
is interpreted as a 'mystatedir' command and fails

    interface=$IFACE
    if [ ! "$interface" ]; then

  Perhaps the intention was to 'export mystatedir statedir ...'

  SRU for Jammy:

  [ Impact ]

 * /etc/network/if-{up,down}.d/resolved have a mistype:
 
 mystatedir statedir ifindex interface
 
 And when this line is executed, mystatedir is not found (not a valid 
command)
 and it generates an error log in /var/log/syslog and the terminal output. 
 It's not fatal, and the rest of the code gets executed, but it generates 
the
 message.
 
 # ifup ens3
 /etc/network/if-up.d/resolved: 12: mystatedir: not found

 # ifdown ens3
 /etc/network/if-down.d/resolved: 12: mystatedir: not found 
 
 The fix accepted in kinetic is only to remove this line. The same fix can 
be
 applied to Jammy.
 
  [ Test Plan ]

 With the new package installed, remove netplan configuration and add a 
valid
 /etc/network/interfaces file and then use the commands:
 
 # ifdown 
 # ifup 
 
 And confirm the messages are not displayed and the network configuration
 succeeds.
 
  [ Where problems could occur ]

 If mystatedir would be a valid command or function, which is not the case,
 that could break the script.

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


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


[Touch-packages] [Bug 2007050] Re: Microsoft Surface Laptop 4 keyboard not available during early boot (can't enter disk unlock password)

2023-11-28 Thread Launchpad Bug Tracker
This bug was fixed in the package initramfs-tools - 0.142ubuntu15.1

---
initramfs-tools (0.142ubuntu15.1) mantic; urgency=medium

  * Install intel_lpss_pci and spi_pxa2xx_platform kernel modules for keyboard
on MacBook Pro 2017 (LP: #2042710)
  * Install surface_aggregator_registry for keyboard on Surface Laptop 4
(LP: #2007050)

 -- Benjamin Drung   Tue, 14 Nov 2023 20:02:42 +0100

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

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

Title:
  Microsoft Surface Laptop 4 keyboard not available during early boot
  (can't enter disk unlock password)

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Mantic:
  Fix Released
Status in linux source package in Mantic:
  Invalid

Bug description:
  [ Impact ]

  With 22.04 LTS, fully updated, freshly built initrd's for both 5.15
  (linux-generic-hwe-22.04) and 5.19 (linux-generic-hwe-22.04-edge)
  kernels, the embedded keyboard of a Microsoft Surface 4 Laptop model
  1950 (Intel Gen 11), namely "Microsoft Surface 045E:09AE Keyboard", is
  not available during early boot, such as for entering a full disk
  encryption passphrase. Just pressing enter at said prompt has no
  effect. Connecting an external keyboard via USB and typing the
  passphrase from there works around it.

  The keyboard works fine on the fully booted system.

  Secure boot is disabled on this system.

  [ Test Plan ]

  The -generic kernel and probably all kernel flavors contain the needed driver 
(on amd64). On mantic systems, you can verify the current initrd doesn't 
contain these modules by decompressing the initramfs and listing its files:
  $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 
'surface_aggregator_registry\|intel-lpss-pci'

  After installing the updated initramfs-tools package, your current initramfs 
should be automatically rebuilt and pick up the kernel modules:
  $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 
'surface_aggregator_registry\|intel-lpss-pci'
  usr/lib/modules/6.5.0-10-generic/kernel/drivers/mfd/intel-lpss-pci.ko.zst
  
usr/lib/modules/6.5.0-10-generic/kernel/drivers/platform/surface/surface_aggregator_registry.ko.zst

  Test case on Microsoft Surface Laptop 4: Remove all previous
  workarounds. Install the fixed initramfs-tools version. Then the
  keyboard should work during boot to enter the passphrase.

  [ Where problems could occur ]

  This is making the initramfs slightly bigger. In my testing, both
  added were 11,868 bytes in total (or 0.01 % on a 102 MB initramfs).

  [ Apport report ]

  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 13 00:53:34 2023
  Dependencies:
   adduser 3.118ubuntu5
   apt 2.4.8
   apt-utils 2.4.8
   busybox-initramfs 1:1.30.1-7ubuntu3
   ca-certificates 20211016ubuntu0.22.04.1
   coreutils 8.32-4.1ubuntu1
   cpio 2.13+dfsg-7
   debconf 1.5.79ubuntu1
   debconf-i18n 1.5.79ubuntu1
   dmsetup 2:1.02.175-2.1ubuntu4
   dpkg 1.21.1ubuntu2.1
   gcc-12-base 12.1.0-2ubuntu1~22.04
   gettext-base 0.21-4ubuntu4
   gpgv 2.2.27-3ubuntu2.1
   grub-common 2.06-2ubuntu7.1
   grub-gfxpayload-lists 0.7
   grub-pc 2.06-2ubuntu7.1
   grub-pc-bin 2.06-2ubuntu7.1
   grub2-common 2.06-2ubuntu7.1
   init-system-helpers 1.62
   initramfs-tools 0.140ubuntu13.1
   initramfs-tools-bin 0.140ubuntu13.1
   initramfs-tools-core 0.140ubuntu13.1
   klibc-utils 2.0.10-4
   kmod 29-1ubuntu1
   libacl1 2.3.1-1
   libapt-pkg6.0 2.4.8
   libattr1 1:2.5.1-1build1
   libaudit-common 1:3.0.7-1build1
   libaudit1 1:3.0.7-1build1
   libblkid1 2.37.2-4ubuntu3
   libbrotli1 1.0.9-2build6
   libbz2-1.0 1.0.8-5build1
   libc6 2.35-0ubuntu3.1
   libcap-ng0 0.7.9-2.2build3
   libcap2 1:2.44-1build3
   libcom-err2 1.46.5-2ubuntu1.1
   libcrypt1 1:4.4.27-1
   libdb5.3 5.3.28+dfsg1-0.8ubuntu3
   libdevmapper1.02.1 2:1.02.175-2.1ubuntu4
   libefiboot1 37-6ubuntu2
   libefivar1 37-6ubuntu2
   libffi8 3.4.2-4
   libfreetype6 2.11.1+dfsg-1ubuntu0.1
   libfuse3-3 3.10.5-1build1
   libgcc-s1 12.1.0-2ubuntu1~22.04
   libgcrypt20 1.9.4-3ubuntu3
   libgmp10 2:6.2.1+dfsg-3ubuntu1
   libgnutls30 3.7.3-4ubuntu1.1
   libgpg-error0 1.43-3
   libgssapi-krb5-2 1.19.2-2ubuntu0.1
   libhogweed6 3.7.3-1build2
   libidn2-0 2.3.2-2build1
   libk5crypto3 1.19.2-2ubuntu0.1
   libkeyutils1 1.6.1-2ubuntu3
   libklibc 2.0.10-4
   libkmod2 29-1ubuntu1
   libkrb5-3 1.19.2-2ubuntu0.1
   libkrb5support0 1.19.2-2ubuntu0.1
   liblocale-gettext-perl 1.07-4build3
   liblz4-1 1.9.3-2build2
   liblzma5 5.2.5-2ubuntu1
   libmount1 2.37.2-4ubuntu3
   libnettle8 3.7.3-1build2
   libnsl2 1.3.0-2build2
   libp11-kit0 0.24.0-6build1
   libpam-modules 1.4.0-11ub

[Touch-packages] [Bug 2040113] Update Released

2023-11-28 Thread Brian Murray
The verification of the Stable Release Update for gdb 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 gdb in Ubuntu.
https://bugs.launchpad.net/bugs/2040113

Title:
  gdb crashes upon `run` on some arm64 machines

Status in gdb package in Ubuntu:
  Fix Released
Status in gdb source package in Lunar:
  Fix Released

Bug description:
  [ Impact ]

   * gdb 13.1 as shipped in lunar is affected by a bug where it crashes upon 
`run` 
 on some arm64 machines (confirmed on Apple M-series, both under hypervisor 
 and bare metal, everything else with PAC should also be affected).

   * It was fixed upstream in gdb 13.2: https://inbox.sourceware.org/gdb- 
 patches/20230316103904.1947447-1-luis.mach...@arm.com/.

   * Debian bookworm's gdb_13.1-3 also includes the same patch as 
`aarch64-pauth- 
 registers.patch`.

  [ Test Plan ]

   * This diff is confirmed to fix gdb 13.1 in lunar on my arm64 laptop.

   * This could be tested by running any program under lunar's gdb 
 on any ARM64 PAC machine.

  [ Where problems could occur ]

   * Problems aren't particularly likely as the exact patch was included in the 
 last Debian stable.

   * In theory, a gdb rebuild could possibly cause breakage.

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


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


[Touch-packages] [Bug 2040113] Re: gdb crashes upon `run` on some arm64 machines

2023-11-28 Thread Launchpad Bug Tracker
This bug was fixed in the package gdb - 13.1-2ubuntu2.1

---
gdb (13.1-2ubuntu2.1) lunar; urgency=medium

  [ Mate Kukri ]
  * Fixes (LP: #2040113)

  [ Emanuele Rocca ]
  * aarch64: add aarch64-pauth-registers.patch to check for valid inferior
thread/regcache before reading pauth registers. (Closes: #1034611)

 -- Mate Kukri   Wed, 15 Nov 2023 13:27:25
+

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

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

Title:
  gdb crashes upon `run` on some arm64 machines

Status in gdb package in Ubuntu:
  Fix Released
Status in gdb source package in Lunar:
  Fix Released

Bug description:
  [ Impact ]

   * gdb 13.1 as shipped in lunar is affected by a bug where it crashes upon 
`run` 
 on some arm64 machines (confirmed on Apple M-series, both under hypervisor 
 and bare metal, everything else with PAC should also be affected).

   * It was fixed upstream in gdb 13.2: https://inbox.sourceware.org/gdb- 
 patches/20230316103904.1947447-1-luis.mach...@arm.com/.

   * Debian bookworm's gdb_13.1-3 also includes the same patch as 
`aarch64-pauth- 
 registers.patch`.

  [ Test Plan ]

   * This diff is confirmed to fix gdb 13.1 in lunar on my arm64 laptop.

   * This could be tested by running any program under lunar's gdb 
 on any ARM64 PAC machine.

  [ Where problems could occur ]

   * Problems aren't particularly likely as the exact patch was included in the 
 last Debian stable.

   * In theory, a gdb rebuild could possibly cause breakage.

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


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


[Touch-packages] [Bug 2045072] Re: Bug on galaky book2 750xed

2023-11-28 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  Bug on galaky book2 750xed

Status in xorg package in Ubuntu:
  New

Bug description:
  I had to set nomode parameter to avoid the screen become dark and then
  change the line of the file /etc/default/grub

  from "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

  to "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_dc=0
  intel_idle.max_cstate=2"

  then add to the file /etc/systemd/logind.conf

  the instructions:

  HandleLidSwitch=ignore
  HandleLidSwitchExternalPower=ignore
  HandleLidSwitchDocked=ignore

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 28 22:00:43 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) 
(prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Alder Lake-UP3 GT2 [Iris Xe 
Graphics] [144d:c1c6]
  InstallationDate: Installed on 2023-11-13 (15 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=it_IT.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=681212a7-b32a-4fbf-a9a1-b51bef0216f7 ro quiet splash i915.enable_dc=0 
intel_idle.max_cstate=2 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2023
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P13CFG.039.230726.HQ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP750XED-KC2IT
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SAMSUNG_SW_REVISION_12345+0.0.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP13CFG.039.230726.HQ:bd07/26/2023:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn750XED:pvrP13CFG:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP750XED-KC2IT:rvrSAMSUNG_SW_REVISION_12345+0.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-ADLP-PCFG:
  dmi.product.family: Galaxy Book2
  dmi.product.name: 750XED
  dmi.product.sku: SCAI-A5A5-A5A5-ADLP-PCFG
  dmi.product.version: P13CFG
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Touch-packages] [Bug 2042710] Re: Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14, 1) due to missing kernel modules in initramfs

2023-11-28 Thread Launchpad Bug Tracker
This bug was fixed in the package initramfs-tools - 0.142ubuntu15.1

---
initramfs-tools (0.142ubuntu15.1) mantic; urgency=medium

  * Install intel_lpss_pci and spi_pxa2xx_platform kernel modules for keyboard
on MacBook Pro 2017 (LP: #2042710)
  * Install surface_aggregator_registry for keyboard on Surface Laptop 4
(LP: #2007050)

 -- Benjamin Drung   Tue, 14 Nov 2023 20:02:42 +0100

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

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

Title:
  Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14,1)
  due to missing kernel modules in initramfs

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

Bug description:
  [ Impact ]

  I have a MacBook Pro 2017 (MacBookPro14,1) with an encrypted root
  partition, which I decrypt via passphrase during boot, at the "Please
  unlock disk nvme0n1p4_crypt" prompt.

  Using 23.04 "Lunar" this worked fine. However after upgrading to 23.10
  "Mantic", the built-in keyboard doesn't work for entering the
  passphrase.

  Quickest workaround: plug in a USB keyboard for entering the
  passphrase.

  Workaround: add the following modules to "/etc/initramfs-
  tools/modules":

  spi_pxa2xx_platform
  intel_lpss_pci

  ... then "sudo update-initramfs -u".

  I found that both kernel modules were required to get the keyboard
  recognised in initramfs.

  [ Test Plan ]

  The -generic kernel and probably all kernel flavors contain the SPI and PCI 
driver (on amd64). On mantic systems, you can verify the current initrd doesn't 
contain these modules by decompressing the initramfs and listing its files:
  $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 
'spi-pxa2xx-platform\|intel-lpss-pci'

  After installing the updated initramfs-tools package, your current initramfs 
should be automatically rebuilt and pick up the kernel modules:
  $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 
'spi-pxa2xx-platform\|intel-lpss-pci'
  usr/lib/modules/6.5.0-10-generic/kernel/drivers/mfd/intel-lpss-pci.ko.zst
  usr/lib/modules/6.5.0-10-generic/kernel/drivers/spi/spi-pxa2xx-platform.ko.zst

  Test case on MacBook Pro 2017 laptops: Remove all previous
  workarounds. Install the fixed initramfs-tools version. Then the
  keyboard should work during boot to enter the passphrase.

  [ Where problems could occur ]

  This is making the initramfs slightly bigger. In my testing, both
  added were 23,852 bytes in total (or 0.02 % on a 102 MB initramfs).

  [ Remaining original report ]

  I did a bit of digging into what changed for 23.10. It could
  potentially (?) be commit 2df78bbb143884b9601a32608e12e43d40ccb0b0 "Do
  not install ARM/RISCV specific modules on other architectures".

  I had a look into how dracut handles it. Turns out that they
  specifically include "spi_pxa2xx_platform" after reporting a similar
  bug report in Fedora:
  https://bugzilla.redhat.com/show_bug.cgi?id=2166209

  I don't know how (if?) they handle the 2nd module, "intel_lpss_pci".

  Anyway, I don't need an immediate fix since the workaround works for
  me. Just posting this for further investigation, and for any other
  MacBook Pro users in the same situation. Thanks for working on Ubuntu,
  I think you're all amazing!

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


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


[Touch-packages] [Bug 2045072] [NEW] Bug on galaky book2 750xed

2023-11-28 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I had to set nomode parameter to avoid the screen become dark and then
change the line of the file /etc/default/grub

from "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

to "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_dc=0
intel_idle.max_cstate=2"

then add to the file /etc/systemd/logind.conf

the instructions:

HandleLidSwitch=ignore
HandleLidSwitchExternalPower=ignore
HandleLidSwitchDocked=ignore

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 28 22:00:43 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) 
(prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd Alder Lake-UP3 GT2 [Iris Xe Graphics] 
[144d:c1c6]
InstallationDate: Installed on 2023-11-13 (15 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
 LANG=it_IT.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=681212a7-b32a-4fbf-a9a1-b51bef0216f7 ro quiet splash i915.enable_dc=0 
intel_idle.max_cstate=2 vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/26/2023
dmi.bios.release: 5.25
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: P13CFG.039.230726.HQ
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP750XED-KC2IT
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SAMSUNG_SW_REVISION_12345+0.0.
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP13CFG.039.230726.HQ:bd07/26/2023:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn750XED:pvrP13CFG:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP750XED-KC2IT:rvrSAMSUNG_SW_REVISION_12345+0.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-ADLP-PCFG:
dmi.product.family: Galaxy Book2
dmi.product.name: 750XED
dmi.product.sku: SCAI-A5A5-A5A5-ADLP-PCFG
dmi.product.version: P13CFG
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug mantic ubuntu wayland-session
-- 
Bug on galaky book2 750xed
https://bugs.launchpad.net/bugs/2045072
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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


[Touch-packages] [Bug 2042710] Update Released

2023-11-28 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/2042710

Title:
  Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14,1)
  due to missing kernel modules in initramfs

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

  I have a MacBook Pro 2017 (MacBookPro14,1) with an encrypted root
  partition, which I decrypt via passphrase during boot, at the "Please
  unlock disk nvme0n1p4_crypt" prompt.

  Using 23.04 "Lunar" this worked fine. However after upgrading to 23.10
  "Mantic", the built-in keyboard doesn't work for entering the
  passphrase.

  Quickest workaround: plug in a USB keyboard for entering the
  passphrase.

  Workaround: add the following modules to "/etc/initramfs-
  tools/modules":

  spi_pxa2xx_platform
  intel_lpss_pci

  ... then "sudo update-initramfs -u".

  I found that both kernel modules were required to get the keyboard
  recognised in initramfs.

  [ Test Plan ]

  The -generic kernel and probably all kernel flavors contain the SPI and PCI 
driver (on amd64). On mantic systems, you can verify the current initrd doesn't 
contain these modules by decompressing the initramfs and listing its files:
  $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 
'spi-pxa2xx-platform\|intel-lpss-pci'

  After installing the updated initramfs-tools package, your current initramfs 
should be automatically rebuilt and pick up the kernel modules:
  $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 
'spi-pxa2xx-platform\|intel-lpss-pci'
  usr/lib/modules/6.5.0-10-generic/kernel/drivers/mfd/intel-lpss-pci.ko.zst
  usr/lib/modules/6.5.0-10-generic/kernel/drivers/spi/spi-pxa2xx-platform.ko.zst

  Test case on MacBook Pro 2017 laptops: Remove all previous
  workarounds. Install the fixed initramfs-tools version. Then the
  keyboard should work during boot to enter the passphrase.

  [ Where problems could occur ]

  This is making the initramfs slightly bigger. In my testing, both
  added were 23,852 bytes in total (or 0.02 % on a 102 MB initramfs).

  [ Remaining original report ]

  I did a bit of digging into what changed for 23.10. It could
  potentially (?) be commit 2df78bbb143884b9601a32608e12e43d40ccb0b0 "Do
  not install ARM/RISCV specific modules on other architectures".

  I had a look into how dracut handles it. Turns out that they
  specifically include "spi_pxa2xx_platform" after reporting a similar
  bug report in Fedora:
  https://bugzilla.redhat.com/show_bug.cgi?id=2166209

  I don't know how (if?) they handle the 2nd module, "intel_lpss_pci".

  Anyway, I don't need an immediate fix since the workaround works for
  me. Just posting this for further investigation, and for any other
  MacBook Pro users in the same situation. Thanks for working on Ubuntu,
  I think you're all amazing!

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


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


[Touch-packages] [Bug 2007050] Update Released

2023-11-28 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/2007050

Title:
  Microsoft Surface Laptop 4 keyboard not available during early boot
  (can't enter disk unlock password)

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Mantic:
  Fix Committed
Status in linux source package in Mantic:
  Invalid

Bug description:
  [ Impact ]

  With 22.04 LTS, fully updated, freshly built initrd's for both 5.15
  (linux-generic-hwe-22.04) and 5.19 (linux-generic-hwe-22.04-edge)
  kernels, the embedded keyboard of a Microsoft Surface 4 Laptop model
  1950 (Intel Gen 11), namely "Microsoft Surface 045E:09AE Keyboard", is
  not available during early boot, such as for entering a full disk
  encryption passphrase. Just pressing enter at said prompt has no
  effect. Connecting an external keyboard via USB and typing the
  passphrase from there works around it.

  The keyboard works fine on the fully booted system.

  Secure boot is disabled on this system.

  [ Test Plan ]

  The -generic kernel and probably all kernel flavors contain the needed driver 
(on amd64). On mantic systems, you can verify the current initrd doesn't 
contain these modules by decompressing the initramfs and listing its files:
  $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 
'surface_aggregator_registry\|intel-lpss-pci'

  After installing the updated initramfs-tools package, your current initramfs 
should be automatically rebuilt and pick up the kernel modules:
  $ lsinitramfs /boot/initrd.img-6.5.0-10-generic | grep 
'surface_aggregator_registry\|intel-lpss-pci'
  usr/lib/modules/6.5.0-10-generic/kernel/drivers/mfd/intel-lpss-pci.ko.zst
  
usr/lib/modules/6.5.0-10-generic/kernel/drivers/platform/surface/surface_aggregator_registry.ko.zst

  Test case on Microsoft Surface Laptop 4: Remove all previous
  workarounds. Install the fixed initramfs-tools version. Then the
  keyboard should work during boot to enter the passphrase.

  [ Where problems could occur ]

  This is making the initramfs slightly bigger. In my testing, both
  added were 11,868 bytes in total (or 0.01 % on a 102 MB initramfs).

  [ Apport report ]

  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 13 00:53:34 2023
  Dependencies:
   adduser 3.118ubuntu5
   apt 2.4.8
   apt-utils 2.4.8
   busybox-initramfs 1:1.30.1-7ubuntu3
   ca-certificates 20211016ubuntu0.22.04.1
   coreutils 8.32-4.1ubuntu1
   cpio 2.13+dfsg-7
   debconf 1.5.79ubuntu1
   debconf-i18n 1.5.79ubuntu1
   dmsetup 2:1.02.175-2.1ubuntu4
   dpkg 1.21.1ubuntu2.1
   gcc-12-base 12.1.0-2ubuntu1~22.04
   gettext-base 0.21-4ubuntu4
   gpgv 2.2.27-3ubuntu2.1
   grub-common 2.06-2ubuntu7.1
   grub-gfxpayload-lists 0.7
   grub-pc 2.06-2ubuntu7.1
   grub-pc-bin 2.06-2ubuntu7.1
   grub2-common 2.06-2ubuntu7.1
   init-system-helpers 1.62
   initramfs-tools 0.140ubuntu13.1
   initramfs-tools-bin 0.140ubuntu13.1
   initramfs-tools-core 0.140ubuntu13.1
   klibc-utils 2.0.10-4
   kmod 29-1ubuntu1
   libacl1 2.3.1-1
   libapt-pkg6.0 2.4.8
   libattr1 1:2.5.1-1build1
   libaudit-common 1:3.0.7-1build1
   libaudit1 1:3.0.7-1build1
   libblkid1 2.37.2-4ubuntu3
   libbrotli1 1.0.9-2build6
   libbz2-1.0 1.0.8-5build1
   libc6 2.35-0ubuntu3.1
   libcap-ng0 0.7.9-2.2build3
   libcap2 1:2.44-1build3
   libcom-err2 1.46.5-2ubuntu1.1
   libcrypt1 1:4.4.27-1
   libdb5.3 5.3.28+dfsg1-0.8ubuntu3
   libdevmapper1.02.1 2:1.02.175-2.1ubuntu4
   libefiboot1 37-6ubuntu2
   libefivar1 37-6ubuntu2
   libffi8 3.4.2-4
   libfreetype6 2.11.1+dfsg-1ubuntu0.1
   libfuse3-3 3.10.5-1build1
   libgcc-s1 12.1.0-2ubuntu1~22.04
   libgcrypt20 1.9.4-3ubuntu3
   libgmp10 2:6.2.1+dfsg-3ubuntu1
   libgnutls30 3.7.3-4ubuntu1.1
   libgpg-error0 1.43-3
   libgssapi-krb5-2 1.19.2-2ubuntu0.1
   libhogweed6 3.7.3-1build2
   libidn2-0 2.3.2-2build1
   libk5crypto3 1.19.2-2ubuntu0.1
   libkeyutils1 1.6.1-2ubuntu3
   libklibc 2.0.10-4
   libkmod2 29-1ubuntu1
   libkrb5-3 1.19.2-2ubuntu0.1
   libkrb5support0 1.19.2-2ubuntu0.1
   liblocale-gettext-perl 1.07-4build3
   liblz4-1 1.9.3-2build2
   liblzma5 5.2.5-2ubuntu1
   libmount1 2.37.2-4ubuntu3
   libnettle8 3.7.3-1build2
   libnsl2 1.3.0-2build2
   libp11-kit0 0.24.0-6build1
   libpam-modules 1.4.0-11ubuntu2.3
   libpam-modules-b

[Touch-packages] [Bug 2045075] Re: Framework Laptop Expansion Card enabling auto suspend

2023-11-28 Thread Matt Hartley
** Tags added: systemd

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

Title:
  Framework Laptop Expansion Card enabling auto suspend

Status in systemd package in Ubuntu:
  New

Bug description:
  
  Framework provides expansion cards. For the HDMI and DisplayPort, these 
benefit power management via enabling auto suspend.

  Ubuntu 22.04.3 LTS
  6.1.0-1026-oem
  systemd 249 (249.11-0ubuntu3.11)

  #
  # Framework
  #

  # HDMI Expansion Card
  usb:v32ACp0002*
  # DisplayPort Expansion Card
  usb:v32ACp0003*
   ID_AUTOSUSPEND=1

  
  Commit in question: 
https://github.com/systemd/systemd/commit/9023630cb7025650aa4d01ee794b0bb68bfdf2c1

  When looking at 60-autosuspend.hwdb for Ubuntu 22.04.3, we do not have
  the additional entry shown above available for HDMI and DisplayPort
  expansion cards.

  I'd like to see this added to 22.04 for future inclusion.

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


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


[Touch-packages] [Bug 2045075] [NEW] Framework Laptop Expansion Card enabling auto suspend

2023-11-28 Thread Matt Hartley
Public bug reported:


Framework provides expansion cards. For the HDMI and DisplayPort, these benefit 
power management via enabling auto suspend.

Ubuntu 22.04.3 LTS
6.1.0-1026-oem
systemd 249 (249.11-0ubuntu3.11)

#
# Framework
#

# HDMI Expansion Card
usb:v32ACp0002*
# DisplayPort Expansion Card
usb:v32ACp0003*
 ID_AUTOSUSPEND=1


Commit in question: 
https://github.com/systemd/systemd/commit/9023630cb7025650aa4d01ee794b0bb68bfdf2c1

When looking at 60-autosuspend.hwdb for Ubuntu 22.04.3, we do not have
the additional entry shown above available for HDMI and DisplayPort
expansion cards.

I'd like to see this added to 22.04 for future inclusion.

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

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

Title:
  Framework Laptop Expansion Card enabling auto suspend

Status in systemd package in Ubuntu:
  New

Bug description:
  
  Framework provides expansion cards. For the HDMI and DisplayPort, these 
benefit power management via enabling auto suspend.

  Ubuntu 22.04.3 LTS
  6.1.0-1026-oem
  systemd 249 (249.11-0ubuntu3.11)

  #
  # Framework
  #

  # HDMI Expansion Card
  usb:v32ACp0002*
  # DisplayPort Expansion Card
  usb:v32ACp0003*
   ID_AUTOSUSPEND=1

  
  Commit in question: 
https://github.com/systemd/systemd/commit/9023630cb7025650aa4d01ee794b0bb68bfdf2c1

  When looking at 60-autosuspend.hwdb for Ubuntu 22.04.3, we do not have
  the additional entry shown above available for HDMI and DisplayPort
  expansion cards.

  I'd like to see this added to 22.04 for future inclusion.

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


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


[Touch-packages] [Bug 2044654] Re: No debugging symbols found in libgdk-3.so.0

2023-11-28 Thread Sebastien Bacher
Ah, that would have been something important to mention in the bug
description no? It should be reassigned to the ubuntu-debuginfod project
but launchpad doesn't let me do that for some reason

** Changed in: gtk+3.0 (Ubuntu)
   Status: Incomplete => New

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

Title:
  No debugging symbols found in libgdk-3.so.0

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Attach gdb to a running yelp process!

  (gdb) share libgdk
  Reading symbols from /lib/x86_64-linux-gnu/libgdk-3.so.0...
  (No debugging symbols found in /lib/x86_64-linux-gnu/libgdk-3.so.0)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgtk-3-0 3.24.33-1ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-1016.16~22.04.1-azure 6.2.16
  Uname: Linux 6.2.0-1016-azure x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 26 13:11:15 2023
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2044654/+subscriptions


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


[Touch-packages] [Bug 2044604] Re: package apparmor 2.12-4ubuntu5.3+esm1 installed the 20.04 release, with words, "mer/upgrade: new apparmor package pre-installation script subprocess returned error e

2023-11-28 Thread Georgia Garcia
*** This bug is a duplicate of bug 2032851 ***
https://bugs.launchpad.net/bugs/2032851

** This bug has been marked a duplicate of bug 2032851
   package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new apparmor 
package pre-installation script subprocess returned error exit status 1

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

Title:
  package apparmor 2.12-4ubuntu5.3+esm1 installed the 20.04 release,
  with words, "mer/upgrade: new apparmor package pre-installation script
  subprocess returned error exit status 1

Status in apparmor package in Ubuntu:
  New

Bug description:
  rors occurred" did manual reboot. But system just logged out and back in 
quickly. I pressed start button to reboot, and the system took a half hout to 
connect until I right clicked the start-page. Then the log-in page appeared and 
the system came up.
  h94b@h94b-HP-EliteBook-8460p:~$ dpkg -1 | grep linux-image
  dpkg: error: unknown option -1

  Type dpkg --help for help about installing and deinstalling packages [*];
  Use 'apt' or 'aptitude' for user-friendly package management;
  Type dpkg -Dhelp for a list of dpkg debug flag values;
  Type dpkg --force-help for a list of forcing options;
  Type dpkg-deb --help for help about manipulating *.deb files;

  Options marked [*] produce a lot of output - pipe it through 'less' or 'more' 
!
  h94b@h94b-HP-EliteBook-8460p:~$ cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu 20.04.6 LTS"
  h94b@h94b-HP-EliteBook-8460p:~$ 

  thank You

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: apparmor 2.12-4ubuntu5.3+esm1
  ProcVersionSignature: Ubuntu 5.4.0-167.184~18.04.1-generic 5.4.252
  Uname: Linux 5.4.0-167-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.29
  Architecture: amd64
  Date: Sat Nov 25 04:39:23 2023
  DuplicateSignature:
   package:apparmor:2.12-4ubuntu5.3+esm1
   Preparing to unpack .../09-apparmor_2.13.3-7ubuntu5.2_amd64.deb ...
   rm: cannot remove '/etc/apparmor.d/cache/e10c1cf9.0': Is a directory
   dpkg: error processing archive 
/tmp/apt-dpkg-install-x2AWLZ/09-apparmor_2.13.3-7ubuntu5.2_amd64.deb (--unpack):
new apparmor package pre-installation script subprocess returned error exit 
status 1
  ErrorMessage: new apparmor package pre-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2023-11-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 
(20210915)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-167-generic 
root=UUID=4bc5fd69-6854-4ec0-b0bb-a914ce15ecce ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.10
  SourcePackage: apparmor
  Title: package apparmor 2.12-4ubuntu5.3+esm1 failed to install/upgrade: new 
apparmor package pre-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to focal on 2023-11-25 (0 days ago)

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


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


[Touch-packages] [Bug 2044654] Re: No debugging symbols found in libgdk-3.so.0

2023-11-28 Thread Christopher Yeleighton
No, I do not.  The bug affects debuginfod.

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

Title:
  No debugging symbols found in libgdk-3.so.0

Status in gtk+3.0 package in Ubuntu:
  Incomplete

Bug description:
  Attach gdb to a running yelp process!

  (gdb) share libgdk
  Reading symbols from /lib/x86_64-linux-gnu/libgdk-3.so.0...
  (No debugging symbols found in /lib/x86_64-linux-gnu/libgdk-3.so.0)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgtk-3-0 3.24.33-1ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-1016.16~22.04.1-azure 6.2.16
  Uname: Linux 6.2.0-1016-azure x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 26 13:11:15 2023
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2044654/+subscriptions


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


[Touch-packages] [Bug 2045033] [NEW] Merge rsyslog 8.2310.0-2 from Debian

2023-11-28 Thread Heinrich Schuchardt
Public bug reported:

Debian has released rsyslog 8.2310.0-4. Merge it.

** Affects: rsyslog (Ubuntu)
 Importance: Undecided
 Assignee: Heinrich Schuchardt (xypron)
 Status: New

** Changed in: rsyslog (Ubuntu)
 Assignee: (unassigned) => Heinrich Schuchardt (xypron)

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

Title:
  Merge rsyslog 8.2310.0-2 from Debian

Status in rsyslog package in Ubuntu:
  New

Bug description:
  Debian has released rsyslog 8.2310.0-4. Merge it.

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


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


[Touch-packages] [Bug 2045028] [NEW] client-server autopkgtest fails: Failed to set LLMNR configuration: Link 3 not known

2023-11-28 Thread Benjamin Drung
Public bug reported:

client-server autopkgtest fails. Relevant log:

```
115s + ip netns exec client dhclient ptp-veth-client
116s Setting LLMNR support level "yes" for "3", but the global support level is 
"no".
116s Failed to set LLMNR configuration: Link 3 not known
116s Failed to set MulticastDNS configuration: Link 3 not known
116s Failed to set domain configuration: Link 3 not known
116s Failed to set DNS configuration: Link 3 not known
116s + ip netns exec client ip addr
116s 1: lo:  mtu 65536 qdisc noop state DOWN group default qlen 1000
116s link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
116s 3: ptp-veth-client@if4:  mtu 1500 qdisc 
noqueue state UP group default qlen 1000
116s link/ether 26:d9:c1:82:7f:fa brd ff:ff:ff:ff:ff:ff link-netns server
116s inet 10.42.42.10/24 brd 10.42.42.255 scope global dynamic 
ptp-veth-client
116svalid_lft 600sec preferred_lft 600sec
116s inet6 fe80::24d9:c1ff:fe82:7ffa/64 scope link 
116svalid_lft forever preferred_lft forever
116s + grep 1.1.1.1 /etc/netns/client/resolv.conf
```

Full log: https://autopkgtest.ubuntu.com/results/autopkgtest-
noble/noble/amd64/i/isc-dhcp/20231127_150240_2bc90@/log.gz

** Affects: isc-dhcp (Ubuntu)
 Importance: High
 Status: New

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

Title:
  client-server autopkgtest fails: Failed to set LLMNR configuration:
  Link 3 not known

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  client-server autopkgtest fails. Relevant log:

  ```
  115s + ip netns exec client dhclient ptp-veth-client
  116s Setting LLMNR support level "yes" for "3", but the global support level 
is "no".
  116s Failed to set LLMNR configuration: Link 3 not known
  116s Failed to set MulticastDNS configuration: Link 3 not known
  116s Failed to set domain configuration: Link 3 not known
  116s Failed to set DNS configuration: Link 3 not known
  116s + ip netns exec client ip addr
  116s 1: lo:  mtu 65536 qdisc noop state DOWN group default qlen 1000
  116s link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  116s 3: ptp-veth-client@if4:  mtu 1500 qdisc 
noqueue state UP group default qlen 1000
  116s link/ether 26:d9:c1:82:7f:fa brd ff:ff:ff:ff:ff:ff link-netns server
  116s inet 10.42.42.10/24 brd 10.42.42.255 scope global dynamic 
ptp-veth-client
  116svalid_lft 600sec preferred_lft 600sec
  116s inet6 fe80::24d9:c1ff:fe82:7ffa/64 scope link 
  116svalid_lft forever preferred_lft forever
  116s + grep 1.1.1.1 /etc/netns/client/resolv.conf
  ```

  Full log: https://autopkgtest.ubuntu.com/results/autopkgtest-
  noble/noble/amd64/i/isc-dhcp/20231127_150240_2bc90@/log.gz

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


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


[Touch-packages] [Bug 2045027] [NEW] Regression in poppler bionic - 0.62.0-2ubuntu2.14+esm2

2023-11-28 Thread Nishit Majithia
Public bug reported:

The latest version of poppler-utils in bionic esm has a regression that
produces blank PDF files.

root@maximum-titmouse:~# apt-cache policy poppler-utils
poppler-utils:
Installed: 0.62.0-2ubuntu2.14
Candidate: 0.62.0-2ubuntu2.14
Version table:
*** 0.62.0-2ubuntu2.14 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages
100 /var/lib/dpkg/status
0.62.0-2ubuntu2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

I created a test file with the text "Test test 123", then ran `pdfunite
in.pdf out.pdf"

Opening this file in a PDF viewer shows the text "Test test 123".

Then I attached a Pro token and updated poppler-utils

root@maximum-titmouse:~# apt-cache policy poppler-utils
poppler-utils:
Installed: 0.62.0-2ubuntu2.14+esm2
Candidate: 0.62.0-2ubuntu2.14+esm2
Version table:
*** 0.62.0-2ubuntu2.14+esm2 510
510 https://esm.ubuntu.com/infra/ubuntu bionic-infra-security/main amd64 
Packages
100 /var/lib/dpkg/status
0.62.0-2ubuntu2.14 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages
0.62.0-2ubuntu2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

And again ran `pdfunite in.pdf out2.pdf"

This second file in a PDF viewer is completely blank. It's also missing
a lot of metadata and is significantly smaller in size when checked
using "strings"

root@maximum-titmouse:~# strings out.pdf | wc -l
186
root@maximum-titmouse:~# strings out2.pdf | wc -l
25

** Affects: poppler (Ubuntu)
 Importance: Undecided
 Assignee: Nishit Majithia (0xnishit)
 Status: New

** Affects: poppler (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Nishit Majithia (0xnishit)
 Status: New

** Also affects: poppler (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: poppler (Ubuntu Bionic)
 Assignee: (unassigned) => Nishit Majithia (0xnishit)

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

Title:
  Regression in poppler bionic - 0.62.0-2ubuntu2.14+esm2

Status in poppler package in Ubuntu:
  New
Status in poppler source package in Bionic:
  New

Bug description:
  The latest version of poppler-utils in bionic esm has a regression
  that produces blank PDF files.

  root@maximum-titmouse:~# apt-cache policy poppler-utils
  poppler-utils:
  Installed: 0.62.0-2ubuntu2.14
  Candidate: 0.62.0-2ubuntu2.14
  Version table:
  *** 0.62.0-2ubuntu2.14 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages
  100 /var/lib/dpkg/status
  0.62.0-2ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  I created a test file with the text "Test test 123", then ran
  `pdfunite in.pdf out.pdf"

  Opening this file in a PDF viewer shows the text "Test test 123".

  Then I attached a Pro token and updated poppler-utils

  root@maximum-titmouse:~# apt-cache policy poppler-utils
  poppler-utils:
  Installed: 0.62.0-2ubuntu2.14+esm2
  Candidate: 0.62.0-2ubuntu2.14+esm2
  Version table:
  *** 0.62.0-2ubuntu2.14+esm2 510
  510 https://esm.ubuntu.com/infra/ubuntu bionic-infra-security/main amd64 
Packages
  100 /var/lib/dpkg/status
  0.62.0-2ubuntu2.14 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages
  0.62.0-2ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  And again ran `pdfunite in.pdf out2.pdf"

  This second file in a PDF viewer is completely blank. It's also
  missing a lot of metadata and is significantly smaller in size when
  checked using "strings"

  root@maximum-titmouse:~# strings out.pdf | wc -l
  186
  root@maximum-titmouse:~# strings out2.pdf | wc -l
  25

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


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


[Touch-packages] [Bug 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade

2023-11-28 Thread Green Cattow
-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2036358

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

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

Bug description:
  [NOTE]

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

  $ systemctl disable --now systemd-networkd.service

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

  [Impact]

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

  [Test Plan]

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

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

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

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

  3. Re-generate and apply the netplan configuration.

  $ netplan generate
  $ netplan apply

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

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

  [Where problems could occur]

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

  [Original Description]

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

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

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


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


[Touch-packages] [Bug 2038998] Re: [amdgpu] Screen artifacts/UI oddities on Wayland

2023-11-28 Thread DooMMasteR
This issue never happened to me with my 3x FHD setup at work, but now I
am working from home with 2x 4K and 1x FHD and I am getting constant
corruptions.

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

Title:
  [amdgpu] Screen artifacts/UI oddities on Wayland

Status in GNOME Shell:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

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

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

  Wayland
  Kernel 6.5.0-9-generic

  * * * * *

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

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

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

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

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

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

  * * * * *

  Please see subsequent posts for video/images.

  Happy to provide any other information as needed. Thanks!

  * * * * *

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2038998/+subscriptions


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


[Touch-packages] [Bug 2044654] Re: No debugging symbols found in libgdk-3.so.0

2023-11-28 Thread Sebastien Bacher
Thank you for your bug report, do you have libgtk-3-0-dbgsym and
libwebkit2gtk-4.0-37-dbgsym installed?

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Incomplete

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => Low

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

Title:
  No debugging symbols found in libgdk-3.so.0

Status in gtk+3.0 package in Ubuntu:
  Incomplete

Bug description:
  Attach gdb to a running yelp process!

  (gdb) share libgdk
  Reading symbols from /lib/x86_64-linux-gnu/libgdk-3.so.0...
  (No debugging symbols found in /lib/x86_64-linux-gnu/libgdk-3.so.0)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgtk-3-0 3.24.33-1ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-1016.16~22.04.1-azure 6.2.16
  Uname: Linux 6.2.0-1016-azure x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 26 13:11:15 2023
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2044654/+subscriptions


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