date:20230526

[Touch-packages] [Bug 2020604] Re: After Mesa upgrades, Chrome won't show graphics

2023-05-26 Thread Sam

** Summary changed:

- After mesa upgrades, Chrome won't show graphics
+ After Mesa upgrades, Chrome won't show graphics

** Description changed:

- After today's Ubuntu 22.04 mesa upgrades many of our users reported
+ After today's Ubuntu 22.04 Mesa upgrades many of our users reported
  problems viewing graphics when using Google Chrome (Stable).
  
- The mesa upgrades we installed were:
+ The Mesa upgrades we installed were:
  
  [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  
  We documented the problem in AskUbuntu before we realized it was
- probably related to mesa, so wanted to link to that report here:
+ probably related to Mesa, so wanted to link to that report here:
  
  https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
  updates-chrome-wont-display-website-graphi
  
  There are several useful pointers and bypasses listed in that AskUbuntu
  link (one being to remove affected users' GPUCache directories, which
  does not destroy their profiles and seems to work in many but not all
  cases).
  
- Not sure if this is an issue with mesa or Chrome or specific machine
+ Not sure if this is an issue with Mesa or Chrome or specific machine
  graphics or an interaction between them.

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

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

Status in chromium-browser package in Ubuntu:
  Fix Committed
Status in mesa package in Ubuntu:
  Triaged

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

  The Mesa upgrades we installed were:

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

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

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

  There are several useful pointers and bypasses listed in that
  AskUbuntu link (one being to remove affected users' GPUCache
  directories, which does not destroy their profiles and seems to work
  in many but not all cases).

  Not sure if this is an issue with Mesa or Chrome or specific machine
  graphics or an interaction between them.

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


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

[Touch-packages] [Bug 2021362] Re: package libpam-modules 1.3.1-5ubuntu4.6 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2

2023-05-26 Thread Steve Langasek

The issue is precisely as described in the output of the maintainer
script:

you are using pam_tally or pam_tally2 in your configuration
The pam_tally and pam_tally2 modules have been removed from PAM. You are
using one of these modules in your PAM configuration in /etc/pam.d. You
must remove the uses of these modules before PAM can be upgraded;
including these modules in your PAM configuration after the upgrade will
stop users from being able to log into the system.

It is recommended to always use do-release-upgrade or update-manager to
upgrade between releases.  The release-upgrader presents this message
before you start the upgrade, rather than it happening unavoidably
partway through the upgrade leaving the package database in a state that
may be difficult to recover from.

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

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

Title:
  package libpam-modules 1.3.1-5ubuntu4.6 failed to install/upgrade: new
  libpam-modules:amd64 package pre-installation script subprocess
  returned error exit status 2

Status in pam package in Ubuntu:
  Invalid

Bug description:
  System upgrade using live upgrade.  Detailed bug report attached.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libpam-modules 1.3.1-5ubuntu4.6
  ProcVersionSignature: Ubuntu 5.4.0-1102.110+fips1-aws-fips 5.4.233
  Uname: Linux 5.4.0-1102-aws-fips x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri May 26 22:06:56 2023
  Ec2AMI: ami-08d4ac5b634553e16
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1c
  Ec2InstanceType: t3.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ErrorMessage: new libpam-modules:amd64 package pre-installation script 
subprocess returned error exit status 2
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: pam
  Title: package libpam-modules 1.3.1-5ubuntu4.6 failed to install/upgrade: new 
libpam-modules:amd64 package pre-installation script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to focal on 2023-05-27 (0 days ago)
  mtime.conffile..etc.security.limits.conf: 2023-05-26T21:06:16.816903

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2021362/+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 2021362] Re: package libpam-modules 1.3.1-5ubuntu4.6 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2

2023-05-26 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package libpam-modules 1.3.1-5ubuntu4.6 failed to install/upgrade: new
  libpam-modules:amd64 package pre-installation script subprocess
  returned error exit status 2

Status in pam package in Ubuntu:
  New

Bug description:
  System upgrade using live upgrade.  Detailed bug report attached.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libpam-modules 1.3.1-5ubuntu4.6
  ProcVersionSignature: Ubuntu 5.4.0-1102.110+fips1-aws-fips 5.4.233
  Uname: Linux 5.4.0-1102-aws-fips x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri May 26 22:06:56 2023
  Ec2AMI: ami-08d4ac5b634553e16
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1c
  Ec2InstanceType: t3.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ErrorMessage: new libpam-modules:amd64 package pre-installation script 
subprocess returned error exit status 2
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: pam
  Title: package libpam-modules 1.3.1-5ubuntu4.6 failed to install/upgrade: new 
libpam-modules:amd64 package pre-installation script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to focal on 2023-05-27 (0 days ago)
  mtime.conffile..etc.security.limits.conf: 2023-05-26T21:06:16.816903

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2021362/+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 2021362] [NEW] package libpam-modules 1.3.1-5ubuntu4.6 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2

2023-05-26 Thread Scott E. MacKenzie

Public bug reported:

System upgrade using live upgrade.  Detailed bug report attached.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libpam-modules 1.3.1-5ubuntu4.6
ProcVersionSignature: Ubuntu 5.4.0-1102.110+fips1-aws-fips 5.4.233
Uname: Linux 5.4.0-1102-aws-fips x86_64
ApportVersion: 2.20.11-0ubuntu27.26
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri May 26 22:06:56 2023
Ec2AMI: ami-08d4ac5b634553e16
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1c
Ec2InstanceType: t3.large
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
ErrorMessage: new libpam-modules:amd64 package pre-installation script 
subprocess returned error exit status 2
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.9
SourcePackage: pam
Title: package libpam-modules 1.3.1-5ubuntu4.6 failed to install/upgrade: new 
libpam-modules:amd64 package pre-installation script subprocess returned error 
exit status 2
UpgradeStatus: Upgraded to focal on 2023-05-27 (0 days ago)
mtime.conffile..etc.security.limits.conf: 2023-05-26T21:06:16.816903

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


** Tags: amd64 apport-package ec2-images focal third-party-packages

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

Title:
  package libpam-modules 1.3.1-5ubuntu4.6 failed to install/upgrade: new
  libpam-modules:amd64 package pre-installation script subprocess
  returned error exit status 2

Status in pam package in Ubuntu:
  New

Bug description:
  System upgrade using live upgrade.  Detailed bug report attached.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libpam-modules 1.3.1-5ubuntu4.6
  ProcVersionSignature: Ubuntu 5.4.0-1102.110+fips1-aws-fips 5.4.233
  Uname: Linux 5.4.0-1102-aws-fips x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri May 26 22:06:56 2023
  Ec2AMI: ami-08d4ac5b634553e16
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1c
  Ec2InstanceType: t3.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ErrorMessage: new libpam-modules:amd64 package pre-installation script 
subprocess returned error exit status 2
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: pam
  Title: package libpam-modules 1.3.1-5ubuntu4.6 failed to install/upgrade: new 
libpam-modules:amd64 package pre-installation script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to focal on 2023-05-27 (0 days ago)
  mtime.conffile..etc.security.limits.conf: 2023-05-26T21:06:16.816903

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2021362/+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 2020840] Re: package linux-image-5.15.0-72-generic 5.15.0-72.79 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2023-05-26 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  error update

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-72-generic 5.15.0-72.79
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  Date: Fri May 26 00:30:10 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  ProcFB: 0 hyperv_drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=LABEL=desktop-rootfs ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu7.1
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-5.15.0-72-generic 5.15.0-72.79 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/06/2022
  dmi.bios.release: 4.1
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.1
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.1
  dmi.chassis.asset.tag: 4521-1608-3807-0735-4847-9464-59
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.1
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.1:bd04/06/2022:br4.1:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.1:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.1:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.1:skuNone:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.1
  dmi.sys.vendor: Microsoft Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2020840/+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 2020840] Re: package linux-image-5.15.0-72-generic 5.15.0-72.79 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2023-05-26 Thread Seth Arnold

Hello, it looks like your /boot filesystem is probably full. Recovering
from this isn't great fun. There's some advice on
https://askubuntu.com/q/89710/33812 that might be helpful.

Processing triggers for linux-image-5.15.0-72-generic (5.15.0-72.79) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.15.0-72-generic
zstd: error 25 : Write error : No space left on device (cannot write compressed 
block) 

Thanks

** Information type changed from Private Security to Public

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

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  error update

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-72-generic 5.15.0-72.79
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  Date: Fri May 26 00:30:10 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  ProcFB: 0 hyperv_drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=LABEL=desktop-rootfs ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu7.1
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-5.15.0-72-generic 5.15.0-72.79 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/06/2022
  dmi.bios.release: 4.1
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.1
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.1
  dmi.chassis.asset.tag: 4521-1608-3807-0735-4847-9464-59
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.1
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.1:bd04/06/2022:br4.1:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.1:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.1:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.1:skuNone:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.1
  dmi.sys.vendor: Microsoft Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2020840/+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 2020838] Re: [regression][jammy] augenrules Error sending add rule data request (No such file or directory)

2023-05-26 Thread Seth Arnold

Hello, my guess is /home or /home/ubuntu may not exist when the audit
rules are loaded.

The file and directory watches work by setting up inotify watches on the
underlying objects, and if the file or directory doesn't exist, there's
nothing to watch. So, it errors.

You can add -i to the configuration file to have it continue onwards
despite the error:

   -i When given by itself, ignore errors when reading rules
  from a file. This causes auditctl to always return a
  success exit code. If passed as an argument to -s then
  it gives an interpretation of the numbers to human
  readable words if possible.


I'm not sure what to suggest for actually working around the problem, though. 
Reloading the rules some point after booting, once all the filesystems are 
mounted, would make sense, but I'm not sure how to ask systemd to do that.

Thanks

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

Title:
  [regression][jammy] augenrules Error sending add rule data request (No
  such file or directory)

Status in audit package in Ubuntu:
  New

Bug description:
  The rule '-a always,exit -F path=/home/ubuntu/test.sh -F perm=x -F
  auid>=1000 -F auid!=unset -k privileged' can not be loaded during
  system boot up.

  # lsb_release -rc
  Release:  22.04
  Codename: jammy

  # dpkg -l|grep audit
  ii  auditd  1:3.0.7-1build1 
amd64User space tools for security auditing
  ii  libaudit-common 1:3.0.7-1build1 
all  Dynamic library for security auditing - common files
  ii  libaudit1:amd64 1:3.0.7-1build1 
amd64Dynamic library for security auditing
  ii  libauparse0:amd64   1:3.0.7-1build1 
amd64Dynamic library for parsing security auditing

  # cat /etc/audit/rules.d/audit.rules|grep -v ^#|grep -v ^$
  -D
  -a always,exit -F path=/home/ubuntu/test.sh -F perm=x -F auid>=1000 -F 
auid!=unset -k privileged
  -a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=unset -k mounts
  -b 8192
  --backlog_wait_time 6
  -f 1

  # ls -l /home/ubuntu/test.sh 
  -rwxr-xr-x 1 root ubuntu 19 May 25 14:19 /home/ubuntu/test.sh

  # cat /home/ubuntu/test.sh
  #!/bin/bash
  echo 1

  
  # >/etc/audit/audit.rules

  reboot the system, no rule can be loaded

  # auditctl -l
  No rules

  syslog:

  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: Error sending add rule 
data request (No such file or directory)
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: There was an error in 
line 5 of /etc/audit/audit.rules
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: No rules
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: enabled 1
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: failure 1
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: pid 476
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: rate_limit 0
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_limit 8192
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: lost 0
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog 0
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_wait_time 15000
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_wait_time_actual 0
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: enabled 1
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: failure 1
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: pid 476
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: rate_limit 0
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_limit 8192
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: lost 0
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog 0
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_wait_time 15000
  May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_wait_time_actual 0

  # cat /etc/audit/audit.rules
  ## This file is automatically generated from /etc/audit/rules.d
  -D
  -b 8192
  -f 1
  -a always,exit -F path=/home/ubuntu/test.sh -F perm=x -F auid>=1000 -F 
auid!=unset -k privileged
  -a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=unset -k mounts
  --backlog_wait_time 6

  But I can manually load the rule file. Seems this issue only happen
  during system boot up.

  # auditctl -R /etc/audit/audit.rules
  No rules
  enabled 1
  failure 1
  pid 476
  rate_limit 0
  backlog_limit 8192
  lost 0
  backlog 4
  backlog_wait_time 15000
  backlog_wait_time_actual 0
  enabled 1
  failure 1
  pid 476
  rate_limit 0
  backlog_limit 8192
  lost 0
  backlog 4
  backlog_wait_time 15000
  backlog_wait_time_actual 0
  enabled 1
  failure 1
  pid 476
  rate_limit 0
  backlog_limit 8192
  lost 0
  backlog 14

Re: [Touch-packages] [Bug 2020604] Re: After mesa upgrades, Chrome won't show graphics

2023-05-26 Thread Chris Hall

Well, on one of my machines I installed Mesa from the kisak more stable 
ppa ("turtle"), which is more up to date than mesa from the jammy 
repository. I was able to re-enable hardware acceleration with no 
problems. So there is something in the whole collection of mesa packages 
that broke several chromium based browsers.

On 5/26/23 11:14 AM, Nathan Teodosio wrote:
>> Any idea if the mesa driver
>> problem will be addressed in the next update?
> Time will tell, if my reading of #12 is correct then this isn't really a
> problem with Mesa but with upstream.
>
>> An ironic thing about the about://gpu url is that unless you disable the
>> gpu, it's not possible to even read  the url. A real chicken and egg
>> problem.
> One could do a blind
>
> Ctrl+L
> about:gpu
> 
> 
>
> to get the report to clipboard, but you would never know that without
> seeing the page. (:
>
> That information isn't otherwise available even with
> --enable-logging=stderr --v=1...
>

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

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

Status in chromium-browser package in Ubuntu:
  Fix Committed
Status in mesa package in Ubuntu:
  Triaged

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

  The mesa upgrades we installed were:

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

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

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

  There are several useful pointers and bypasses listed in that
  AskUbuntu link (one being to remove affected users' GPUCache
  directories, which does not destroy their profiles and seems to work
  in many but not all cases).

  Not sure if this is an issue with mesa or Chrome or specific machine
  graphics or an interaction between them.

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


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

Re: [Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 66

2023-05-26 Thread Steve Langasek

On Fri, May 26, 2023 at 11:46:47PM -, Benjamin Drung wrote:
> There is a simple test case that does not need any external sources:

> Check the build log of the package. It should *not* contain
> "UserWarning: The version specified ($version) is an invalid version,
> this may not work as expected with newer versions of setuptools, pip,
> and PyPI. Please see PEP 440 for more details."

Ok but that's not actually a problem, it's just a warning.  What is a test
case that demonstrates the practical problem without, as I said, an
unnatural mix of apt and pip?

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  New
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  New
Status in python-debian source package in Kinetic:
  New
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'

  The official opinion of the setuptools maintainers seems to be that
  version strings of this form haven't *really* been allowed

[Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 66

2023-05-26 Thread Benjamin Drung

Here is the debdiff for python-debian 0.1.46ubuntu1 for kinetic.

** Patch added: "python-debian_0.1.46ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/distro-info/+bug/1991606/+attachment/5675921/+files/python-debian_0.1.46ubuntu1.debdiff

** Changed in: python-debian (Ubuntu Kinetic)
   Status: Invalid => New

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  New
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  New
Status in python-debian source package in Kinetic:
  New
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'

  The official opinion of the setuptools maintainers seems to be that
  version strings of this form haven't *really* been allowed since about
  2014, and distributions need to change their package version naming
  scheme for Python packages they install, so that the resulting version
  strings obey PEP440. See for example

[Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 66

2023-05-26 Thread Benjamin Drung

There is a simple test case that does not need any external sources:

Check the build log of the package. It should *not* contain
"UserWarning: The version specified ($version) is an invalid version,
this may not work as expected with newer versions of setuptools, pip,
and PyPI. Please see PEP 440 for more details."

I marked python-debian/kinetic as invalid, because version 0.1.46 in
kinetic is compliant with PEP440.

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  New
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  New
Status in python-debian source package in Kinetic:
  New
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'

  The official opinion of the setuptools maintainers seems to be that
  version strings of this form haven't *really* been allowed since about
  2014, and distributions need to change their package version naming
  scheme for Python packages they install, so that the

[Touch-packages] [Bug 2017434] Re: README.Debian.gz instructions for disabling socket activation inaccurate

2023-05-26 Thread Steve Langasek

** Changed in: openssh (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  README.Debian.gz instructions for disabling socket activation
  inaccurate

Status in openssh package in Ubuntu:
  Fix Committed

Bug description:
  The documentation about how to roll back socket activation of sshd
  became inaccurate after version 1:9.0p1-1ubuntu4 when we started using
  a drop-in file to finalize activation rather than this being
  configured statically in ssh.service.  The drop-in file
  /etc/systemd/system/ssh.service.d/00-socket.conf must also be removed
  first.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2017434/+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 1991606] Re: Invalid PEP440 package version breaking setuptools >= 66

2023-05-26 Thread Steve Langasek

The security update for distro-info, 0.18ubuntu0.18.04.1, was published
in 2019.  I don't think it's correct to say that this introduced the
regression; the regression was introduced when upstream setuptools
changed its behavior.

This does not preclude us moving forward with an SRU, I just want the
record to be precise.

I do think the test case given in the bug report seems contrived.  A
number of packages are necessarily installed using apt to set up the
environment; but then setuptools is specifically pulled from pip instead
of from the Ubuntu archive?  Why?  Is there a test case that can be used
to demonstrate the problem without what seems an unnatural mix of apt
and pip?

My counterargument against this affecting CI pipelines is that,
precisely because these packages are in all of our images, the SRU will
also be seen on all Ubuntu systems - whether or not they are trying to
use latest upstream setuptools - increasing the risk of a failure on
upgrade; not because I think there's anything buggy about the proposed
change, but because sometimes upgrade failures happen anyway, and while
this normally doesn't weight very much, it's more of a consideration
when there's a proposed update on the margin of the SRU policy to a core
package.

I see that you have appropriately scoped the tasks on the various
packages to only include those in releases where the version number
curretnly violates the policy.  Is the python-debian/kinetic task marked
invalid because the version number there currently complies, or because
when building with a source package version that doesn't comply the
package will still be PEP440-compliant?  If it's only the former, then
it would be best if we did do an SRU of it but kept it in -proposed with
block-proposed.

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  New
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  New
Status in python-debian source package in Kinetic:
  Invalid
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File

[Touch-packages] [Bug 2020470] Re: Please merge 1.9.13p3-1 into mantic

2023-05-26 Thread Steve Langasek

** Changed in: sudo (Ubuntu)
   Status: New => Fix Committed

** Changed in: sudo (Ubuntu)
 Assignee: (unassigned) => William Wilson (jawn-smith)

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

Title:
  Please merge 1.9.13p3-1 into mantic

Status in sudo package in Ubuntu:
  Fix Committed

Bug description:
  tracking bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2020470/+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 2020814] Re: xmllint does not recognize emdash ( )

2023-05-26 Thread Thorsten Glaser

Hmm. I normally use libxml2 via xmlstarlet which has a somewhat nicer UX
than xmllint.

My guess is that you didn’t give a DTD, so it could only check that all
present entities are syntactically valid, but not expand them.

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

Title:
xmllint does not recognize emdash ()

Status in libxml2 package in Ubuntu:
Invalid

Bug description:
I'm using Ubuntu 20.04.2 LTS, x85_64, fully patched. I'm using DocBook to
build a PDF. One of the steps I use in my build script is to validate and
format the XML using xmllint from libxml2-utils
2.9.13+dfsg-1ubuntu0.3:

echo "Validating book..."
if ! xmllint --xinclude --noout --postvalid book.xml
then
echo "Validation failed. Exiting."
exit 1
fi
echo "Complete."

echo "Formatting source code..."
for file in *.xml
do
if xmllint --format "${file}" --output "${file}.format"
then
mv "${file}.format" "${file}"
fi
done
echo "Complete."

When I added an emdash () the book failed to format:

Validating book...
Complete.
Formatting source code...
ch02.xml:58: parser error : Entity 'mdash' not defined
injections are remediated using several methods. And two output devices

^
ch02.xml:58: parser error : Entity 'mdash' not defined
methods. And two output devices the printer and plaintext email

^
Complete.

The text is:

... And two output devices the printer and plaintext
email do not require...

It seems like emdash should be recognized.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04.2 LTS
Release:22.04
Codename: jammy

$ xmllint --version
xmllint: using libxml version 20913
compiled with: Threads Tree Output Push Reader Patterns Writer SAXv1 FTP
HTTP DTDValid HTML Legacy C14N Catalog XPath XPointer XInclude Iconv ICU
ISO8859X Unicode Regexps Automata Schemas Schematron Modules Debug Zlib Lzma

$ command -v xmllint
/usr/bin/xmllint

$ dpkg -S /usr/bin/xmllint
libxml2-utils: /usr/bin/xmllint

$ apt-cache show libxml2-utils
Package: libxml2-utils
Architecture: amd64
Version: 2.9.13+dfsg-1ubuntu0.3
Multi-Arch: foreign
Priority: optional
Section: text
Source: libxml2
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Debian XML/SGML Group

Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 202
Depends: libc6 (>= 2.34), libxml2 (>= 2.9.0)
Filename:
pool/main/libx/libxml2/libxml2-utils_2.9.13+dfsg-1ubuntu0.3_amd64.deb
Size: 40192
MD5sum: 3ca7de07562010fcaabf255ea8fea9c4
SHA1: 128a9cfaff49e85f2ab08578f389eecb21f17766
SHA256: c279c07caf909545e2cedb7845b5ac652e0a70f9784e5faf799a1a01441b4649
SHA512:
51600d7206c9a5568fdaeee9adddbc48962fc094cc479f4bd42c0714b3725cd3200937f8c876a897db08fc50d891005d7dbabfb6ae12ad27ad6ed416f8b6a03d
Homepage: http://xmlsoft.org
...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/2020814/+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 2020814] Re: xmllint does not recognize emdash ( )

2023-05-26 Thread Jeffrey Walton

Thorsten, a quick question...

The first part of my book build script has this:

echo "Validating book..."
if ! xmllint --xinclude --noout --postvalid book.xml
then
echo "Validation failed. Exiting."
exit 1
fi
echo "Complete."

Why did the book pass validation when using emdash entity reference? It
seems like that should have failed.

An example of the build script can be found at
https://github.com/noloader/POWER8-crypto/tree/master/docbook. make-
book.sh builds the book, and it includes the snippet.

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

Title:
xmllint does not recognize emdash ()

Status in libxml2 package in Ubuntu:
Invalid

echo "Validating book..."
if ! xmllint --xinclude --noout --postvalid book.xml
then
echo "Validation failed. Exiting."
exit 1
fi
echo "Complete."

echo "Formatting source code..."
for file in *.xml
do
if xmllint --format "${file}" --output "${file}.format"
then
mv "${file}.format" "${file}"
fi
done
echo "Complete."

When I added an emdash () the book failed to format:

Validating book...
Complete.
Formatting source code...
ch02.xml:58: parser error : Entity 'mdash' not defined
injections are remediated using several methods. And two output devices

^
ch02.xml:58: parser error : Entity 'mdash' not defined
methods. And two output devices the printer and plaintext email

^
Complete.

The text is:

... And two output devices the printer and plaintext
email do not require...

It seems like emdash should be recognized.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04.2 LTS
Release:22.04
Codename: jammy

$ command -v xmllint
/usr/bin/xmllint

$ dpkg -S /usr/bin/xmllint
libxml2-utils: /usr/bin/xmllint

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/2020814/+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 2020814] Re: xmllint does not recognize emdash ( )

2023-05-26 Thread Thorsten Glaser

Yeah well, those portability problems were back in the 1990s when people
used latin1 or whatever codepages.

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

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

Title:
  xmllint does not recognize emdash ()

Status in libxml2 package in Ubuntu:
  Invalid

Bug description:
  I'm using Ubuntu 20.04.2 LTS, x85_64, fully patched. I'm using DocBook to 
build a PDF. One of the steps I use in my build script is to validate and 
format the XML using xmllint from libxml2-utils
  2.9.13+dfsg-1ubuntu0.3:

  echo "Validating book..."
  if ! xmllint --xinclude --noout --postvalid book.xml
  then
  echo "Validation failed. Exiting."
  exit 1
  fi
  echo "Complete."

  echo "Formatting source code..."
  for file in *.xml
  do
  if xmllint --format "${file}" --output "${file}.format"
  then
  mv "${file}.format" "${file}"
  fi
  done
  echo "Complete."

  When I added an emdash () the book failed to format:

  Validating book...
  Complete.
  Formatting source code...
  ch02.xml:58: parser error : Entity 'mdash' not defined
   injections are remediated using several methods. And two output devices 


 ^
  ch02.xml:58: parser error : Entity 'mdash' not defined
   methods. And two output devices  the printer and plaintext email 


 ^
  Complete.

  The text is:

  ... And two output devices  the printer and plaintext
  email  do not require...

  It seems like emdash should be recognized.

  -

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 22.04.2 LTS
  Release:22.04
  Codename:   jammy

  -

  $ xmllint --version
  xmllint: using libxml version 20913
 compiled with: Threads Tree Output Push Reader Patterns Writer SAXv1 FTP 
HTTP DTDValid HTML Legacy C14N Catalog XPath XPointer XInclude Iconv ICU 
ISO8859X Unicode Regexps Automata Schemas Schematron Modules Debug Zlib Lzma

  $ command -v xmllint
  /usr/bin/xmllint

  $ dpkg -S /usr/bin/xmllint
  libxml2-utils: /usr/bin/xmllint

  $ apt-cache show libxml2-utils
  Package: libxml2-utils
  Architecture: amd64
  Version: 2.9.13+dfsg-1ubuntu0.3
  Multi-Arch: foreign
  Priority: optional
  Section: text
  Source: libxml2
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian XML/SGML Group 

  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 202
  Depends: libc6 (>= 2.34), libxml2 (>= 2.9.0)
  Filename: 
pool/main/libx/libxml2/libxml2-utils_2.9.13+dfsg-1ubuntu0.3_amd64.deb
  Size: 40192
  MD5sum: 3ca7de07562010fcaabf255ea8fea9c4
  SHA1: 128a9cfaff49e85f2ab08578f389eecb21f17766
  SHA256: c279c07caf909545e2cedb7845b5ac652e0a70f9784e5faf799a1a01441b4649
  SHA512: 
51600d7206c9a5568fdaeee9adddbc48962fc094cc479f4bd42c0714b3725cd3200937f8c876a897db08fc50d891005d7dbabfb6ae12ad27ad6ed416f8b6a03d
  Homepage: http://xmlsoft.org
  ...

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


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

[Touch-packages] [Bug 2020604] Re: After mesa upgrades, Chrome won't show graphics

2023-05-26 Thread Mario Limonciello

It seems a way that this may be avoided is for GL_RENDERER string to
always be updated when mesa updates.

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

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

Status in chromium-browser package in Ubuntu:
  Fix Committed
Status in mesa package in Ubuntu:
  Triaged

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

  The mesa upgrades we installed were:

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

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

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

  There are several useful pointers and bypasses listed in that
  AskUbuntu link (one being to remove affected users' GPUCache
  directories, which does not destroy their profiles and seems to work
  in many but not all cases).

  Not sure if this is an issue with mesa or Chrome or specific machine
  graphics or an interaction between them.

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


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

[Touch-packages] [Bug 2018538] Re: All PDFs when printed come out mirror image

2023-05-26 Thread Ondrej Maly

** Attachment added: "QL-800.error_log"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2018538/+attachment/5675906/+files/QL-800.error_log

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

Title:
  All PDFs when printed come out mirror image

Status in cups package in Ubuntu:
  Incomplete

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

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

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

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

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

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


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

[Touch-packages] [Bug 2018538] Re: All PDFs when printed come out mirror image

2023-05-26 Thread Ondrej Maly

** Attachment added: "QL-800.ppd"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2018538/+attachment/5675905/+files/QL-800.ppd

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

Title:
  All PDFs when printed come out mirror image

Status in cups package in Ubuntu:
  Incomplete

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

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

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

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

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

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


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

Re: [Touch-packages] [Bug 2020812] Re: Unable to change color highlight in apt output

2023-05-26 Thread StevenT

On 5/26/23 12:27 AM, Julian Andres Klode wrote:
> I think you need to url encode the sequence, but not sure. I don't think
> there's anything we can do here about handling backslashes, the problem
> is backspaces do happen in actual config items and we can't introduce a
> behavior change for them as that would cause regressions.
>
> You should be free to also printf the actual special character into the
> config option or the command line argument.
>

Thanks, the printf worked.

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

Title:
  Unable to change color highlight in apt output

Status in apt package in Ubuntu:
  New

Bug description:
  Ubuntu Release:
  lsb_release -rd
  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04

  Source package and version:
  dpkg-query -W apt
  apt   2.4.9

  Binary apt command has support for color output on some commands such
  as "apt list " Where enabled the default color output is
  unbolded green color. This is due to the apt configuration item,
  APT::Color::Highlight being set to the default ANSI color code of
  "\x1B[32m", Setting it to another ANSI code should alter the apt
  output.

  Expectation:Setting the Highlight configuration option to another ANSI
  code should alter the apt output to the specified color code.

  $ apt list apt -o apt::color::highlight="\x1b[31m" should set the
  highlighted package name to an unbold red color.

  What happens:
  $ apt list apt -o apt::color::highlight="\x1b[31m"
  Listing... Done
  \x1b[31mapt/jammy-updates,now 2.4.9 amd64 [installed,automatic]
  \x1b[31mapt/jammy-updates 2.4.9 i386

  Prepends literal string of \x1b[31m instead of producing colored
  output.

  "\033[31m" doesn't work either.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2020812/+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 2020460] Re: Please merge 1:2.66-4 into mantic

2023-05-26 Thread Steve Langasek

Uploaded, thanks!

** Changed in: libcap2 (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Please merge 1:2.66-4 into mantic

Status in libcap2 package in Ubuntu:
  Fix Committed

Bug description:
  tracking bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2020460/+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 2020913] [NEW] /etc/profile.d/debuginfd.{sh, csh} are created with 600 permissions

2023-05-26 Thread Russell Greene

Public bug reported:

In a fresh container, installing libdebuginfod-common gives a
/etc/profile.d that looks like this:

```
root@32f34f7e271e:/etc/profile.d# ls -lah
total 24K
drwxr-xr-x 1 root root 4.0K May 26 17:23 .
drwxr-xr-x 1 root root 4.0K May 26 17:23 ..
-rw-r--r-- 1 root root   96 Oct 15  2021 01-locale-fix.sh
-rw--- 1 root root  677 May 26 17:23 debuginfod.csh
-rw--- 1 root root  692 May 26 17:23 debuginfod.sh

```

when I login as a nonprivledged user, DEBUGINFOD_URLS is not set because
the permissions are incorrect on the profile files.

```
# dpkg -l  | grep libdebug
ii  libdebuginfod-common0.186-1build1   all 
 configuration to enable the Debian debug info server
```

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

** Description changed:

  In a fresh container, installing libdebuginfod-common gives a
  /etc/profile.d that looks like this:
  
  ```
  root@32f34f7e271e:/etc/profile.d# ls -lah
  total 24K
  drwxr-xr-x 1 root root 4.0K May 26 17:23 .
  drwxr-xr-x 1 root root 4.0K May 26 17:23 ..
  -rw-r--r-- 1 root root   96 Oct 15  2021 01-locale-fix.sh
  -rw--- 1 root root  677 May 26 17:23 debuginfod.csh
  -rw--- 1 root root  692 May 26 17:23 debuginfod.sh
  
  ```
  
+ when I login as a nonprivledged user, DEBUGINFOD_URLS is not set because
+ the permissions are incorrect on the profile files.
  
- when I login as a nonprivledged user, DEBUGINFOD_URLS is not set because the 
permissions are incorrect on the profile files.
+ ```
+ # dpkg -l  | grep libdebug
+ ii  libdebuginfod-common0.186-1build1   all   
   configuration to enable the Debian debug info server
+ ```

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

Title:
  /etc/profile.d/debuginfd.{sh,csh} are created with 600 permissions

Status in elfutils package in Ubuntu:
  New

Bug description:
  In a fresh container, installing libdebuginfod-common gives a
  /etc/profile.d that looks like this:

  ```
  root@32f34f7e271e:/etc/profile.d# ls -lah
  total 24K
  drwxr-xr-x 1 root root 4.0K May 26 17:23 .
  drwxr-xr-x 1 root root 4.0K May 26 17:23 ..
  -rw-r--r-- 1 root root   96 Oct 15  2021 01-locale-fix.sh
  -rw--- 1 root root  677 May 26 17:23 debuginfod.csh
  -rw--- 1 root root  692 May 26 17:23 debuginfod.sh

  ```

  when I login as a nonprivledged user, DEBUGINFOD_URLS is not set
  because the permissions are incorrect on the profile files.

  ```
  # dpkg -l  | grep libdebug
  ii  libdebuginfod-common0.186-1build1   all   
   configuration to enable the Debian debug info server
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/2020913/+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 1991606] Re: Invalid PEP440 package version breaking setuptools >= 66

2023-05-26 Thread Benjamin Drung

Taking an Ubuntu docker image (or similar) and installing the latest
pip/setuptools is a very common use case for CI pipelines and building
containers. Since distro-info and python-debian are in most images, all
those use cases are affected. The bug is that these Ubuntu packages
violate the Python versioning. So we should fix the packages that are
broken instead to work around them in other places.

So I suggest that we backport fixing the broken version numbers for
distro-info and python-debian (but do not SRU the other affected
packages). The security update for distro-info in bionic introduced the
regression (0.18 was a valid version, but 0.18ubuntu0.18.04.1 is not).

** Changed in: python-debian (Ubuntu)
 Assignee: (unassigned) => Benjamin Drung (bdrung)

** Changed in: distro-info (Ubuntu)
 Assignee: (unassigned) => Benjamin Drung (bdrung)

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  New
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  New
Status in python-debian source package in Kinetic:
  Invalid
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",

[Touch-packages] [Bug 2020604] Re: After mesa upgrades, Chrome won't show graphics

2023-05-26 Thread Dave Chiluk

As I have multiple profiles, I chose to simply delete all Cache
directories


$ find ~/.config/google-chrome \( -name "*Cache" \) | xargs -d '\n' -L 1 rm -rf

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

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

Status in chromium-browser package in Ubuntu:
  Fix Committed
Status in mesa package in Ubuntu:
  Triaged

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

  The mesa upgrades we installed were:

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

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

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

  There are several useful pointers and bypasses listed in that
  AskUbuntu link (one being to remove affected users' GPUCache
  directories, which does not destroy their profiles and seems to work
  in many but not all cases).

  Not sure if this is an issue with mesa or Chrome or specific machine
  graphics or an interaction between them.

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


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

[Touch-packages] [Bug 2020604] Re: After mesa upgrades, Chrome won't show graphics

2023-05-26 Thread Nathan Teodosio

The workaround is available in candidate channel (currently only ready
for amd64).

  snap refresh --candidate chromium

If someone could please verify the workaround, I can bump to stable.

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

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

Status in chromium-browser package in Ubuntu:
  Fix Committed
Status in mesa package in Ubuntu:
  Triaged

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

  The mesa upgrades we installed were:

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

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

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

  There are several useful pointers and bypasses listed in that
  AskUbuntu link (one being to remove affected users' GPUCache
  directories, which does not destroy their profiles and seems to work
  in many but not all cases).

  Not sure if this is an issue with mesa or Chrome or specific machine
  graphics or an interaction between them.

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


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

[Touch-packages] [Bug 2020474] Re: openssh-server-1:9.2p1-2ubuntu1 cannot be installed from active ssh session

2023-05-26 Thread Jeremy Bícha

** Changed in: openssh (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  openssh-server-1:9.2p1-2ubuntu1 cannot be installed from active ssh
  session

Status in openssh package in Ubuntu:
  Fix Committed

Bug description:
  Installation seems to fail on restarting ssh.socket via systemctl

  Setting up openssh-server (1:9.2p1-2ubuntu1) ...
  rescue-ssh.target is a disabled or a static unit not running, not starting it.
  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
  dpkg: error processing package openssh-server (--configure):
   installed openssh-server package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   openssh-server
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  $ systemctl status ssh.socket
  × ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
   Active: failed (Result: resources) since Tue 2023-05-23 15:01:41 CEST; 
48s ago
 Duration: 3h 6min 36.071s
 Triggers: ● ssh.service
   Listen: [::]:22 (Stream)
  CPU: 2ms

  May 23 11:55:05 venus2 systemd[1]: Listening on ssh.socket - OpenBSD Secure 
Shell server socket.
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Deactivated successfully.
  May 23 15:01:41 venus2 systemd[1]: Closed ssh.socket - OpenBSD Secure Shell 
server socket.
  May 23 15:01:41 venus2 systemd[1]: Stopping ssh.socket - OpenBSD Secure Shell 
server socket...
  May 23 15:01:41 venus2 systemd[2631]: ssh.socket: Failed to create listening 
socket ([::]:22): Address already in use
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to receive listening 
socket ([::]:22): Input/output error
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to listen on sockets: 
Input/output error
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed with result 'resources'.
  May 23 15:01:41 venus2 systemd[1]: Failed to listen on ssh.socket - OpenBSD 
Secure Shell server socket.

  At this point, sshd is no longer listening for new connections.  A
  manual systemctl restart of ssh.socket fails with the same error.  I
  am ssh-ed into this box, so I *think* the failure is because my
  session is already sitting on port 22, maybe?  The only way I can be
  sure I will be able to ssh to this box again is to reboot it (so that
  ssh.socket can start cleanly).

  $ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu Mantic Minotaur (development branch)
  Release:  23.10

  $ apt policy openssh-server
  openssh-server:
Installed: 1:9.2p1-2ubuntu1
Candidate: 1:9.2p1-2ubuntu1
Version table:
   *** 1:9.2p1-2ubuntu1 500
  500 http://ch.ports.ubuntu.com/ubuntu-ports mantic-proposed/main 
riscv64 Packages
  100 /var/lib/dpkg/status
   1:9.0p1-1ubuntu8.1 500
  500 http://ch.ports.ubuntu.com/ubuntu-ports mantic/main riscv64 
Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: openssh-server 1:9.2p1-2ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-19.19.1-generic 6.2.6
  Uname: Linux 6.2.0-19-generic riscv64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230413.1
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue May 23 14:58:35 2023
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: 
/etc/ssh/sshd_config.d/50-cloud-init.conf: Permission denied
  SourcePackage: openssh
  UpgradeStatus: Upgraded to mantic on 2023-05-12 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2020474/+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 1991606] Re: Invalid PEP440 package version breaking setuptools >= 66

2023-05-26 Thread Philippe Warren

Here is another example of a tool that fails to work as expected because
it expects strict compliance to PEP 440: https://github.com/tox-
dev/pipdeptree/issues/235 .

This affects older Ubuntu releases like Bionic and Focal too.
I hope adding another example like this helps to justify fixing this on older 
versions of Ubuntu as well, even if setuptools is not affected there. 

** Bug watch added: github.com/tox-dev/pipdeptree/issues #235
   https://github.com/tox-dev/pipdeptree/issues/235

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  New
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  New
Status in python-debian source package in Kinetic:
  Invalid
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'

  The official opinion of the setuptools maintainers seems to be that
  version strings of this form haven't *really* been allowed since about
  2014, and distributions need to change their package

[Touch-packages] [Bug 2020749] Re: Please merge console-setup 1.221 into mantic

2023-05-26 Thread Shengjing Zhu

PPA for review https://launchpad.net/~zhsj/+archive/ubuntu/console-
setup-merge-lp2020749

** Changed in: console-setup (Ubuntu)
   Status: New => In Progress

** Merge proposal linked:
   
https://code.launchpad.net/~zhsj/ubuntu/+source/console-setup/+git/console-setup/+merge/443641

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

Title:
  Please merge console-setup 1.221 into mantic

Status in console-setup package in Ubuntu:
  In Progress

Bug description:
  console-setup (1.221) unstable; urgency=medium

* Team upload.

[ Updated translations ]
* Belarusian (be.po) by Viktar Siarheichyk
* Bengali (bn.po) by Indrani Roy
* Norwegian Nynorsk (nn.po) by Yngve Spjeld-Landro

  console-setup (1.220) unstable; urgency=medium

* Team upload.

[ Updated translations ]
* Norwegian Bokmal (nb.po) by Kjetil Sørlund
* Norwegian Nynorsk (nn.po) by Kjetil Sørlund

  console-setup (1.219) unstable; urgency=medium

[ Updated translations ]
* Georgian (ka.po) by Temuri Doghonadze

  console-setup (1.218) unstable; urgency=medium

* Team upload.

[ Updated translations ]
* German (de.po) by Holger Wansing
* Vietnamese (vi.po) by tictactoe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/2020749/+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 2020789] Re: pcscd should depend on vsmartcard-vpcd

2023-05-26 Thread Nathan Teodosio

Absolutely, now I remember I was testing vsmartcard... Trying to
understand the whole smart card stack I lost track of it, sorry. (:

** Changed in: pcsc-lite (Ubuntu)
   Status: New => Invalid

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

Title:
  pcscd should depend on vsmartcard-vpcd

Status in pcsc-lite package in Ubuntu:
  Invalid

Bug description:
  If I install pcscd but not vsmartcard-vpcd, the service fails to
  start:

  --->
  × pcscd.service - PC/SC Smart Card Daemon
   Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; preset: 
enabled)
   Active: failed (Result: exit-code) since Thu 2023-05-25 16:11:31 CEST; 
1min 52s ago
 Duration: 59ms
  TriggeredBy: ● pcscd.socket
 Docs: man:pcscd(8)
  Process: 410224 ExecStart=/usr/sbin/pcscd --foreground --auto-exit 
$PCSCD_ARGS (code=exited, status=1/FAILURE)
 Main PID: 410224 (code=exited, status=1/FAILURE)
  CPU: 8ms

  mai 25 16:11:30 canonical systemd[1]: Started pcscd.service - PC/SC Smart 
Card Daemon.
  mai 25 16:11:31 canonical pcscd[410224]:  
configfile.l:163:evaluatetoken() Error with library 
/usr/lib/pcsc/drivers/serial/libifdvpcd.so: No such file or directory
  mai 25 16:11:31 canonical pcscd[410224]: 00017989 
pcscdaemon.c:835:clean_temp_files() Cannot remove /run/pcscd/pcscd.pid: No such 
file or directory
  mai 25 16:11:31 canonical systemd[1]: pcscd.service: Main process exited, 
code=exited, status=1/FAILURE
  mai 25 16:11:31 canonical systemd[1]: pcscd.service: Failed with result 
'exit-code'.
  <---

  Should pcscd depend on it?

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


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

[Touch-packages] [Bug 2020604] Re: After mesa upgrades, Chrome won't show graphics

2023-05-26 Thread Timo Aaltonen

seems like this is a generic issue with chromium not being able to
invalidate the gpucache when the GL_RENDERER string changes, which is
every time Mesa is updated

** Package changed: mesa (Ubuntu) => chromium-browser (Ubuntu)

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

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

Status in chromium-browser package in Ubuntu:
  Confirmed

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

  The mesa upgrades we installed were:

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

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

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

  There are several useful pointers and bypasses listed in that
  AskUbuntu link (one being to remove affected users' GPUCache
  directories, which does not destroy their profiles and seems to work
  in many but not all cases).

  Not sure if this is an issue with mesa or Chrome or specific machine
  graphics or an interaction between them.

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


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

[Touch-packages] [Bug 2019940] Re: Directly manipulating NetworkManager keyfiles

2023-05-26 Thread Alexandre Detiste

Please provide output of "cruft-ng" on an updated system. I'm not
running Ubuntu.

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

Title:
  Directly manipulating NetworkManager keyfiles

Status in augeas package in Ubuntu:
  New
Status in calamares package in Ubuntu:
  New
Status in cloud-init package in Ubuntu:
  Invalid
Status in cruft package in Ubuntu:
  Won't Fix
Status in cruft-ng package in Ubuntu:
  New
Status in dracut package in Ubuntu:
  New
Status in forensic-artifacts package in Ubuntu:
  New
Status in guestfs-tools package in Ubuntu:
  New
Status in guix package in Ubuntu:
  New
Status in ltsp package in Ubuntu:
  Invalid
Status in netcfg package in Ubuntu:
  Won't Fix
Status in netplan.io package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  New
Status in refpolicy package in Ubuntu:
  New
Status in sosreport package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  New
Status in uhd package in Ubuntu:
  New
Status in vagrant package in Ubuntu:
  New

Bug description:
  The affected packages can manipulate NetworkManager keyfiles directly
  on disk, which might not be appropriate anymore on Ubuntu, since the
  Netplan integration was enabled in NetworkManager (starting with
  Mantic), migrating any keyfile configuration from
  /etc/NetworkManager/system-connections/*[.nmconnection] to
  /etc/netplan/90-NM-*.yaml

  See Netplan's documentation for how connections are handled:
  https://netplan.readthedocs.io/en/latest/netplan-everywhere/

  PS: Packages were queried using:
  
https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1

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


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

[Touch-packages] [Bug 2020604] Re: After Mesa upgrades, Chrome won't show graphics

[Touch-packages] [Bug 2021362] Re: package libpam-modules 1.3.1-5ubuntu4.6 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2

[Touch-packages] [Bug 2021362] Re: package libpam-modules 1.3.1-5ubuntu4.6 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2

[Touch-packages] [Bug 2021362] [NEW] package libpam-modules 1.3.1-5ubuntu4.6 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2

[Touch-packages] [Bug 2020840] Re: package linux-image-5.15.0-72-generic 5.15.0-72.79 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Touch-packages] [Bug 2020840] Re: package linux-image-5.15.0-72-generic 5.15.0-72.79 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Touch-packages] [Bug 2020838] Re: [regression][jammy] augenrules Error sending add rule data request (No such file or directory)

Re: [Touch-packages] [Bug 2020604] Re: After mesa upgrades, Chrome won't show graphics

Re: [Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 66

[Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 66

[Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 66

[Touch-packages] [Bug 2017434] Re: README.Debian.gz instructions for disabling socket activation inaccurate

[Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 66

[Touch-packages] [Bug 2020470] Re: Please merge 1.9.13p3-1 into mantic

[Touch-packages] [Bug 2020814] Re: xmllint does not recognize emdash ( )

[Touch-packages] [Bug 2020814] Re: xmllint does not recognize emdash ( )

[Touch-packages] [Bug 2020814] Re: xmllint does not recognize emdash ( )

[Touch-packages] [Bug 2020604] Re: After mesa upgrades, Chrome won't show graphics

[Touch-packages] [Bug 2018538] Re: All PDFs when printed come out mirror image

[Touch-packages] [Bug 2018538] Re: All PDFs when printed come out mirror image

Re: [Touch-packages] [Bug 2020812] Re: Unable to change color highlight in apt output

[Touch-packages] [Bug 2020460] Re: Please merge 1:2.66-4 into mantic

[Touch-packages] [Bug 2020913] [NEW] /etc/profile.d/debuginfd.{sh, csh} are created with 600 permissions

[Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 66

[Touch-packages] [Bug 2020604] Re: After mesa upgrades, Chrome won't show graphics

[Touch-packages] [Bug 2020604] Re: After mesa upgrades, Chrome won't show graphics

[Touch-packages] [Bug 2020474] Re: openssh-server-1:9.2p1-2ubuntu1 cannot be installed from active ssh session

[Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 66

[Touch-packages] [Bug 2020749] Re: Please merge console-setup 1.221 into mantic

[Touch-packages] [Bug 2020789] Re: pcscd should depend on vsmartcard-vpcd

[Touch-packages] [Bug 2020604] Re: After mesa upgrades, Chrome won't show graphics

[Touch-packages] [Bug 2019940] Re: Directly manipulating NetworkManager keyfiles

32 matches

Site Navigation

Mail list logo

Footer information