date:20230713

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

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

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

Title:
  package libssl1.0.0:i386 1.0.1f-1ubuntu2.15 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in openssl package in Ubuntu:
  Expired

Bug description:
  liugt

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libssl1.0.0:i386 1.0.1f-1ubuntu2.15
  ProcVersionSignature: Ubuntu 3.13.0-55.94-generic 3.13.11-ckt20
  Uname: Linux 3.13.0-55-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  Date: Mon Jul 13 11:53:17 2015
  DuplicateSignature: package:libssl1.0.0:i386:1.0.1f-1ubuntu2.15:package is in 
a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2013-03-26 (839 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  PackageArchitecture: i386
  SourcePackage: openssl
  Title: package libssl1.0.0:i386 1.0.1f-1ubuntu2.15 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: Upgraded to trusty on 2014-04-23 (446 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1474103/+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 1706601] Re: Atstart up the bud appears But te program continous package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: lib/x86_64-linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-g

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

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

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

Title:
  Atstart up the bud appears But te program continous package
  libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: lib/x86_64-linux-
  gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/lib4758cca.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgost.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libnuron.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libubsec.so
  usr/share/doc/libssl1.0.0/changelog.Debian.gz] failed to
  install/upgrade: pakket libssl1.0.0:amd64 is niet gereed voor
  configuratie  kan het niet configureren (huidige status 'half-
  installed')

Status in openssl package in Ubuntu:
  Expired

Bug description:
  At start up the bug appears. However the program continous

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: 
lib/x86_64-linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/lib4758cca.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgost.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libnuron.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libubsec.so 
usr/share/doc/libssl1.0.0/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-27-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Jul 26 14:51:13 2017
  ErrorMessage: pakket libssl1.0.0:amd64 is niet gereed voor configuratie  kan 
het niet configureren (huidige status 'half-installed')
  InstallationDate: Installed on 2017-06-06 (49 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1706601/+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 1832834] Re: Irregular system freezes after updating to 1.1.1b-1ubuntu2.2

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

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

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

Title:
  Irregular system freezes after updating to 1.1.1b-1ubuntu2.2

Status in openssl package in Ubuntu:
  Expired

Bug description:
  Yesterday, I've updated openssl on my Raspberry Pi 3B+ running disco
  arm64 from 1.1.1b-1ubuntu2.1 to 1.1.1b-1ubuntu2.2 . That was at 10:41
  CEST. About 12:36 the system froze. I was able to reset the system at
  around 17:17. It froze again at around 17:55. Reset it again 19:09,
  froze again 00:15.

  Freeze = solid green "busy" light and doesn't answer to anything.
  Since it's a headless system, I only have the logfiles but they don't
  show anything obvious.

  At 01:06, I've downgraded back to 1.1.1b-1ubuntu2.1 and didn't have
  ANY freeze at all since then (13:13 now here).

  The system is running ejabberd, SyncThing and a few more programs,
  that make heavy use of OpenSSL.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832834/+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 2026307] Re: ssh-askpass-gnome pops up for every sudo command

2023-07-13 Thread john doe

Thanks for getting back. I refactored my application to use pkexec, so
idk when i'll get around to testing this. Unfortunately, due to the
super old policykit package in debian/ubuntu my app still doesn't work
in ubuntu and probably won't support ubuntu until 23.10, assuming
policykit-1 122 makes it in. Also, looks like it has some gtk4 bugs that
don't happen in fedora. I'll see how 23.10 fairs. Just some volunteered
data for the project. :)

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

Title:
  ssh-askpass-gnome pops up for every sudo command

Status in openssh package in Ubuntu:
  New
Status in openssh source package in Jammy:
  Triaged
Status in openssh source package in Kinetic:
  Triaged
Status in openssh source package in Lunar:
  Triaged

Bug description:
  When running multiple commands like this:
   
  SUDO_ASKPASS=/usr/lib/openssh/gnome-ssh-askpass sudo -A cp ./ez_bkup 
/usr/local/bin/ 

  from my gtk4 app, the ssh-askpass-gnome dialog and the gnome
  inhibitShortcutsDialog pops up. i click allow on the
  inhibitShortcutsDialog, then enter my password, which is accepted,
  then they both pop up again for each of these sudo commands my app
  calls.

  This happens in ubuntu 22.04-23.04 (completely updated) using gnome.
  If i use xfce in the same ubuntu versions, the gnome dialog doesn't
  pop up, of course, and ssh-askpass-gnome works properly (one entry and
  then all commands executed without further prompting). Fedora 37 works
  properly with gnome x11 or wayland, and xfce. Not sure if this is a
  bug in ubuntu's ssh-askpass-gnome, gnome-shell, or both/something
  else.

  ubuntu 23.04 is using GNOME Shell 44.2 and ssh-askpass-gnome
  1:9.0p1-1ubuntu8.2

  fedora is using openssh-askpass-8.8p1-10.fc37 and GNOME Shell 43.6

  thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2026307/+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 1724623] Re: Update ubuntu cloud info

This bug was fixed in the package cloud-init - 23.2.1-0ubuntu0~22.04.1

---
cloud-init (23.2.1-0ubuntu0~22.04.1) jammy; urgency=medium

  * Upstream snapshot based on 23.2.1. (LP: #2025180).
List of changes from upstream can be found at
https://raw.githubusercontent.com/canonical/cloud-init/23.2.1/ChangeLog

cloud-init (23.2-0ubuntu0~22.04.1) jammy; urgency=medium

  * d/control: Remove pep8 dependency. It is no longer used.
  * d/apport-general-hook.py: Add general apport hook to append cloud type,
image and instance size information to bug reports (LP: #1724623)
  * d/cloud-init.preinst: Oracle to remove vestigial /etc/cloud.cloud.cfg.d/
99-disable-network-config.cfg because system config is now honored before
datasource config (LP: #1956788)
  * d/cloud-init.preinst: Clean up vestigial
/etc/cloud/cloud.cfg.d/99-disable-network-activation.cfg on GCE instances
after fix in upstream google-guest-agent.
  * Refresh patches against upstream/main
- d/p/expire-on-hashed-users.patch
- d/p/retain-netplan-world-readable.patch
  * Upstream snapshot based on 23.2. (LP: #2023110).
List of changes from upstream can be found at
https://raw.githubusercontent.com/canonical/cloud-init/23.2/ChangeLog

 -- Brett Holman   Wed, 28 Jun 2023 16:16:26
-0600

** Changed in: cloud-init (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

** Changed in: cloud-init (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Update ubuntu cloud info

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Focal:
  Fix Released
Status in cloud-init source package in Jammy:
  Fix Released
Status in cloud-init source package in Kinetic:
  Fix Released
Status in apport source package in Lunar:
  New
Status in cloud-init source package in Lunar:
  Fix Released

Bug description:
  [ Impact ]
  Apport reported bug add invalid bug tags such as `uec-images` which no longer 
has meaning or `ec2-images` on openstack. Since cloud-init is installed in all 
these images and detects the correct datasource, leverage cloud-init's 
instance-data.json or cloud-id

  [ Test Plan ]

  1. Launch LXD container for each series
  2. upgrade to cloud-init from -proposed.
  3. Execute apport-bug cloud-init and view report to assess that correct tags 
are present for LXD datasource.
  4. replace /run/cloud-init/instance-data.json cloud-id content with examples 
from openstack, ec2, configdrive and assert appropriate tags match the platform 
details.

  verification scriptlet (attached):

  #!/bin/bash
  set -ex

  cat > setup_proposed.sh  openstack.json  ec2.json << EOF
  {
    "ds": {
  "imageId": "ami-123",
  "instanceType": "m1.tiny",
  "region": "us-east-1"
    },
    "v1": {
  "cloud_name": "aws",
  "distro": "ubuntu",
  "distro_release": "jammy",
  "distro_version": "22.04",
  "instance_id": "i-06b5687b4d7b8595d",
  "machine": "x86_64",
  "platform": "ec2",
  "python_version": "3.10.4",
  "region": "us-east-2",
  "variant": "ubuntu"
    }
  }
  EOF

  for release in focal jammy kinetic lunar; do
   VM=sru-$release
   lxc launch ubuntu-daily:$release $VM
   while ! lxc exec $VM -- cloud-init status --wait --long; do
  sleep 5
   done
   echo --- 1. Generate current apport report, selecting Openstack as cloud.
   echo --- step through prompts and select 'K' to keep report
   echo --- VERSION OF APPORT ---
   lxc exec $VM -- apport-bug --version
   lxc exec $VM -- apport-bug cloud-init
   APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport)
   lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.orig
   lxc exec $VM rm /tmp/$APPORT_FILE

   lxc file push setup_proposed.sh $VM/
   lxc exec $VM -- bash /setup_proposed.sh | grep cloud-init

   lxc file push openstack.json $VM/run/cloud-init/instance-data.json
   echo --- 2. Generate -proposed apport report which sources openstack 
instance-data.json, selecting Openstack as cloud.
   lxc exec $VM -- apport-bug cloud-init
   APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport)
   lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.openstack-proposed
   lxc exec $VM rm /tmp/$APPORT_FILE

   echo --- 3. Generate -proposed apport report which sources ec2 
instance-data, selecting Ec2 as cloud.
   lxc file push ec2.json $VM/run/cloud-init/instance-data.json
   lxc exec $VM -- apport-bug cloud-init
   APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport)
   lxc file pull

[Touch-packages] [Bug 1724623] Re: Update ubuntu cloud info

This bug was fixed in the package cloud-init - 23.2.1-0ubuntu0~20.04.2

---
cloud-init (23.2.1-0ubuntu0~20.04.2) focal; urgency=medium

  * d/apport-general-hook: correct type hints on Dict for py3.8
(LP: #2025376)

cloud-init (23.2.1-0ubuntu0~20.04.1) focal; urgency=medium

  * Upstream snapshot based on 23.2.1. (LP: #2025180).
List of changes from upstream can be found at
https://raw.githubusercontent.com/canonical/cloud-init/23.2.1/ChangeLog

cloud-init (23.2-0ubuntu0~20.04.1) focal; urgency=medium

  * d/control: Remove pep8 dependency. It is no longer used
  * d/patches/netplan99-cannot-use-default.patch:
- Retain routes' definitions compatible with netplan 0.99 (Fixes: #4133)
  * d/apport-general-hook.py: Add general apport hook to append cloud type,
image and instance size information to bug reports (LP: #1724623)
  * d/cloud-init.preinst: Oracle to remove vestigial /etc/cloud.cloud.cfg.d/
99-disable-network-config.cfg because system config is now honored before
datasource config (LP: #1956788)
  * d/cloud-init.preinst: Clean up vestigial
/etc/cloud/cloud.cfg.d/99-disable-network-activation.cfg on GCE instances
after fix in upstream google-guest-agent.
  * Refresh patches against upstream/main:
- d/p/expire-on-hashed-users.patch
- d/p/retain-netplan-world-readable.patch
  * Upstream snapshot based on 23.2. (LP: #2023110).
List of changes from upstream can be found at
https://raw.githubusercontent.com/canonical/cloud-init/23.2/ChangeLog

 -- Chad Smith   Thu, 29 Jun 2023 09:41:13
-0600

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

Title:
  Update ubuntu cloud info

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Focal:
  Fix Released
Status in cloud-init source package in Jammy:
  Fix Released
Status in cloud-init source package in Kinetic:
  Fix Released
Status in apport source package in Lunar:
  New
Status in cloud-init source package in Lunar:
  Fix Released

Bug description:
  [ Impact ]
  Apport reported bug add invalid bug tags such as `uec-images` which no longer 
has meaning or `ec2-images` on openstack. Since cloud-init is installed in all 
these images and detects the correct datasource, leverage cloud-init's 
instance-data.json or cloud-id

  [ Test Plan ]

  1. Launch LXD container for each series
  2. upgrade to cloud-init from -proposed.
  3. Execute apport-bug cloud-init and view report to assess that correct tags 
are present for LXD datasource.
  4. replace /run/cloud-init/instance-data.json cloud-id content with examples 
from openstack, ec2, configdrive and assert appropriate tags match the platform 
details.

  verification scriptlet (attached):

  #!/bin/bash
  set -ex

  cat > setup_proposed.sh  openstack.json  ec2.json << EOF
  {
    "ds": {
  "imageId": "ami-123",
  "instanceType": "m1.tiny",
  "region": "us-east-1"
    },
    "v1": {
  "cloud_name": "aws",
  "distro": "ubuntu",
  "distro_release": "jammy",
  "distro_version": "22.04",
  "instance_id": "i-06b5687b4d7b8595d",
  "machine": "x86_64",
  "platform": "ec2",
  "python_version": "3.10.4",
  "region": "us-east-2",
  "variant": "ubuntu"
    }
  }
  EOF

  for release in focal jammy kinetic lunar; do
   VM=sru-$release
   lxc launch ubuntu-daily:$release $VM
   while ! lxc exec $VM -- cloud-init status --wait --long; do
  sleep 5
   done
   echo --- 1. Generate current apport report, selecting Openstack as cloud.
   echo --- step through prompts and select 'K' to keep report
   echo --- VERSION OF APPORT ---
   lxc exec $VM -- apport-bug --version
   lxc exec $VM -- apport-bug cloud-init
   APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport)
   lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.orig
   lxc exec $VM rm /tmp/$APPORT_FILE

   lxc file push setup_proposed.sh $VM/
   lxc exec $VM -- bash /setup_proposed.sh | grep cloud-init

   lxc file push openstack.json $VM/run/cloud-init/instance-data.json
   echo --- 2. Generate -proposed apport report which sources openstack 
instance-data.json, selecting Openstack as cloud.
   lxc exec $VM -- apport-bug cloud-init
   APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport)
   lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.openstack-proposed
   lxc exec $VM rm /tmp/$APPORT_FILE

   echo --- 3. Generate -proposed apport report which sources ec2 
instance-data, selecting Ec2 as cloud.
   lxc file push ec2.json $VM/run/cloud-init/instance-data.json
   lxc exec $VM

[Touch-packages] [Bug 1724623] Update Released

2023-07-13 Thread Andreas Hasenack

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

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

Title:
  Update ubuntu cloud info

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Focal:
  Fix Released
Status in cloud-init source package in Jammy:
  Fix Released
Status in cloud-init source package in Kinetic:
  Fix Released
Status in apport source package in Lunar:
  New
Status in cloud-init source package in Lunar:
  Fix Released

Bug description:
  [ Impact ]
  Apport reported bug add invalid bug tags such as `uec-images` which no longer 
has meaning or `ec2-images` on openstack. Since cloud-init is installed in all 
these images and detects the correct datasource, leverage cloud-init's 
instance-data.json or cloud-id

  [ Test Plan ]

  1. Launch LXD container for each series
  2. upgrade to cloud-init from -proposed.
  3. Execute apport-bug cloud-init and view report to assess that correct tags 
are present for LXD datasource.
  4. replace /run/cloud-init/instance-data.json cloud-id content with examples 
from openstack, ec2, configdrive and assert appropriate tags match the platform 
details.

  verification scriptlet (attached):

  #!/bin/bash
  set -ex

  cat > setup_proposed.sh  openstack.json  ec2.json << EOF
  {
    "ds": {
  "imageId": "ami-123",
  "instanceType": "m1.tiny",
  "region": "us-east-1"
    },
    "v1": {
  "cloud_name": "aws",
  "distro": "ubuntu",
  "distro_release": "jammy",
  "distro_version": "22.04",
  "instance_id": "i-06b5687b4d7b8595d",
  "machine": "x86_64",
  "platform": "ec2",
  "python_version": "3.10.4",
  "region": "us-east-2",
  "variant": "ubuntu"
    }
  }
  EOF

  for release in focal jammy kinetic lunar; do
   VM=sru-$release
   lxc launch ubuntu-daily:$release $VM
   while ! lxc exec $VM -- cloud-init status --wait --long; do
  sleep 5
   done
   echo --- 1. Generate current apport report, selecting Openstack as cloud.
   echo --- step through prompts and select 'K' to keep report
   echo --- VERSION OF APPORT ---
   lxc exec $VM -- apport-bug --version
   lxc exec $VM -- apport-bug cloud-init
   APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport)
   lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.orig
   lxc exec $VM rm /tmp/$APPORT_FILE

   lxc file push setup_proposed.sh $VM/
   lxc exec $VM -- bash /setup_proposed.sh | grep cloud-init

   lxc file push openstack.json $VM/run/cloud-init/instance-data.json
   echo --- 2. Generate -proposed apport report which sources openstack 
instance-data.json, selecting Openstack as cloud.
   lxc exec $VM -- apport-bug cloud-init
   APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport)
   lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.openstack-proposed
   lxc exec $VM rm /tmp/$APPORT_FILE

   echo --- 3. Generate -proposed apport report which sources ec2 
instance-data, selecting Ec2 as cloud.
   lxc file push ec2.json $VM/run/cloud-init/instance-data.json
   lxc exec $VM -- apport-bug cloud-init
   APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport)
   lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.ec2-proposed
   lxc exec $VM rm /tmp/$APPORT_FILE

   # redact logs lines for easy diffs
   for file in `ls apport*`; do
   sed -i '1,/logs.tgz/!d' $file
   done
   echo --- 4. Inspect diff tags of orig to openstack-proposed report
   diff -urN apport-$VM.orig apport-$VM.openstack-proposed || true
   echo --- 5. Inspect diff tags of openstack-proposed to ec2-proposed report
   diff -urN apport-$VM.openstack-proposed apport-$VM.ec2-proposed || true

  done

  [ Where problems could occur ]
  apport-bug could traceback on poor logic preventing simple bug filing at 
apport CLI. It could omit tags if unable to process 
cloud-init/instance-data.json. nothing critical to daily performance, uptime or 
security

  [ Other Info ]

  [Original description]

  Issues:
   - Using the presence of cloud-init to flag an image as a cloud image is 
incorrect now that ubuntu-server includes cloud-init (and ubuntu-core images)
   - Using the presence of EC2 metadata source is incorrect a

[Touch-packages] [Bug 1724623] Re: Update ubuntu cloud info

This bug was fixed in the package cloud-init - 23.2.1-0ubuntu0~22.10.1

---
cloud-init (23.2.1-0ubuntu0~22.10.1) kinetic; urgency=medium

  * Upstream snapshot based on 23.2.1. (LP: #2025180).
List of changes from upstream can be found at
https://raw.githubusercontent.com/canonical/cloud-init/23.2.1/ChangeLog

cloud-init (23.2-0ubuntu0~22.10.1) kinetic; urgency=medium

  * d/control: Remove pep8 dependency. It is no longer used.
  * d/apport-general-hook.py: Add general apport hook to append cloud type,
image and instance size information to bug reports (LP: #1724623)
  * d/cloud-init.preinst: Oracle to remove vestigial /etc/cloud.cloud.cfg.d/
99-disable-network-config.cfg because system config is now honored before
datasource config (LP: #1956788)
  * d/cloud-init.preinst: Clean up vestigial
/etc/cloud/cloud.cfg.d/99-disable-network-activation.cfg on GCE instances
after fix in upstream google-guest-agent.
  * Upstream snapshot based on 23.2. (LP: #2023110).
List of changes from upstream can be found at
https://raw.githubusercontent.com/canonical/cloud-init/23.2/ChangeLog

 -- Brett Holman   Wed, 28 Jun 2023 14:24:21
-0600

** Changed in: cloud-init (Ubuntu Kinetic)
   Status: Fix Committed => Fix Released

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

Title:
  Update ubuntu cloud info

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Focal:
  Fix Released
Status in cloud-init source package in Jammy:
  Fix Released
Status in cloud-init source package in Kinetic:
  Fix Released
Status in apport source package in Lunar:
  New
Status in cloud-init source package in Lunar:
  Fix Released

Bug description:
  [ Impact ]
  Apport reported bug add invalid bug tags such as `uec-images` which no longer 
has meaning or `ec2-images` on openstack. Since cloud-init is installed in all 
these images and detects the correct datasource, leverage cloud-init's 
instance-data.json or cloud-id

  [ Test Plan ]

  1. Launch LXD container for each series
  2. upgrade to cloud-init from -proposed.
  3. Execute apport-bug cloud-init and view report to assess that correct tags 
are present for LXD datasource.
  4. replace /run/cloud-init/instance-data.json cloud-id content with examples 
from openstack, ec2, configdrive and assert appropriate tags match the platform 
details.

  verification scriptlet (attached):

  #!/bin/bash
  set -ex

  cat > setup_proposed.sh  openstack.json  ec2.json << EOF
  {
    "ds": {
  "imageId": "ami-123",
  "instanceType": "m1.tiny",
  "region": "us-east-1"
    },
    "v1": {
  "cloud_name": "aws",
  "distro": "ubuntu",
  "distro_release": "jammy",
  "distro_version": "22.04",
  "instance_id": "i-06b5687b4d7b8595d",
  "machine": "x86_64",
  "platform": "ec2",
  "python_version": "3.10.4",
  "region": "us-east-2",
  "variant": "ubuntu"
    }
  }
  EOF

  for release in focal jammy kinetic lunar; do
   VM=sru-$release
   lxc launch ubuntu-daily:$release $VM
   while ! lxc exec $VM -- cloud-init status --wait --long; do
  sleep 5
   done
   echo --- 1. Generate current apport report, selecting Openstack as cloud.
   echo --- step through prompts and select 'K' to keep report
   echo --- VERSION OF APPORT ---
   lxc exec $VM -- apport-bug --version
   lxc exec $VM -- apport-bug cloud-init
   APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport)
   lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.orig
   lxc exec $VM rm /tmp/$APPORT_FILE

   lxc file push setup_proposed.sh $VM/
   lxc exec $VM -- bash /setup_proposed.sh | grep cloud-init

   lxc file push openstack.json $VM/run/cloud-init/instance-data.json
   echo --- 2. Generate -proposed apport report which sources openstack 
instance-data.json, selecting Openstack as cloud.
   lxc exec $VM -- apport-bug cloud-init
   APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport)
   lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.openstack-proposed
   lxc exec $VM rm /tmp/$APPORT_FILE

   echo --- 3. Generate -proposed apport report which sources ec2 
instance-data, selecting Ec2 as cloud.
   lxc file push ec2.json $VM/run/cloud-init/instance-data.json
   lxc exec $VM -- apport-bug cloud-init
   APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport)
   lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.ec2-proposed
   lxc exec $VM rm /tmp/$APPORT_FILE

   # redact logs lines for easy diffs
   for file in `ls apport*`; do
   sed -i '1,/logs.tgz/!d' $file
   done
   echo --

[Touch-packages] [Bug 1958019]

2023-07-13 Thread antidense

Thank you for the info. I have AMD graphics, but might still be the same
issue.

When I look at the dmesg I only see mt7921e errors. I tried unloading
the wifi driver but it didn't make a difference.

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]

2023-07-13 Thread cam

This is probably the same as an Nvidia driver issue that I've had... Or 
similar... I had the same issue with the Gen 6, and gave up hibernating 
completely with the gen7/8.

I could hibernate & resume 1-2 times, and then when resuming... the 
laptop would hang, eventually my desktop session would crash and I'd get 
the login screen. When not using the Nvidia GPU at all, it worked 
consistently.

This is the error I'd see in dmesg:
[   14.045062] nvidia :01:00.0: PM: failed to quiesce async: error -

Seems you can't even shutdown... I don't remember if I encountered that 
problem.

Try uninstalling the Nvidia drivers or blacklisting the nvidia module 
and see if it still occurs.

On 7/12/23 16:24, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #769 from antide...@gmail.com ---
> I have the Legion S7 16ARHA7 w/ Cirrus amp. I've been patching the kernel
> using
> lenovo-7i-gen7-sound-6.2.0-rc3-0.0.5b-002.patch with working sound. However,
> I'm not able to hibernate my laptop successfully. It will hang after saving
> to
> disk but it won't shut off on it's own - just stays on with a black screen
> with
> the fan going. Then it drains the battery until it dies. If I turn it on
> again,
> it will successfully resume from hibernation. I'm not sure what is causing
> it.
> It works find if nothing is open (just gnome-shell), but as soon as I open
> firefox or chrome the problem recurs if it goes to hibernate. Did anyone else
> have the same issue?
>

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]

2023-07-13 Thread antidense

I have the Legion S7 16ARHA7 w/ Cirrus amp. I've been patching the
kernel using lenovo-7i-gen7-sound-6.2.0-rc3-0.0.5b-002.patch with
working sound. However, I'm not able to hibernate my laptop
successfully. It will hang after saving to disk but it won't shut off on
it's own - just stays on with a black screen with the fan going. Then it
drains the battery until it dies. If I turn it on again, it will
successfully resume from hibernation. I'm not sure what is causing it.
It works find if nothing is open (just gnome-shell), but as soon as I
open firefox or chrome the problem recurs if it goes to hibernate. Did
anyone else have the same issue?

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 2027636] Re: [SRU] ucsi drivers missing in initramfs

2023-07-13 Thread Loïc Minier

Hi Benjamin, I wasn't aware of LP #2027575, thanks for looking at
combining the two in a single update and preparing a debdiff for both
issues!

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

Title:
  [SRU] ucsi drivers missing in initramfs

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

Bug description:
  [Impact]

  Some systems rely on a USB type-C UCSI connection; without the
  corresponding driver in the initramfs, USB storage might not be
  accessible. This is notably affecting NVIDIA Tegra systems such as
  Jetson AGX or the IGX and prevents completing USB boot for
  installation purposes.

  The initramfs-tools package has a list of relevant USB drivers to
  include for the default MODULES=most configuration, but didn't list
  the recently introduced ucsi one.

  [ Test Plan ]

  The -generic kernel and probably all kernel flavors contain the ucsi driver. 
On jammy system, you can verify the current initrd doesn't contain 
typec_ucsi.ko by decompressing the initramfs and listing its files:
  $ lsinitramfs /boot/initrd.img-5.19.0-46-generic | grep typec_ucsi.ko

  After installing the updated initramfs-tools package, your current initramfs 
should be automatically rebuilt and pick up typec_ucsi.ko:
  $ lsinitramfs /boot/initrd.img-5.19.0-46-generic | grep typec_ucsi.ko
  usr/lib/modules/5.19.0-46-generic/kernel/drivers/usb/typec/ucsi/typec_ucsi.ko

  [ Where problems could occur ]

  This is making the initramfs slightly bigger. In my testing,
  typec_ucsi.ko was 99913B and /boot/initrd.img-5.19.0-46-generic grew
  by 93403B from 122298948B to 122392351B, so by less than 0.08%.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2027636/+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 1724623] Re: Update ubuntu cloud info

2023-07-13 Thread Chad Smith

While SRU verification did test lunar. I had forgotten the original
release of 23.1 was already published to lunar containing the cloud-init
changes for apport/general-hooks/cloud-init.py and apport/package-
hooks/cloud-init.py that we are verifying here.


I've marked Lunar task as fix-released since 23.1 already contains this 
published fix. The verification script just stands to validate it works as 
advertised.

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

Title:
  Update ubuntu cloud info

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Focal:
  Fix Committed
Status in cloud-init source package in Jammy:
  Fix Committed
Status in cloud-init source package in Kinetic:
  Fix Committed
Status in apport source package in Lunar:
  New
Status in cloud-init source package in Lunar:
  Fix Released

Bug description:
  [ Impact ]
  Apport reported bug add invalid bug tags such as `uec-images` which no longer 
has meaning or `ec2-images` on openstack. Since cloud-init is installed in all 
these images and detects the correct datasource, leverage cloud-init's 
instance-data.json or cloud-id

  [ Test Plan ]

  1. Launch LXD container for each series
  2. upgrade to cloud-init from -proposed.
  3. Execute apport-bug cloud-init and view report to assess that correct tags 
are present for LXD datasource.
  4. replace /run/cloud-init/instance-data.json cloud-id content with examples 
from openstack, ec2, configdrive and assert appropriate tags match the platform 
details.

  verification scriptlet (attached):

  #!/bin/bash
  set -ex

  cat > setup_proposed.sh  openstack.json  ec2.json << EOF
  {
    "ds": {
  "imageId": "ami-123",
  "instanceType": "m1.tiny",
  "region": "us-east-1"
    },
    "v1": {
  "cloud_name": "aws",
  "distro": "ubuntu",
  "distro_release": "jammy",
  "distro_version": "22.04",
  "instance_id": "i-06b5687b4d7b8595d",
  "machine": "x86_64",
  "platform": "ec2",
  "python_version": "3.10.4",
  "region": "us-east-2",
  "variant": "ubuntu"
    }
  }
  EOF

  for release in focal jammy kinetic lunar; do
   VM=sru-$release
   lxc launch ubuntu-daily:$release $VM
   while ! lxc exec $VM -- cloud-init status --wait --long; do
  sleep 5
   done
   echo --- 1. Generate current apport report, selecting Openstack as cloud.
   echo --- step through prompts and select 'K' to keep report
   echo --- VERSION OF APPORT ---
   lxc exec $VM -- apport-bug --version
   lxc exec $VM -- apport-bug cloud-init
   APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport)
   lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.orig
   lxc exec $VM rm /tmp/$APPORT_FILE

   lxc file push setup_proposed.sh $VM/
   lxc exec $VM -- bash /setup_proposed.sh | grep cloud-init

   lxc file push openstack.json $VM/run/cloud-init/instance-data.json
   echo --- 2. Generate -proposed apport report which sources openstack 
instance-data.json, selecting Openstack as cloud.
   lxc exec $VM -- apport-bug cloud-init
   APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport)
   lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.openstack-proposed
   lxc exec $VM rm /tmp/$APPORT_FILE

   echo --- 3. Generate -proposed apport report which sources ec2 
instance-data, selecting Ec2 as cloud.
   lxc file push ec2.json $VM/run/cloud-init/instance-data.json
   lxc exec $VM -- apport-bug cloud-init
   APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport)
   lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.ec2-proposed
   lxc exec $VM rm /tmp/$APPORT_FILE

   # redact logs lines for easy diffs
   for file in `ls apport*`; do
   sed -i '1,/logs.tgz/!d' $file
   done
   echo --- 4. Inspect diff tags of orig to openstack-proposed report
   diff -urN apport-$VM.orig apport-$VM.openstack-proposed || true
   echo --- 5. Inspect diff tags of openstack-proposed to ec2-proposed report
   diff -urN apport-$VM.openstack-proposed apport-$VM.ec2-proposed || true

  done

  [ Where problems could occur ]
  apport-bug could traceback on poor logic preventing simple bug filing at 
apport CLI. It could omit tags if unable to process 
cloud-init/instance-data.json. nothing critical to daily performance, uptime or 
security

  [ Other Info ]

  [Original description]

  Issues:
   - Using the presence of cloud-init to flag an image as a cloud image is 
incorrect now that ubuntu-server includes cloud-init (and ubuntu-core images)
   - Using the presence of EC2 metadata source is incorrect as many non-EC2 
clouds provide EC2 metadata.

[Touch-packages] [Bug 1724623] Re: Update ubuntu cloud info

2023-07-13 Thread Chad Smith

Updated test script asserting specific cloud-init version 23.2.1 as
lunar was not installing from lunar-proposed by default without apt
install -tlunar-proposed.

also changed test to specifically assert expected
CloudName/PlatformSubplatform or Region  and collect FAILED logs
otherwise


Test verification results:
=
csmith@midtown:~$ ./sru-1724623.sh 
+ cat
+ cat
+ cat
+ rm -f failures
+ for release in focal jammy kinetic lunar
+ VM=sru-focal
+ lxc launch ubuntu-daily:focal sru-focal
Creating sru-focal
Starting sru-focal
+ lxc exec sru-focal -- cloud-init status --wait --long

status: done
boot_status_code: enabled-by-generator
last_update: Thu, 13 Jul 2023 19:31:03 +
detail:
DataSourceNoCloud [seed=/var/lib/cloud/seed/nocloud-net][dsmode=net]
+ echo --- 1. Generate current apport report, selecting Openstack as cloud.
--- 1. Generate current apport report, selecting Openstack as cloud.
+ echo --- step through prompts and select K to keep report
--- step through prompts and select K to keep report
+ echo --- VERSION OF APPORT ---
--- VERSION OF APPORT ---
+ lxc exec sru-focal -- apport-bug --version
2.20.11
+ lxc exec sru-focal -- apport-bug cloud-init

*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
..
*** Your device details (lshw) may be useful to developers when addressing this 
bug, but gathering it requires admin privileges. Would you like to include this 
info?


What would you like to do? Your options are:
  Y: Yes
  N: No
  C: Cancel
Please choose (Y/N/C): n

*** Is this machine running in a cloud environment?


What would you like to do? Your options are:
  Y: Yes
  N: No
  C: Cancel
Please choose (Y/N/C): y

*** Please select the cloud vendor or environment in which this instance
is running


Choices:
  1: AliYun
  2: AltCloud
  3: Amazon - Ec2
  4: Azure
  5: Bigstep
  6: Brightbox
  7: CloudSigma
  8: CloudStack
  9: DigitalOcean
  10: E24Cloud
  11: GCE - Google Compute Engine
  12: Huawei Cloud
  13: Exoscale
  14: Hetzner Cloud
  15: NWCS
  16: IBM - (aka SoftLayer or BlueMix)
  17: LXD
  18: MAAS
  19: NoCloud
  20: OpenNebula
  21: OpenStack
  22: Oracle
  23: OVF
  24: RbxCloud - (HyperOne, Rootbox, Rubikon)
  25: OpenTelekomCloud
  26: SAP Converged Cloud
  27: Scaleway
  28: SmartOS
  29: UpCloud
  30: VMware
  31: Vultr
  32: ZStack
  33: Outscale
  34: Other
  C: Cancel
Please choose 
(1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/19/20/21/22/23/24/25/26/27/28/29/30/31/32/33/34/C):
 21


*** Your user-data, cloud-config or autoinstall files can optionally  be 
provided from /var/lib/cloud/instance/user-data.txt and could be useful to 
developers when addressing this bug. Do you wish to attach user-data to this 
bug?


What would you like to do? Your options are:
  Y: Yes
  N: No
  C: Cancel
Please choose (Y/N/C): y
...

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

What would you like to do? Your options are:
  S: Send report (43.7 KB)
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  I: Cancel and ignore future crashes of this program version
  C: Cancel
Please choose (S/V/K/I/C): k
Problem report file: /tmp/apport.cloud-init.svir_fqp.apport
++ lxc exec sru-focal ls /tmp
++ grep apport
+ APPORT_FILE=apport.cloud-init.svir_fqp.apport
+ lxc file pull sru-focal/tmp/apport.cloud-init.svir_fqp.apport 
apport-sru-focal.orig
+ lxc exec sru-focal rm /tmp/apport.cloud-init.svir_fqp.apport
+ lxc file push setup_proposed.sh sru-focal/
+ lxc exec sru-focal -- bash /setup_proposed.sh 
 
+ grep cloud-init
  cloud-init
Get:1 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 cloud-init all 
23.2.1-0ubuntu0~20.04.2 [532 kB]
dpkg-preconfigure: unable to re-open stdin: No such file or directory
Preparing to unpack .../cloud-init_23.2.1-0ubuntu0~20.04.2_all.deb ...
Unpacking cloud-init (23.2.1-0ubuntu0~20.04.2) over (23.1.2-0ubuntu0~20.04.2) 
...
Setting up cloud-init (23.2.1-0ubuntu0~20.04.2) ...
++ lxc exec sru-focal -- cloud-init --version
+ VERSION='/usr/bin/cloud-init 23.2.1-0ubuntu0~20.04.2'
+ '[' '/usr/bin/cloud-init ~20.04.2' '!=' '/usr/bin/cloud-init 
23.2.1-0ubuntu0~20.04.2' ']'
+ lxc file push openstack.json sru-focal/run/cloud-init/instance-data.json
+ echo --- 2. Generate -proposed apport report which sources openstack 
instance-data.json, selecting Openstack as cloud.
--- 2. Generate -proposed apport report which sources openstack 
instance-data.json, selecting Openstack as cloud.
+ lxc exec sru-focal -- apport-bug cloud-init

*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
...
*** Your device details (lshw) may be useful to developers when

[Touch-packages] [Bug 1969365] Re: focal: backport kexec fallback patch

2023-07-13 Thread Dan Watkins

Thanks for the reply, Nick!

I think it's important enough to land because:

* you cannot execute `kexec` correctly on an Ubuntu 20.04 system without this 
patch (it will fall back to performing a full reboot),
* kexec can be used to reduce downtime for critical systems which take a long 
time to reboot (e.g. because they have a lot of hardware to initialise), and
* kexec-tools is in main (and has been since at least trusty) which indicates 
to me that it is expected that kexec will work on Ubuntu

I'd also add that the patch is three lines in a code path which is only
used by people opting into using `kexec`, so the potential downside is
pretty minimal.

(I'll set the bug back to New for now, until you have a chance to
respond.)

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

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

Title:
  focal: backport kexec fallback patch

Status in systemd package in Ubuntu:
  New

Bug description:
  It would be great if focal's systemd could have
  
https://github.com/systemd/systemd/commit/71180f8e57f8fbb55978b00a13990c79093ff7b3
  backported to it.

  [Impact]

  We have observed that kexec'ing to another kernel will fail as the
  drive containing the `kexec` binary has been unmounted by the time
  systemd attempts to do so, indicated in the console:

   Starting Reboot via kexec...
  [  163.960938] shutdown[1]: (sd-kexec) failed with exit status 1.
  [  163.963463] reboot: Restarting system

  [Test Plan]

  1) Launch a 20.04 instance
  2) `apt-get install kexec-tools`
  3) In `/boot`, filling in whatever  needed in your environment:

  kexec -l vmlinuz --initrd initrd.img --append ''

  4) `reboot`

  (I have reproduced this in a single-disk VM, so I assume it reproduces
  ~everywhere: if not, `apt-get remove kexec-tools` before the `reboot`
  could be used to emulate the unmounting.)

  [Where problems could occur]

  Users could inadvertently be relying on the current behaviour: if they
  have configured their systems to kexec, they currently will be
  rebooting normally, and this patch would cause them to start actually
  kexec'ing.

  [Other info]

  We're currently maintaining a systemd tree with only this patch added
  to focal's tree: this patch has received a bunch of testing from us in
  focal.

  This patch landed in v246, so it's already present in supported
  releases later than focal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1969365/+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 2027707] Re: Edubuntu Mantic 23.10 crashed on shutdown

Invalid due to bootloader had not started yet.
Please see bug/2027709
See all log files there for systemd crash.

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

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

Title:
  Edubuntu Mantic 23.10 crashed on shutdown

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Edubuntu Manic 23.10 bootloader crashed
  Finished the install, remove the disc and press enter.
  Crash no reboot.
  Physically shutdown the VM and started it to make this bug report.
  Daily build 20230713
  QA Testing using Virtual Box

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: grub2 (not installed)
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 13 09:22:20 2023
  InstallationDate: Installed on 2023-07-13 (0 days ago)
  InstallationMedia: Edubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230713)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: grub2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2027707/+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 2027709] Re: Edubuntu Manic 23.10 systemd crashed on shutdown

*** This bug is a duplicate of bug 2027707 ***
https://bugs.launchpad.net/bugs/2027707

** Summary changed:

- Edubuntu Manic 23.10 bootloader crashed on shutdown
+ Edubuntu Manic 23.10 systemd crashed on shutdown

** Description changed:

- Edubuntu Manic 23.10 bootloader crashed
+ Edubuntu Manic 23.10 systemd crashed
  Finished the install, remove the disc and press enter.
  Crash no reboot.
  Physically shutdown the VM and started it to make this bug report.
  Daily build 20230713
  QA Testing using Virtual Box
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: systemd 252.5-2ubuntu3
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 13 09:59:42 2023
  InstallationDate: Installed on 2023-07-13 (0 days ago)
  InstallationMedia: Edubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230713)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-  Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
-  Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
+  Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
-  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M
-  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
-  |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
+  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M
+  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
+  |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcEnviron:
-  LANG=en_US.UTF-8
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  TERM=xterm-256color
-  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  TERM=xterm-256color
+  XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.3.0-7-generic 
root=UUID=832daf85-6927-4fb0-bfc9-d8ef8bec72ba ro quiet splash
  SourcePackage: systemd
  SystemdFailedUnits:
-  Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
-  Unit \xe2\x97\x8f.service could not be found.
+  Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
+  Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

** Description changed:

  Edubuntu Manic 23.10 systemd crashed
- Finished the install, remove the disc and press enter.
+ Finished the install. After install, Notification to remove the disc and 
press enter. Pressed Enter, systemd crashed.
  Crash no reboot.
  Physically shutdown the VM and started it to make this bug report.
  Daily build 20230713
  QA Testing using Virtual Box
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: systemd 252.5-2ubuntu3
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 13 09:59:42 2023
  InstallationDate: Installed on 2023-07-13 (0 days ago)
  InstallationMedia: Edubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230713)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.3.0-7-generic 
root=UUID=832daf85-

[Touch-packages] [Bug 2027679] Re: package iptables 1.8.4-3ubuntu2.1 failed to install/upgrade: installed iptables package post-installation script subprocess returned error exit status 2

2023-07-13 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 iptables in Ubuntu.
https://bugs.launchpad.net/bugs/2027679

Title:
  package iptables 1.8.4-3ubuntu2.1 failed to install/upgrade: installed
  iptables package post-installation script subprocess returned error
  exit status 2

Status in iptables package in Ubuntu:
  New

Bug description:
  The system keeps sending a pop up display saying the System detected a
  problem

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: iptables 1.8.4-3ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-73.80~20.04.1-generic 5.15.98
  Uname: Linux 5.15.0-73-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  AptOrdering:
   accountsservice:amd64: Install
   libaccountsservice0:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Jul  9 21:15:09 2023
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  DpkgHistoryLog:
   Start-Date: 2023-07-09  21:15:08
   Commandline: /usr/bin/unattended-upgrade
   Upgrade: accountsservice:amd64 (0.6.55-0ubuntu12~20.04.5, 
0.6.55-0ubuntu12~20.04.6), libaccountsservice0:amd64 (0.6.55-0ubuntu12~20.04.5, 
0.6.55-0ubuntu12~20.04.6)
  DuplicateSignature:
   package:iptables:1.8.4-3ubuntu2.1
   Setting up google-chrome-stable (114.0.5735.90-1) ...
   update-alternatives: error: cannot stat file '/usr/bin/nodejs': Too many 
levels of symbolic links
   dpkg: error processing package google-chrome-stable (--configure):
installed google-chrome-stable package post-installation script subprocess 
returned error exit status 2
  ErrorMessage: installed iptables package post-installation script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2023-03-09 (125 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: iptables
  Title: package iptables 1.8.4-3ubuntu2.1 failed to install/upgrade: installed 
iptables package post-installation script subprocess returned error exit status 
2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/2027679/+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 2027679] Re: package iptables 1.8.4-3ubuntu2.1 failed to install/upgrade: installed iptables package post-installation script subprocess returned error exit status 2

2023-07-13 Thread Leonidas S. Barbosa

** 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 iptables in Ubuntu.
https://bugs.launchpad.net/bugs/2027679

Title:
  package iptables 1.8.4-3ubuntu2.1 failed to install/upgrade: installed
  iptables package post-installation script subprocess returned error
  exit status 2

Status in iptables package in Ubuntu:
  New

Bug description:
  The system keeps sending a pop up display saying the System detected a
  problem

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: iptables 1.8.4-3ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-73.80~20.04.1-generic 5.15.98
  Uname: Linux 5.15.0-73-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  AptOrdering:
   accountsservice:amd64: Install
   libaccountsservice0:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Jul  9 21:15:09 2023
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  DpkgHistoryLog:
   Start-Date: 2023-07-09  21:15:08
   Commandline: /usr/bin/unattended-upgrade
   Upgrade: accountsservice:amd64 (0.6.55-0ubuntu12~20.04.5, 
0.6.55-0ubuntu12~20.04.6), libaccountsservice0:amd64 (0.6.55-0ubuntu12~20.04.5, 
0.6.55-0ubuntu12~20.04.6)
  DuplicateSignature:
   package:iptables:1.8.4-3ubuntu2.1
   Setting up google-chrome-stable (114.0.5735.90-1) ...
   update-alternatives: error: cannot stat file '/usr/bin/nodejs': Too many 
levels of symbolic links
   dpkg: error processing package google-chrome-stable (--configure):
installed google-chrome-stable package post-installation script subprocess 
returned error exit status 2
  ErrorMessage: installed iptables package post-installation script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2023-03-09 (125 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: iptables
  Title: package iptables 1.8.4-3ubuntu2.1 failed to install/upgrade: installed 
iptables package post-installation script subprocess returned error exit status 
2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/2027679/+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 1971242] Re: printing PDF appears always grey, no color

2023-07-13 Thread Andreas Hasenack

Till, could you please clarify if kinetic and lunar are fixed?

It seems only cups 2.4.3[1] fixed the issue, and kinetic and lunar have
2.4.2. I checked the code in the packages with patches applied and I
don't see the fix there (in kinetic and lunar).

1. https://github.com/OpenPrinting/cups/releases/tag/v2.4.3

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

Title:
  printing PDF appears always grey, no color

Status in CUPS:
  Fix Released
Status in atril package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Fix Released
Status in okular package in Ubuntu:
  Confirmed
Status in cups source package in Jammy:
  Fix Committed

Bug description:
  After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
  document. The print appears always b/w regardless color printing was
  enabled or not. Printing from LibreOffice produces a color print. This
  behavior (bug) is reproducible on three upgraded machines. It would be
  nice to have color print back again.

  [ Impact ]

  If the PPD file for a printer has a ColorModel option and the only
  choice in it for printing in color is not named RGB but CMYK instead,
  the printer cannot be made printing in color with intuitive methods,
  usually selcting the color choice in the print dialog (which makes
  ColorModel=CMYK be sent along with the job).

  Only an ugly command-line-based workaround, running the command

  lpadmin -p PRINTER -o print-color-mode-default=color

  makes the printer print in color.

  An example for printers with such PPDs are printers from RICOH and OEM
  (Lanier, InfoTec, Savin, ..), so many high-end color laser printers
  are affected.

  [ Test Plan ]

  Remove the workaround if you had applied it:

  lpadmin -p PRINTER -R print-color-mode-default

  If you have an affected printer, print a PDF file (or use the print
  functionality in an application) with colored content and choose the
  setting for color printing in the print dialog. When printing via
  command line do

  lp -d PRINTER -o ColorModel=CMYK FILE.pdf

  Without the SRU applied you will get a grayscale/monochrome printout,
  with it applied, you will get a colored printout.

  To test without a printer:

  Stop CUPS:

  sudo systemctl stop cups

  Edit /etc/cups/cups-files.conf to have a line

  FiileDevice Yes

  and start CUPS again:

  sudo systemctl start cups

  Then create a queue using the attached sample PPD file:

  lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-
  PDF_Printer-PDF.ppd

  Print a file to this queue as described above. When the job is done
  ("lpstat" does not show it any more), open /tmp/printout with a text
  editor. Check whether it contains a line

  @PJL SET RENDERMODE=COLOR

  near its beginning, and NOT a line

  @PJL SET RENDERMODE=GRAYSCALE

  [ Where problems could occur ]

  The patches are simple and they are also for some time in newer CUPS
  versions (2.4.2 and newer) which are included in several distributions
  (Ubuntu 22.10, 23.04, and others) and did not cause any complaints
  about color printing. So the regression potential is very low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1971242/+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 2009544] Re: OpenSSL 3 performance regression

2023-07-13 Thread Bryce Harrington

Upstream has an umbrella bug that covers this and other associated
performance related problems:

https://github.com/openssl/openssl/issues/17627


** Bug watch added: github.com/openssl/openssl/issues #17627
   https://github.com/openssl/openssl/issues/17627

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

Title:
  OpenSSL 3 performance regression

Status in openssl package in Ubuntu:
  New

Bug description:
  Hello, it sounds like there's some significant performance regressions
  in OpenSSL 3:

  https://github.com/openssl/openssl/issues/20286#issuecomment-1438826816

  Some we might be able to address with:
  https://github.com/openssl/openssl/pull/18151

  Some of the performance differences may be subject to ongoing work.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2009544/+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 1799265] Re: avahi-daemon high cpu, unusable networking

2023-07-13 Thread Avi B

Hi,

I'm wondering if the fix for this is
https://github.com/lathiat/avahi/pull/366 and whether or not that fix
can be SRU'd into Jammy, which uses avahi 0.8-5ubuntu5.1 ?

That patch was already pulled in to 0.8-6
(https://salsa.debian.org/utopia-
team/avahi/-/commit/cf97e08b52cd2194c4f7a516c3929ea79d39696a) which is
included in Kinetic+.

Thanks for considering this :)

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

Title:
  avahi-daemon high cpu, unusable networking

Status in Avahi:
  New
Status in avahi package in Ubuntu:
  Triaged

Bug description:
  Currently running Kubuntu 18.10, Dell XPS 13 9350

  Since updating from Kubuntu 18.04 to 18.10, the avahi-daemon has been
  consistently hampering network performance and using CPU for long
  periods of time.

  When booting machine from off state, avahi-daemon uses an entire CPU
  at max load for approx 10 minutes. During this time, internet
  connectivity via wifi is essentially unusable. The wifi connection is
  good, but it seems that http transactions are cutoff mid-way so no
  webpage is able to load.

  When waking from sleep, the avahi-daemon causes similar symptoms, but
  with less than 1 full cpu usage, and with somewhat less degraded
  network performance, but still quite unusable.

  I have never had issues with avahi prior to the 18.10 upgrade, so I am
  fairly confident the issue is rooted in that change.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: avahi-daemon 0.7-4ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Oct 22 10:00:34 2018
  InstallationDate: Installed on 2017-07-24 (455 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   LD_PRELOAD=
   SHELL=/bin/bash
  SourcePackage: avahi
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/avahi/+bug/1799265/+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 2007621] Re: gio open exits with success even though the underlying exec failed

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

** Changed in: glib2.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  gio open exits with success even though the underlying exec failed

Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  This is a sort of annoyingly complex interaction, so bear with me. The
  observed problem is that xdg-open does not exit with a non-zero exit
  code when it fails to open.

  ```
  $ unset DISPLAY 
  $ xdg-open http://example.com
  exo-open: Cannot open display: .
  $ echo $?
  0
  ```

  It turns out to not exactly be xdg-open's fault, though:
  ```
  $ sh -x $(which xdg-open) http://example.com 2>&1 | tail -n10
  + return 0
  + open_xfce http://example.com
  + exo-open --help
  + gio help open
  + gio open http://example.com
  exo-open: Cannot open display: .
  + [ 0 -eq 0 ]
  + exit_success
  + [ 0 -gt 0 ]
  + exit 0
  ```

  So, from this we see that xdg-open uses `exo-open --help` to see if
  exo-open works, but it fails due to the DISPLAY, so it falls back to
  gio open. gio open ends up turning around and calling exo-open again,
  but gio swallows the exit code, so xdg-open thinks it worked.

  ```
  $ exo-open http://example.com
  exo-open: Cannot open display: .
  $ echo $?
  1
  $ gio open http://example.com
  exo-open: Cannot open display: .
  $ echo $?
  0
  ```

  Versions:
  $ lsb_release -rd  
  Description:Ubuntu 22.04.1 LTS
  Release:22.04
  $ xdg-open --version   
  xdg-open 1.1.3
  $ exo-open --version | head -n1
  exo-open 4.16.3
  $ gio --version   
  2.72.4

  Specifically:
  exo-utils:
Installed: 4.16.3-1
Candidate: 4.16.3-1
Version table:
   *** 4.16.3-1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status
  libglib2.0-bin:
Installed: 2.72.4-0ubuntu1
Candidate: 2.72.4-0ubuntu1
Version table:
   *** 2.72.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.72.1-1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  xdg-utils:
Installed: 1.1.3-4.1ubuntu3~22.04.1
Candidate: 1.1.3-4.1ubuntu3~22.04.1
Version table:
   *** 1.1.3-4.1ubuntu3~22.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1.1.3-4.1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2007621/+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 2027707] Re: Edubuntu Manic 23.10 crashed on shutdown

2023-07-13 Thread Nick Rosbrook

Can you please provide some logs and explain why you think this is a
systemd bug?

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

** Summary changed:

- Edubuntu Manic 23.10 crashed on shutdown
+ Edubuntu Mantic 23.10 crashed on shutdown

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

Title:
  Edubuntu Mantic 23.10 crashed on shutdown

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Edubuntu Manic 23.10 bootloader crashed
  Finished the install, remove the disc and press enter.
  Crash no reboot.
  Physically shutdown the VM and started it to make this bug report.
  Daily build 20230713
  QA Testing using Virtual Box

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: grub2 (not installed)
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 13 09:22:20 2023
  InstallationDate: Installed on 2023-07-13 (0 days ago)
  InstallationMedia: Edubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230713)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: grub2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2027707/+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 2026826] Re: glib2.0 (2.77.0 ) breaks Netplan build

2023-07-13 Thread Lukas Märdian

Thank you! The Netplan build seems to be fixed now. Removing the tag.

** Tags removed: block-proposed

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

Title:
  glib2.0 (2.77.0 ) breaks Netplan build

Status in GLib:
  New
Status in glib2.0 package in Ubuntu:
  Fix Committed

Bug description:
  Netplan FTBFS as of the latest release of glib2.0 (2.77.0-0ubuntu1) in
  mantic-proposed.

  See: https://launchpad.net/ubuntu/+source/netplan.io/0.106.1-3

  When I downgrade glib in my sbuild environment, everything works as
  expected:

  $ apt install libglib2.0-0=2.76.3-1ubuntu1
  libglib2.0-bin=2.76.3-1ubuntu1 libglib2.0-dev=2.76.3-1ubuntu1
  libglib2.0-dev-bin=2.76.3-1ubuntu1 libglib2.0-data=2.76.3-1ubuntu1

  The build also works fine in Debian unstable, which is using glib2.0
  2.74.6-2.

  Netplan is using plenty of GLib's keyfile functions
  (https://docs.gtk.org/glib/struct.KeyFile.html), which seem to
  producing a different output with this newer release (some strange
  line breaks injected in the middle of a keyfile).

  
  Example keyfile from the test_wifis.test_wifi_wowlan test, that should be 
generated by Netplan and the way it fails:

  Expected output:
  ```
  [connection]
  id=netplan-wl0-homenet
  type=wifi
  interface-name=wl0

  [wifi]
  wake-on-wlan=330
  ssid=homenet
  mode=infrastructure

  [ipv4]
  method=link-local

  [ipv6]
  method=ignore
  ```

  Failure:
  ```
  E   AssertionError: '[con[88 
chars]330\n\nssid=homenet\nmode=infrastructure\n[ipv[44 chars]re\n' != '[con[88 
chars]330\nssid=homenet\nmode=infrastructure\n\n[ipv[44 chars]re\n'
  E [connection]
  E id=netplan-wl0-homenet
  E type=wifi
  E interface-name=wl0
  E 
  E [wifi]
  E wake-on-wlan=330
  E   - 
  E ssid=homenet
  E mode=infrastructure
  E   + 
  E [ipv4]
  E method=link-local
  E 
  E [ipv6]
  E method=ignore
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/2026826/+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 2027709] [NEW] Edubuntu Manic 23.10 bootloader crashed on shutdown

*** This bug is a duplicate of bug 2027707 ***
https://bugs.launchpad.net/bugs/2027707

Public bug reported:

Edubuntu Manic 23.10 bootloader crashed
Finished the install, remove the disc and press enter.
Crash no reboot.
Physically shutdown the VM and started it to make this bug report.
Daily build 20230713
QA Testing using Virtual Box

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: systemd 252.5-2ubuntu3
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
ApportVersion: 2.26.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul 13 09:59:42 2023
InstallationDate: Installed on 2023-07-13 (0 days ago)
InstallationMedia: Edubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230713)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
 |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: innotek GmbH VirtualBox
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.3.0-7-generic 
root=UUID=832daf85-6927-4fb0-bfc9-d8ef8bec72ba ro quiet splash
SourcePackage: systemd
SystemdFailedUnits:
 Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: 
Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
 Unit \xe2\x97\x8f.service could not be found.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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


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

** This bug has been marked a duplicate of bug 2027707
   Edubuntu Manic 23.10 crashed on shutdown

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

Title:
  Edubuntu Manic 23.10 bootloader crashed on shutdown

Status in systemd package in Ubuntu:
  New

Bug description:
  Edubuntu Manic 23.10 bootloader crashed
  Finished the install, remove the disc and press enter.
  Crash no reboot.
  Physically shutdown the VM and started it to make this bug report.
  Daily build 20230713
  QA Testing using Virtual Box

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: systemd 252.5-2ubuntu3
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 13 09:59:42 2023
  InstallationDate: Installed on 2023-07-13 (0 days ago)
  InstallationMedia: Edubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230713)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.3.0-7-generic 
root=UUID=832daf85-6927-4fb0-bfc9-d8ef8bec72ba ro quiet splash
  SourcePackage: systemd
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporatio

[Touch-packages] [Bug 2027709] Re: Edubuntu Manic 23.10 bootloader crashed on shutdown

*** This bug is a duplicate of bug 2027707 ***
https://bugs.launchpad.net/bugs/2027707

In the Terminal:
b3@b3-VirtualBox:~$ ubuntu-bug systemd
b3@b3-VirtualBox:~$ update.go:85: cannot change mount namespace according to 
change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs 
/usr/share/xubuntu-docs none bind,ro 0 0): cannot open directory "/var/lib": 
permission denied
[ERROR viaduct::backend::ffi] Missing HTTP status
[ERROR viaduct::backend::ffi] Missing HTTP status

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

Title:
  Edubuntu Manic 23.10 bootloader crashed on shutdown

Status in systemd package in Ubuntu:
  New

Bug description:
  Edubuntu Manic 23.10 bootloader crashed
  Finished the install, remove the disc and press enter.
  Crash no reboot.
  Physically shutdown the VM and started it to make this bug report.
  Daily build 20230713
  QA Testing using Virtual Box

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: systemd 252.5-2ubuntu3
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 13 09:59:42 2023
  InstallationDate: Installed on 2023-07-13 (0 days ago)
  InstallationMedia: Edubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230713)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.3.0-7-generic 
root=UUID=832daf85-6927-4fb0-bfc9-d8ef8bec72ba ro quiet splash
  SourcePackage: systemd
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2027709/+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 2027707] Re: Edubuntu Manic 23.10 crashed on shutdown

2023-07-13 Thread Ubuntu QA Website

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

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

** Tags added: iso-testing

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

Title:
  Edubuntu Manic 23.10 crashed on shutdown

Status in systemd package in Ubuntu:
  New

Bug description:
  Edubuntu Manic 23.10 bootloader crashed
  Finished the install, remove the disc and press enter.
  Crash no reboot.
  Physically shutdown the VM and started it to make this bug report.
  Daily build 20230713
  QA Testing using Virtual Box

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: grub2 (not installed)
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 13 09:22:20 2023
  InstallationDate: Installed on 2023-07-13 (0 days ago)
  InstallationMedia: Edubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230713)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: grub2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2027707/+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 2027707] Re: Edubuntu Manic 23.10 bootloader crashed

2023-07-13 Thread Erich Eickmeyer

** Package changed: grub2 (Ubuntu) => systemd (Ubuntu)

** Summary changed:

- Edubuntu Manic 23.10 bootloader crashed
+ Edubuntu Manic 23.10 crashed on shutdown

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

Title:
  Edubuntu Manic 23.10 crashed on shutdown

Status in systemd package in Ubuntu:
  New

Bug description:
  Edubuntu Manic 23.10 bootloader crashed
  Finished the install, remove the disc and press enter.
  Crash no reboot.
  Physically shutdown the VM and started it to make this bug report.
  Daily build 20230713
  QA Testing using Virtual Box

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: grub2 (not installed)
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 13 09:22:20 2023
  InstallationDate: Installed on 2023-07-13 (0 days ago)
  InstallationMedia: Edubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230713)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: grub2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2027707/+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 2026757] Re: dnsmasq on Ubuntu Jammy/Lunar crashes on neutron-dhcp-agent updates

2023-07-13 Thread Julia Kreger

Greetings Yatin!

So, the failure appears to be rooted in ipxe failing to get the complete
set of data from the server. My guess is that is something to do with
spanning tree as iPXE for ubuntu has also changed it's behavior. My
feeling is this is rooted with some spanning tree behavior, which we
merged a patch after your last recheck to disable. I've re-rechecked
your test patch to hopefully provide us an additional data point.

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

Title:
  dnsmasq on Ubuntu Jammy/Lunar crashes on neutron-dhcp-agent updates

Status in Ironic:
  New
Status in neutron:
  New
Status in dnsmasq package in Ubuntu:
  Confirmed

Bug description:
  The Ironic project's CI has been having major blocking issues moving
  to utilizing Ubuntu Jammy and with some investigation we were able to
  isolate the issues down to the dhcp updates causing dnsmasq to crash
  on Ubuntu Jammy, which ships with dnsmasq 2.86. This issue sounds
  similar to an issue known about to the dnsmasq maintainers, where
  dnsmasq would crash with updates occurring due to configuration
  refresh[0].

  This resulted in us upgrading dnsmasq to the version which ships with
  Ubuntu Lunar.

  Which was no better. Dnsmasq still crashed upon record updates for
  addresses and ports getting configuration added/changed/removed.

  We later downgraded to the version of dnsmasq shipped in Ubuntu Focal,
  and dnsmasq stopped crashing and appeared stable enough to utilize for
  CI purposes.

  ** Kernel log from Ubuntu Jammy Package **

  [229798.876726] dnsmasq[81586]: segfault at 7c28 ip 7f6e8313147e sp 
7fffb3d6f830 error 4 in libc.so.6[7f6e830b4000+195000]
  [229798.876745] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [229805.444912] dnsmasq[401428]: segfault at dce8 ip 7fe63bf6a47e sp 
7ffdb105b440 error 4 in libc.so.6[7fe63beed000+195000]
  [229805.444933] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [230414.213448] dnsmasq[401538]: segfault at 78b8 ip 7f12160e447e sp 
7ffed6ef2190 error 4 in libc.so.6[7f1216067000+195000]
  [230414.213467] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [230465.098989] dnsmasq[402665]: segfault at c378 ip 7f81458f047e sp 
7fff0db334a0 error 4 in libc.so.6[7f8145873000+195000]
  [230465.099005] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [231787.247374] dnsmasq[402863]: segfault at 7318 ip 7f3940b9147e sp 
7ffc8df4f010 error 4 in libc.so.6[7f3940b14000+195000]
  [231787.247392] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [231844.886399] dnsmasq[405182]: segfault at dc58 ip 7f32a29e147e sp 
7ffddedd7480 error 4 in libc.so.6[7f32a2964000+195000]
  [231844.886420] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [234692.482154] dnsmasq[405289]: segfault at 67d8 ip 7fab0c5c447e sp 
7fffd6fd8fa0 error 4 in libc.so.6[7fab0c547000+195000]
  [234692.482173] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a

  ** Kernel log entries from Ubuntu Lunar package **

  [234724.842339] dnsmasq[409843]: segfault at fffd ip 
7f35a147647e sp 7ffd536038c0 error 5 in libc.so.6[7f35a13f9000+195000]
  [234724.842368] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [234784.918116] dnsmasq[410019]: segfault at fffd ip 
7f634233947e sp 7fff33877f20 error 5 in libc.so.6[7f63422bc000+195000]
  [234784.918133] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [235022.163339] dnsmasq[410151]: segfault at ff

[Touch-packages] [Bug 2026730] Re: Merge dash 0.5.12-6 from debian

2023-07-13 Thread Dominik Viererbe

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

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

Title:
  Merge dash 0.5.12-6 from debian

Status in dash package in Ubuntu:
  Fix Committed

Bug description:
  This is a tracking bug to merge dash 0.5.12-6 from debian.

  Below now follows the report of the automated merge of the Ubuntu
  changes to the dash source package against the new Debian version.

  This file is designed to be both human readable and machine-parseable.
  Any line beginning with four spaces is a file that should be
  downloaded for the complete merge set.

  
  Here are the particulars of the three versions of dash that were
  chosen for the merge.  The base is the newest version that is a common
  ancestor of both the Ubuntu and Debian packages.  It may be of a
  different upstream version, but that's not usually a problem.

  The files are the source package itself, and the patch from the common
  base to that version.

  base: 0.5.12-2
  dash_0.5.12-2.dsc
  dash_0.5.12.orig.tar.gz
  dash_0.5.12-2.debian.tar.xz

  ubuntu: 0.5.12-2ubuntu1
  dash_0.5.12-2ubuntu1.dsc
  dash_0.5.12.orig.tar.gz
  dash_0.5.12-2ubuntu1.debian.tar.xz

  base -> ubuntu
  dash_0.5.12-2ubuntu1.patch

  debian: 0.5.12-6
  dash_0.5.12-6.dsc
  dash_0.5.12.orig.tar.gz
  dash_0.5.12-6.debian.tar.xz

  base -> debian
  dash_0.5.12-6.patch

  
  Generated Result
  

  Due to conflict or error, it was not possible to automatically create
  a source package.  Instead the result of the merge has been placed
  into the following tar file which you will need to turn into a source
  package once the problems have been resolved.

  dash_0.5.12-6ubuntu1.src.tar.gz

  
  Conflicts
  =

  In one or more cases, there were different changes made in both Ubuntu
  and Debian to the same file; these are known as conflicts.

  It is not possible for these to be automatically resolved, so this
  source needs human attention.

  Those files marked with 'C ' contain diff3 conflict markers, which can
  be resolved using the text editor of your choice.  Those marked with
  'C*' could not be merged that way, so you will find .UBUNTU and
  .DEBIAN files instead and should choose one of them or a combination
  of both, moving it to the real filename and deleting the other.

C  debian/tests/control

  
  Once you have a source package you are happy to upload, you should
  make sure you include the orig.tar.* if appropriate and information
  about all the versions included in the merge.

  Use the following command to generate a correct .changes file:

$ dpkg-genchanges -S -v0.5.12-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dash/+bug/2026730/+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

This bug was fixed in the package python-debian - 0.1.46ubuntu1

---
python-debian (0.1.46ubuntu1) kinetic; urgency=medium

  * Make Python version PEP440 compliant (LP: #1991606)

 -- Benjamin Drung   Sat, 27 May 2023 01:51:02 +0200

** Changed in: python-debian (Ubuntu Kinetic)
   Status: Fix Committed => Fix Released

** Changed in: python-debian (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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 dput 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:
  Fix Released
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 dput 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:
  Fix Committed
Status in dput source package in Focal:
  Fix Released
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  Fix Committed
Status in python-debian source package in Focal:
  Fix Released
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  Fix Released
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:
  Fix Committed
Status in dput source package in Jammy:
  Fix Released
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  Fix Committed
Status in python-debian source package in Jammy:
  Fix Released
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 dput 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:
  Fix Released
Status in python-debian source package in Kinetic:
  Fix Released
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
Status in dput source package in Lunar:
  Fix Released

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__
  rai

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

This bug was fixed in the package python-debian - 0.1.36ubuntu1.1

---
python-debian (0.1.36ubuntu1.1) focal; urgency=medium

  * Make Python version PEP440 compliant (LP: #1991606)

 -- Benjamin Drung   Tue, 25 Apr 2023 20:39:33 +0200

-- 
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 dput 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:
  Fix Released
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 dput 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:
  Fix Committed
Status in dput source package in Focal:
  Fix Released
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  Fix Committed
Status in python-debian source package in Focal:
  Fix Released
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  Fix Released
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:
  Fix Committed
Status in dput source package in Jammy:
  Fix Released
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  Fix Committed
Status in python-debian source package in Jammy:
  Fix Released
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 dput 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:
  Fix Released
Status in python-debian source package in Kinetic:
  Fix Released
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
Status in dput source package in Lunar:
  Fix Released

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 setuptool

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

This bug was fixed in the package python-debian - 0.1.43ubuntu1.1

---
python-debian (0.1.43ubuntu1.1) jammy; urgency=medium

  * Make Python version PEP440 compliant (LP: #1991606)

 -- Benjamin Drung   Tue, 25 Apr 2023 18:25:44 +0200

** Changed in: python-debian (Ubuntu Focal)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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 dput 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:
  Fix Released
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 dput 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:
  Fix Committed
Status in dput source package in Focal:
  Fix Released
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  Fix Committed
Status in python-debian source package in Focal:
  Fix Released
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  Fix Released
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:
  Fix Committed
Status in dput source package in Jammy:
  Fix Released
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  Fix Committed
Status in python-debian source package in Jammy:
  Fix Released
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 dput 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:
  Fix Released
Status in python-debian source package in Kinetic:
  Fix Released
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
Status in dput source package in Lunar:
  Fix Released

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.versio

[Touch-packages] [Bug 2026757] Re: dnsmasq on Ubuntu Jammy/Lunar crashes on neutron-dhcp-agent updates

2023-07-13 Thread yatin

I tried to setup dnsmasq-2.87 with
https://review.opendev.org/c/openstack/ironic/+/888121 by using source
install and avoiding newer package from lunar, still sometime some of
tests fails but i no longer see any segfault for dnsmasq with it. May be
someone from ironic Team could check and see if it's related to dnsmasq
or some other known issue.

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

Title:
  dnsmasq on Ubuntu Jammy/Lunar crashes on neutron-dhcp-agent updates

Status in Ironic:
  New
Status in neutron:
  New
Status in dnsmasq package in Ubuntu:
  Confirmed

Bug description:
  The Ironic project's CI has been having major blocking issues moving
  to utilizing Ubuntu Jammy and with some investigation we were able to
  isolate the issues down to the dhcp updates causing dnsmasq to crash
  on Ubuntu Jammy, which ships with dnsmasq 2.86. This issue sounds
  similar to an issue known about to the dnsmasq maintainers, where
  dnsmasq would crash with updates occurring due to configuration
  refresh[0].

  This resulted in us upgrading dnsmasq to the version which ships with
  Ubuntu Lunar.

  Which was no better. Dnsmasq still crashed upon record updates for
  addresses and ports getting configuration added/changed/removed.

  We later downgraded to the version of dnsmasq shipped in Ubuntu Focal,
  and dnsmasq stopped crashing and appeared stable enough to utilize for
  CI purposes.

  ** Kernel log from Ubuntu Jammy Package **

  [229798.876726] dnsmasq[81586]: segfault at 7c28 ip 7f6e8313147e sp 
7fffb3d6f830 error 4 in libc.so.6[7f6e830b4000+195000]
  [229798.876745] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [229805.444912] dnsmasq[401428]: segfault at dce8 ip 7fe63bf6a47e sp 
7ffdb105b440 error 4 in libc.so.6[7fe63beed000+195000]
  [229805.444933] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [230414.213448] dnsmasq[401538]: segfault at 78b8 ip 7f12160e447e sp 
7ffed6ef2190 error 4 in libc.so.6[7f1216067000+195000]
  [230414.213467] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [230465.098989] dnsmasq[402665]: segfault at c378 ip 7f81458f047e sp 
7fff0db334a0 error 4 in libc.so.6[7f8145873000+195000]
  [230465.099005] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [231787.247374] dnsmasq[402863]: segfault at 7318 ip 7f3940b9147e sp 
7ffc8df4f010 error 4 in libc.so.6[7f3940b14000+195000]
  [231787.247392] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [231844.886399] dnsmasq[405182]: segfault at dc58 ip 7f32a29e147e sp 
7ffddedd7480 error 4 in libc.so.6[7f32a2964000+195000]
  [231844.886420] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [234692.482154] dnsmasq[405289]: segfault at 67d8 ip 7fab0c5c447e sp 
7fffd6fd8fa0 error 4 in libc.so.6[7fab0c547000+195000]
  [234692.482173] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a

  ** Kernel log entries from Ubuntu Lunar package **

  [234724.842339] dnsmasq[409843]: segfault at fffd ip 
7f35a147647e sp 7ffd536038c0 error 5 in libc.so.6[7f35a13f9000+195000]
  [234724.842368] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [234784.918116] dnsmasq[410019]: segfault at fffd ip 
7f634233947e sp 7fff33877f20 error 5 in libc.so.6[7f63422bc000+195000]
  [234784.918133] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [235022.163339] dnsmasq[410151]: segfault at fffd ip 
7f21dd37f47e sp 7fff9bf416d0 error 5 in libc.so.6[7f21dd302000

[Touch-packages] [Bug 2027575] Re: autopkgtest net is failing on 6.2 kernels with 'System is deadlocked on memory'

2023-07-13 Thread Roxana Nicolescu

Thanks Benjamin for preparing the debdiff and apologize for not picking
this up earlier.

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

Title:
  autopkgtest net is failing on 6.2 kernels with 'System is deadlocked
  on memory'

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

Bug description:
  [Impact]
  In debian/tests/run-image we instantiate an image with 512Mb of ram, but 
recent jammy/lunar 6.2 kernels need more than that.

  Example of a test failure:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/i/initramfs-tools/20230619_135049_ab1cb@/log.gz

  'net' test fails with a kernel panic due to out-of-memory.

  It also relies on an existing and working cloud image. If the cloud
  image is not available, the test will silently succeed.

  [Fix]

  The net autopkgtest was ported to the common test framework in
  initramfs-tools 0.142ubuntu3. This makes the test more robust by
  relying on the minimum needed for the integration test.

  [Test Plan]

  Check that the autopkgtest succeed or test it manually:

  1. Download a lunar image:
  $ autopkgtest-buildvm-ubuntu-cloud -v -a amd64 -r lunar
  2. Run autotestpkg tests from initramfs-tools package. The "net" test is the 
one that depends on the image instantiated by 'run-image'. The testcase should 
complete successfully without the kernel panic.
  $ autopkgtest initramfs-tools -- qemu autopkgtest-lunar-amd64.img

  [Where problems could occur]
  The usage of a larger image for the tests could fail if the the test system 
is low on ram size.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2027575/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

This bug was fixed in the package evince - 44.1-1ubuntu0.1

---
evince (44.1-1ubuntu0.1) lunar; urgency=medium

  * Allow evince to spawn browsers distributed as snaps (LP: #1794064)
- debian/apparmor-profile: include snap-browsers abstracted profile
  and allow transitions to them in evince

 -- Georgia Garcia   Mon, 05 Jun 2023
16:32:15 -0300

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

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Fix Released
Status in evince package in Ubuntu:
  Fix Released
Status in apparmor source package in Jammy:
  Fix Committed
Status in evince source package in Jammy:
  In Progress
Status in apparmor source package in Lunar:
  Fix Released
Status in evince source package in Lunar:
  Fix Released
Status in apparmor package in Debian:
  New
Status in evince package in Debian:
  Confirmed

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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

This bug was fixed in the package dput - 1.1.0ubuntu2.1

---
dput (1.1.0ubuntu2.1) jammy; urgency=medium

  * Make versions with Ubuntu suffixes compliant with PEP 440 (LP:
#1991606)

 -- Benjamin Drung   Thu, 29 Jun 2023 15:45:46 +0200

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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 dput 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:
  Fix Released
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 dput 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:
  Fix Committed
Status in dput source package in Focal:
  Fix Released
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  Fix Committed
Status in python-debian source package in Focal:
  Fix Committed
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  Fix Released
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:
  Fix Committed
Status in dput source package in Jammy:
  Fix Released
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  Fix Committed
Status in python-debian source package in Jammy:
  Fix Committed
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 dput 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:
  Fix Released
Status in python-debian source package in Kinetic:
  Fix Committed
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
Status in dput source package in Lunar:
  Fix Released

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.Inv

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

This bug was fixed in the package dput - 1.0.3ubuntu1.1

---
dput (1.0.3ubuntu1.1) focal; urgency=medium

  * Make versions with Ubuntu suffixes compliant with PEP 440 (LP:
#1991606)

 -- Benjamin Drung   Thu, 29 Jun 2023 16:58:12 +0200

-- 
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 dput 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:
  Fix Released
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 dput 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:
  Fix Committed
Status in dput source package in Focal:
  Fix Released
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  Fix Committed
Status in python-debian source package in Focal:
  Fix Committed
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  Fix Released
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:
  Fix Committed
Status in dput source package in Jammy:
  Fix Released
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  Fix Committed
Status in python-debian source package in Jammy:
  Fix Committed
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 dput 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:
  Fix Released
Status in python-debian source package in Kinetic:
  Fix Committed
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
Status in dput source package in Lunar:
  Fix Released

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 setup

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

This bug was fixed in the package dput - 1.1.2ubuntu2.1

---
dput (1.1.2ubuntu2.1) kinetic; urgency=medium

  * Make versions with Ubuntu suffixes compliant with PEP 440 (LP:
#1991606)

 -- Benjamin Drung   Thu, 29 Jun 2023 14:54:30 +0200

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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 dput 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:
  Fix Released
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 dput 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:
  Fix Committed
Status in dput source package in Focal:
  Fix Released
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  Fix Committed
Status in python-debian source package in Focal:
  Fix Committed
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  Fix Released
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:
  Fix Committed
Status in dput source package in Jammy:
  Fix Released
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  Fix Committed
Status in python-debian source package in Jammy:
  Fix Committed
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 dput 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:
  Fix Released
Status in python-debian source package in Kinetic:
  Fix Committed
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
Status in dput source package in Lunar:
  Fix Released

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 Invalid

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

This bug was fixed in the package dput - 1.1.3ubuntu2.1

---
dput (1.1.3ubuntu2.1) lunar; urgency=medium

  * Make PEP 440 version conversion more robust for SRUs (LP: #1991606)

 -- Benjamin Drung   Sat, 01 Jul 2023 01:49:41 +0200

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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 dput 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:
  Fix Released
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 dput 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:
  Fix Committed
Status in dput source package in Focal:
  Fix Released
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  Fix Committed
Status in python-debian source package in Focal:
  Fix Committed
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  Fix Released
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:
  Fix Committed
Status in dput source package in Jammy:
  Fix Released
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  Fix Committed
Status in python-debian source package in Jammy:
  Fix Committed
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 dput 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:
  Fix Released
Status in python-debian source package in Kinetic:
  Fix Committed
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
Status in dput source package in Lunar:
  Fix Released

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.InvalidV

[Touch-packages] [Bug 1991606] Update Released

2023-07-13 Thread Andreas Hasenack

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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 dput 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:
  Fix Released
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 dput 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:
  Fix Committed
Status in dput source package in Focal:
  Fix Released
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  Fix Committed
Status in python-debian source package in Focal:
  Fix Committed
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  Fix Released
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:
  Fix Committed
Status in dput source package in Jammy:
  Fix Released
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  Fix Committed
Status in python-debian source package in Jammy:
  Fix Committed
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 dput 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:
  Fix Released
Status in python-debian source package in Kinetic:
  Fix Committed
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
Status in dput source package in Lunar:
  Fix Released

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 2027575] Re: autopkgtest net is failing on 6.2 kernels with 'System is deadlocked on memory'

** Description changed:

[Impact]
In debian/tests/run-image we instantiate an image with 512Mb of ram, but
recent jammy/lunar 6.2 kernels need more than that.

Example of a test failure:

https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/i/initramfs-tools/20230619_135049_ab1cb@/log.gz

'net' test fails with a kernel panic due to out-of-memory.

+ It also relies on an existing and working cloud image. If the cloud
+ image is not available, the test will silently succeed.
+
[Fix]

- Increase the size to 1Gb.
+ The net autopkgtest was ported to the common test framework in
+ initramfs-tools 0.142ubuntu3. This makes the test more robust by relying
+ on the minimum needed for the integration test.

[Test Plan]
+
+ Check that the autopkgtest succeed or test it manually:
+
1. Download a lunar image:
$ autopkgtest-buildvm-ubuntu-cloud -v -a amd64 -r lunar
2. Run autotestpkg tests from initramfs-tools package. The "net" test is the
one that depends on the image instantiated by 'run-image'. The testcase should
complete successfully without the kernel panic.
$ autopkgtest initramfs-tools -- qemu autopkgtest-lunar-amd64.img

[Where problems could occur]
The usage of a larger image for the tests could fail if the the test system
is low on ram size.
-
- Notes:
- It seems Mantic already uses 1G, so nothing has to be changed there. I also
tested it locally and I confirm it works as expected there.

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

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

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

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

Title:
autopkgtest net is failing on 6.2 kernels with 'System is deadlocked
on memory'

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

Bug description:
[Impact]
In debian/tests/run-image we instantiate an image with 512Mb of ram, but
recent jammy/lunar 6.2 kernels need more than that.

Example of a test failure:

https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/i/initramfs-tools/20230619_135049_ab1cb@/log.gz

'net' test fails with a kernel panic due to out-of-memory.

It also relies on an existing and working cloud image. If the cloud
image is not available, the test will silently succeed.

[Fix]

The net autopkgtest was ported to the common test framework in
initramfs-tools 0.142ubuntu3. This makes the test more robust by
relying on the minimum needed for the integration test.

[Test Plan]

Check that the autopkgtest succeed or test it manually:

1. Download a lunar image:
$ autopkgtest-buildvm-ubuntu-cloud -v -a amd64 -r lunar
2. Run autotestpkg tests from initramfs-tools package. The "net" test is the
one that depends on the image instantiated by 'run-image'. The testcase should
complete successfully without the kernel panic.
$ autopkgtest initramfs-tools -- qemu autopkgtest-lunar-amd64.img

[Where problems could occur]
The usage of a larger image for the tests could fail if the the test system
is low on ram size.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2027575/+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 2026826] Re: glib2.0 (2.77.0 ) breaks Netplan build

2023-07-13 Thread Jeremy Bícha

I've cherry-picked the !3498 upstream merge proposal for this issue.

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

Title:
  glib2.0 (2.77.0 ) breaks Netplan build

Status in GLib:
  New
Status in glib2.0 package in Ubuntu:
  Fix Committed

Bug description:
  Netplan FTBFS as of the latest release of glib2.0 (2.77.0-0ubuntu1) in
  mantic-proposed.

  See: https://launchpad.net/ubuntu/+source/netplan.io/0.106.1-3

  When I downgrade glib in my sbuild environment, everything works as
  expected:

  $ apt install libglib2.0-0=2.76.3-1ubuntu1
  libglib2.0-bin=2.76.3-1ubuntu1 libglib2.0-dev=2.76.3-1ubuntu1
  libglib2.0-dev-bin=2.76.3-1ubuntu1 libglib2.0-data=2.76.3-1ubuntu1

  The build also works fine in Debian unstable, which is using glib2.0
  2.74.6-2.

  Netplan is using plenty of GLib's keyfile functions
  (https://docs.gtk.org/glib/struct.KeyFile.html), which seem to
  producing a different output with this newer release (some strange
  line breaks injected in the middle of a keyfile).

  
  Example keyfile from the test_wifis.test_wifi_wowlan test, that should be 
generated by Netplan and the way it fails:

  Expected output:
  ```
  [connection]
  id=netplan-wl0-homenet
  type=wifi
  interface-name=wl0

  [wifi]
  wake-on-wlan=330
  ssid=homenet
  mode=infrastructure

  [ipv4]
  method=link-local

  [ipv6]
  method=ignore
  ```

  Failure:
  ```
  E   AssertionError: '[con[88 
chars]330\n\nssid=homenet\nmode=infrastructure\n[ipv[44 chars]re\n' != '[con[88 
chars]330\nssid=homenet\nmode=infrastructure\n\n[ipv[44 chars]re\n'
  E [connection]
  E id=netplan-wl0-homenet
  E type=wifi
  E interface-name=wl0
  E 
  E [wifi]
  E wake-on-wlan=330
  E   - 
  E ssid=homenet
  E mode=infrastructure
  E   + 
  E [ipv4]
  E method=link-local
  E 
  E [ipv6]
  E method=ignore
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/2026826/+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 2027636] Re: [SRU] ucsi drivers missing in initramfs

Here is the debdiff for lunar with the autopkgtest fix. Also pushed to
https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/initramfs-
tools/+git/initramfs-tools/+ref/ubuntu/lunar

** Patch added: "initramfs-tools_0.142ubuntu2.1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2027636/+attachment/5686040/+files/initramfs-tools_0.142ubuntu2.1.debdiff

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

Title:
  [SRU] ucsi drivers missing in initramfs

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

Bug description:
  [Impact]

  Some systems rely on a USB type-C UCSI connection; without the
  corresponding driver in the initramfs, USB storage might not be
  accessible. This is notably affecting NVIDIA Tegra systems such as
  Jetson AGX or the IGX and prevents completing USB boot for
  installation purposes.

  The initramfs-tools package has a list of relevant USB drivers to
  include for the default MODULES=most configuration, but didn't list
  the recently introduced ucsi one.

  [ Test Plan ]

  The -generic kernel and probably all kernel flavors contain the ucsi driver. 
On jammy system, you can verify the current initrd doesn't contain 
typec_ucsi.ko by decompressing the initramfs and listing its files:
  $ lsinitramfs /boot/initrd.img-5.19.0-46-generic | grep typec_ucsi.ko

  After installing the updated initramfs-tools package, your current initramfs 
should be automatically rebuilt and pick up typec_ucsi.ko:
  $ lsinitramfs /boot/initrd.img-5.19.0-46-generic | grep typec_ucsi.ko
  usr/lib/modules/5.19.0-46-generic/kernel/drivers/usb/typec/ucsi/typec_ucsi.ko

  [ Where problems could occur ]

  This is making the initramfs slightly bigger. In my testing,
  typec_ucsi.ko was 99913B and /boot/initrd.img-5.19.0-46-generic grew
  by 93403B from 122298948B to 122392351B, so by less than 0.08%.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2027636/+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 1494240] Re: Xmir crashes immediately on startup using glamor on Nexus4

2023-07-13 Thread Daniel van Vugt

** Changed in: libepoxy (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => (unassigned)

** Changed in: libhybris (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => (unassigned)

** Changed in: xorg-server (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => (unassigned)

** Changed in: libepoxy (Ubuntu)
   Status: Triaged => Won't Fix

** Changed in: libhybris (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Xmir crashes immediately on startup using glamor on Nexus4

Status in libepoxy package in Ubuntu:
  Won't Fix
Status in libhybris package in Ubuntu:
  Won't Fix
Status in xorg-server package in Ubuntu:
  Won't Fix

Bug description:
  Xmir crashes immediately on startup using glamor on Nexus4.

  glamor GL version: OpenGL ES 3.0 V@53.0 AU@  (CL@)
  ...
  glamor GLSL version: OpenGL ES GLSL ES 3.00
  (EE)
  (EE) Backtrace:
  (EE)
  (EE) Segmentation fault at address 0x0
  (EE)
  Fatal server error:
  (EE) Caught signal 11 (Segmentation fault). Server aborting
  (EE)

  The stack trace is lost. However the problem appears to be the
  glGetStringi() function. This function is new in GLESv3 and libepoxy
  only uses it because the GLES version is 3.0 on mako. However,
  libhybris fails to implement glGetStringi() and forward it to the
  driver correctly. At least that seems to be the problem. Our hybris
  GLESv2 is missing the function but the Android GLESv2 on the device
  has it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libepoxy/+bug/1494240/+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 2027636] Re: [SRU] ucsi drivers missing in initramfs

Here is the debdiff for jammy with the autopkgtest fix. Also pushed to
https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/initramfs-
tools/+git/initramfs-tools/+ref/ubuntu/jammy

** Patch added: "initramfs-tools_0.140ubuntu13.3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2027636/+attachment/5686037/+files/initramfs-tools_0.140ubuntu13.3.debdiff

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

Title:
  [SRU] ucsi drivers missing in initramfs

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

Bug description:
  [Impact]

  Some systems rely on a USB type-C UCSI connection; without the
  corresponding driver in the initramfs, USB storage might not be
  accessible. This is notably affecting NVIDIA Tegra systems such as
  Jetson AGX or the IGX and prevents completing USB boot for
  installation purposes.

  The initramfs-tools package has a list of relevant USB drivers to
  include for the default MODULES=most configuration, but didn't list
  the recently introduced ucsi one.

  [ Test Plan ]

  The -generic kernel and probably all kernel flavors contain the ucsi driver. 
On jammy system, you can verify the current initrd doesn't contain 
typec_ucsi.ko by decompressing the initramfs and listing its files:
  $ lsinitramfs /boot/initrd.img-5.19.0-46-generic | grep typec_ucsi.ko

  After installing the updated initramfs-tools package, your current initramfs 
should be automatically rebuilt and pick up typec_ucsi.ko:
  $ lsinitramfs /boot/initrd.img-5.19.0-46-generic | grep typec_ucsi.ko
  usr/lib/modules/5.19.0-46-generic/kernel/drivers/usb/typec/ucsi/typec_ucsi.ko

  [ Where problems could occur ]

  This is making the initramfs slightly bigger. In my testing,
  typec_ucsi.ko was 99913B and /boot/initrd.img-5.19.0-46-generic grew
  by 93403B from 122298948B to 122392351B, so by less than 0.08%.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2027636/+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 2026826] Re: glib2.0 (2.77.0 ) breaks Netplan build

2023-07-13 Thread Bug Watch Updater

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

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

Title:
  glib2.0 (2.77.0 ) breaks Netplan build

Status in GLib:
  New
Status in glib2.0 package in Ubuntu:
  In Progress

Bug description:
  Netplan FTBFS as of the latest release of glib2.0 (2.77.0-0ubuntu1) in
  mantic-proposed.

  See: https://launchpad.net/ubuntu/+source/netplan.io/0.106.1-3

  When I downgrade glib in my sbuild environment, everything works as
  expected:

  $ apt install libglib2.0-0=2.76.3-1ubuntu1
  libglib2.0-bin=2.76.3-1ubuntu1 libglib2.0-dev=2.76.3-1ubuntu1
  libglib2.0-dev-bin=2.76.3-1ubuntu1 libglib2.0-data=2.76.3-1ubuntu1

  The build also works fine in Debian unstable, which is using glib2.0
  2.74.6-2.

  Netplan is using plenty of GLib's keyfile functions
  (https://docs.gtk.org/glib/struct.KeyFile.html), which seem to
  producing a different output with this newer release (some strange
  line breaks injected in the middle of a keyfile).

  
  Example keyfile from the test_wifis.test_wifi_wowlan test, that should be 
generated by Netplan and the way it fails:

  Expected output:
  ```
  [connection]
  id=netplan-wl0-homenet
  type=wifi
  interface-name=wl0

  [wifi]
  wake-on-wlan=330
  ssid=homenet
  mode=infrastructure

  [ipv4]
  method=link-local

  [ipv6]
  method=ignore
  ```

  Failure:
  ```
  E   AssertionError: '[con[88 
chars]330\n\nssid=homenet\nmode=infrastructure\n[ipv[44 chars]re\n' != '[con[88 
chars]330\nssid=homenet\nmode=infrastructure\n\n[ipv[44 chars]re\n'
  E [connection]
  E id=netplan-wl0-homenet
  E type=wifi
  E interface-name=wl0
  E 
  E [wifi]
  E wake-on-wlan=330
  E   - 
  E ssid=homenet
  E mode=infrastructure
  E   + 
  E [ipv4]
  E method=link-local
  E 
  E [ipv6]
  E method=ignore
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/2026826/+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 2027575] Re: autopkgtest net is failing on 6.2 kernels with 'System is deadlocked on memory'

I'll go ahead and prepare a combined debdiff to also address bug
#2027636.

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

Title:
  autopkgtest net is failing on 6.2 kernels with 'System is deadlocked
  on memory'

Status in initramfs-tools package in Ubuntu:
  New
Status in initramfs-tools source package in Jammy:
  New
Status in initramfs-tools source package in Lunar:
  New

Bug description:
  [Impact]
  In debian/tests/run-image we instantiate an image with 512Mb of ram, but 
recent jammy/lunar 6.2 kernels need more than that.

  Example of a test failure:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/i/initramfs-tools/20230619_135049_ab1cb@/log.gz

  'net' test fails with a kernel panic due to out-of-memory.

  [Fix]

  Increase the size to 1Gb.

  [Test Plan]
  1. Download a lunar image:
  $ autopkgtest-buildvm-ubuntu-cloud -v -a amd64 -r lunar
  2. Run autotestpkg tests from initramfs-tools package. The "net" test is the 
one that depends on the image instantiated by 'run-image'. The testcase should 
complete successfully without the kernel panic.
  $ autopkgtest initramfs-tools -- qemu autopkgtest-lunar-amd64.img

  [Where problems could occur]
  The usage of a larger image for the tests could fail if the the test system 
is low on ram size.

  Notes:
  It seems Mantic already uses 1G, so nothing has to be changed there. I also 
tested it locally and I confirm it works as expected there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2027575/+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 2027636] Re: [SRU] ucsi drivers missing in initramfs

I'll go ahead and prepare a combined debdiff for both issues.

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

Title:
  [SRU] ucsi drivers missing in initramfs

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

Bug description:
  [Impact]

  Some systems rely on a USB type-C UCSI connection; without the
  corresponding driver in the initramfs, USB storage might not be
  accessible. This is notably affecting NVIDIA Tegra systems such as
  Jetson AGX or the IGX and prevents completing USB boot for
  installation purposes.

  The initramfs-tools package has a list of relevant USB drivers to
  include for the default MODULES=most configuration, but didn't list
  the recently introduced ucsi one.

  [ Test Plan ]

  The -generic kernel and probably all kernel flavors contain the ucsi driver. 
On jammy system, you can verify the current initrd doesn't contain 
typec_ucsi.ko by decompressing the initramfs and listing its files:
  $ lsinitramfs /boot/initrd.img-5.19.0-46-generic | grep typec_ucsi.ko

  After installing the updated initramfs-tools package, your current initramfs 
should be automatically rebuilt and pick up typec_ucsi.ko:
  $ lsinitramfs /boot/initrd.img-5.19.0-46-generic | grep typec_ucsi.ko
  usr/lib/modules/5.19.0-46-generic/kernel/drivers/usb/typec/ucsi/typec_ucsi.ko

  [ Where problems could occur ]

  This is making the initramfs slightly bigger. In my testing,
  typec_ucsi.ko was 99913B and /boot/initrd.img-5.19.0-46-generic grew
  by 93403B from 122298948B to 122392351B, so by less than 0.08%.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2027636/+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 2027674] Re: apt dist-upgrade shows crap messages (really poor user experience)

2023-07-13 Thread Julian Andres Klode

apt is not responsible for ubuntu pro messages. As advertised by the
introductory message you can turn off pro's news feature with sudo pro
config set apt_news=False

** Package changed: apt (Ubuntu) => ubuntu-advantage-tools (Ubuntu)

** Changed in: ubuntu-advantage-tools (Ubuntu)
   Status: New => Opinion

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

Title:
  apt dist-upgrade shows crap messages (really poor user experience)

Status in ubuntu-advantage-tools package in Ubuntu:
  Opinion

Bug description:
  I executed following in terminal

  $ sudo apt update && sudo apt dist-upgrade

  and received following mess:

  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  Get more security updates through Ubuntu Pro with 'esm-apps' enabled:
vlc-plugin-qt libvlc5 libimage-magick-perl vlc-data maven libvlccore9 vlc
imagemagick vlc-bin libjs-jquery-ui vlc-l10n libmaven3-core-java
libavdevice58 ffmpeg libopenexr25 libmagick++-6.q16-8 python3-scipy
libpostproc55 libmagickcore-6.q16-6-extra vlc-plugin-samba libavcodec58
libimage-magick-q16-perl libmagickwand-6.q16-6 vlc-plugin-notify libavutil56
imagemagick-6.q16 libswscale5 libeditorconfig0 libmagickcore-6.q16-6
vlc-plugin-access-extra vlc-plugin-skins2 vlc-plugin-video-splitter
libswresample3 imagemagick-6-common vlc-plugin-video-output libavformat58
libvlc-bin vlc-plugin-base vlc-plugin-visualization libavfilter7
  Learn more about Ubuntu Pro at https://ubuntu.com/pro
  #
  # An OpenSSL vulnerability has recently been fixed with USN-6188-1 & 6119-1:
  # CVE-2023-2650: possible DoS translating ASN.1 object identifiers.
  # Ensure you have updated the package to its latest version.
  #
  The following packages have been kept back:
gjs libgjs0g libspeechd2 python3-speechd speech-dispatcher 
speech-dispatcher-audio-plugins speech-dispatcher-espeak-ng
  The following packages will be upgraded:
alsa-ucm-conf debootstrap dkms ghostscript ghostscript-x gir1.2-adw-1 
gir1.2-gnomedesktop-3.0 gir1.2-mutter-10 gnome-desktop3-data gnome-shell
gnome-shell-common gnome-shell-extension-prefs initramfs-tools 
initramfs-tools-bin initramfs-tools-core iotop libadwaita-1-0 libgnome-bg-4-1
libgnome-desktop-3-19 libgnome-desktop-4-1 libgs9 libgs9-common libllvm15 
libllvm15:i386 libmutter-10-0 libruby3.0 libvirt-clients
libvirt-daemon libvirt-daemon-config-network libvirt-daemon-config-nwfilter 
libvirt-daemon-driver-qemu libvirt-daemon-driver-storage-rbd
libvirt-daemon-system libvirt-daemon-system-systemd libvirt0 mutter 
mutter-common python3-ubuntutools ruby3.0 thunderbird
thunderbird-gnome-support thunderbird-locale-fi ubuntu-advantage-tools 
ubuntu-dev-tools
  44 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
  11 standard LTS security updates
  Need to get 136 MB of archives.
  After this operation, 30,7 kB of additional disk space will be used.
  Do you want to continue? [Y/n]

  
  This has two big problems:

  (1) Ubuntu Pro ad cannot be disabled which causes lots of extra
  clutter on the output which will result in *training people to skip
  reading* the output of dist-upgdade. This is obviously a big problem
  and to "fix" that problem, new "important" message has been prefixed
  with "# " to make it more visible. If this trend continues, I'm sure
  next message will have "# * NOTICE THIS IMPORTANT
  MESSAGE!!#"!"!!! *" to make people notice the important part.
  Command line administrative tools should be about real stuff, not a
  shouting contest over ads. If you truly think ads should be enforced,
  keep it to the login message only.

  (2) The new message is unneeded crap about unspecified openssl package
  *that I already have installed*! I found this by googling the warning
  message and finding page https://ubuntu.com/security/CVE-2023-2650
  which clearly tells me that jammy has this bug fixed in package
  openssl version 3.0.2-0ubuntu1.10.

  
  If you think that the message about CVE-2023-2650 is important enough to be 
displayed even if the package has already been installed ("tell friends about 
this"), then very minimum should be explicitly saying the package name and 
minimum version with the fix. Only having text "the package" doesn't cut.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.4.9
  ProcVersionSignature: Ubuntu 5.19.0-1027.28~22.04.1-lowlatency 5.19.17
  Uname: Linux 5.19.0-1027-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Thu Jul 13 13:04:19 2023
  InstallationDate: Installed on 2022-03-25 (475 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  RebootRequiredPkgs: Error: path contained s

[Touch-packages] [Bug 2027674] [NEW] apt dist-upgrade shows crap messages (really poor user experience)

2023-07-13 Thread Mikko Rantalainen

Public bug reported:

I executed following in terminal

$ sudo apt update && sudo apt dist-upgrade

and received following mess:

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
Get more security updates through Ubuntu Pro with 'esm-apps' enabled:
  vlc-plugin-qt libvlc5 libimage-magick-perl vlc-data maven libvlccore9 vlc
  imagemagick vlc-bin libjs-jquery-ui vlc-l10n libmaven3-core-java
  libavdevice58 ffmpeg libopenexr25 libmagick++-6.q16-8 python3-scipy
  libpostproc55 libmagickcore-6.q16-6-extra vlc-plugin-samba libavcodec58
  libimage-magick-q16-perl libmagickwand-6.q16-6 vlc-plugin-notify libavutil56
  imagemagick-6.q16 libswscale5 libeditorconfig0 libmagickcore-6.q16-6
  vlc-plugin-access-extra vlc-plugin-skins2 vlc-plugin-video-splitter
  libswresample3 imagemagick-6-common vlc-plugin-video-output libavformat58
  libvlc-bin vlc-plugin-base vlc-plugin-visualization libavfilter7
Learn more about Ubuntu Pro at https://ubuntu.com/pro
#
# An OpenSSL vulnerability has recently been fixed with USN-6188-1 & 6119-1:
# CVE-2023-2650: possible DoS translating ASN.1 object identifiers.
# Ensure you have updated the package to its latest version.
#
The following packages have been kept back:
  gjs libgjs0g libspeechd2 python3-speechd speech-dispatcher 
speech-dispatcher-audio-plugins speech-dispatcher-espeak-ng
The following packages will be upgraded:
  alsa-ucm-conf debootstrap dkms ghostscript ghostscript-x gir1.2-adw-1 
gir1.2-gnomedesktop-3.0 gir1.2-mutter-10 gnome-desktop3-data gnome-shell
  gnome-shell-common gnome-shell-extension-prefs initramfs-tools 
initramfs-tools-bin initramfs-tools-core iotop libadwaita-1-0 libgnome-bg-4-1
  libgnome-desktop-3-19 libgnome-desktop-4-1 libgs9 libgs9-common libllvm15 
libllvm15:i386 libmutter-10-0 libruby3.0 libvirt-clients
  libvirt-daemon libvirt-daemon-config-network libvirt-daemon-config-nwfilter 
libvirt-daemon-driver-qemu libvirt-daemon-driver-storage-rbd
  libvirt-daemon-system libvirt-daemon-system-systemd libvirt0 mutter 
mutter-common python3-ubuntutools ruby3.0 thunderbird
  thunderbird-gnome-support thunderbird-locale-fi ubuntu-advantage-tools 
ubuntu-dev-tools
44 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
11 standard LTS security updates
Need to get 136 MB of archives.
After this operation, 30,7 kB of additional disk space will be used.
Do you want to continue? [Y/n]


This has two big problems:

(1) Ubuntu Pro ad cannot be disabled which causes lots of extra clutter
on the output which will result in *training people to skip reading* the
output of dist-upgdade. This is obviously a big problem and to "fix"
that problem, new "important" message has been prefixed with "# " to
make it more visible. If this trend continues, I'm sure next message
will have "# * NOTICE THIS IMPORTANT MESSAGE!!#"!"!!! *" to
make people notice the important part. Command line administrative tools
should be about real stuff, not a shouting contest over ads. If you
truly think ads should be enforced, keep it to the login message only.

(2) The new message is unneeded crap about unspecified openssl package
*that I already have installed*! I found this by googling the warning
message and finding page https://ubuntu.com/security/CVE-2023-2650 which
clearly tells me that jammy has this bug fixed in package openssl
version 3.0.2-0ubuntu1.10.


If you think that the message about CVE-2023-2650 is important enough to be 
displayed even if the package has already been installed ("tell friends about 
this"), then very minimum should be explicitly saying the package name and 
minimum version with the fix. Only having text "the package" doesn't cut.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: apt 2.4.9
ProcVersionSignature: Ubuntu 5.19.0-1027.28~22.04.1-lowlatency 5.19.17
Uname: Linux 5.19.0-1027-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: MATE
Date: Thu Jul 13 13:04:19 2023
InstallationDate: Installed on 2022-03-25 (475 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: apt
UpgradeStatus: Upgraded to jammy on 2023-05-25 (48 days ago)

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


** Tags: amd64 apport-bug jammy

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

Title:
  apt dist-upgrade shows crap messages (really poor user experience)

Status in apt package in Ubuntu:
  New

Bug description:
  I executed following in terminal

  $ sudo apt update && sudo apt dist-upgrade

  and received following mess:

  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  Ge

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

The livecd-rootfs/2.765.20 regression is not caused by distro-info:
gzip: stdout: No space left on device

-- 
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 dput 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:
  Fix Released
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 dput 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:
  Fix Committed
Status in dput source package in Focal:
  Fix Committed
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  Fix Committed
Status in python-debian source package in Focal:
  Fix Committed
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  Fix Released
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:
  Fix Committed
Status in dput source package in Jammy:
  Fix Committed
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  Fix Committed
Status in python-debian source package in Jammy:
  Fix Committed
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 dput source package in Kinetic:
  Fix Committed
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  Fix Released
Status in python-debian source package in Kinetic:
  Fix Committed
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
Status in dput source package in Lunar:
  Fix Committed

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

[Touch-packages] [Bug 2027636] Re: [SRU] ucsi drivers missing in initramfs

** Also affects: initramfs-tools (Ubuntu Lunar)
   Importance: Undecided
   Status: New

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

Title:
  [SRU] ucsi drivers missing in initramfs

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

Bug description:
  [Impact]

  Some systems rely on a USB type-C UCSI connection; without the
  corresponding driver in the initramfs, USB storage might not be
  accessible. This is notably affecting NVIDIA Tegra systems such as
  Jetson AGX or the IGX and prevents completing USB boot for
  installation purposes.

  The initramfs-tools package has a list of relevant USB drivers to
  include for the default MODULES=most configuration, but didn't list
  the recently introduced ucsi one.

  [ Test Plan ]

  The -generic kernel and probably all kernel flavors contain the ucsi driver. 
On jammy system, you can verify the current initrd doesn't contain 
typec_ucsi.ko by decompressing the initramfs and listing its files:
  $ lsinitramfs /boot/initrd.img-5.19.0-46-generic | grep typec_ucsi.ko

  After installing the updated initramfs-tools package, your current initramfs 
should be automatically rebuilt and pick up typec_ucsi.ko:
  $ lsinitramfs /boot/initrd.img-5.19.0-46-generic | grep typec_ucsi.ko
  usr/lib/modules/5.19.0-46-generic/kernel/drivers/usb/typec/ucsi/typec_ucsi.ko

  [ Where problems could occur ]

  This is making the initramfs slightly bigger. In my testing,
  typec_ucsi.ko was 99913B and /boot/initrd.img-5.19.0-46-generic grew
  by 93403B from 122298948B to 122392351B, so by less than 0.08%.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2027636/+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 2027636] Re: [SRU] ucsi drivers missing in initramfs

** Description changed:

  [Impact]
  
  Some systems rely on a USB type-C UCSI connection; without the
  corresponding driver in the initramfs, USB storage might not be
  accessible. This is notably affecting NVIDIA Tegra systems such as
  Jetson AGX or the IGX and prevents completing USB boot for installation
  purposes.
  
  The initramfs-tools package has a list of relevant USB drivers to
  include for the default MODULES=most configuration, but didn't list the
  recently introduced ucsi one.
  
  [ Test Plan ]
  
  The -generic kernel and probably all kernel flavors contain the ucsi driver. 
On jammy system, you can verify the current initrd doesn't contain 
typec_ucsi.ko by decompressing the initramfs and listing its files:
- $ zstdcat /boot/initrd.img-5.19.0-46-generic >/tmp/initrd
- $ lsinitramfs /tmp/initrd |grep typec_ucsi.ko
- cpio: premature end of archive
- 
+ $ lsinitramfs /boot/initrd.img-5.19.0-46-generic | grep typec_ucsi.ko
  
  After installing the updated initramfs-tools package, your current initramfs 
should be automatically rebuilt and pick up typec_ucsi.ko:
- $ zstdcat /boot/initrd.img-5.19.0-46-generic >/tmp/initrd
- $ lsinitramfs /tmp/initrd |grep typec_ucsi.ko
+ $ lsinitramfs /boot/initrd.img-5.19.0-46-generic | grep typec_ucsi.ko
  usr/lib/modules/5.19.0-46-generic/kernel/drivers/usb/typec/ucsi/typec_ucsi.ko
- cpio: premature end of archive
  
  [ Where problems could occur ]
  
  This is making the initramfs slightly bigger. In my testing,
  typec_ucsi.ko was 99913B and /boot/initrd.img-5.19.0-46-generic grew by
  93403B from 122298948B to 122392351B, so by less than 0.08%.

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

Title:
  [SRU] ucsi drivers missing in initramfs

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

Bug description:
  [Impact]

  Some systems rely on a USB type-C UCSI connection; without the
  corresponding driver in the initramfs, USB storage might not be
  accessible. This is notably affecting NVIDIA Tegra systems such as
  Jetson AGX or the IGX and prevents completing USB boot for
  installation purposes.

  The initramfs-tools package has a list of relevant USB drivers to
  include for the default MODULES=most configuration, but didn't list
  the recently introduced ucsi one.

  [ Test Plan ]

  The -generic kernel and probably all kernel flavors contain the ucsi driver. 
On jammy system, you can verify the current initrd doesn't contain 
typec_ucsi.ko by decompressing the initramfs and listing its files:
  $ lsinitramfs /boot/initrd.img-5.19.0-46-generic | grep typec_ucsi.ko

  After installing the updated initramfs-tools package, your current initramfs 
should be automatically rebuilt and pick up typec_ucsi.ko:
  $ lsinitramfs /boot/initrd.img-5.19.0-46-generic | grep typec_ucsi.ko
  usr/lib/modules/5.19.0-46-generic/kernel/drivers/usb/typec/ucsi/typec_ucsi.ko

  [ Where problems could occur ]

  This is making the initramfs slightly bigger. In my testing,
  typec_ucsi.ko was 99913B and /boot/initrd.img-5.19.0-46-generic grew
  by 93403B from 122298948B to 122392351B, so by less than 0.08%.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2027636/+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 1974483] Re: autoinstall ssh:install-server:false is misleading in 22.04

2023-07-13 Thread Nobuto Murata

fwiw, this worked for me with 22.04 LTS ISO.


#cloud-config
autoinstall:
  version: 1
  identity:
hostname: ubuntu-server
username: ubuntu
# password=ubuntu
password: 
"$6$exDY1mhS4KUYCE/2$zmn9ToZwTKLhCw.b4/b.ZRTIZM30JZ4QrOQ2aOXJ8yk96xpcCof0kxKwuX1kqLG/ygbJ1f8wxED22bTL4F46P0"
  ssh:
install-server: yes  # https://launchpad.net/bugs/1974483
allow-pw: no


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

Title:
  autoinstall ssh:install-server:false is misleading in 22.04

Status in subiquity:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-meta source package in Jammy:
  Confirmed

Bug description:
  With 22.04, openssh-server is baked into the image curtin copies to
  the target.  The ssh:install-server key no longer controls whether
  openssh-server gets installed.  It should be easy enough to have the
  bit of code that installs openssh-server when the key is true also
  remove it when the key is false.

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1974483/+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 1974483] Re: autoinstall ssh:install-server:false is misleading in 22.04

2023-07-13 Thread Andreas Lindhé

It seems to me like `allow-pw: false` does not work either. Could that
also be a side effect of 22.04 having the server built in?

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

Title:
  autoinstall ssh:install-server:false is misleading in 22.04

Status in subiquity:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-meta source package in Jammy:
  Confirmed

Bug description:
  With 22.04, openssh-server is baked into the image curtin copies to
  the target.  The ssh:install-server key no longer controls whether
  openssh-server gets installed.  It should be easy enough to have the
  bit of code that installs openssh-server when the key is true also
  remove it when the key is false.

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1974483/+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 2027581] Re: useradd grants root privileges to admin user

2023-07-13 Thread Oliver Grawert

On UbuntuCore the default user added by console-conf is automatically
granted passwordless sudo.

the /etc/group file is on a readonly filesystem and contains the sudo
group, this usually prevents you from accidentially adding extra sudo
users (UbuntuCore exclusively uses /var/lib/extrausers for addtional
users and snapd (being the management authority) normally creates
snippets in /etc/sudoers.d on a per user basis)

in earlier UbuntuCore releases the admin group still existed in the
readonly /etc/group so adding such a user would have been prevented by
the readonly state of the file.

now you can unconditionally create such a user and automatically get
sudo privs without having to go through a system-user assertion managed
by snapd (which is the only process that can create snippets in
/etc/sudoers.d on these systems)

if not considered a security hole (due to the fact that you can
circumvent the documented locked down user creation process via system-
user-assertions for this type of systems) this is at least a heavy
inconsistency ... we should either add an admin group to the core snaps
readonly /etc/group or wipe the admin line from sudoers so we match the
documented behavior.

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

Title:
  useradd grants root privileges to admin user

Status in sudo package in Ubuntu:
  New

Bug description:
  Hi,

  As part of the Ubuntu Core 20, if a developer creates a user named
  either admin or Admin, it will have  root privileges by default. I
  think that this is a security issue but it requires input from the
  security engineers/specialists.

  Basically, if you look at the sudoers file under `/etc/sudoers`, you
  will realize the following line;

  ```
  # Members of the admin group may gain root privileges
  %admin ALL=(ALL) ALL
  ```

  And if someone creates a user by using admin as name, the system
  provide root privilege.

  ```
  sudo useradd -s /bin/bash -u 8003 -d /home/Admin --extrausers Admin
  iotuc@ubuntu:~$ su Admin
  Password:
  Admin@ubuntu:/home/iotuc$ cat /etc/sudoers
  cat: /etc/sudoers: Permission denied
  Admin@ubuntu:/home/iotuc$ sudo cat /etc/sudoers
  [sudo] password for Admin:
  #
  # This file MUST be edited with the 'visudo' command as root.
  #
  # Please consider adding local content in /etc/sudoers.d/ instead of
  # directly modifying this file.
  #
  # See the man page for details on how to write a sudoers file.
  #
  Defaultsenv_reset
  Defaultsmail_badpass
  Defaults
secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin"
  # Host alias specification
  # User alias specification
  # Cmnd alias specification
  # User privilege specification
  rootALL=(ALL:ALL) ALL
  # Members of the admin group may gain root privileges
  %admin ALL=(ALL) ALL
  # Allow members of group sudo to execute any command
  %sudoALL=(ALL:ALL) ALL
  # See sudoers(5) for more information on "#include" directives:
  #includedir /etc/sudoers.d
  Admin@ubuntu:/home/iotuc$
  ```

  Similarly, if I create a username called aydogar, it does not have
  root privilege and this is expected.

  ```
  sudo useradd -s /bin/bash -u 8004 -d /home/aydogar --extrausers aydogar
  iotuc@ubuntu:~$ su aydogar
  Password:
  aydogar@ubuntu:/home/iotuc$ cat /etc/sudoers
  cat: /etc/sudoers: Permission denied
  aydogar@ubuntu:/home/iotuc$ sudo cat /etc/sudoers
  [sudo] password for aydogar:
  aydogar is not in the sudoers file.  This incident will be reported.
  aydogar@ubuntu:/home/iotuc$
  ```

  I think, this is a bug but would love here other ideas and inputs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2027581/+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 2027636] Re: [SRU] ucsi drivers missing in initramfs