date:20230609

Stefano, thanks, that does feel much closer to a test case that models a
real-world scenario.

The doubt I still have is, if you're pulling something as fundamental as
setuptools from pip, why are you using virtualenv --system-site-packages
at all?  Is this because it's embedded in third-party code that's hard
for the user to change?

This fails:

$ sudo apt install python3-virtualenv python3-distro-info
$ virtualenv --system-site-packages foo
$ foo/bin/python -m pip install -U setuptools
$ foo/bin/python -c "import pkg_resources; pkg_resources.require('distro-info')"

But this succeeds:

$ sudo apt install python3-virtualenv python3-distro-info
$ virtualenv --system-site-packages foo
$ foo/bin/python -m pip install -U setuptools
$ foo/bin/python -c "import pkg_resources; pkg_resources.require('filelock')"

as does this:

$ sudo apt install python3-virtualenv python3-distro-info
$ virtualenv --system-site-packages foo
$ foo/bin/python -m pip install -U setuptools distro-info
$ foo/bin/python -c "import pkg_resources; pkg_resources.require('distro-info')"

It's only when trying to use a setuptools newer than the one in the
distro, with distro versions of specific python modules, that I can
reproduce a failure.  So, uh, why do that?

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  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 drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  Fix Released
Status in python-debian source package in Kinetic:
  Incomplete
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New

Bug description:
  [ Impact ]

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

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

[Touch-packages] [Bug 1980991] Re: /usr/sbin/on_ac_power incorrectly reporting ac power status

2023-06-09 Thread Gordon Lack

/lib/systemd/systemd-ac-power works (on lunar). on_ac_power still does
not.

Perhaps on_ac_power should just be made a symlink to this - or the
script should exec that systemd executable if it exists?

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

Title:
  /usr/sbin/on_ac_power incorrectly reporting ac power status

Status in powermgmt-base package in Ubuntu:
  Triaged
Status in powermgmt-base source package in Kinetic:
  Triaged

Bug description:
  Good afternoon, folks.

  I believe I discovered a bug in the /usr/sbin/on_ac_power script. I
  have a Dell OptiPlex 5090 host that has an entry in
  /sys/class/power_supply for "ucsi-source-psy-USBC000:001". I believe
  this is the USB-C power delivery port on the front of the chassis. The
  issue I'm encountering is that /usr/sbin/on_ac_power is exiting with
  code 1 which states: (1 (false) if not on AC power) when that isn't
  the case.

  This looks to be because of the ucsi-source-psy-USBC000:001 entry
  reporting the "online" status as 0, presumably because nothing is
  currently connected to that USB-C port.

  This causes /usr/sbin/on_ac_power to incorrectly report that the
  machine isn't connected to AC power and causes other utilities like
  unattended-upgrades to quit when using the default configuration since
  it believes the machine isn't connected to AC power.

  There is a workaround with unattended-upgrades where you can specify
  it to run regardless of if AC power is connected, but as more and more
  chassis implement power-delivery USB-C ports I foresee this becoming
  more of an issue.

  I'm not sure if it's anything to look into, but I figured I would
  share my findings. Please let me know if you have any questions or if
  I can provide any additional information, troubleshooting, or testing.

  Thanks!
  -Kevin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1980991/+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 1998872] Re: unattended-updates failing in kinetic as AC power detection is bugged

2023-06-09 Thread Gordon Lack

I've tested /lib/systemd/systemd-ac-power on my laptop (which gives 0/1
for mains/battery) and it now returns 0 (mains) for my NUC10i3FNYHN.

(But the fix isn't in Lunar for on_ac_power.)

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

Title:
  unattended-updates failing in kinetic as AC power detection is bugged

Status in e2fsprogs package in Ubuntu:
  New
Status in logrotate package in Ubuntu:
  New
Status in man-db package in Ubuntu:
  New
Status in plocate package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  New
Status in e2fsprogs source package in Kinetic:
  New
Status in logrotate source package in Kinetic:
  New
Status in man-db source package in Kinetic:
  New
Status in plocate source package in Kinetic:
  New
Status in systemd source package in Kinetic:
  Won't Fix
Status in unattended-upgrades source package in Kinetic:
  New

Bug description:
  The ConditionACPower testing code does not work correctly on some
  systems. This prevents the unattended-updates systemd service running
  as it thinks that a system (a NUC10i3FNYHN) is running on battery. It
  isn't - it just has  a power supply that can *provide* power over USB.

  This (unattended-updrades) was OK in Jammy, but started to fail when I
  upgraded to Kinetic.

  (A systemd override file for apt-daily-upgrade.service to remove the
  condition gets the service working again.)

  The problem is similar (or perhaps identical) to the problem with the
  on_ac_power script (from the powermgmt-base package).

  That has been reported in bug #1980991.  There are more details there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1998872/+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] Please test proposed package

Hello Robert, or anyone else affected,

Accepted cloud-init into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/23.2-0ubuntu0~20.04.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

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.
  5. Assert no stray uec-images or invalid ec2-images tags on openstack.

  scriptlet TBD:

  cat > openstack.json  ec2.json << EOF
  {
    "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
   lxc launch ubuntu-daily:$release sru-$release
   lxc exec sru-f -- cloud-init status --wait --long
   lxc exec sru-f -- apport-bug cloud-init
   # step through prompts and select view/save report
   # inspect tags to assert cloud platform is proper tags where value is 
non-empty/null
  CloudID, CloudName, CloudArchitecture CloudPlatform, CloudRegion, 
CloudSubPlatform

   echo ### validate openstack apport-bug
   lxc file push openstack.json dev-$release/run/cloud-init/instance-data.json
   lxc exec sru-f -- apport-bug cloud-init
   # step through prompts and select view/save report
   # inspect tags to assert cloud platform is proper tags where value is 
non-empty/null
  CloudID, CloudName, CloudArchitecture CloudPlatform, CloudRegion,

   echo ### validate ec2 apport-bug
   lxc file push ec2.json dev-$release/run/cloud-init/instance-data.json
   lxc exec sru-f -- apport-bug cloud-init
   # step through prompts and select view/save report
   # inspect tags to assert cloud platform is proper tags where value is 
non-empty/null
  CloudID, CloudName, CloudArchitecture CloudPlatform, CloudRegion,

  done

  [ Where problems could occur ]
  apport-bug could traceback on poor logic preventing simple bug filing at 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.  Thus we have bugs like bug #1722946 that are 
tagged as an 'ec2-images' bug which are clearly on openstack
   - Marking all bugs that have cloud-init but no EC2 metadata source as an 
'uec-images' bug uses a name that no longer has

[Touch-packages] [Bug 1724623] Please test proposed package

Hello Robert, or anyone else affected,

Accepted cloud-init into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/23.2-0ubuntu0~22.04.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed-focal

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

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.
  5. Assert no stray uec-images or invalid ec2-images tags on openstack.

  scriptlet TBD:

  cat > openstack.json  ec2.json << EOF
  {
    "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
   lxc launch ubuntu-daily:$release sru-$release
   lxc exec sru-f -- cloud-init status --wait --long
   lxc exec sru-f -- apport-bug cloud-init
   # step through prompts and select view/save report
   # inspect tags to assert cloud platform is proper tags where value is 
non-empty/null
  CloudID, CloudName, CloudArchitecture CloudPlatform, CloudRegion, 
CloudSubPlatform

   echo ### validate openstack apport-bug
   lxc file push openstack.json dev-$release/run/cloud-init/instance-data.json
   lxc exec sru-f -- apport-bug cloud-init
   # step through prompts and select view/save report
   # inspect tags to assert cloud platform is proper tags where value is 
non-empty/null
  CloudID, CloudName, CloudArchitecture CloudPlatform, CloudRegion,

   echo ### validate ec2 apport-bug
   lxc file push ec2.json dev-$release/run/cloud-init/instance-data.json
   lxc exec sru-f -- apport-bug cloud-init
   # step through prompts and select view/save report
   # inspect tags to assert cloud platform is proper tags where value is 
non-empty/null
  CloudID, CloudName, CloudArchitecture CloudPlatform, CloudRegion,

  done

  [ Where problems could occur ]
  apport-bug could traceback on poor logic preventing simple bug filing at 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.  Thus we have bugs like bug #1722946 that are 
tagged as an 'ec2-images' bug which are clearly on openstack
   -

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

Hello Robert, or anyone else affected,

Accepted cloud-init into kinetic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/cloud-
init/23.2-0ubuntu0~22.10.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
kinetic to verification-done-kinetic. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-kinetic. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed verification-needed-kinetic

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

** Tags added: verification-needed-jammy

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

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.
  5. Assert no stray uec-images or invalid ec2-images tags on openstack.

  scriptlet TBD:

  cat > openstack.json  ec2.json << EOF
  {
    "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
   lxc launch ubuntu-daily:$release sru-$release
   lxc exec sru-f -- cloud-init status --wait --long
   lxc exec sru-f -- apport-bug cloud-init
   # step through prompts and select view/save report
   # inspect tags to assert cloud platform is proper tags where value is 
non-empty/null
  CloudID, CloudName, CloudArchitecture CloudPlatform, CloudRegion, 
CloudSubPlatform

   echo ### validate openstack apport-bug
   lxc file push openstack.json dev-$release/run/cloud-init/instance-data.json
   lxc exec sru-f -- apport-bug cloud-init
   # step through prompts and select view/save report
   # inspect tags to assert cloud platform is proper tags where value is 
non-empty/null
  CloudID, CloudName, CloudArchitecture CloudPlatform, CloudRegion,

   echo ### validate ec2 apport-bug
   lxc file push ec2.json dev-$release/run/cloud-init/instance-data.json
   lxc exec sru-f -- apport-bug cloud-init
   # step through prompts and select view/save report
   # inspect tags to assert cloud platform is proper tags where value is 
non-empty/null
  CloudID, CloudName, CloudArchitecture CloudPlatform, CloudRegion,

  done

  [ Where problems could occur ]
  apport-bug could traceback on poor logic preventing simple bug filing at 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

[Touch-packages] [Bug 1782577] Re: docker: impossible to create image with python3 because tzdata

** Changed in: debconf (Debian)
   Status: New => Fix Released

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

Title:
  docker: impossible to create image with python3 because tzdata

Status in cloud-images:
  New
Status in debconf package in Ubuntu:
  Confirmed
Status in debconf package in Debian:
  Fix Released

Bug description:
  In my application I have to use both "supervisor" and some ML stuff,
  so I need to include python-3, numpy and pandas

  FROM ubuntu:latest
  RUN apt-get update
  RUN apt-get install -y supervisor python3 python3-pip python3-pymongo 
python3-numpy python3-pandas

  This appends with the current ubuntu:latest

  sha256:30e04ddada6eb09c12330c7df72cad1573916c7100168c34076808169ff6d805

  When I try to make a built of this, I seems that python3 depends on
  tzdata (and many other things), but then it stops waiting for a user
  input, and I unable to send an input by hand or other way

  Setting up libldap-common (2.4.45+dfsg-1ubuntu1) ...
  Setting up libreadline7:amd64 (7.0-3) ...
  Setting up tzdata (2018d-1) ...
  debconf: unable to initialize frontend: Dialog
  debconf: (TERM is not set, so the dialog frontend is not usable.)
  debconf: falling back to frontend: Readline
  Configuring tzdata
  --

  Please select the geographic area in which you live. Subsequent configuration
  questions will narrow this down by presenting a list of cities, representing
  the time zones in which they are located.

1. Africa  4. Australia  7. Atlantic  10. Pacific  13. Etc
2. America 5. Arctic 8. Europe11. SystemV
3. Antarctica  6. Asia   9. Indian12. US
  Geographic area: 

  So I am unable to create my docker image!!

  This is some kind of regression, 2 weeks ago it worked

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1782577/+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 2019026] Re: systemd /tmp cleaning is suboptimal

(setting bug back to New because I don't see any request for
information)

** Changed in: systemd (Ubuntu)
   Status: Incomplete => 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/2019026

Title:
  systemd /tmp cleaning is suboptimal

Status in systemd package in Ubuntu:
  New

Bug description:
  Historically on Debian and Ubuntu, before systemd, the default
  handling of /tmp was to periodically, and at boot, remove all
  files/directories older than 30 days; and leave other contents alone.

  With the move to systemd, the "default" (really, hard-coded in
  /usr/lib/tmpfiles.d/tmp.conf) is to not clean /tmp periodically, but
  at boot to remove all contents.

  This is suboptimal for two reasons.

  By cleaning /tmp *only* at boot, if a system makes heavy use of /tmp
  and has lots of inodes under it, possibly due to failures of some
  process to clean up after itself, at boot the system will be
  unavailable for an unnecessarily long time while these files are
  removed.

  By cleaning *all* files under /tmp, this makes a reboot an Event where
  in-progress files may be unnecessarily lost.

  While the FHS does not *guarantee* that files under /tmp will persist
  across boot (because /tmp may be a tmpfs), it also does not *require*
  that /tmp be cleared on boot.

 Although data stored in /tmp may be deleted in a site-specific
 manner, it is recommended that files and directories located in
 /tmp be deleted whenever the system is booted.

 FHS added this recommendation on the basis of historical
 precedent and common practice, but did not make it a
 requirement because system administration is not within the
 scope of this standard.

  I therefore believe the correct value for /usr/lib/tmpfiles.d/tmp.conf
  to restore past behavior is 'd /tmp 1777 root root 30d'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2019026/+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 2019026] Re: systemd /tmp cleaning is suboptimal

The reason it's specifically important to me not to clean at boot is
that schroot bind mounts /tmp by default but does not bind mount
/var/tmp by default, so I am accustomed (since long before the systemd
behavior became the norm) to using this directory for sharing data
between the host system and chroots and relying on it persisting across
reboots (since it's not old).  (And I don't use /home because it's stuff
I *do* want garbage-collected for me - just not at reboot!)

When you say you've "become very accustomed to the current behavior
where /tmp is emptied on reboot" - how would it impact you if it was NOT
cleaned at reboot?

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

Title:
  systemd /tmp cleaning is suboptimal

Status in systemd package in Ubuntu:
  New

Bug description:
  Historically on Debian and Ubuntu, before systemd, the default
  handling of /tmp was to periodically, and at boot, remove all
  files/directories older than 30 days; and leave other contents alone.

  With the move to systemd, the "default" (really, hard-coded in
  /usr/lib/tmpfiles.d/tmp.conf) is to not clean /tmp periodically, but
  at boot to remove all contents.

  This is suboptimal for two reasons.

  By cleaning /tmp *only* at boot, if a system makes heavy use of /tmp
  and has lots of inodes under it, possibly due to failures of some
  process to clean up after itself, at boot the system will be
  unavailable for an unnecessarily long time while these files are
  removed.

  By cleaning *all* files under /tmp, this makes a reboot an Event where
  in-progress files may be unnecessarily lost.

  While the FHS does not *guarantee* that files under /tmp will persist
  across boot (because /tmp may be a tmpfs), it also does not *require*
  that /tmp be cleared on boot.

 Although data stored in /tmp may be deleted in a site-specific
 manner, it is recommended that files and directories located in
 /tmp be deleted whenever the system is booted.

 FHS added this recommendation on the basis of historical
 precedent and common practice, but did not make it a
 requirement because system administration is not within the
 scope of this standard.

  I therefore believe the correct value for /usr/lib/tmpfiles.d/tmp.conf
  to restore past behavior is 'd /tmp 1777 root root 30d'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2019026/+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-06-09 Thread Chad Smith

** Description changed:

- [ 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 
+ [ 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.
  5. Assert no stray uec-images or invalid ec2-images tags on openstack.
  
- 
  scriptlet TBD:
- 
  
  cat > openstack.json  ec2.son << EOF
+ cat > ec2.json << EOF
  {
-   "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"
-   }
+   "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
+  lxc launch ubuntu-daily:$release sru-$release
+  lxc exec sru-f -- cloud-init status --wait --long
+  lxc exec sru-f -- apport-bug cloud-init
+  # step through prompts and select view/save report
+  # inspect tags to assert cloud platform is proper tags where value is 
non-empty/null
+ CloudID, CloudName, CloudArchitecture CloudPlatform, CloudRegion, 
CloudSubPlatform
  
- for release in focal jammy kinetic lunar; do
-  lxc launch ubuntu-daily:$release sru-$release
-  lxc exec sru-f -- cloud-init status --wait --long
-  lxc exec sru-f -- apport-bug cloud-init
-  # step through prompts and select view/save report
-  # inspect tags to assert cloud platform is proper tags where value is 
non-empty/null
- CloudID, CloudName, CloudArchitecture CloudPlatform, CloudRegion, 
CloudSubPlatform
+  echo ### validate openstack apport-bug
+  lxc file push openstack.json dev-$release/run/cloud-init/instance-data.json
+  lxc exec sru-f -- apport-bug cloud-init
+  # step through prompts and select view/save report
+  # inspect tags to assert cloud platform is proper tags where value is 
non-empty/null
+ CloudID, CloudName, CloudArchitecture CloudPlatform, CloudRegion,
  
-  echo ### validate openstack apport-bug
-  lxc file push openstack.json dev-$release/run/cloud-init/instance-data,json
-  lxc exec sru-f -- apport-bug cloud-init
-  # step through prompts and select view/save report
-  # inspect tags to assert cloud platform is proper tags where value is 
non-empty/null
- CloudID, CloudName, CloudArchitecture CloudPlatform, CloudRegion, 
+  echo ### validate ec2 apport-bug
+  lxc file push ec2.json dev-$release/run/cloud-init/instance-data.json
+  lxc exec sru-f -- apport-bug cloud-init
+  # step through prompts and select view/save report
+  # inspect tags to assert cloud platform is proper tags where value is 
non-empty/null
+ CloudID, CloudName, CloudArchitecture CloudPlatform, CloudRegion,
  
-  echo ### validate ec2 apport-bug
-  lxc file push ec2.json dev-$release/run/cloud-init/instance-data,json
-  lxc exec sru-f -- apport-bug cloud-init
-  # step through prompts and select view/save report
-  # inspect tags to assert cloud platform is proper tags where value is 
non-empty/null
- CloudID, CloudName, CloudArchitecture CloudPlatform, CloudRegion, 
- 
- 
- done 
- 
+ done
  
  [ Where problems could occur ]
  apport-bug could traceback on poor logic preventing simple bug filing at 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

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

2023-06-09 Thread Chad Smith

** Description changed:

- add_cloud_info() in data/general-hooks/ubuntu.py needs an overhaul.
+ [ 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.
+ 5. Assert no stray uec-images or invalid ec2-images tags on openstack.
+ 
+ 
+ scriptlet TBD:
+ 
+ 
+ cat > openstack.json  ec2.son << EOF
+ {
+   "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
+  lxc launch ubuntu-daily:$release sru-$release
+  lxc exec sru-f -- cloud-init status --wait --long
+  lxc exec sru-f -- apport-bug cloud-init
+  # step through prompts and select view/save report
+  # inspect tags to assert cloud platform is proper tags where value is 
non-empty/null
+ CloudID, CloudName, CloudArchitecture CloudPlatform, CloudRegion, 
CloudSubPlatform
+ 
+  echo ### validate openstack apport-bug
+  lxc file push openstack.json dev-$release/run/cloud-init/instance-data,json
+  lxc exec sru-f -- apport-bug cloud-init
+  # step through prompts and select view/save report
+  # inspect tags to assert cloud platform is proper tags where value is 
non-empty/null
+ CloudID, CloudName, CloudArchitecture CloudPlatform, CloudRegion, 
+ 
+  echo ### validate ec2 apport-bug
+  lxc file push ec2.json dev-$release/run/cloud-init/instance-data,json
+  lxc exec sru-f -- apport-bug cloud-init
+  # step through prompts and select view/save report
+  # inspect tags to assert cloud platform is proper tags where value is 
non-empty/null
+ CloudID, CloudName, CloudArchitecture CloudPlatform, CloudRegion, 
+ 
+ 
+ done 
+ 
+ 
+ [ Where problems could occur ]
+ apport-bug could traceback on poor logic preventing simple bug filing at 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.  Thus we have bugs like bug #1722946 that are 
tagged as an 'ec2-images' bug which are clearly on openstack
   - Marking all bugs that have cloud-init but no EC2 metadata source as an 
'uec-images' bug uses a name that no longer has meaning.
  
  Solution:
   - If cloud-init is present, check for /etc/cloud/build.info to indicate an 
Ubuntu cloud images, tag as 'cloud-images'.  Pull the build_name and serial 
from that file into the bug comments.
   - If cloud-init is present, check for the presence of 
/run/cloud-init/cloud.cfg.  Parse this yaml to determine the datasource type.  
Add the datasource used to the bug comment.
  
  I have filed bug #1724626 to ask cloud-init development to surface more
  information from ds-identify to help ID the cloud so that we can better
  tag/annotate the bug.  There may also be some info we can get to
  indicate the image ID on more clouds than just AWS.  At a minimum I
  would like to see dsidentify make the EC2 platform it found available
  for consumers in cloud.cfg.  This would allow us to identify AWS EC2
  from look-alike datasources so that we can tag a bug as ec2-images for
  bug really on AWS and add EC2 specific fields to the
  description/attachments.

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

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

[Touch-packages] [Bug 2013072] Re: Missing symlink /sbin/resolvconf -> /bin/resolvectl makes openfortivpn mess with /etc/resolv.conf

This is done in the systemd-resolved package, which exists in Kinetic
and newer (previously systemd-resolved components were shipped in the
main systemd package).

However, I don't think this is something that we will SRU to Jammy or
Focal.

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

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

Title:
  Missing symlink /sbin/resolvconf -> /bin/resolvectl makes openfortivpn
  mess with /etc/resolv.conf

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  In jammy (22.04) and focal (20.04) the executable /usr/bin/resolvectl
  is provided by the package "systemd". If you install the packages
  libnss-resolve and openfortivpn and run "openfortivpn vpn.example.com
  -u user -v" you get undesired behavior:

  [...]
  INFO:   Adding VPN nameservers...
  DEBUG:  Attempting to modify /etc/resolv.conf directly.
  DEBUG:  Adding "nameserver 10.10.10.10", to /etc/resolv.conf.
  DEBUG:  Adding "search ~10.in-addr.arpa ~example.com", to /etc/resolv.conf.
  [...]

  resolvectl can emulate the behavior of resolvconf so if you create a
  symbolic link "sudo ln -s /usr/bin/resolvectl /sbin/resolvconf" then
  openfortivpn happily uses resolvconf instead of messing with
  /etc/resolv.conf:

  [...]
  INFO:   Adding VPN nameservers...
  DEBUG:  Attempting to run /sbin/resolvconf.
  DEBUG:  resolvconf_call: /sbin/resolvconf -a "ppp0.openfortivpn"
  [...]

  So it would be great if the symlink could be included in the package
  "systemd". Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2013072/+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 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)

2023-06-09 Thread Alexsander de Souza

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

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

Title:
  udev fails to make prctl() syscall with apparmor=0 (as used by maas by
  default)

Status in AppArmor:
  New
Status in MAAS:
  Fix Committed
Status in maas-images:
  Invalid
Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Invalid
Status in apparmor source package in Lunar:
  Confirmed
Status in linux source package in Lunar:
  Fix Committed
Status in systemd source package in Lunar:
  Invalid

Bug description:
  I'm assuming the image being used for these deploys is 20230417 or
  20230417.1 based on the fact that I saw a 6.2 kernel being used which
  I don't believe was part of the 20230319 serial. I don't have access
  to the maas server, so I can't directly check any log files.

  MAAS Version: 3.3.2

  Here's where the serial log indicates it can't download the squashfs. The 
full log is attached as scobee-lunar-no-squashfs.log (there are some other 
console message intermixed):
  no search or nameservers found in /run/net-BOOTIF.conf /run/net-*.conf 
/run/net6
  -*.conf
  :: 
root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.04/lunar/candi
  date/squa[  206.804704] Btrfs loaded, crc32c=crc32c-generic, zoned=yes, 
fsverity
  =yes
  shfs
  :: mount_squash downloading 
http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.0
  4/lunar/candidate/squashfs to /root.tmp.img
  Connecting to 10.229.32.21:5248 (10.229.32.21:5248)
  wget: can't connect to remote host (10.229.32.21): Network is unreachable
  :: mount -t squashfs -o loop  '/root.tmp.img' '/root.tmp'
  mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory
  done.

  Still gathering logs and info and will update as I go.

  
  Kernel Bug / Apparmor
  reproducer

  $ wget 
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-kernel
  $ wget 
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-initrd
  $ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd 
./boot-initrd -append 'console=ttyS0 break=modules apparmor=0'

  #start the VM
  
  Starting systemd-udevd version 252.5-2ubuntu3
  Spawning shell within the initramfs

  BusyBox v1.35.0 (Ubuntu 1:1.35.0-4ubuntu1) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  (initramfs) udevadm info --export-db
  Failed to set death signal: Invalid argument

  Observe that udevadm fails to setup death signal, with in systemd code
  is this

  
https://github.com/systemd/systemd/blob/08c2f9c626e0f0052d505b1b7e52f335c0fbfa1d/src/basic/process-
  util.c#L1252

  if (flags & (FORK_DEATHSIG|FORK_DEATHSIG_SIGINT))
  if (prctl(PR_SET_PDEATHSIG, (flags & FORK_DEATHSIG_SIGINT) ? 
SIGINT : SIGTERM) < 0) {
  log_full_errno(prio, errno, "Failed to set death 
signal: %m");
  _exit(EXIT_FAILURE);
  }

  
  workaround set kernel commandline to `apparmor=1`
  

  MAAS bug
  Why is maas setting `apparmor=0` ? Ubuntu shouldn't be used without apparmor. 
Even for deployment and commisioning.

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

2023-06-09 Thread Georgia Garcia

Hi Steve.
I updated the patches containing the requested changes and uploaded them to 
https://launchpad.net/~georgiag/+archive/ubuntu/lp1794064/+packages
Please let me know if you prefer I attached the debdiffs here.

I'm resubscribing ~ubuntu-sponsors. Thanks

** Patch removed: "evince_42.1-3ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581877/+files/evince_42.1-3ubuntu1.debdiff

** Patch removed: "evince_40.4-2ubuntu0.1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581878/+files/evince_40.4-2ubuntu0.1.debdiff

** Patch removed: "evince_3.36.10-0ubuntu1.1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581879/+files/evince_3.36.10-0ubuntu1.1.debdiff

** Patch removed: "evince_3.28.4-0ubuntu1.3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581880/+files/evince_3.28.4-0ubuntu1.3.debdiff

** Patch removed: "apparmor_3.0.4-2ubuntu3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581881/+files/apparmor_3.0.4-2ubuntu3.debdiff

** Patch removed: "apparmor_3.0.3-0ubuntu1.1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581882/+files/apparmor_3.0.3-0ubuntu1.1.debdiff

** Patch removed: "apparmor_2.13.3-7ubuntu5.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581884/+files/apparmor_2.13.3-7ubuntu5.2.debdiff

** Patch removed: "apparmor_2.12-4ubuntu5.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581885/+files/apparmor_2.12-4ubuntu5.2.debdiff

-- 
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:
  Confirmed
Status in evince package in Ubuntu:
  Incomplete
Status in apparmor source package in Jammy:
  Confirmed
Status in evince source package in Jammy:
  Incomplete
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 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)

2023-06-09 Thread Ubuntu Kernel Bot

This bug is awaiting verification that the linux-
nvidia-6.2/6.2.0-1003.3~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still exists, change the tag
'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-nvidia-6.2

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

Title:
  udev fails to make prctl() syscall with apparmor=0 (as used by maas by
  default)

Status in AppArmor:
  New
Status in MAAS:
  Fix Committed
Status in maas-images:
  Invalid
Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Invalid
Status in apparmor source package in Lunar:
  Confirmed
Status in linux source package in Lunar:
  Fix Committed
Status in systemd source package in Lunar:
  Invalid

Bug description:
  I'm assuming the image being used for these deploys is 20230417 or
  20230417.1 based on the fact that I saw a 6.2 kernel being used which
  I don't believe was part of the 20230319 serial. I don't have access
  to the maas server, so I can't directly check any log files.

  MAAS Version: 3.3.2

  Here's where the serial log indicates it can't download the squashfs. The 
full log is attached as scobee-lunar-no-squashfs.log (there are some other 
console message intermixed):
  no search or nameservers found in /run/net-BOOTIF.conf /run/net-*.conf 
/run/net6
  -*.conf
  :: 
root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.04/lunar/candi
  date/squa[  206.804704] Btrfs loaded, crc32c=crc32c-generic, zoned=yes, 
fsverity
  =yes
  shfs
  :: mount_squash downloading 
http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.0
  4/lunar/candidate/squashfs to /root.tmp.img
  Connecting to 10.229.32.21:5248 (10.229.32.21:5248)
  wget: can't connect to remote host (10.229.32.21): Network is unreachable
  :: mount -t squashfs -o loop  '/root.tmp.img' '/root.tmp'
  mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory
  done.

  Still gathering logs and info and will update as I go.

  
  Kernel Bug / Apparmor
  reproducer

  $ wget 
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-kernel
  $ wget 
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-initrd
  $ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd 
./boot-initrd -append 'console=ttyS0 break=modules apparmor=0'

  #start the VM
  
  Starting systemd-udevd version 252.5-2ubuntu3
  Spawning shell within the initramfs

  BusyBox v1.35.0 (Ubuntu 1:1.35.0-4ubuntu1) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  (initramfs) udevadm info --export-db
  Failed to set death signal: Invalid argument

  Observe that udevadm fails to setup death signal, with in systemd code
  is this

  
https://github.com/systemd/systemd/blob/08c2f9c626e0f0052d505b1b7e52f335c0fbfa1d/src/basic/process-
  util.c#L1252

  if (flags & (FORK_DEATHSIG|FORK_DEATHSIG_SIGINT))
  if (prctl(PR_SET_PDEATHSIG, (flags & FORK_DEATHSIG_SIGINT) ? 
SIGINT : SIGTERM) < 0) {
  log_full_errno(prio, errno, "Failed to set death 
signal: %m");
  _exit(EXIT_FAILURE);
  }

  
  workaround set kernel commandline to `apparmor=1`
  

  MAAS bug
  Why is maas setting `apparmor=0` ? Ubuntu shouldn't be used without apparmor. 
Even for deployment and commisioning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/2016908/+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 2017317] Re: Ubuntu: upon reboot, forever waiting for encrypted swapfile ...

What release is this exactly? Have you tried any suggestions from
askubuntu? E.g. this one looks related (though I have not tested it)
https://askubuntu.com/questions/1254772/cryptsetup-waiting-for-
encrypted-source-device-swapfile-fstab-empty.

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

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

Title:
Ubuntu: upon reboot, forever waiting for encrypted swapfile ...

Status in systemd package in Ubuntu:
Incomplete

Bug description:
### Issue description
When restarting my machine, cryptsetup waits forever. Waiting for the
swapfile. Unable to start Ubuntu at all. Error message is:

```
cryptsetup: Waiting for encrypted source device /swapfile...
```

### Steps for reproducing the issue
1. Do a fresh installation of Ubuntu, unencrypted.
2. Later, due to restrictions at work, encrypt Ubuntu POST installation
accordingly to this article:
https://jumpcloud.com/blog/how-to-encrypt-ubuntu-20-04-desktop-post-installation
3. Reboot, all works fine, but ...
4. Later, after a couple of months, install a new Linux kernel and then ...
5. Upon boot cryptsetup gets stuck, waits forever. See attached photo.

### Additional info
I've found a temporary, painful workaround by rebooting in recovery mode and
running this command every time:

```
sudo update-initramfs -u -k all
```

Then I can boot again. But I have to do this every time. Why?

### Debug log

Hard to say but here's the output of this command `journalctl | grep
crypt`, not sure if you can find anything interesting about it:

```
Apr 21 13:48:28 M1 audit[179547]: AVC apparmor="DENIED" operation="getattr"
class="file" info="Failed name lookup - disconnected path" error=-13
profile="/usr/bin/evince-thumbnailer"
name="home/.ecryptfs/michael-heuberger/.Private/ECRYPTFS_FNEK_ENCRYPTED.FWaKkF5ZO-vAFETGnoPriOb55KN8iA.SprD0W8LFNkfXu75b-QusjTdAA---/ECRYPTFS_FNEK_ENCRYPTED.FXaKkF5ZO-vAFETGnoPriOb55KN8iA.SprD0JjExLlqv3Fk6x4GGYcQdjXda2554lHGsMAmCwjYZWGA-"
pid=179547 comm="evince-thumbnai" requested_mask="r" denied_mask="r"
fsuid=1000 ouid=1000
Apr 21 17:01:49 M1 gdm-password][219451]: pam_ecryptfs: pam_sm_authenticate:
/home/michael-heuberger is already mounted
Apr 21 17:26:59 M1 systemd[1]: Requested transaction contradicts existing
jobs: Transaction for plymouth-quit.service/start is destructive
(dev-disk-by\x2did-dm\x2duuid\x2dCRYPT\x2dPLAIN\x2dcryptswap1.swap has 'stop'
job queued, but 'start' is included in transaction).
Apr 21 17:26:59 M1 systemd[1]: gdm.service: Failed to enqueue OnFailure= job,
ignoring: Transaction for plymouth-quit.service/start is destructive
(dev-disk-by\x2did-dm\x2duuid\x2dCRYPT\x2dPLAIN\x2dcryptswap1.swap has 'stop'
job queued, but 'start' is included in transaction).
Apr 21 17:26:59 M1 systemd[3094]: Stopping GnuPG cryptographic agent and
passphrase cache...
Apr 21 17:27:00 M1 systemd[3094]: Stopped GnuPG cryptographic agent and
passphrase cache.
Apr 21 17:27:07 M1 systemd[1]: Stopped target Local Encrypted Volumes.
Apr 21 17:27:08 M1 umount.ecryptfs[231225]: Failed to find key with sig
[2bda85c181b04823]: Required key not available
Apr 21 17:27:08 M1 umount.ecryptfs[231225]: Failed to find key with sig
[96c111e5680ecc45]: Required key not available
Apr 21 17:27:09 M1 systemd[1]: Deactivating swap
/dev/disk/by-id/dm-name-cryptswap1...
Apr 21 17:27:09 M1 systemd[1]: dev-disk-by\x2dlabel-cryptswap1.swap:
Deactivated successfully.
Apr 21 17:27:09 M1 systemd[1]: Deactivated swap /dev/disk/by-label/cryptswap1.
```

Do you have any tips, advice please, how to fix this, how can I reboot
my machine without running `update-initramfs` every time? Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2017317/+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 2019026] Re: systemd /tmp cleaning is suboptimal

I personally have become very accustomed to the current behavior where
/tmp is emptied on reboot -- I have no idea what most users would say
about this, so I wonder if changing that behavior would be unwelcome. I
do think it could be nice to have the 30d behavior back, however.

In other words, if we did change this I think my preference would be:

 D /tmp 1777 root root 30d

so that we still always clear on boot, but also after 30d if needed.

On the other hand, this feels like it might be something that most
people don't care about, and those that do are welcome to change their
local system.

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

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

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

Title:
  systemd /tmp cleaning is suboptimal

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Historically on Debian and Ubuntu, before systemd, the default
  handling of /tmp was to periodically, and at boot, remove all
  files/directories older than 30 days; and leave other contents alone.

  With the move to systemd, the "default" (really, hard-coded in
  /usr/lib/tmpfiles.d/tmp.conf) is to not clean /tmp periodically, but
  at boot to remove all contents.

  This is suboptimal for two reasons.

  By cleaning /tmp *only* at boot, if a system makes heavy use of /tmp
  and has lots of inodes under it, possibly due to failures of some
  process to clean up after itself, at boot the system will be
  unavailable for an unnecessarily long time while these files are
  removed.

  By cleaning *all* files under /tmp, this makes a reboot an Event where
  in-progress files may be unnecessarily lost.

  While the FHS does not *guarantee* that files under /tmp will persist
  across boot (because /tmp may be a tmpfs), it also does not *require*
  that /tmp be cleared on boot.

 Although data stored in /tmp may be deleted in a site-specific
 manner, it is recommended that files and directories located in
 /tmp be deleted whenever the system is booted.

 FHS added this recommendation on the basis of historical
 precedent and common practice, but did not make it a
 requirement because system administration is not within the
 scope of this standard.

  I therefore believe the correct value for /usr/lib/tmpfiles.d/tmp.conf
  to restore past behavior is 'd /tmp 1777 root root 30d'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2019026/+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 2008952] Re: DNS failure while trying to fetch user-data

2023-06-09 Thread Dan Bungert

** Changed in: subiquity
   Status: New => 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/2008952

Title:
  DNS failure while trying to fetch user-data

Status in cloud-init:
  Fix Released
Status in netplan:
  Invalid
Status in subiquity:
  Invalid
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  In testing netboot + autoinstall of the new ubuntu desktop subiquity
  based installer for 23.04 I found cloud-init is failing to retrieve
  user-data because it can't resolved the hostname in the URL.  This
  same configuration does work for 22.04 based subiquity, so seems a
  regression.

  From the ipxe config:

  imgargs vmlinuz initrd=initrd \
   ip=dhcp \
   iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso 
\
   fsck.mode=skip \
   layerfs-path=minimal.standard.live.squashfs \
   autoinstall \
   'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \

  That fails, but if we replace boot.linuxgroove.com with the IP it
  works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/2008952/+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 2008952] Re: DNS failure while trying to fetch user-data

My understanding from a quick read is that there is nothing to do in
systemd. Please re-open if I am mistaken.

** Changed in: systemd (Ubuntu)
   Status: New => 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/2008952

Title:
  DNS failure while trying to fetch user-data

Status in cloud-init:
  Fix Released
Status in netplan:
  Invalid
Status in subiquity:
  New
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  In testing netboot + autoinstall of the new ubuntu desktop subiquity
  based installer for 23.04 I found cloud-init is failing to retrieve
  user-data because it can't resolved the hostname in the URL.  This
  same configuration does work for 22.04 based subiquity, so seems a
  regression.

  From the ipxe config:

  imgargs vmlinuz initrd=initrd \
   ip=dhcp \
   iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso 
\
   fsck.mode=skip \
   layerfs-path=minimal.standard.live.squashfs \
   autoinstall \
   'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \

  That fails, but if we replace boot.linuxgroove.com with the IP it
  works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/2008952/+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 2020177] Re: Leaking sessions in pam_systemd

What makes you say the sessions are "leaked", exactly? Is there
something odd about the sessions listed? I realize that is a large
number, however.

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

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

Title:
  Leaking sessions in pam_systemd

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  May 19 12:38:38 s20.wr0.ru sshd[3793128]: pam_systemd(sshd:session):
  Failed to create session: Maximum number of sessions (8192) reached,
  refusing further sessions.

  # loginctl list-sessions|wc -l
  8195

  
   # loginctl session-status 302548700
  302548700 - topaz (450)
 Since: Tue 2022-10-18 09:29:02; 7 months 0 days ago
Leader: 2637625
Remote: 92.42.15.122
   Service: sshd; type tty; class user
 State: closing
  Unit: session-302548700.scope

  # ps axf|wc -l
  72

  
  The only way I could figure to fix this is to reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.21
  Uname: Linux 4.15.0 x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDmesg:
   
  Date: Fri May 19 12:58:47 2023
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.utf8
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcInterrupts: Error: [Errno 2] No such file or directory: '/proc/interrupts'
  ProcKernelCmdLine: quiet
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2022-01-26 (478 days ago)
  acpidump:
   
  mtime.conffile..etc.systemd.journald.conf: 2022-08-19T16:13:27.570934

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2020177/+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 2001556] Re: systemd-cryptenroll poorly communicates libtss2-rc0 dependency

I think the current log levels and messages are appropriate, so marking
this won't fix.

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

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

Title:
  systemd-cryptenroll poorly communicates libtss2-rc0 dependency

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Description:

  tpm2 support was added to jammy in 249.11-0ubuntu3.3 via LP1969375.
  libtss2-rc0 was added as a suggested package.

  $ systemd-cryptenroll --tpm2-device=list
  TPM2 support is not installed.

  Installing libtss2-rc0 allows this to resolve:
  $ sudo apt install libtss2-rc0
  $ systemd-cryptenroll --tpm2-device=list
  PATHDEVICE  DRIVER
  /dev/tpmrm0 VTPM0101:00 tpm_crb

  While this isn't inherently an issue, two things are notable:

  + The manpage for systemd-cryptenroll makes no mention that the
  suggested package needs to be installed (that I could find), this is
  only noted via `apt depends`. I only happened to find this while
  building from source.

  + The presented error implies that the pkg was build with -Dtpm2=false
  (as I read it), which is not actually the case. It should properly
  indicate the missing dep.

  The choice to leave this as a suggested dep was deliberate, so I
  believe resolution of the above two issues would suffice to provide
  enduser clarity.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2001556/+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 1862378] Re: libsystemd-shared broken in Multi-Arch

According to the Debian bug, this is fixed in 251.2-3 by shipped a
separate libsystemd-shared package.

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

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

Title:
  libsystemd-shared broken in Multi-Arch

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  I noticed that systemd-machined was failing to start on an arm64 box.
  This box had armhf enabled, and turns out systemd had been cross-
  graded over to systemd:armhf[*]. It still had systemd-container:arm64
  installed, so now I had an arm64 /lib/systemd/systemd-machine, but an
  armhf /lib/systemd/libsystemd-shared-244.so.

  libsystemd-shared-244.so is from the systemd package. Since systemd is
  marked Multi-Arch: foreign, systemd:armhf was able to incorrectly
  satisfy systemd-container:arm64's dependency on systemd.

  [*] kudos to Multi-Arch that I simply hadn't noticed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1862378/+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 2012437] Re: Ship a static libsystemd.a

Sorry for the delay, I got side tracked after initially proposing this
change to Debian. I will try and get this done for Mantic.

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

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Nick Rosbrook (enr0n)

** Tags added: foundations-todo

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

Title:
  Ship a static libsystemd.a

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  More and more things are requiring linking against libsystemd.  In
  particular, because dbus is now linked against libsystemd, anything
  that wants to make a dbus client call needs it.  By not shipping a
  static libsystemd.a, all such users are prevented from building
  statically.  This includes tools like the lxc-init container init, and
  stacker container build tool, which both want to be re-execed inside a
  container which may have completely different - or no - distro.

  With the attached debdiff, libsystemd-dev ships a libsystem.a so tools
  can be built statically.

  The package has been built (for lunar) with this debdiff at ppa:serge-
  hallyn/systemd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2012437/+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 1995048] Re: reboot reboots system when --poweroff is passed

The man page should be up-to-date for Lunar and newer.

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

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

Title:
  reboot reboots system when --poweroff is passed

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  The feature of passing "--poweroff" to the reboot command to "Power-
  off the machine, regardless of which one of the three commands is
  invoked." is broken. Either that or the man page is. This doesn't
  matter much to me anymore now that I found out that you can also pass
  "-f" to "poweroff" when debugging, but it confused me a lot at first.

  $ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  $ apt-cache policy systemd-sysv
  systemd-sysv:
Installed: 249.11-0ubuntu3.6
Candidate: 249.11-0ubuntu3.6
Version table:
   *** 249.11-0ubuntu3.6 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   249.11-0ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  # Expected behaviour

  The system to power off.

  # Actual behaviour

  The system reboots.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-09-19 (39 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Lsusb:
   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 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
  Package: systemd 249.11-0ubuntu3.6
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic 
root=UUID=11e9994e-8b05-42e7-949a-2f635b160285 ro text debug
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Tags:  jammy
  Uname: Linux 5.15.0-52-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  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/1995048/+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 915215] Re: rc.local should support a runparts of rc.local.d

I don't think this is relevant anymore.

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

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

Title:
  rc.local should support a runparts of rc.local.d

Status in systemd package in Ubuntu:
  Won't Fix
Status in sysvinit package in Ubuntu:
  Triaged

Bug description:
  the current rc.local script that gets installed is difficult to work
  with.

  For doing simple things like "i just want to run this at the  end of
  boot", the 'exit 0' at the end means  that human editing is almost
  required to do so without possibly breaking other content that might
  be in it.

  ie, right now we have:
  ---
  #!/bin/sh
  # some comments here

  exit 0
  

  that makes it very difficult to add a command.

  2 solutions for this:
  1.) drop 'exit 0', its completely unnecessary
  2.) support runparts

  runparts means something that wants to simply add a script can do so,
  and it can easily be deleted.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: initscripts 2.88dsf-13.10ubuntu8
  ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7
  Uname: Linux 3.2.0-7-generic x86_64
  ApportVersion: 1.90-0ubuntu1
  Architecture: amd64
  Date: Thu Jan 12 10:12:59 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: sysvinit
  UpgradeStatus: Upgraded to precise on 2011-11-07 (65 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/915215/+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 1664818] Re: Not possible to render pre-up, pre-down, post-up, or post-down snippets

It does not sound like there is anything for us to do on systemd. If
someone is still interested in a related feature request, please open an
RFE with upstream:
https://github.com/systemd/systemd/labels/RFE%20%F0%9F%8E%81.

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

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

Title:
  Not possible to render pre-up, pre-down, post-up, or post-down
  snippets

Status in netplan:
  Fix Committed
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Many configurations require scripts to run before or after an
  interface comes up or down.

  Example: I had a situation where I needed to render a post-up script
  to monitor an interface with ifupdown (and with the interface set to
  manual mode, because if the link was down I didn't want to require
  DHCP to run before the system continued booting). This is similar to
  what NetworkManager does in order to launch (or kill) a DHCP client.

  Other use cases involve setting up custom routes (such as when complex
  logic involving metrics or source routing is required) or anything
  else the designers of the netplan rendering engine didn't think of,
  such as invoking workarounds or special settings required for a
  particular NIC or environment, iptables rules that should be added or
  removed, etc.

  A follow-on issue is, it should be possible to ask that custom scripts
  run if the *link* is detected to come up or down. But I'll be happy if
  netplan first can simply replicate the custom-script-invoking behavior
  of ifupdown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1664818/+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 2019856] Re: Add missing ARM-cores to support Grace-based systems

This looks low risk, but also low impact (how important is it to have
the correct model name output in lscpu?) in a core package installed on
all users' systems.  I'm fine with the idea of such a change being
included in an SRU, but I think we wouldn't normally push an SRU *just*
for a change such as this.

I would be ok with this being tagged block-proposed to keep it in
-proposed until another high-impact change comes along, or having it
bundled now with other high-impact fixes if there are any.  Does that
sound appropriate to you?

** Changed in: util-linux (Ubuntu Lunar)
   Status: In Progress => Incomplete

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

Title:
  Add missing ARM-cores to support Grace-based systems

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Jammy:
  In Progress
Status in util-linux source package in Kinetic:
  Won't Fix
Status in util-linux source package in Lunar:
  Incomplete
Status in util-linux source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  When running "lscpu" on a Grace-based system + Ubuntu 22.04, it
  doesn't report a model name:

  Vendor ID: ARM
  Model: 0

  [Fix]

  Adding the additional arm_part to sys-utils/lscpu-arm.c solves the
  problem. The commit below adds the specific codes missing from Jammy's
  version.

  https://github.com/util-linux/util-
  linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740

  [Test Steps]

  * Verify whether output of lscpu is correct on new CPUs; eg:
  Vendor ID: ARM
  Model name: Neoverse-V2

  * Verify whether output of lscpu doesn't change on old CPUs; eg:
  Vendor ID: ARM
  Model name: Neoverse-N1

  [What Could Go Wrong]

  The fix only introduces additional model identifiers to match
  against and print a model name string, thus regression impact
  should be contained within lscpu and printing cpus model name
  on ARM systems. 

  Output doesn't change on systems with non-affected CPU models.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+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 1991661] Re: systemd mounts /run without noexec

** Tags removed: foundations-todo

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

Title:
  systemd mounts /run without noexec

Status in initramfs-tools package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  initramfs-tools in Bionic+, when mounting the filesystem, mounts /run
  with noexec

  Cloud images run without initramfs and rely on systemd for the mounts.
  systemd, however, mounts /run without noexec. Snip from mount-setup.c
  (either in src/core/mount-setup.c < 248 or src/shared/mount-setup.c in
  >= 248 )

  ```
  #if ENABLE_SMACK
  { "tmpfs",   "/run",  "tmpfs",  
"mode=755,smackfsroot=*" TMPFS_LIMITS_RUN, MS_NOSUID|MS_NODEV|MS_STRICTATIME,
mac_smack_use, MNT_FATAL  },
  #endif
  { "tmpfs",   "/run",  "tmpfs",  
"mode=755" TMPFS_LIMITS_RUN,   MS_NOSUID|MS_NODEV|MS_STRICTATIME,
NULL,  MNT_FATAL|MNT_IN_CONTAINER },
  ```

  Originally raised in an askubuntu forum: 
  https://askubuntu.com/questions/1432383/mounting-run-as-noexec/1433208

  CPC hasn't received word from any partners yet, but it does constitute
  a possible regression from how the system was mounted in Bionic and
  Focal before moving to optimized boots in 2020/2021.

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


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

Re: [Touch-packages] [Bug 2021902] Re: package linux-image-5.4.0-1108-azure 5.4.0-1108.114 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2023-06-09 Thread marc torres

Marc:
As it turns out, I executed this command and it appears the package
successfully installed:
 sudo apt autoremove.
Thanks Marc

On Fri, Jun 9, 2023 at 2:27 PM Marc Deslauriers <2021...@bugs.launchpad.net>
wrote:

> Thanks for taking the time to report this bug and helping to make Ubuntu
> better. We appreciate the difficulties you are facing, but this appears
> to be a "regular" (non-security) bug.  I have unmarked it as a security
> issue since this bug does not show evidence of allowing attackers to
> cross privilege boundaries nor directly cause loss of data/privacy.
> Please feel free to report any other bugs you may find.
>
> ** Information type changed from Private Security to Public
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2021902
>
> Title:
>   package linux-image-5.4.0-1108-azure 5.4.0-1108.114 failed to
>   install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
>   exited with return code 1
>
> Status in initramfs-tools package in Ubuntu:
>   New
>
> Bug description:
>   /etc/kernel/postinst.d/initramfs-tools:
>   update-initramfs: Generating /boot/initrd.img-5.4.0-1108-azure
>   Error 24 : Write error : cannot write compressed block
>   E: mkinitramfs failure cpio 141 lz4 -9 -l 24
>
>   dpkg: error processing package linux-image-5.4.0-1108-azure
> (--configure):
>installed linux-image-5.4.0-1108-azure package post-installation script
> subprocess returned error exit status 1
>   Errors were encountered while processing:
>linux-image-5.4.0-1108-azure
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 20.04
>   Package: linux-image-5.4.0-1108-azure 5.4.0-1108.114
>   ProcVersionSignature: Ubuntu 5.4.0-1108.114~18.04.1-azure 5.4.233
>   Uname: Linux 5.4.0-1108-azure x86_64
>   NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
>   ApportVersion: 2.20.11-0ubuntu27.26
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   Date: Tue May 30 16:13:43 2023
>   ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited
> with return code 1
>   Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal,
> 3.8.2-0ubuntu2
>   PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2,
> 2.7.17-4
>   RelatedPackageVersions:
>dpkg 1.19.7ubuntu3.2
>apt  2.0.9
>   SourcePackage: initramfs-tools
>   Title: package linux-image-5.4.0-1108-azure 5.4.0-1108.114 failed to
> install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited
> with return code 1
>   UpgradeStatus: Upgraded to focal on 2023-05-30 (0 days ago)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2021902/+subscriptions
>
>

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

Title:
  package linux-image-5.4.0-1108-azure 5.4.0-1108.114 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-5.4.0-1108-azure
  Error 24 : Write error : cannot write compressed block
  E: mkinitramfs failure cpio 141 lz4 -9 -l 24

  dpkg: error processing package linux-image-5.4.0-1108-azure (--configure):
   installed linux-image-5.4.0-1108-azure package post-installation script 
subprocess returned error exit status 1
  Errors were encountered while processing:
   linux-image-5.4.0-1108-azure

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-1108-azure 5.4.0-1108.114
  ProcVersionSignature: Ubuntu 5.4.0-1108.114~18.04.1-azure 5.4.233
  Uname: Linux 5.4.0-1108-azure x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue May 30 16:13:43 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: initramfs-tools
  Title: package linux-image-5.4.0-1108-azure 5.4.0-1108.114 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to focal on 2023-05-30 (0 days ago)

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


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

[Touch-packages] [Bug 1918328] Re: kernel emits error "Bad value for 'hidepid'" with new systemd on old kernel

The upstream consensus was basically "won't fix", and I don't think we
have a kernel/systemd combo in supported releases that would observe
this (focal has 5.4 kernel but systemd 245, and jammy has kernel 5.15).

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

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

Title:
  kernel emits error "Bad value for 'hidepid'" with new systemd on old
  kernel

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  When using a newer systemd (>=247) and older kernel (<5.8), systemd
  attempts to mount /proc using a value for the 'hidepid' parameter that
  the older kernel doesn't understand, which causes the kernel to emit a
  warning message like:

  [4083297.870684] proc: Bad value for 'hidepid'

  This is harmless, as systemd falls back to the 'old' mount method,
  however the logged error message can be confusing.

  Since there is no ubuntu release where the newer systemd might be
  directly used with a kernel older than 5.8, this can only reasonably
  happen in a container on a older ubuntu release. For example, on a
  focal release with the 5.4 kernel, a hirsute container can be created,
  and when it starts up the host dmesg will log the kernel error
  messages shown above.

  Note that if using a lxd container, as there is a bug where lxd
  prevents mounting any fs (which mostly breaks systemd), you must set
  the 'security.nesting' parameter for the lxd container, e.g.:

  $ lxc launch ubuntu-daily:hirsute test-h
  $ lxc set config test-h security.nesting true

  
  Note that this hasn't been fixed upstream, and as it's purely cosmetic, it's 
possible it won't get fixed upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1918328/+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 273049] Re: update-manager should guess an estimative of upgrade size to prevent running out of free disk

2023-06-09 Thread Brian Murray

** Summary changed:

- update-manager should guest an estimative of upgrade size to prevent running 
out of free disk
+ update-manager should guess an estimative of upgrade size to prevent running 
out of free disk

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

Title:
  update-manager should guess an estimative of upgrade size to prevent
  running out of free disk

Status in apt package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: update-manager

  This is a wishbug!
  When users upgrade to the development version using update-manager -d or 
do-release-upgrade -d stats should be collected and sent to some kind of 
archive (after user allows them to) so that a approximated size necessary can 
be calculated in order to prevent running out of free disk on future dist 
upgrades by users (either still on development versions or Stable releases).

  A rough number can be the size of the packages plus the necessary amount 
unpack.
  We could tie the old kernel clean up (last good kernel [1]) with 
update-manager so more disk can be freed up in case there ain't enough free 
disk.

  This ticket groups from #106804, #221855 and "595473
  Related blueprint: cleanup-cruft [2]

  [1] https://wiki.ubuntu.com/KernelTeam/removing-old-kernels
  [2] https://blueprints.edge.launchpad.net/ubuntu/+spec/cleanup-cruft

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/273049/+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 2023229] Re: Autopkgtest failure for tests-in-lxd

It looks like this is actually new LXD behavior introduced in 5.14:
https://github.com/lxc/lxd/commit/ac09cfaff4. Previously, this would
have been fine to do, but the --reuse flag is needed to allow this.

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

** Changed in: systemd (Ubuntu Kinetic)
   Status: Confirmed => Triaged

** Changed in: systemd (Ubuntu Lunar)
   Status: Confirmed => Triaged

** Changed in: systemd (Ubuntu Mantic)
   Status: Confirmed => Triaged

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

Title:
  Autopkgtest failure for tests-in-lxd

Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Jammy:
  Triaged
Status in systemd source package in Kinetic:
  Triaged
Status in systemd source package in Lunar:
  Triaged
Status in systemd source package in Mantic:
  Triaged

Bug description:
  Autopackagetests on multiple Jammy kernels show the same failure on
  the test-in-lxd test

  Error: Aliases already exists: autopkgtest/ubuntu/jammy/amd64
  autopkgtest [16:33:58]: test tests-in-lxd: ---]
  autopkgtest [16:33:58]: test tests-in-lxd:  - - - - - - - - - - results - - - 
- - - - - - -
  tests-in-lxd FAIL non-zero exit status 1

  Where the error seems to be triggered by debian/tests/tests-in-lxd

  lxc publish systemd-lxc --alias $IMAGE

  
  To be determined if this a problem in the autopkgtest infrastructure or test 
bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2023229/+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 2021948] Re: New bugfix release 23.0.4

2023-06-09 Thread Launchpad Bug Tracker

This bug was fixed in the package mesa - 23.0.4-0ubuntu1

---
mesa (23.0.4-0ubuntu1) mantic; urgency=medium

  * New upstream release. (LP: #2021948)
- add a revert for amdgpu which missed 23.0.x branch

 -- Timo Aaltonen   Fri, 09 Jun 2023 12:53:37 +0300

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

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

Title:
  New bugfix release 23.0.4

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  New
Status in mesa source package in Lunar:
  New

Bug description:
  [Impact]

  This is the last point-release of the 23.0.x-series, we should put it
  in lunar so latest bugfixes would get there, and in jammy for 22.04.3
  image.

  We'll include an additional bugfix (a revert) to fix GPU hangs on some
  AMD gpu's running certain games.

  [Test case]

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

  [Where things could go wrong]

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2021948/+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 2021902] Re: package linux-image-5.4.0-1108-azure 5.4.0-1108.114 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2023-06-09 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-5.4.0-1108-azure 5.4.0-1108.114 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-5.4.0-1108-azure
  Error 24 : Write error : cannot write compressed block
  E: mkinitramfs failure cpio 141 lz4 -9 -l 24

  dpkg: error processing package linux-image-5.4.0-1108-azure (--configure):
   installed linux-image-5.4.0-1108-azure package post-installation script 
subprocess returned error exit status 1
  Errors were encountered while processing:
   linux-image-5.4.0-1108-azure

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-1108-azure 5.4.0-1108.114
  ProcVersionSignature: Ubuntu 5.4.0-1108.114~18.04.1-azure 5.4.233
  Uname: Linux 5.4.0-1108-azure x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue May 30 16:13:43 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: initramfs-tools
  Title: package linux-image-5.4.0-1108-azure 5.4.0-1108.114 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to focal on 2023-05-30 (0 days ago)

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

2023-06-09 Thread Marc Deslauriers

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package linux-image-5.4.0-1108-azure 5.4.0-1108.114 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-5.4.0-1108-azure
  Error 24 : Write error : cannot write compressed block
  E: mkinitramfs failure cpio 141 lz4 -9 -l 24

  dpkg: error processing package linux-image-5.4.0-1108-azure (--configure):
   installed linux-image-5.4.0-1108-azure package post-installation script 
subprocess returned error exit status 1
  Errors were encountered while processing:
   linux-image-5.4.0-1108-azure

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-1108-azure 5.4.0-1108.114
  ProcVersionSignature: Ubuntu 5.4.0-1108.114~18.04.1-azure 5.4.233
  Uname: Linux 5.4.0-1108-azure x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue May 30 16:13:43 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: initramfs-tools
  Title: package linux-image-5.4.0-1108-azure 5.4.0-1108.114 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to focal on 2023-05-30 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2021902/+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 1937019] Re: FIDO2 tokens not supported on this build

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

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

Title:
  FIDO2 tokens not supported on this build

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  I'm trying to test systemd-cryptenroll with FIDO2 keys in the new
  systemd version 248 on impish.

  Running "systemd-cryptenroll --fido2-device=list" results in the
  message:

  FIDO2 tokens not supported on this build.

  Would it be possible to build systemd with FIDO support in time for
  the impish release?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937019/+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 2009498] Re: autopkg test failure

** Changed in: ganeti (Debian)
   Status: Unknown => Confirmed

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

Title:
  autopkg test failure

Status in ganeti package in Ubuntu:
  Fix Released
Status in procps package in Ubuntu:
  Fix Released
Status in ganeti package in Debian:
  Confirmed

Bug description:
  pgrep -u '-1'; echo $?

  used to yield 1 but with procps 4.0.3 it yields 2.

  Negative uids don't exist in the Linux kernel.

  
  Function testRequestUnusedUid() is wrong in assuming that -1 will be 
considered an unused uid.

  See Debian bug#1031765: ganeti-testsuite: autopkgtest failure with
  procps 2:4.0.3-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ganeti/+bug/2009498/+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 1998872] Re: unattended-updates failing in kinetic as AC power detection is bugged

The referenced commit should be in Lunar and newer. Marking Won't Fix
for Kinetic as we are not planning on another SRU for that release.

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

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

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

Title:
  unattended-updates failing in kinetic as AC power detection is bugged

Status in e2fsprogs package in Ubuntu:
  New
Status in logrotate package in Ubuntu:
  New
Status in man-db package in Ubuntu:
  New
Status in plocate package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  New
Status in e2fsprogs source package in Kinetic:
  New
Status in logrotate source package in Kinetic:
  New
Status in man-db source package in Kinetic:
  New
Status in plocate source package in Kinetic:
  New
Status in systemd source package in Kinetic:
  Won't Fix
Status in unattended-upgrades source package in Kinetic:
  New

Bug description:
  The ConditionACPower testing code does not work correctly on some
  systems. This prevents the unattended-updates systemd service running
  as it thinks that a system (a NUC10i3FNYHN) is running on battery. It
  isn't - it just has  a power supply that can *provide* power over USB.

  This (unattended-updrades) was OK in Jammy, but started to fail when I
  upgraded to Kinetic.

  (A systemd override file for apt-daily-upgrade.service to remove the
  condition gets the service working again.)

  The problem is similar (or perhaps identical) to the problem with the
  on_ac_power script (from the powermgmt-base package).

  That has been reported in bug #1980991.  There are more details there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1998872/+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 2023229] Re: Autopkgtest failure for tests-in-lxd

I am seeing this in logs for all releases Jammy and newer.

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

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

** Also affects: systemd (Ubuntu Mantic)
   Importance: Undecided
   Status: Confirmed

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

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

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

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

** Tags added: foundations-todo

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

Title:
  Autopkgtest failure for tests-in-lxd

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Jammy:
  Confirmed
Status in systemd source package in Kinetic:
  Confirmed
Status in systemd source package in Lunar:
  Confirmed
Status in systemd source package in Mantic:
  Confirmed

Bug description:
  Autopackagetests on multiple Jammy kernels show the same failure on
  the test-in-lxd test

  Error: Aliases already exists: autopkgtest/ubuntu/jammy/amd64
  autopkgtest [16:33:58]: test tests-in-lxd: ---]
  autopkgtest [16:33:58]: test tests-in-lxd:  - - - - - - - - - - results - - - 
- - - - - - -
  tests-in-lxd FAIL non-zero exit status 1

  Where the error seems to be triggered by debian/tests/tests-in-lxd

  lxc publish systemd-lxc --alias $IMAGE

  
  To be determined if this a problem in the autopkgtest infrastructure or test 
bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2023229/+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 2023229] Re: Autopkgtest failure for tests-in-lxd

Sorry, I realize the relevant snippet was already posted in the
description.

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

Title:
  Autopkgtest failure for tests-in-lxd

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Jammy:
  Confirmed
Status in systemd source package in Kinetic:
  Confirmed
Status in systemd source package in Lunar:
  Confirmed
Status in systemd source package in Mantic:
  Confirmed

Bug description:
  Autopackagetests on multiple Jammy kernels show the same failure on
  the test-in-lxd test

  Error: Aliases already exists: autopkgtest/ubuntu/jammy/amd64
  autopkgtest [16:33:58]: test tests-in-lxd: ---]
  autopkgtest [16:33:58]: test tests-in-lxd:  - - - - - - - - - - results - - - 
- - - - - - -
  tests-in-lxd FAIL non-zero exit status 1

  Where the error seems to be triggered by debian/tests/tests-in-lxd

  lxc publish systemd-lxc --alias $IMAGE

  
  To be determined if this a problem in the autopkgtest infrastructure or test 
bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2023229/+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 2023229] Re: Autopkgtest failure for tests-in-lxd

It looks like this is the problem:

Error: Aliases already exists: autopkgtest/ubuntu/jammy/amd64
autopkgtest [16:21:39]: test tests-in-lxd: ---]

I am not sure why that image exists already now. Maybe we need to use a
random string in the image name somewhere to avoid collisions.

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

Title:
  Autopkgtest failure for tests-in-lxd

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Jammy:
  Confirmed
Status in systemd source package in Kinetic:
  Confirmed
Status in systemd source package in Lunar:
  Confirmed
Status in systemd source package in Mantic:
  Confirmed

Bug description:
  Autopackagetests on multiple Jammy kernels show the same failure on
  the test-in-lxd test

  Error: Aliases already exists: autopkgtest/ubuntu/jammy/amd64
  autopkgtest [16:33:58]: test tests-in-lxd: ---]
  autopkgtest [16:33:58]: test tests-in-lxd:  - - - - - - - - - - results - - - 
- - - - - - -
  tests-in-lxd FAIL non-zero exit status 1

  Where the error seems to be triggered by debian/tests/tests-in-lxd

  lxc publish systemd-lxc --alias $IMAGE

  
  To be determined if this a problem in the autopkgtest infrastructure or test 
bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2023229/+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 2017846] Re: System kept waking up after pressing power button

I do see the behavior you are describing in those logs:

Apr 27 00:34:53 Y4M1-II systemd-logind[2855]: Power key pressed short.
Apr 27 00:34:53 Y4M1-II systemd-logind[2855]: The system will suspend now!
Apr 27 00:35:10 Y4M1-II systemd-logind[2855]: Operation 'sleep' finished.
Apr 27 00:35:45 Y4M1-II systemd-logind[2855]: Power key pressed short.
Apr 27 00:35:45 Y4M1-II systemd-logind[2855]: The system will suspend now!
Apr 27 00:36:02 Y4M1-II systemd-logind[2855]: Operation 'sleep' finished.
Apr 27 00:40:00 Y4M1-II systemd-logind[2855]: Power key pressed short.
Apr 27 00:40:00 Y4M1-II systemd-logind[2855]: The system will suspend now!
Apr 27 00:40:17 Y4M1-II systemd-logind[2855]: Operation 'sleep' finished.
Apr 27 00:50:15 Y4M1-II systemd-logind[2855]: The system will power off now!
Apr 27 00:50:15 Y4M1-II systemd-logind[2855]: System is powering down.

Each gap is 17 seconds, which is interesting I guess.

If you are using suspend-then-hibernate (/etc/systemd/sleep.conf) and
your battery is low, the system might be waking up from suspend to then
hibernate (it does not look like you are on batter power though).
Otherwise there might be a timer unit installed with WakeSystem=true
that happens to be firing when you suspend. Besides that I don't think
systemd would do anything else to wake the system (I don't see any other
relevant uses of CLOCK_BOOTTIME_ALARM). If you want to investigate
systemd involvement further, than you can enable debug logs for systemd-
logind and attach updated logs if this issue occurs again.

$ cat > /etc/systemd/system/systemd-logind.service.d/debug-logs.conf << EOF
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
EOF

Probably best to reboot for that to take effect.

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

Title:
  System kept waking up after pressing power button

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Tried it 3 times in the last 15min, each time it keeps waking back up.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yamiyuki  42974 F wireplumber
   /dev/snd/controlC3:  yamiyuki  42974 F wireplumber
   /dev/snd/controlC0:  yamiyuki  42974 F wireplumber
   /dev/snd/seq:yamiyuki  42972 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Apr 27 00:45:37 2023
  InstallationDate: Installed on 2022-01-14 (468 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro 
rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 
vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x 
quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago)
  dmi.bios.date: 02/08/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F5a
  dmi.board.asset.tag: Default string
  dmi.board.name: X570S AORUS MASTER
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570S AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE

[Touch-packages] [Bug 1992979] Re: kinetic ppc64le reporting Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected

Only marked won't fix for Kinetic. Thanks for confirming it happens on
other releases.

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

Title:
  kinetic ppc64le reporting Failed to send WATCHDOG=1 notification
  message: Transport endpoint is not connected

Status in systemd package in Ubuntu:
  Incomplete
Status in systemd source package in Kinetic:
  Won't Fix
Status in systemd source package in Lunar:
  Incomplete

Bug description:
  Upgraded from Jammy to Kinetic (14 Oct 2022) on ppc64le in QEMU,
  single CPU, 1GB memory, rebooted, can NO longer login. Stuck in
  systems boot phase.

  Attached is an image of the hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1992979/+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 1992979] Re: kinetic ppc64le reporting Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected

2023-06-09 Thread Colin Ian King

Why won't fix? It occurs on other releases too.

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

Title:
  kinetic ppc64le reporting Failed to send WATCHDOG=1 notification
  message: Transport endpoint is not connected

Status in systemd package in Ubuntu:
  Incomplete
Status in systemd source package in Kinetic:
  Won't Fix
Status in systemd source package in Lunar:
  Incomplete

Bug description:
  Upgraded from Jammy to Kinetic (14 Oct 2022) on ppc64le in QEMU,
  single CPU, 1GB memory, rebooted, can NO longer login. Stuck in
  systems boot phase.

  Attached is an image of the hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1992979/+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 2013543] Re: systemctl daemon-reexec forgets running services and starts everything new

Sorry for the delay in response. I have not had sufficient time to
investigate this further. Since it sounds like this can be observed on
recent systemd releases, and there are no Ubuntu specific patches that
stand out to me that might be causing this, please open an upstream bug
report so that the issue can be investigated further.

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

Title:
  systemctl daemon-reexec forgets running services and starts everything
  new

Status in systemd package in Ubuntu:
  Incomplete
Status in systemd source package in Jammy:
  Incomplete

Bug description:
  # Our problem #

  During a regular update of our container environment, `systemd` (and
  the related packages libpam-systemd, libsystemd0, libudev1, systemd-
  sysv and udev) were updated from `249.11-0ubuntu3.6` to
  `249.11-0ubuntu3.7`. We're talking only about Ubuntu 22.04. Our Ubuntu
  20.04 is working fine with `systemctl daemon-reexec`.

  In my opinion, the update was not the problem because we've tried
  downgrading and tried these versions: (current) `249.11-0ubuntu3.7`,
  `249.11-0ubuntu3.6`, `249.11-0ubuntu3.4` and `249.11-0ubuntu3.3`. The
  symptoms were the same.

  # Symptoms #

  The `/var/lib/dpkg/info/systemd.postinst` executes a `systemctl
  daemon-reexec` and that ended in a disaster. It seems that `systemd`
  is forgetting all it started children and tries to start nearly every
  configured service again. Naturally, the old services are still
  running, and the ports can't be opened twice and `systemd` won't give
  up. Here are some(!) of the logfiles:

  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Starting Create Volatile Files and 
Directories...
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: systemd-udevd.service: Found 
left-over process 130 (systemd-udevd) in control group while starting unit. 
Ignoring.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: This usually indicates unclean 
termination of a previous run, or service implementation deficiencies.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: systemd-udevd.service: Found 
left-over process 31475 (systemd-udevd) in control group while starting unit. 
Ignoring.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: This usually indicates unclean 
termination of a previous run, or service implementation deficiencies.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: systemd-udevd.service: Found 
left-over process 31476 (systemd-udevd) in control group while starting unit. 
Ignoring.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: This usually indicates unclean 
termination of a previous run, or service implementation deficiencies.

  And...

  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Reached target System 
Initialization.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Daily apt download 
activities.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Daily apt upgrade and clean 
activities.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Daily dpkg database backup 
timer.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Periodic ext4 Online 
Metadata Check for All Filesystems.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Condition check resulted in Discard 
unused blocks once a week being skipped.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Daily rotation of log files.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Daily man-db regeneration.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Message of the Day.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Clean PHP session files 
every 30 mins.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Update the plocate database 
daily.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Daily Cleanup of Temporary 
Directories.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Reached target Basic System.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: System is tainted: cgroupsv1
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Reached target Timer Units.

  And...

  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: atd.service: Found left-over 
process 206 (atd) in control group while starting unit. Ignoring.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: This usually indicates unclean 
termination of a previous run, or service implementation deficiencies.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Starting Deferred execution 
scheduler...
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: cron.service: Found left-over 
process 164 (cron) in control group while starting unit. Ignoring.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: This usually indicates unclean 
termination of a previous run, or service implementation deficiencies.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Regular background program 
processing daemon.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: dbus.service: Found left-over 
process 177 (dbus-daemon) in control group while starting unit. Ignoring.
  Mar 31 12:51:39

[Touch-packages] [Bug 1699942] Re: network-manager fails to deprecate addresses

This bug is stale, and it remains unclear if there is a systemd bug, so
marking invalid.

** 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/1699942

Title:
  network-manager fails to deprecate addresses

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  network manager does not properly deprecate autoconfigured temporary IP 
addresses when ValidLifetime for a prefix is 0 in router advertisements. This 
behaviour is non-compliant with RFC 4861 § 6.3.4, which reads:
  If the prefix is already present in the host's Prefix List as
  the result of a previously received advertisement, reset its
  invalidation timer to the Valid Lifetime value in the Prefix
  Information option.  If the new Lifetime value is zero, time-out
  the prefix immediately.

  The hosts instead continued to use temporary addresses configured
  until they reached their timeout, rather than immediately dropping the
  addresses. It further appears that it is generating new temporary
  addresses when the previous ones expire, but I have not been
  monitoring hosts closely enough to tell for sure---I will update on
  this when I have further information.

  This problem was discovered on Ubuntu Studio 16.04.2; it is not
  present on Ubuntu Server (which uses Debian networking scripts).

  Additional Info:

  $ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  $ apt-cache policy network-manager
  network-manager:
Installed: 1.2.6-0ubuntu0.16.04.1
Candidate: 1.2.6-0ubuntu0.16.04.1
Version table:
   *** 1.2.6-0ubuntu0.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.2.2-0ubuntu0.16.04.4 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   1.1.93-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699942/+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 1930738] Re: network configuration failed on reboot

According to the reporter, this issue was not observed in Ubuntu 21.04
forward. I do not think there is a strong case for addressing this in
focal or bionic.

** Changed in: systemd (Ubuntu Bionic)
   Status: Incomplete => Won't Fix

** Changed in: systemd (Ubuntu Focal)
   Status: Incomplete => Won't Fix

** 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/1930738

Title:
  network configuration failed on reboot

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Bionic:
  Won't Fix
Status in systemd source package in Focal:
  Won't Fix

Bug description:
  [impact]

  number of statically defined addresses for an interface in systemd-
  networkd is limited

  [test case]

  Note: this only occurs in a container; this is not reproducable in a
  VM or bare metal.

  Configure netplan with the attached yaml file (10-test.yaml)

  enable debug for systemd-networkd

  reboot the system and check the journalctl output to see if any errors
  were reported for systemd-networkd, e.g.:

  $ journalctl -b -u systemd-networkd | grep 'could not set'
  Jul 23 13:16:52 lp1930738-b systemd-networkd[189]: eth0: could not set 
address: Connection timed out
  ...

  Note that systemd may be able to actually correctly set all addresses,
  but fails to communicate with netlink to determine the addresses are
  set, so just checking the output of 'ip a' is not enough, the systemd-
  networkd debug log should be checked

  [regression potential]

  possible failure to correctly apply all statically defined interfaces

  [scope]

  TBD, not fully fixed upstream

  this is needed in f and b

  this is fixed upstream with commits
  628f08b66d43d1947b03419409d817d28eb47321 and PR 16982 which are
  included in v246 and later, so this is fixed in h and later

  [other info]

  I elided upstream commit d31f33e3c9f6ea3bdc873ee52f4398edbec74527 as
  that changes the udev-related behavior of networkd-manager inside a
  container, which is not appropriate for SRU for this bug, as I don't
  see any clear bug-related reason to change that behavior.

  Additionally this requires the typo fix from commit
  4934ba2121d76229659939e19ab7d70a89446629

  [original description]

  This issue was reported at
  https://github.com/systemd/systemd/issues/17012

  **Used distribution**
   > Ubuntu 20.04.1 LTS

  **systemd version the issue has been seen with**
  > 245.4-4ubuntu3.2

  **Issue details**
  I configured 255 IPv4 address (including primary IP) using netplan but when 
the server restart, it time out on configuring the interface.  If I limit total 
IPv4 addresses to 181 or less, it works. But anything larger than 181 fails.

  Below are my configurations and error logs.

  **/etc/netplan/10-ens3.yaml**
  ```
  network:
    version: 2
    renderer: networkd
    ethernets:
  ens3:
    dhcp4: no
    addresses:
  - 140.XX.XX.XX/23
  - 103.XXX.XX.1/24
  - 103.XXX.XX.2/24
  - CONTINUED IP ADDRESS UPTO BELOW ...
  - 103.XXX.XX.254/24
    gateway4: 140.XX.XX.X
    nameservers:
  addresses: [1.1.1.1, 1.0.0.1]
    routes:
  - to: 169.254.0.0/16
    via: 140.XX.XX.X
    metric: 100
  ```
  The above config works if I run `netplan apply` but when I reboot, it does 
not work.

  **networkctl**
  ```
  IDX LINK TYPE OPERATIONAL SETUP
    1 lo   loopback carrier unmanaged
    2 ens3 etherroutablefailed

  2 links listed.
  ```

  **/etc/systemd/system/systemd-networkd.service.d/override.conf**
  ```
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug
  ```

  **systemctl status systemd-networkd.service**
  ```
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; 
enabled-runtime; vendor preset: enabled)
  Drop-In: /etc/systemd/system/systemd-networkd.service.d
   └─override.conf
   Active: active (running) since Thu 2020-09-10 19:46:58 UTC; 1min 36s ago
     Docs: man:systemd-networkd.service(8)
     Main PID: 346 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 1074)
   Memory: 3.8M
   CGroup: /system.slice/systemd-networkd.service
   └─346 /lib/systemd/systemd-networkd

  Sep 10 19:47:03 test-server systemd-networkd[346]: NDISC: Sent Router 
Solicitation, next solicitation in 7s
  Sep 10 19:47:11 test-server systemd-networkd[346]: NDISC: No RA received 
before link confirmation timeout
  Sep 10 19:47:11 test-server systemd-networkd[346]: NDISC: Invoking callback 
for 'timeout' event.
  Sep 10 19:47:11 test-server systemd-networkd[346]: NDISC: Sent Router 
Solicitation, next solicitation in 15s
  Sep 10 19:47:23 test-server systemd-networkd[346]: Assertion 'm->sealed' 
failed at

[Touch-packages] [Bug 1979352] Re: system frozen after sleep

** 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/1979352

Title:
  system frozen after sleep

Status in Ubuntu MATE:
  Incomplete
Status in acpid package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid
Status in upower package in Ubuntu:
  Incomplete

Bug description:
  Linux V330 5.15.0-39-generic #42-Ubuntu SMP Thu Jun 9 23:42:32 UTC
  2022 x86_64 x86_64 x86_64 GNU/Linux

  This is a bug that I reported with Ubuntu Mate 20.04 if I remember correctly 
but, at that time it was only apparent when I was using video ripping software 
on separate laptops and only when the machines became idle once the ripping 
program had finished.
  I don't think this bug was ever fixed and so I'm returning to it because I 
left my laptop in sleep mode over meal time to come back to a frozen system. I 
was not using the video ripping program this time, just surfing the Net. No 
other program was open.

  I run a Lenovo i7 V330-151KB and a Lenovo i5 Z50 but, the bug has
  happened when using an old Dell 1530 laptop.

  I do not believe I am unique in having this bug as someone has a
  similar bug when they have minimised Google Chrome and their system
  had went to sleep. I was also using Chrome this time but, as I have
  already said I was having this happen using another program and not
  using Chrome.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1979352/+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 2023403] [NEW] Dell XPS-17 trackpad stutters frequently

2023-06-09 Thread Célian Godefroid

Public bug reported:

Randomly, my trackpad has a lot of trouble detecting movement, for 10 to
20 seconds, until it comes back. Used to happen every day in previous
versions, now every 3 days or so.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun  9 16:43:21 2023
DistUpgraded: 2023-04-21 10:53:49,032 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: lunar
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 
00 [VGA controller])
   Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:098f]
   Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:098f]
InstallationDate: Installed on 2021-04-12 (787 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: Dell Inc. XPS 17 9700
ProcEnviron:
 LANG=fr_FR.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to lunar on 2023-04-21 (49 days ago)
dmi.bios.date: 03/14/2023
dmi.bios.release: 1.24
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.24.0
dmi.board.name: 0PV91W
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.24.0:bd03/14/2023:br1.24:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0PV91W:rvrA00:cvnDellInc.:ct10:cvr:sku098F:
dmi.product.family: XPS
dmi.product.name: XPS 17 9700
dmi.product.sku: 098F
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.114-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug lunar performance ubuntu wayland-session

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

Title:
  Dell XPS-17 trackpad stutters frequently

Status in xorg package in Ubuntu:
  New

Bug description:
  Randomly, my trackpad has a lot of trouble detecting movement, for 10
  to 20 seconds, until it comes back. Used to happen every day in
  previous versions, now every 3 days or so.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  9 16:43:21 2023
  DistUpgraded: 2023-04-21 10:53:49,032 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:098f]
 Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:098f]
  InstallationDate: Installed on 2021-04-12 (787 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. XPS 17 9700
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (49 days ago)
  dmi.bios.date: 03/14/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.24.0
  dmi.board.name: 0PV91W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.24.0:bd03/14/2023:br1.24:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0PV91W:rvrA00:cvnDellInc.:ct10:cvr:sku098F:
  dmi.product.family: XPS

[Touch-packages] [Bug 1992979] Re: kinetic ppc64le reporting Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected

** Changed in: systemd (Ubuntu Kinetic)
   Status: Confirmed => Won't Fix

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

Title:
  kinetic ppc64le reporting Failed to send WATCHDOG=1 notification
  message: Transport endpoint is not connected

Status in systemd package in Ubuntu:
  Incomplete
Status in systemd source package in Kinetic:
  Won't Fix
Status in systemd source package in Lunar:
  Incomplete

Bug description:
  Upgraded from Jammy to Kinetic (14 Oct 2022) on ppc64le in QEMU,
  single CPU, 1GB memory, rebooted, can NO longer login. Stuck in
  systems boot phase.

  Attached is an image of the hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1992979/+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 1996820] Re: command-not-found claims bootctl can be installed with `sudo apt install systemd`

This turned out to be an issue with some infrastructure that command-
not-found uses to map binaries to package names. Nothing to do for
systemd.

** 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/1996820

Title:
  command-not-found claims bootctl can be installed with `sudo apt
  install systemd`

Status in command-not-found package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  On a fresh 22.10 install, I tried to install systemd-boot by running
  bootctl. I get a message saying

  "
  Command 'bootctl' not found, but can be installed with:
  sudo apt install systemd
  "

  But actually the package to install is systemd-boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1996820/+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 2023401] [NEW] Upon shutdown, shutdown process doesn't complete and the computer stays on

2023-06-09 Thread Célian Godefroid

Public bug reported:

When I want to shutdown my computer, very often since last Ubuntu
version, the process seems not to go to the end, and the computer never
shuts down. I used not to notice it, physically close my laptop and put
it back in my bag, then hours later find it very hot and with fans going
at full speed.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun  9 16:35:50 2023
DistUpgraded: 2023-04-21 10:53:49,032 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: lunar
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 
00 [VGA controller])
   Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:098f]
   Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:098f]
InstallationDate: Installed on 2021-04-12 (787 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: Dell Inc. XPS 17 9700
ProcEnviron:
 LANG=fr_FR.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to lunar on 2023-04-21 (49 days ago)
dmi.bios.date: 03/14/2023
dmi.bios.release: 1.24
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.24.0
dmi.board.name: 0PV91W
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.24.0:bd03/14/2023:br1.24:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0PV91W:rvrA00:cvnDellInc.:ct10:cvr:sku098F:
dmi.product.family: XPS
dmi.product.name: XPS 17 9700
dmi.product.sku: 098F
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.114-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug freeze lunar ubuntu wayland-session

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

Title:
  Upon shutdown, shutdown process doesn't complete and the computer
  stays on

Status in xorg package in Ubuntu:
  New

Bug description:
  When I want to shutdown my computer, very often since last Ubuntu
  version, the process seems not to go to the end, and the computer
  never shuts down. I used not to notice it, physically close my laptop
  and put it back in my bag, then hours later find it very hot and with
  fans going at full speed.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  9 16:35:50 2023
  DistUpgraded: 2023-04-21 10:53:49,032 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:098f]
 Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:098f]
  InstallationDate: Installed on 2021-04-12 (787 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. XPS 17 9700
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine:

[Touch-packages] [Bug 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

This bug is stale, so marking Won't Fix for systemd. For any similar
issues on newer releases/hardware, new bugs should be opened.

** Changed in: systemd (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in pm-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1574120/+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 1780332] Re: vaultlocker does not ensure that udev is triggered to create /dev/disk/by-uuid/ symlink and fails

Marking as invalid for systemd since the bug is stale and it remains
unclear if there is a bug in systemd.

** 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/1780332

Title:
  vaultlocker does not ensure that udev is triggered to create
  /dev/disk/by-uuid/ symlink and fails

Status in vaultlocker:
  Fix Released
Status in cryptsetup package in Ubuntu:
  Incomplete
Status in lvm2 package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  When an encrypted device is setup up a UUID (osd_fsid) is passed from
  the charm to be used in the cryptsetup command which accepts a UUID to
  place into the LUKS header (shown in cryptsetup luksDump ).

  
https://github.com/openstack/charm-ceph-osd/blob/stable/18.05/lib/ceph/utils.py#L1788-L1804
 
  UUID comes from osd_fsid

  
https://github.com/openstack-charmers/vaultlocker/blob/8c9cb85dc3ed5dbf18c66a810d189a5230d85c34/vaultlocker/shell.py#L69-L80
  # else statement is used here
   block_uuid = str(uuid.uuid4()) if not args.uuid else args.uuid

   dmcrypt.luks_format(key, block_device, block_uuid) # creates a LUKS 
header
  # ...
   dmcrypt.luks_open(key, block_uuid) # sets up a device with device mapper 
decrypting it via dmcrypt

  https://github.com/openstack-
  
charmers/vaultlocker/blob/d813233179bdf2eec8ed101c702a8e552a966f44/vaultlocker/dmcrypt.py#L44-L56

  This UUID is visible in blkid output

  /dev/sdc: UUID="" TYPE="crypto_LUKS"

  and a udev rule exists to create a /dev/disk/by-uuid/ symlink (which is normally used for filesystem -> block device
  resolution)

  
https://git.launchpad.net/~usd-import-team/ubuntu/+source/lvm2/tree/udev/13-dm-disk.rules.in#n25
  ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_UUID_ENC}=="?*", 
SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}"

  
  Where vaultlocker fails is in luks_open command (right after luks_format) 

   # cryptsetup --batch-mode --key-file - open UUID=
  crypt- --type luks

  because it tries to access /dev/disk/by-uuid/ which
  does not exist.

  This happens since udev rules are not re-triggered to create this
  symlink after a LUKS device is created.

  Solution: call the command below after luks_format before luks_open

  udevadm settle --exit-if-exists=/dev/disk/by-uuid/

To manage notifications about this bug go to:
https://bugs.launchpad.net/vaultlocker/+bug/1780332/+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 2023400] [NEW] Upon clicking Thunderbird e-mail notifications, the e-mail doesn't open until clicking on a second notification

2023-06-09 Thread Célian Godefroid

Public bug reported:

When I receive an e-mail, a notification appears. I click it in order
for Thunderbird to open on the correct e-mail. But Thunderbird doesn't
open right away, a new notification "'Thunderbird' is ready" appears,
which I have to click in order for Thunderbird to open correctly.

Related : https://bugzilla.mozilla.org/show_bug.cgi?id=1745714

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun  9 16:31:36 2023
DistUpgraded: 2023-04-21 10:53:49,032 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: lunar
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 
00 [VGA controller])
   Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:098f]
   Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:098f]
InstallationDate: Installed on 2021-04-12 (787 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: Dell Inc. XPS 17 9700
ProcEnviron:
 LANG=fr_FR.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to lunar on 2023-04-21 (49 days ago)
dmi.bios.date: 03/14/2023
dmi.bios.release: 1.24
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.24.0
dmi.board.name: 0PV91W
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.24.0:bd03/14/2023:br1.24:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0PV91W:rvrA00:cvnDellInc.:ct10:cvr:sku098F:
dmi.product.family: XPS
dmi.product.name: XPS 17 9700
dmi.product.sku: 098F
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.114-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug lunar ubuntu wayland-session

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

Title:
  Upon clicking Thunderbird e-mail notifications, the e-mail doesn't
  open until clicking on a second notification

Status in xorg package in Ubuntu:
  New

Bug description:
  When I receive an e-mail, a notification appears. I click it in order
  for Thunderbird to open on the correct e-mail. But Thunderbird doesn't
  open right away, a new notification "'Thunderbird' is ready" appears,
  which I have to click in order for Thunderbird to open correctly.

  Related : https://bugzilla.mozilla.org/show_bug.cgi?id=1745714

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  9 16:31:36 2023
  DistUpgraded: 2023-04-21 10:53:49,032 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:098f]
 Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:098f]
  InstallationDate: Installed on 2021-04-12 (787 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. XPS 17 9700
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (49 days ago)
  dmi.bios.date: 03/14/2023

[Touch-packages] [Bug 1908140] Re: Bond DHCP fails on Ubuntu Server 20.04 netplan

** 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/1908140

Title:
  Bond DHCP fails on Ubuntu Server 20.04 netplan

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I recently installed Ubuntu Server 20.04 to replace an ESXi server.
  During the installation, I configured a bonded interface for two
  ethernet interfaces. I configured the bond on my ZyXel GS1900-8 as a
  static LAG. During the setup process, the link came up successfully
  and was leased an IP via DHCP.

  All subsequent boots have failed to acquire an IP address for the
  bonded interface. Sometimes, if I allow dhcp4 on the enslaved
  interfaces, and run sudo dhclient -r && sudo dhclient, the enslaved
  interfaces will be leased an IP address _and_ the bond will get an IP
  address. I know this is not proper as dhclient and systemd-networkd do
  not mix.

  Also, I would like to configure this as a LACP bond instead. I have
  enabled LACP on the switch with priority 65535 and "IP/MAC address"
  load balancing algorithm, switched the LAG from static to LACP, and
  altered netplan to use the 802.3ad bond mode.

  Please let me know what, if anything, I'm doing wrong here. I've
  looked around at as many netplan DHCP bond posts here as I could find
  to no avail. See below for configuration files and command outputs. I
  cannot give you the output of `lsb_release -rd` as the package is not
  installed and there's no connection to install it.

  $ cat /etc/netplan/00-bond.yaml
  network:
version: 2
renderer: networkd
ethernets:
  eth0:
dhcp4: false
  eth1:
dhcp4: false
bonds:
  bond0:
dhcp4: true
interfaces:
  - eth0
  - eth1
parameters:
  mode: 802.3ad

  $ sudo journalctl -b -u systemd-networkd
  Dec 14 08:06:47 lore systemd[1]: Starting Network Service...
  Dec 14 08:06:47 lore systemd-networkd[852]: bond0: netdev ready
  Dec 14 08:06:47 lore systemd-networkd[852]: Enumeration completed.
  Dec 14 08:06:47 lore systemd[1]: Started Network Service.
  Dec 14 08:06:47 lore systemd-networkd[852]: bond0: IPv6 successfully enabled
  Dec 14 08:06:47 lore systemd-networkd[852]: bond0: Link UP
  Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link 
'7' we don't know about, ignoring.
  Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link 
'7' we don't know about, ignoring.
  Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link 
'7' we don't know about, ignoring.
  Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link 
'7' we don't know about, ignoring.
  Dec 14 08:08:53 lore systemd-networkd[852]: docker0: Link UP

  $ sudo ip a
  lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred lft forever
  eno1:  mtu 1500 qdisk noop state DOWN group default qlen 
1000
  link/ether 0c:c4:7a:c6:c3:46 brd ff:ff:ff:ff:ff:ff
  eno2:  mtu 1500 qdisk noop state DOWN group default qlen 
1000
  link/ether 0c:c4:7a:c6:c3:47 brd ff:ff:ff:ff:ff:ff
  eth0:  mtu 1500 qdisc noop state DOWN group default qlen 
1000
  link/ether 0c:c4:7a:c6:c6:a2 brd ff:ff:ff:ff:ff:ff
  eth1:  mtu 1500 qdisc noop state DOWN group default qlen 
1000
  link/ether 0c:c4:7a:c6:c6:a3 brd ff:ff:ff:ff:ff:ff
  bond0:  mtu 1500 qdisk noqueue 
state DOWN group default qlen 1000
  link/ether 52:8b:2c:cc:a0:15 brd ff:ff:ff:ff:ff:ff
  docker0:  mtu 1500 qdisc noqueue state 
DOWN group default
  link/ether 02:42:26:1c:1b:39 brd ff:ff:ff:ff:ff:ff
  inet 172.17.0.1/16 brd 172.17.255.255 scope global docker 0
 valid_lft forever preferred_lft forever

  $ cat /run/systemd/network/10-netplan-bond0.netdev
  [NetDev]
  Name=bond0
  Kind=bond

  [Bond]
  Mode=802.3ad

  $ cat /run/systemd/network/10-netplan-bond0.network
  [Match]
  Name=bond0

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6
  ConfigureWithoutCarrier=yes

  [DHCP]
  RouteMetric=100
  UseMTU=true

  $ cat /run/systemd/network/10-netplan-eth0.network
  [Match]
  Name=eth0

  [Network]
  LinkLocalAddressing=no
  Bond=bond0

  $ cat /run/systemd/network/10-netplan-eth1.network
  [Match]
  Name=eth1

  [Network]
  LinkLocalAddressing=no
  Bond=bond0

  $ cat /proc/net/bonding/bond0
  Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

  Bonding Mode: IEEE 802.3ad Dynamic link aggregation
  Transmit Hash Policy: layer2 (0)
  MII Status: down
  MII Polling Interval (ms): 100
  Up Delay (ms): 0
  Down Delay (ms): 0
  Peer Notification Delay (ms): 0

  802.3ad info
  LACP rate: slow
  Min links: 0

[Touch-packages] [Bug 1910775] Re: netdev does not support the independent flag for vxlan

There is no plan to SRU this to Focal. This feature should be available
in the 22.04 LTS, which ships systemd v249.11.

** Changed in: systemd (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  netdev does not support the independent flag for vxlan

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  systemd.netdev does support the independet option for various types of
  interfaces but not for type vxlan. This options was added in a later
  release of systemd (247) with this PR:
  https://github.com/systemd/systemd/pull/17073.

  Since it is currently not possible to create a interface with type
  vxlan it would be nice the include this change in the current LTS
  release (focal).

  "We also need":
  1) Description: Ubuntu 20.04.1 LTS, Release: 20.04
  2) systemd:
Installed: 245.4-4ubuntu3.3
Candidate: 245.4-4ubuntu3.3
  3) systemd support the flag
  4) it does not support it

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1910775/+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 1882034] Re: cannot start X session with NIS account

Marking invalid for systemd due to age, and it being unclear whether
this is in fact a systemd bug.

** 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/1882034

Title:
  cannot start X session with NIS account

Status in gdm3 package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  When login with a NIS account, X does not start, or more precisely it
  starts and exits immediately.

  Only errors in logs is:
   (EE) systemd-logind: failed to get session: PID 4335 does not belong to any 
known session

  X11/gdm login works fine with local accounts.

  SSH/terminal console login with NIS accounts works fine.

  /etc/X11/Xwrapper.config:
allowed_users=anybody

  I've seen several reports of such problems under other versions (eg
  19.10), but no working solutions was found. It seems that the problem
  is the same with lightdm.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun  4 08:59:25 2020
  InstallationDate: Installed on 2019-11-26 (190 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to focal on 2020-04-24 (40 days ago)

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

** Changed in: evince (Debian)
   Status: New => Confirmed

-- 
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:
  Confirmed
Status in evince package in Ubuntu:
  Incomplete
Status in apparmor source package in Jammy:
  Confirmed
Status in evince source package in Jammy:
  Incomplete
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 1971984] Re: pcscd.socket is disabled after installation