[Touch-packages] [Bug 2012781] Re: package cups 2.4.1op1-1ubuntu4.1 failed to install/upgrade: o subprocesso instalado, do pacote cups, o script post-installation foi morto pelo sinal (Erro no barrame

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

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

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

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

Title:
  package cups 2.4.1op1-1ubuntu4.1 failed to install/upgrade: o
  subprocesso instalado, do pacote cups, o script post-installation foi
  morto pelo sinal (Erro no barramento), gerou um core

Status in cups package in Ubuntu:
  Invalid

Bug description:
  abc

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4.1
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  AptOrdering:
   printer-driver-splix:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Mar 23 20:47:31 2023
  ErrorMessage: o subprocesso instalado, do pacote cups, o script 
post-installation foi morto pelo sinal (Erro no barramento), gerou um core
  InstallationDate: Installed on 2023-03-20 (4 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5521 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 004: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5584
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=e080f2c9-2ee1-4e8a-a8e4-01af8fec25a1 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=e080f2c9-2ee1-4e8a-a8e4-01af8fec25a1 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: cups
  Title: package cups 2.4.1op1-1ubuntu4.1 failed to install/upgrade: o 
subprocesso instalado, do pacote cups, o script post-installation foi morto 
pelo sinal (Erro no barramento), gerou um core
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2020
  dmi.bios.release: 1.12
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.0
  dmi.board.name: 012D2F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd11/04/2020:br1.12:svnDellInc.:pnInspiron5584:pvr:rvnDellInc.:rn012D2F:rvrA00:cvnDellInc.:ct10:cvr:sku08FA:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5584
  dmi.product.sku: 08FA
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2012781/+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 2012781] Re: package cups 2.4.1op1-1ubuntu4.1 failed to install/upgrade: o subprocesso instalado, do pacote cups, o script post-installation foi morto pelo sinal (Erro no barrame

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  package cups 2.4.1op1-1ubuntu4.1 failed to install/upgrade: o
  subprocesso instalado, do pacote cups, o script post-installation foi
  morto pelo sinal (Erro no barramento), gerou um core

Status in cups package in Ubuntu:
  New

Bug description:
  abc

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4.1
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  AptOrdering:
   printer-driver-splix:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Mar 23 20:47:31 2023
  ErrorMessage: o subprocesso instalado, do pacote cups, o script 
post-installation foi morto pelo sinal (Erro no barramento), gerou um core
  InstallationDate: Installed on 2023-03-20 (4 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5521 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 004: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5584
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=e080f2c9-2ee1-4e8a-a8e4-01af8fec25a1 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=e080f2c9-2ee1-4e8a-a8e4-01af8fec25a1 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: cups
  Title: package cups 2.4.1op1-1ubuntu4.1 failed to install/upgrade: o 
subprocesso instalado, do pacote cups, o script post-installation foi morto 
pelo sinal (Erro no barramento), gerou um core
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2020
  dmi.bios.release: 1.12
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.0
  dmi.board.name: 012D2F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd11/04/2020:br1.12:svnDellInc.:pnInspiron5584:pvr:rvnDellInc.:rn012D2F:rvrA00:cvnDellInc.:ct10:cvr:sku08FA:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5584
  dmi.product.sku: 08FA
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2012781/+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 2012781] [NEW] package cups 2.4.1op1-1ubuntu4.1 failed to install/upgrade: o subprocesso instalado, do pacote cups, o script post-installation foi morto pelo sinal (Erro no barra

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

abc

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: cups 2.4.1op1-1ubuntu4.1
ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-35-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
AptOrdering:
 printer-driver-splix:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: pass
Date: Thu Mar 23 20:47:31 2023
ErrorMessage: o subprocesso instalado, do pacote cups, o script 
post-installation foi morto pelo sinal (Erro no barramento), gerou um core
InstallationDate: Installed on 2023-03-20 (4 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 0bda:5521 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
 Bus 001 Device 004: ID 046d:c534 Logitech, Inc. Unifying Receiver
 Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 5584
Papersize: a4
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=e080f2c9-2ee1-4e8a-a8e4-01af8fec25a1 ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=e080f2c9-2ee1-4e8a-a8e4-01af8fec25a1 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.8
SourcePackage: cups
Title: package cups 2.4.1op1-1ubuntu4.1 failed to install/upgrade: o 
subprocesso instalado, do pacote cups, o script post-installation foi morto 
pelo sinal (Erro no barramento), gerou um core
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/04/2020
dmi.bios.release: 1.12
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.12.0
dmi.board.name: 012D2F
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd11/04/2020:br1.12:svnDellInc.:pnInspiron5584:pvr:rvnDellInc.:rn012D2F:rvrA00:cvnDellInc.:ct10:cvr:sku08FA:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5584
dmi.product.sku: 08FA
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-package jammy
-- 
package cups 2.4.1op1-1ubuntu4.1 failed to install/upgrade: o subprocesso 
instalado, do pacote cups, o script post-installation foi morto pelo sinal 
(Erro no barramento), gerou um core
https://bugs.launchpad.net/bugs/2012781
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to cups in Ubuntu.

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

[Touch-packages] [Bug 2008952] Re: DNS failure while trying to fetch user-data

[Dan Bungert]

What a mess!

I have uploaded the livecd-rootfs change proposed by Chad in #26.  Note
that there is another problem around jsonschema exposed by this that is
in progress.

** Also affects: livecd-rootfs (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: livecd-rootfs (Ubuntu)
   Status: New => Fix Committed

-- 
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:
  In Progress
Status in netplan:
  Invalid
Status in subiquity:
  New
Status in livecd-rootfs package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  New

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 2012599] Please test proposed package

[Brian Murray]

Hello Dariusz, or anyone else affected,

Accepted tzdata into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2023b-0ubuntu0.18.04.0 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-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. 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 tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/2012599

Title:
  tzdata 2023a/2023b release - Egypt restoring DST

Status in tzdata package in Ubuntu:
  Fix Committed
Status in tzdata source package in Bionic:
  Fix Committed
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Kinetic:
  Fix Committed
Status in tzdata source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  Recently the Egyptian authorities decided to restore DST. The first
  switch after the change is expected to take place on last Friday of
  April. The upstream tzdata 2023a release already reflects this change.

  The 2023a release contains the following changes:

  * Egypt now uses DST again, from April through October.
  * This year Morocco springs forward April 23, not April 30.
  * Palestine delays the start of DST this year.
  * Much of Greenland still uses DST from 2024 on.

  [ Test Plan ]

  Test cases were added to the autopkgtest to cover the testing:

  * python: test_2023a
  * python: test_2023b
  * python-icu: test_2023a (only for kinetic, jammy, focal)

  So the test plan is to check that the autopkgtest succeeds.

  Alternatively the python test_2023a can be run manually:

   * Set system timezone to Egypt (e.g. Africa/Cairo).
   * Set system time to 2023-04-27 23:59.
   * Wait and observe what happens at 2023-04-28 0:00

  [Test Case for releases <= 20.04 LTS]

  Additionally, an upstream update of tzdata removed the 'old' SystemV 
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and 
earlier releases. Subsequently, these should be checked for using the following:
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  [ Where problems could occur ]

   * Systems with incorrect timezone set (e.g. located outside of Egypt
  but still using Egyptian time) may observe unexpected time shift.

  [ Other Info ]

   * More information with sources:
  
https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023.

  The SRUs to the stable include the recent changes for generating the
  debconf template and the timezone mappings in convert_timezone().
  Previous SRUs did forget to update them for the changes from upstream.
  All added tests were also backported.

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

[Brian Murray]

Hello Dariusz, or anyone else affected,

Accepted tzdata into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2023b-0ubuntu0.20.04.0 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.

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

** Tags added: verification-needed-bionic

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

Title:
  tzdata 2023a/2023b release - Egypt restoring DST

Status in tzdata package in Ubuntu:
  Fix Committed
Status in tzdata source package in Bionic:
  Fix Committed
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Kinetic:
  Fix Committed
Status in tzdata source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  Recently the Egyptian authorities decided to restore DST. The first
  switch after the change is expected to take place on last Friday of
  April. The upstream tzdata 2023a release already reflects this change.

  The 2023a release contains the following changes:

  * Egypt now uses DST again, from April through October.
  * This year Morocco springs forward April 23, not April 30.
  * Palestine delays the start of DST this year.
  * Much of Greenland still uses DST from 2024 on.

  [ Test Plan ]

  Test cases were added to the autopkgtest to cover the testing:

  * python: test_2023a
  * python: test_2023b
  * python-icu: test_2023a (only for kinetic, jammy, focal)

  So the test plan is to check that the autopkgtest succeeds.

  Alternatively the python test_2023a can be run manually:

   * Set system timezone to Egypt (e.g. Africa/Cairo).
   * Set system time to 2023-04-27 23:59.
   * Wait and observe what happens at 2023-04-28 0:00

  [Test Case for releases <= 20.04 LTS]

  Additionally, an upstream update of tzdata removed the 'old' SystemV 
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and 
earlier releases. Subsequently, these should be checked for using the following:
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  [ Where problems could occur ]

   * Systems with incorrect timezone set (e.g. located outside of Egypt
  but still using Egyptian time) may observe unexpected time shift.

  [ Other Info ]

   * More information with sources:
  
https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023.

  The SRUs to the stable include the recent changes for generating the
  debconf template and the timezone mappings in convert_timezone().
  Previous SRUs did forget to update them for the changes from upstream.
  All added tests were also backported.

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

[Brian Murray]

Hello Benjamin, or anyone else affected,

Accepted tzdata into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2023b-0ubuntu0.20.04.0 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 tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/2003797

Title:
  Pre-1970 timestamps are knowingly wrong

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Bionic:
  New
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Kinetic:
  Fix Committed

Bug description:
  [ Impact ]

  tzdata 2021b says in NEWS: "Merge more location-based Zones whose
  timestamps agree since 1970, as pre-1970 timestamps are out of scope.
  This is part of a process that has been ongoing since 2013.  This does
  not affect post-1970 timestamps, and timezone historians who build
  with 'make PACKRATDATA=backzone' should see no changes to pre-1970
  timestamps." tzdata 2022b finished that process: "Finish moving to
  'backzone' the location-based zones whose timestamps since 1970 are
  duplicates; adjust links accordingly. This change ordinarily affects
  only pre-1970 timestamps, and with the new PACKRATLIST option it does
  not affect any timestamps. In this round the affected zones are
  Antarctica/Vostok, Asia/Brunei, Asia/Kuala_Lumpur, Atlantic/Reykjavik,
  Europe/Amsterdam, Europe/Copenhagen, Europe/Luxembourg, Europe/Monaco,
  Europe/Oslo, Europe/Stockholm, Indian/Christmas, Indian/Cocos,
  Indian/Kerguelen, Indian/Mahe, Indian/Reunion, Pacific/Chuuk,
  Pacific/Funafuti, Pacific/Majuro, Pacific/Pohnpei, Pacific/Wake and
  Pacific/Wallis, and the affected links are Arctic/Longyearbyen,
  Atlantic/Jan_Mayen, Iceland, Pacific/Ponape, Pacific/Truk, and
  Pacific/Yap."

  The Debian/Ubuntu package builds tzdata with the default settings
  (PACKRATDATA unset) which merges zones whose timestamps agree since
  1970. This leads to timestamps before 1970 being knowingly wrong.
  Example: Europe/Oslo is a link to Europe/Berlin since they are
  identical since 1970, but they differed before 1965. Berlin observed
  no summertime between 1950 and 1980, but Oslo did in 1959 to 1965. So
  summer 1960 in Oslo should be UTC+2 compared to UTC+1 in Berlin:

  ```
  $ TZ=Europe/Oslo date -d "1960-07-01 10:00 Z"
  Fri Jul  1 12:00:00 CEST 1960
  $ TZ=Europe/Berlin date -d "1960-07-01 10:00 Z"
  Fri Jul  1 11:00:00 CET 1960
  ```

  There was a big debate upstream (see https://lwn.net/Articles/870478/
  or https://mm.icann.org/pipermail/tz/2021-May/030137.html). The
  Debian/Ubuntu package should ship timezones from backzone. Users that
  care about pre-1970 timestamps will be satisfied and users not caring
  will probably not care about the additional timezones.

  The install size will increase by around 20% and the amount of
  distinct (i.e. not symlinked) timezones will increase by 33%:

  ```
  $ grep ^Zone africa antarctica asia australasia etcetera europe factory 
northamerica southamerica | wc -l
  352
  $ grep ^Zone backzone | wc -l
  119
  ```

  [ Test plan ]

  The test case `test_pre_1970_timestamps` was added to the python
  autopkgtest for testing this change. So the test plan is to check that
  the autopkgtest succeeds.

  [ Where problems could occur ]

  Systems with incorrect timezone set may observe unexpected time shift.

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

[Brian Murray]

Hello Benjamin, or anyone else affected,

Accepted tzdata into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2023b-0ubuntu0.22.04.0 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.

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

Title:
  Pre-1970 timestamps are knowingly wrong

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Bionic:
  New
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Kinetic:
  Fix Committed

Bug description:
  [ Impact ]

  tzdata 2021b says in NEWS: "Merge more location-based Zones whose
  timestamps agree since 1970, as pre-1970 timestamps are out of scope.
  This is part of a process that has been ongoing since 2013.  This does
  not affect post-1970 timestamps, and timezone historians who build
  with 'make PACKRATDATA=backzone' should see no changes to pre-1970
  timestamps." tzdata 2022b finished that process: "Finish moving to
  'backzone' the location-based zones whose timestamps since 1970 are
  duplicates; adjust links accordingly. This change ordinarily affects
  only pre-1970 timestamps, and with the new PACKRATLIST option it does
  not affect any timestamps. In this round the affected zones are
  Antarctica/Vostok, Asia/Brunei, Asia/Kuala_Lumpur, Atlantic/Reykjavik,
  Europe/Amsterdam, Europe/Copenhagen, Europe/Luxembourg, Europe/Monaco,
  Europe/Oslo, Europe/Stockholm, Indian/Christmas, Indian/Cocos,
  Indian/Kerguelen, Indian/Mahe, Indian/Reunion, Pacific/Chuuk,
  Pacific/Funafuti, Pacific/Majuro, Pacific/Pohnpei, Pacific/Wake and
  Pacific/Wallis, and the affected links are Arctic/Longyearbyen,
  Atlantic/Jan_Mayen, Iceland, Pacific/Ponape, Pacific/Truk, and
  Pacific/Yap."

  The Debian/Ubuntu package builds tzdata with the default settings
  (PACKRATDATA unset) which merges zones whose timestamps agree since
  1970. This leads to timestamps before 1970 being knowingly wrong.
  Example: Europe/Oslo is a link to Europe/Berlin since they are
  identical since 1970, but they differed before 1965. Berlin observed
  no summertime between 1950 and 1980, but Oslo did in 1959 to 1965. So
  summer 1960 in Oslo should be UTC+2 compared to UTC+1 in Berlin:

  ```
  $ TZ=Europe/Oslo date -d "1960-07-01 10:00 Z"
  Fri Jul  1 12:00:00 CEST 1960
  $ TZ=Europe/Berlin date -d "1960-07-01 10:00 Z"
  Fri Jul  1 11:00:00 CET 1960
  ```

  There was a big debate upstream (see https://lwn.net/Articles/870478/
  or https://mm.icann.org/pipermail/tz/2021-May/030137.html). The
  Debian/Ubuntu package should ship timezones from backzone. Users that
  care about pre-1970 timestamps will be satisfied and users not caring
  will probably not care about the additional timezones.

  The install size will increase by around 20% and the amount of
  distinct (i.e. not symlinked) timezones will increase by 33%:

  ```
  $ grep ^Zone africa antarctica asia australasia etcetera europe factory 
northamerica southamerica | wc -l
  352
  $ grep ^Zone backzone | wc -l
  119
  ```

  [ Test plan ]

  The test case `test_pre_1970_timestamps` was added to the python
  autopkgtest for testing this change. So the test plan is to check that
  the autopkgtest succeeds.

  [ Where problems could occur ]

  Systems with incorrect timezone set may observe unexpected time shift.

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

[Brian Murray]

Hello Dariusz, or anyone else affected,

Accepted tzdata into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2023b-0ubuntu0.22.04.0 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.

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

Title:
  tzdata 2023a/2023b release - Egypt restoring DST

Status in tzdata package in Ubuntu:
  Fix Committed
Status in tzdata source package in Bionic:
  New
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Kinetic:
  Fix Committed
Status in tzdata source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  Recently the Egyptian authorities decided to restore DST. The first
  switch after the change is expected to take place on last Friday of
  April. The upstream tzdata 2023a release already reflects this change.

  The 2023a release contains the following changes:

  * Egypt now uses DST again, from April through October.
  * This year Morocco springs forward April 23, not April 30.
  * Palestine delays the start of DST this year.
  * Much of Greenland still uses DST from 2024 on.

  [ Test Plan ]

  Test cases were added to the autopkgtest to cover the testing:

  * python: test_2023a
  * python: test_2023b
  * python-icu: test_2023a (only for kinetic, jammy, focal)

  So the test plan is to check that the autopkgtest succeeds.

  Alternatively the python test_2023a can be run manually:

   * Set system timezone to Egypt (e.g. Africa/Cairo).
   * Set system time to 2023-04-27 23:59.
   * Wait and observe what happens at 2023-04-28 0:00

  [Test Case for releases <= 20.04 LTS]

  Additionally, an upstream update of tzdata removed the 'old' SystemV 
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and 
earlier releases. Subsequently, these should be checked for using the following:
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  [ Where problems could occur ]

   * Systems with incorrect timezone set (e.g. located outside of Egypt
  but still using Egyptian time) may observe unexpected time shift.

  [ Other Info ]

   * More information with sources:
  
https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023.

  The SRUs to the stable include the recent changes for generating the
  debconf template and the timezone mappings in convert_timezone().
  Previous SRUs did forget to update them for the changes from upstream.
  All added tests were also backported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+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 2009230] Re: AppArmor denials for rsyslog

[Andreas Hasenack]

We talked a bit on IRC[1], and for now we will start with allowing just
/dev/console access, specially since we are about to enter beta freeze,
and that is the less invasive option.

We will later investigate (maybe still within the beta) the tty group
membership issue. It looks like we had it before, so it's not clear how
we lost it: on purpose, or if the change was just lost.

1. https://irclogs.ubuntu.com/2023/03/23/%23ubuntu-security.html#t19:19

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

Title:
  AppArmor denials for rsyslog

Status in gce-compute-image-packages package in Ubuntu:
  New
Status in rsyslog package in Ubuntu:
  New
Status in gce-compute-image-packages source package in Lunar:
  New
Status in rsyslog source package in Lunar:
  New

Bug description:
  The AppArmor profile for rsyslog, which had been disabled on previous
  Ubuntu versions, was enabled in lunar.

  The package google-compute-engine added a config file to rsyslog which
  requires rw access to /dev/console

  google:ubuntu-23.04-64 /root# cat /etc/rsyslog.d/90-google.conf
  # Google Compute Engine default console logging.
  #
  # daemon: logging from Google provided daemons.
  # kern: logging information in case of an unexpected crash during boot.
  #
  daemon,kern.* /dev/console

  google:ubuntu-23.04-64 /root# apt-file search /etc/rsyslog.d/90-google.conf
  google-compute-engine: /etc/rsyslog.d/90-google.conf

  So in gce cloud images, we are getting the following denials:

  [ 1500.302082] audit: type=1400 audit(1677876883.728:495):
  apparmor="DENIED" operation="open" class="file" profile="rsyslogd"
  name="/dev/console" pid=603 comm=72733A6D61696E20513A526567
  requested_mask="ac" denied_mask="ac" fsuid=101 ouid=0

  To fix it, we just need to add
    /dev/console rw,
  to /etc/apparmor.d/usr.sbin.rsyslogd

  or the same permission should be added to a file in
  /etc/apparmor.d/rsyslog.d/ by the google-compute-engine package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/2009230/+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 2009230] Re: AppArmor denials for rsyslog

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~georgiag/ubuntu/+source/rsyslog/+git/rsyslog/+merge/439655

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

Title:
  AppArmor denials for rsyslog

Status in gce-compute-image-packages package in Ubuntu:
  New
Status in rsyslog package in Ubuntu:
  New
Status in gce-compute-image-packages source package in Lunar:
  New
Status in rsyslog source package in Lunar:
  New

Bug description:
  The AppArmor profile for rsyslog, which had been disabled on previous
  Ubuntu versions, was enabled in lunar.

  The package google-compute-engine added a config file to rsyslog which
  requires rw access to /dev/console

  google:ubuntu-23.04-64 /root# cat /etc/rsyslog.d/90-google.conf
  # Google Compute Engine default console logging.
  #
  # daemon: logging from Google provided daemons.
  # kern: logging information in case of an unexpected crash during boot.
  #
  daemon,kern.* /dev/console

  google:ubuntu-23.04-64 /root# apt-file search /etc/rsyslog.d/90-google.conf
  google-compute-engine: /etc/rsyslog.d/90-google.conf

  So in gce cloud images, we are getting the following denials:

  [ 1500.302082] audit: type=1400 audit(1677876883.728:495):
  apparmor="DENIED" operation="open" class="file" profile="rsyslogd"
  name="/dev/console" pid=603 comm=72733A6D61696E20513A526567
  requested_mask="ac" denied_mask="ac" fsuid=101 ouid=0

  To fix it, we just need to add
    /dev/console rw,
  to /etc/apparmor.d/usr.sbin.rsyslogd

  or the same permission should be added to a file in
  /etc/apparmor.d/rsyslog.d/ by the google-compute-engine package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/2009230/+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 2012288] Re: Ubuntu Gnome Settings / Chrome / CUPS (printing) communications

[beadon]

Update, I found that CUPS was failing to be modified by the gnome(?)
user interface component.

apparmor is getting in the way, "protecting" cupsd.


To fix this, install the apparmor utilities:

sudo apt-get install apparmor-utils


Then set apparmor to complain about cupsd, instead of blocking access:

sudo aa-complain cupsd


You can now print.  I hope this helps someone else too.  This was quite 
difficult to troubleshoot.


ar 24 16:10:45 semiauto google-chrome.desktop[216920]: 
[216913:216943:0324/161045.967690:ERROR:connection_factory_impl.cc(428)] Failed 
to connect to MCS endpoint with error -105
Mar 24 16:10:46 semiauto google-chrome.desktop[216920]: 
[216913:216913:0324/161046.442656:ERROR:device_event_log_impl.cc(222)] 
[16:10:46.442] Printer: local_printer_handler_default.cc:167 Failure 
enumerating local printers, result: kFailed
Mar 24 16:10:46 semiauto google-chrome.desktop[216920]: Warning: disabling flag 
--expose_wasm due to conflicting flags
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]: 
/usr/share/system-config-printer/system-config-printer.py:325: 
DeprecationWarning: Gtk.ActionGroup.list_actions is deprecated
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]:   for action in 
printer_manager_action_group.list_actions ():
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]: 
/usr/share/system-config-printer/system-config-printer.py:326: 
DeprecationWarning: Gtk.Action.set_sensitive is deprecated
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]:   action.set_sensitive 
(False)
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]: 
/usr/share/system-config-printer/system-config-printer.py:334: 
DeprecationWarning: Gtk.ActionGroup.get_action is deprecated
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]:   act = 
printer_manager_action_group.get_action (action)
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]: 
/usr/share/system-config-printer/system-config-printer.py:364: 
DeprecationWarning: Gtk.UIManager.ensure_update is deprecated
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]:   
self.ui_manager.ensure_update ()
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]: 
/usr/share/system-config-printer/system-config-printer.py:365: 
DeprecationWarning: Gtk.UIManager.get_accel_group is deprecated
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]:   
self.PrintersWindow.add_accel_group (self.ui_manager.get_accel_group ())
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]: 
/usr/share/system-config-printer/system-config-printer.py:374: 
DeprecationWarning: Gtk.UIManager.get_action is deprecated
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]:   action = 
self.ui_manager.get_action ("/new-printer")
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]: 
/usr/share/system-config-printer/system-config-printer.py:375: 
DeprecationWarning: Gtk.Action.create_menu_item is deprecated
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]:   newprinteritem = 
action.create_menu_item ()
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]: 
/usr/share/system-config-printer/system-config-printer.py:673: 
DeprecationWarning: Gtk.Action.get_proxies is deprecated
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]:   for widget in 
action.get_proxies ():
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]: 
/usr/share/system-config-printer/system-config-printer.py:2253: 
DeprecationWarning: Gdk.threads_enter is deprecated
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]:   Gdk.threads_enter ()
Mar 24 16:10:51 semiauto dbus-daemon[764]: [system] Activating via systemd: 
service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.1686' (uid=1000 
pid=395280 comm="/usr/bin/python3 /usr/share/system-config-printer/" 
label="unconfined")
Mar 24 16:10:51 semiauto systemd[1]: Starting Hostname Service...
Mar 24 16:10:51 semiauto dbus-daemon[764]: [system] Successfully activated 
service 'org.freedesktop.hostname1'
Mar 24 16:10:51 semiauto systemd[1]: Started Hostname Service.
Mar 24 16:10:53 semiauto kernel: [663246.142511] serial :00:16.3: LSR 
safety check engaged!
Mar 24 16:10:53 semiauto kernel: [663246.142539] audit: type=1400 
audit(1679688653.733:100): apparmor="DENIED" operation="capable" class="cap" 
profile="/usr/sbin/cupsd" pid=395323 comm="serial" capability=21  
capname="sys_admin"


Here were a few other telling messages:
Mar 24 16:13:14 semiauto kernel: [663387.182005] audit: type=1400 
audit(1679688794.769:101): apparmor="DENIED" operation="file_lock" class="file" 
profile="/usr/sbin/cupsd" name="/run/utmp" pid=287961 comm="cupsd" 
requested_mask="k" denied_mask="k" fsuid=0 ouid=0
Mar 24 16:13:17 semiauto kernel: [663389.718118] audit: type=1400 
audit(1679688797.305:102): apparmor="DENIED" operation="file_lock" class="file" 
profile="/usr/sbin/cupsd" name="/run/utmp" pid=287961 comm="cupsd" 
requested_mask="k" denied_mask="k" fsuid=0 ouid=0
Mar 24 16:13:24 semiauto 

[Touch-packages] [Bug 2009230] Re: AppArmor denials for rsyslog

[Georgia Garcia]

I added the consoles abstraction to the rsyslog AppArmor profile and I
also had to add syslog to the tty group, otherwise rsyslog would not
have been able to write to /dev/console due to file permissions (bug
1890177).

I added the proposed changes to this PPA
https://launchpad.net/~georgiag/+archive/ubuntu/rsyslog-console

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

Title:
  AppArmor denials for rsyslog

Status in gce-compute-image-packages package in Ubuntu:
  New
Status in rsyslog package in Ubuntu:
  New
Status in gce-compute-image-packages source package in Lunar:
  New
Status in rsyslog source package in Lunar:
  New

Bug description:
  The AppArmor profile for rsyslog, which had been disabled on previous
  Ubuntu versions, was enabled in lunar.

  The package google-compute-engine added a config file to rsyslog which
  requires rw access to /dev/console

  google:ubuntu-23.04-64 /root# cat /etc/rsyslog.d/90-google.conf
  # Google Compute Engine default console logging.
  #
  # daemon: logging from Google provided daemons.
  # kern: logging information in case of an unexpected crash during boot.
  #
  daemon,kern.* /dev/console

  google:ubuntu-23.04-64 /root# apt-file search /etc/rsyslog.d/90-google.conf
  google-compute-engine: /etc/rsyslog.d/90-google.conf

  So in gce cloud images, we are getting the following denials:

  [ 1500.302082] audit: type=1400 audit(1677876883.728:495):
  apparmor="DENIED" operation="open" class="file" profile="rsyslogd"
  name="/dev/console" pid=603 comm=72733A6D61696E20513A526567
  requested_mask="ac" denied_mask="ac" fsuid=101 ouid=0

  To fix it, we just need to add
    /dev/console rw,
  to /etc/apparmor.d/usr.sbin.rsyslogd

  or the same permission should be added to a file in
  /etc/apparmor.d/rsyslog.d/ by the google-compute-engine package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/2009230/+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 1973149] Re: system uses merged-usr-via-aliased-dirs, going behind dpkg's back, breaking its core assumptions

[Nick Rosbrook]

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

** Changed in: dpkg (Ubuntu Kinetic)
   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/1973149

Title:
  system uses merged-usr-via-aliased-dirs, going behind dpkg's  back,
  breaking its core assumptions

Status in dpkg package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in dpkg source package in Kinetic:
  Fix Released
Status in systemd source package in Kinetic:
  Invalid

Bug description:
  Got this warning on Kinetic, Mate flavor:

  Paramétrage de dpkg (1.21.7ubuntu3) ...
  dpkg: warning:

   This system uses merged-usr-via-aliased-dirs, going behind dpkg's
  back, breaking its core assumptions. This can cause silent file
  overwrites and disappearances, and its general tools misbehavior.

   See .
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  Package: dpkg 1.21.7ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Tags: kinetic package-from-proposed third-party-packages
  Uname: Linux 5.15.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1973149/+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 1930482] Re: netplan crash on ubuntu 20.04 disabling network

[Nick Rosbrook]

** Changed in: systemd (Ubuntu Focal)
   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/1930482

Title:
  netplan crash on ubuntu 20.04 disabling network

Status in netplan:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Invalid

Bug description:
  On ubuntu 20.04 with netplan 0.102-0ubuntu1~20.04.2, the server loss
  both IPv4 and IPv6 address in a while with DHCP config. The are no way
  to restore network, only by rebooting the server.

  Trying to restart the server networking using "systemctl restart
  systemd-networkd" or "netplan apply" fails.

  Note: systemctl and netplay apply fails also with a netplan with
  static IP address

  The server runs on OVS in cloud.ramnode.com

  I'm pasting config, logs, netplan and restart output (IP and mac
  address are masked)

  I don't see a workaound yet, only to restart server to change the
  network configuration.

  File: 50-cloud-init.yaml
  ==
  # This file is generated from information provided by the datasource.  Changes
  # to it will not persist across an instance reboot.  To disable cloud-init's
  # network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  accept-ra: true
  dhcp4: true
  dhcp6: true
  match:
  macaddress: **:**:**:**:**:**:**
  mtu: 1500
  set-name: ens3
  =

  Syslog
  =
  2021-06-01T19:31:01.063935-04:00 server systemd[1]: Stopped Network Service.
  2021-06-01T19:31:01.066766-04:00 server systemd[1]: Starting Network 
Service...
  2021-06-01T19:31:01.161797-04:00 server systemd-networkd[2302]: 
/run/systemd/network/10-netplan-ens3.network: MTUBytes= in [Link] section and 
UseMTU= in [DHCP] section are set. Disabling UseMTU=.
  2021-06-01T19:31:01.161990-04:00 server systemd-networkd[2302]: loop3456: 
netdev ready
  2021-06-01T19:31:01.162073-04:00 server systemd-networkd[2302]: Tunnel127: 
Gained IPv6LL
  2021-06-01T19:31:01.162184-04:00 server systemd-networkd[2302]: Tunnel126: 
Gained IPv6LL
  2021-06-01T19:31:01.162275-04:00 server systemd-networkd[2302]: loop3456: 
Gained IPv6LL
  2021-06-01T19:31:01.162349-04:00 server systemd-networkd[2302]: ens3: Gained 
IPv6LL
  2021-06-01T19:31:01.164685-04:00 server systemd-networkd[2302]: Assertion 
'ifindex' failed at src/network/networkd-link.c:757, function link_get(). 
Aborting.
  2021-06-01T19:31:01.553611-04:00 server systemd[1]: systemd-networkd.service: 
Main process exited, code=dumped, status=6/ABRT
  2021-06-01T19:31:01.553796-04:00 server systemd[1]: systemd-networkd.service: 
Failed with result 'core-dump'.
  2021-06-01T19:31:01.553892-04:00 server systemd[1]: Failed to start Network 
Service.
  2021-06-01T19:31:01.553983-04:00 server systemd[1]: systemd-networkd.service: 
Scheduled restart job, restart counter is at 2.
  

  output of: netapply --debug try
  
  DEBUG:ens3 not found in {}
  DEBUG:loop3456 not found in {}
  DEBUG:Merged config:
  network:
bridges:
  loop3456:
accept-ra: false
addresses:
- 10.65.0.3/32
dhcp4: false
dhcp6: false
interfaces: []
ethernets:
  ens3:
accept-ra: true
addresses:
- XXX.XXX.XXX.XXX/24
dhcp4: false
dhcp6: true
gateway4: XXX.XXX.XXX.XXX
match:
  macaddress: **:**:**:**:**:**:**
mtu: 1500
nameservers:
  addresses:
  - 8.8.8.8
  - 8.8.4.4
  search:
  - uc.edu.ve
set-name: ens3
version: 2

  DEBUG:New interfaces: set()
  ** (generate:1484): DEBUG: 20:14:22.895: Processing input file 
/etc/netplan/50-static.yaml..
  ** (generate:1484): DEBUG: 20:14:22.895: starting new processing pass
  ** (generate:1484): DEBUG: 20:14:22.895: Processing input file 
/etc/netplan/99-local.yaml..
  ** (generate:1484): DEBUG: 20:14:22.895: starting new processing pass
  ** (generate:1484): DEBUG: 20:14:22.895: We have some netdefs, pass them 
through a final round of validation
  ** (generate:1484): DEBUG: 20:14:22.895: ens3: setting default backend to 1
  ** (generate:1484): DEBUG: 20:14:22.895: Configuration is valid
  ** (generate:1484): DEBUG: 20:14:22.895: loop3456: setting default backend to 
1
  ** (generate:1484): DEBUG: 20:14:22.895: Configuration is valid
  ** (generate:1484): DEBUG: 20:14:22.896: Generating output files..
  ** (generate:1484): DEBUG: 20:14:22.896: openvswitch: 

[Touch-packages] [Bug 2012623] Re: 23.04 apparmor package crashed

[Bernard Stafford]

** Changed in: apparmor (Ubuntu)
   Status: Opinion => Invalid

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

Title:
  23.04 apparmor package crashed

Status in apparmor package in Ubuntu:
  Invalid

Bug description:
  Edubuntu 23.04 apparmor package crashed during QA Testing Build 20230323.
  In addition to the crash the mouse pointer/spinner during the
  install did not spin it was stationary.
  Install completed as expected except for the package crash.
  apparmor:
    Installed: 3.0.8-1ubuntu2
    Candidate: 3.0.8-1ubuntu2
    Version table:
   *** 3.0.8-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  100 /var/lib/dpkg/status
  No LSB modules are available.
  Description:  Ubuntu Lunar Lobster (development branch)
  Release:  23.04

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: apparmor 3.0.8-1ubuntu2
  Uname: Linux 6.2.0-18-generic x86_64
  Architecture: amd64
  Date: Thu Mar 23 07:18:57 2023
  ExecutablePath: /usr/sbin/apparmor_parser
  ExecutableTimestamp: 1677622692
  ProcCmdline: apparmor_parser --replace --write-cache -O no-expr-simplify 
--cache-loc=/var/cache/apparmor -j2 --skip-read-cache --quiet 
/var/lib/snapd/apparmor/profiles/snap-update-ns.firefox 
/var/lib/snapd/apparmor/profiles/snap.firefox.firefox 
/var/lib/snapd/apparmor/profiles/snap.firefox.geckodriver 
/var/lib/snapd/apparmor/profiles/snap.firefox.hook.configure 
/var/lib/snapd/apparmor/profiles/snap.firefox.hook.connect-plug-host-hunspell 
/var/lib/snapd/apparmor/profiles/snap.firefox.hook.disconnect-plug-host-hunspell
 /var/lib/snapd/apparmor/profiles/snap.firefox.hook.post-refresh
  ProcCwd: /
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  Signal: 6
  SourcePackage: apparmor
  UserGroups: N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2012623/+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 2003797] Autopkgtest regression report (tzdata/2023a-0ubuntu0.22.10.0)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted tzdata (2023a-0ubuntu0.22.10.0) for 
kinetic have finished running.
The following regressions have been reported in tests triggered by the package:

chrony/4.2-2ubuntu2 (amd64, arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/kinetic/update_excuses.html#tzdata

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Pre-1970 timestamps are knowingly wrong

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Bionic:
  New
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Kinetic:
  Fix Committed

Bug description:
  [ Impact ]

  tzdata 2021b says in NEWS: "Merge more location-based Zones whose
  timestamps agree since 1970, as pre-1970 timestamps are out of scope.
  This is part of a process that has been ongoing since 2013.  This does
  not affect post-1970 timestamps, and timezone historians who build
  with 'make PACKRATDATA=backzone' should see no changes to pre-1970
  timestamps." tzdata 2022b finished that process: "Finish moving to
  'backzone' the location-based zones whose timestamps since 1970 are
  duplicates; adjust links accordingly. This change ordinarily affects
  only pre-1970 timestamps, and with the new PACKRATLIST option it does
  not affect any timestamps. In this round the affected zones are
  Antarctica/Vostok, Asia/Brunei, Asia/Kuala_Lumpur, Atlantic/Reykjavik,
  Europe/Amsterdam, Europe/Copenhagen, Europe/Luxembourg, Europe/Monaco,
  Europe/Oslo, Europe/Stockholm, Indian/Christmas, Indian/Cocos,
  Indian/Kerguelen, Indian/Mahe, Indian/Reunion, Pacific/Chuuk,
  Pacific/Funafuti, Pacific/Majuro, Pacific/Pohnpei, Pacific/Wake and
  Pacific/Wallis, and the affected links are Arctic/Longyearbyen,
  Atlantic/Jan_Mayen, Iceland, Pacific/Ponape, Pacific/Truk, and
  Pacific/Yap."

  The Debian/Ubuntu package builds tzdata with the default settings
  (PACKRATDATA unset) which merges zones whose timestamps agree since
  1970. This leads to timestamps before 1970 being knowingly wrong.
  Example: Europe/Oslo is a link to Europe/Berlin since they are
  identical since 1970, but they differed before 1965. Berlin observed
  no summertime between 1950 and 1980, but Oslo did in 1959 to 1965. So
  summer 1960 in Oslo should be UTC+2 compared to UTC+1 in Berlin:

  ```
  $ TZ=Europe/Oslo date -d "1960-07-01 10:00 Z"
  Fri Jul  1 12:00:00 CEST 1960
  $ TZ=Europe/Berlin date -d "1960-07-01 10:00 Z"
  Fri Jul  1 11:00:00 CET 1960
  ```

  There was a big debate upstream (see https://lwn.net/Articles/870478/
  or https://mm.icann.org/pipermail/tz/2021-May/030137.html). The
  Debian/Ubuntu package should ship timezones from backzone. Users that
  care about pre-1970 timestamps will be satisfied and users not caring
  will probably not care about the additional timezones.

  The install size will increase by around 20% and the amount of
  distinct (i.e. not symlinked) timezones will increase by 33%:

  ```
  $ grep ^Zone africa antarctica asia australasia etcetera europe factory 
northamerica southamerica | wc -l
  352
  $ grep ^Zone backzone | wc -l
  119
  ```

  [ Test plan ]

  The test case `test_pre_1970_timestamps` was added to the python
  autopkgtest for testing this change. So the test plan is to check that
  the autopkgtest succeeds.

  [ Where problems could occur ]

  Systems with incorrect timezone set may observe unexpected time shift.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2003797/+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 2012599] Autopkgtest regression report (tzdata/2023a-0ubuntu0.22.10.0)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted tzdata (2023a-0ubuntu0.22.10.0) for 
kinetic have finished running.
The following regressions have been reported in tests triggered by the package:

chrony/4.2-2ubuntu2 (amd64, arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/kinetic/update_excuses.html#tzdata

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  tzdata 2023a/2023b release - Egypt restoring DST

Status in tzdata package in Ubuntu:
  Fix Committed
Status in tzdata source package in Bionic:
  New
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Kinetic:
  Fix Committed
Status in tzdata source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  Recently the Egyptian authorities decided to restore DST. The first
  switch after the change is expected to take place on last Friday of
  April. The upstream tzdata 2023a release already reflects this change.

  The 2023a release contains the following changes:

  * Egypt now uses DST again, from April through October.
  * This year Morocco springs forward April 23, not April 30.
  * Palestine delays the start of DST this year.
  * Much of Greenland still uses DST from 2024 on.

  [ Test Plan ]

  Test cases were added to the autopkgtest to cover the testing:

  * python: test_2023a
  * python: test_2023b
  * python-icu: test_2023a (only for kinetic, jammy, focal)

  So the test plan is to check that the autopkgtest succeeds.

  Alternatively the python test_2023a can be run manually:

   * Set system timezone to Egypt (e.g. Africa/Cairo).
   * Set system time to 2023-04-27 23:59.
   * Wait and observe what happens at 2023-04-28 0:00

  [Test Case for releases <= 20.04 LTS]

  Additionally, an upstream update of tzdata removed the 'old' SystemV 
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and 
earlier releases. Subsequently, these should be checked for using the following:
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  [ Where problems could occur ]

   * Systems with incorrect timezone set (e.g. located outside of Egypt
  but still using Egyptian time) may observe unexpected time shift.

  [ Other Info ]

   * More information with sources:
  
https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023.

  The SRUs to the stable include the recent changes for generating the
  debconf template and the timezone mappings in convert_timezone().
  Previous SRUs did forget to update them for the changes from upstream.
  All added tests were also backported.

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

[Brian Murray]

Hello Dariusz, or anyone else affected,

Accepted tzdata into kinetic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2023b-0ubuntu0.22.10.0 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.

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

Title:
  tzdata 2023a/2023b release - Egypt restoring DST

Status in tzdata package in Ubuntu:
  Fix Committed
Status in tzdata source package in Bionic:
  New
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Kinetic:
  Fix Committed
Status in tzdata source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  Recently the Egyptian authorities decided to restore DST. The first
  switch after the change is expected to take place on last Friday of
  April. The upstream tzdata 2023a release already reflects this change.

  The 2023a release contains the following changes:

  * Egypt now uses DST again, from April through October.
  * This year Morocco springs forward April 23, not April 30.
  * Palestine delays the start of DST this year.
  * Much of Greenland still uses DST from 2024 on.

  [ Test Plan ]

  Test cases were added to the autopkgtest to cover the testing:

  * python: test_2023a
  * python: test_2023b
  * python-icu: test_2023a (only for kinetic, jammy, focal)

  So the test plan is to check that the autopkgtest succeeds.

  Alternatively the python test_2023a can be run manually:

   * Set system timezone to Egypt (e.g. Africa/Cairo).
   * Set system time to 2023-04-27 23:59.
   * Wait and observe what happens at 2023-04-28 0:00

  [Test Case for releases <= 20.04 LTS]

  Additionally, an upstream update of tzdata removed the 'old' SystemV 
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and 
earlier releases. Subsequently, these should be checked for using the following:
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  [ Where problems could occur ]

   * Systems with incorrect timezone set (e.g. located outside of Egypt
  but still using Egyptian time) may observe unexpected time shift.

  [ Other Info ]

   * More information with sources:
  
https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023.

  The SRUs to the stable include the recent changes for generating the
  debconf template and the timezone mappings in convert_timezone().
  Previous SRUs did forget to update them for the changes from upstream.
  All added tests were also backported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+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 2012623] ThreadStacktrace.txt

[Apport retracing service]

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/2012623/+attachment/5657333/+files/ThreadStacktrace.txt

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/2012623/+attachment/5656864/+files/CoreDump.gz

** Changed in: apparmor (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  23.04 apparmor package crashed

Status in apparmor package in Ubuntu:
  Opinion

Bug description:
  Edubuntu 23.04 apparmor package crashed during QA Testing Build 20230323.
  In addition to the crash the mouse pointer/spinner during the
  install did not spin it was stationary.
  Install completed as expected except for the package crash.
  apparmor:
    Installed: 3.0.8-1ubuntu2
    Candidate: 3.0.8-1ubuntu2
    Version table:
   *** 3.0.8-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  100 /var/lib/dpkg/status
  No LSB modules are available.
  Description:  Ubuntu Lunar Lobster (development branch)
  Release:  23.04

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: apparmor 3.0.8-1ubuntu2
  Uname: Linux 6.2.0-18-generic x86_64
  Architecture: amd64
  Date: Thu Mar 23 07:18:57 2023
  ExecutablePath: /usr/sbin/apparmor_parser
  ExecutableTimestamp: 1677622692
  ProcCmdline: apparmor_parser --replace --write-cache -O no-expr-simplify 
--cache-loc=/var/cache/apparmor -j2 --skip-read-cache --quiet 
/var/lib/snapd/apparmor/profiles/snap-update-ns.firefox 
/var/lib/snapd/apparmor/profiles/snap.firefox.firefox 
/var/lib/snapd/apparmor/profiles/snap.firefox.geckodriver 
/var/lib/snapd/apparmor/profiles/snap.firefox.hook.configure 
/var/lib/snapd/apparmor/profiles/snap.firefox.hook.connect-plug-host-hunspell 
/var/lib/snapd/apparmor/profiles/snap.firefox.hook.disconnect-plug-host-hunspell
 /var/lib/snapd/apparmor/profiles/snap.firefox.hook.post-refresh
  ProcCwd: /
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  Signal: 6
  SourcePackage: apparmor
  UserGroups: N/A

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

[Apport retracing service]

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/2012623/+attachment/5657332/+files/StacktraceSource.txt

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

Title:
  23.04 apparmor package crashed

Status in apparmor package in Ubuntu:
  Opinion

Bug description:
  Edubuntu 23.04 apparmor package crashed during QA Testing Build 20230323.
  In addition to the crash the mouse pointer/spinner during the
  install did not spin it was stationary.
  Install completed as expected except for the package crash.
  apparmor:
    Installed: 3.0.8-1ubuntu2
    Candidate: 3.0.8-1ubuntu2
    Version table:
   *** 3.0.8-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  100 /var/lib/dpkg/status
  No LSB modules are available.
  Description:  Ubuntu Lunar Lobster (development branch)
  Release:  23.04

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: apparmor 3.0.8-1ubuntu2
  Uname: Linux 6.2.0-18-generic x86_64
  Architecture: amd64
  Date: Thu Mar 23 07:18:57 2023
  ExecutablePath: /usr/sbin/apparmor_parser
  ExecutableTimestamp: 1677622692
  ProcCmdline: apparmor_parser --replace --write-cache -O no-expr-simplify 
--cache-loc=/var/cache/apparmor -j2 --skip-read-cache --quiet 
/var/lib/snapd/apparmor/profiles/snap-update-ns.firefox 
/var/lib/snapd/apparmor/profiles/snap.firefox.firefox 
/var/lib/snapd/apparmor/profiles/snap.firefox.geckodriver 
/var/lib/snapd/apparmor/profiles/snap.firefox.hook.configure 
/var/lib/snapd/apparmor/profiles/snap.firefox.hook.connect-plug-host-hunspell 
/var/lib/snapd/apparmor/profiles/snap.firefox.hook.disconnect-plug-host-hunspell
 /var/lib/snapd/apparmor/profiles/snap.firefox.hook.post-refresh
  ProcCwd: /
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  Signal: 6
  SourcePackage: apparmor
  UserGroups: N/A

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

[Apport retracing service]

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/2012623/+attachment/5657331/+files/Stacktrace.txt

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

Title:
  23.04 apparmor package crashed

Status in apparmor package in Ubuntu:
  Opinion

Bug description:
  Edubuntu 23.04 apparmor package crashed during QA Testing Build 20230323.
  In addition to the crash the mouse pointer/spinner during the
  install did not spin it was stationary.
  Install completed as expected except for the package crash.
  apparmor:
    Installed: 3.0.8-1ubuntu2
    Candidate: 3.0.8-1ubuntu2
    Version table:
   *** 3.0.8-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  100 /var/lib/dpkg/status
  No LSB modules are available.
  Description:  Ubuntu Lunar Lobster (development branch)
  Release:  23.04

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: apparmor 3.0.8-1ubuntu2
  Uname: Linux 6.2.0-18-generic x86_64
  Architecture: amd64
  Date: Thu Mar 23 07:18:57 2023
  ExecutablePath: /usr/sbin/apparmor_parser
  ExecutableTimestamp: 1677622692
  ProcCmdline: apparmor_parser --replace --write-cache -O no-expr-simplify 
--cache-loc=/var/cache/apparmor -j2 --skip-read-cache --quiet 
/var/lib/snapd/apparmor/profiles/snap-update-ns.firefox 
/var/lib/snapd/apparmor/profiles/snap.firefox.firefox 
/var/lib/snapd/apparmor/profiles/snap.firefox.geckodriver 
/var/lib/snapd/apparmor/profiles/snap.firefox.hook.configure 
/var/lib/snapd/apparmor/profiles/snap.firefox.hook.connect-plug-host-hunspell 
/var/lib/snapd/apparmor/profiles/snap.firefox.hook.disconnect-plug-host-hunspell
 /var/lib/snapd/apparmor/profiles/snap.firefox.hook.post-refresh
  ProcCwd: /
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  Signal: 6
  SourcePackage: apparmor
  UserGroups: N/A

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

[Apport retracing service]

StacktraceTop:
 __libc_message (fmt=fmt@entry=0x7f9497db890f "%s\n") at 
../sysdeps/posix/libc_fatal.c:150
 malloc_printerr (str=str@entry=0x7f9497db6379 "corrupted double-linked list") 
at ./malloc/malloc.c:5651
 unlink_chunk (p=, av=0x7f9497df6c80 ) at 
./malloc/malloc.c:1611
 malloc_consolidate (av=av@entry=0x7f9497df6c80 ) at 
./malloc/malloc.c:4766
 _int_malloc (av=av@entry=0x7f9497df6c80 , bytes=25928) at 
./malloc/malloc.c:3951

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

Title:
  23.04 apparmor package crashed

Status in apparmor package in Ubuntu:
  Opinion

Bug description:
  Edubuntu 23.04 apparmor package crashed during QA Testing Build 20230323.
  In addition to the crash the mouse pointer/spinner during the
  install did not spin it was stationary.
  Install completed as expected except for the package crash.
  apparmor:
    Installed: 3.0.8-1ubuntu2
    Candidate: 3.0.8-1ubuntu2
    Version table:
   *** 3.0.8-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  100 /var/lib/dpkg/status
  No LSB modules are available.
  Description:  Ubuntu Lunar Lobster (development branch)
  Release:  23.04

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: apparmor 3.0.8-1ubuntu2
  Uname: Linux 6.2.0-18-generic x86_64
  Architecture: amd64
  Date: Thu Mar 23 07:18:57 2023
  ExecutablePath: /usr/sbin/apparmor_parser
  ExecutableTimestamp: 1677622692
  ProcCmdline: apparmor_parser --replace --write-cache -O no-expr-simplify 
--cache-loc=/var/cache/apparmor -j2 --skip-read-cache --quiet 
/var/lib/snapd/apparmor/profiles/snap-update-ns.firefox 
/var/lib/snapd/apparmor/profiles/snap.firefox.firefox 
/var/lib/snapd/apparmor/profiles/snap.firefox.geckodriver 
/var/lib/snapd/apparmor/profiles/snap.firefox.hook.configure 
/var/lib/snapd/apparmor/profiles/snap.firefox.hook.connect-plug-host-hunspell 
/var/lib/snapd/apparmor/profiles/snap.firefox.hook.disconnect-plug-host-hunspell
 /var/lib/snapd/apparmor/profiles/snap.firefox.hook.post-refresh
  ProcCwd: /
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  Signal: 6
  SourcePackage: apparmor
  UserGroups: N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2012623/+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 2012734] Re: no audio after update

[Launchpad Bug Tracker]

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

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

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

Title:
  no audio after update

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 22.10
  Release:  22.10

  
  during normal patching Ubuntu pushed from kernel 5.19.0-31 to 5.19.0-35. 
After this push, I lost audio from my AMD RX570 hdmi. I booted back to -31 
waiting for the next kernel push in the hopes the problem would be caught and 
addressed. It wasn't, and still persists in -38. The card info is below and was 
taken while booted into -38.

  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev ef)
  01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI 
Audio [Radeon RX 470/480 / 570/580/590]

  root@x:~# hwinfo --sound
  35: PCI 100.1: 0403 Audio device
  [Created at pci.386]
  Unique ID: NXNs.TsyFmhFLPLA
  Parent ID: mnDB.fA+tdbAkMSD
  SysFS ID: /devices/pci:00/:00:01.1/:01:00.1
  SysFS BusID: :01:00.1
  Hardware Class: sound
  Model: "ATI Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]"
  Vendor: pci 0x1002 "ATI Technologies Inc"
  Device: pci 0xaaf0 "Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]"
  SubVendor: pci 0x1458 "Gigabyte Technology Co., Ltd"
  SubDevice: pci 0xaaf0
  Driver: "snd_hda_intel"
  Driver Modules: "snd_hda_intel"
  Memory Range: 0xfcf6-0xfcf63fff (rw,non-prefetchable)
  IRQ: 86 (5 events)
  Module Alias: "pci:v1002dAAF0sv1458sdAAF0bc04sc0 3i00"
  Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #31 (PCI bridge)


  The errors I am getting during intialization are:

  [ 4.895282] hdaudio hdaudioC0D0: no AFG or MFG node found
  [ 4.895306] snd_hda_intel :01:00.1: no codecs initialized

  
  and if I try to validate the card

  root@x:~# aplay -l
  aplay: device_list:274: no soundcards found...

  I have tried passing numerous arguments to the module but to no avail.
  Booting back to -31 brings the card right back to fully functioning. I
  believe there has been an update to snd_hda_intel which is causing
  this issue and is most likely a regression situation. Can anyone
  assist? I have searched for a model to be passed specific to AMD
  cards, but can't find one. Any suggestions would be greatly
  appreciated. Additionally, I'm wondering if this should be directed to
  Ubuntu, or should it go to kernel.org the HD-Audio group? Again,
  thanks for your thoughts.

  options snd_hda_intel dmic_detect=0
  options snd_hda_intel model=generic
  options snd_hda_intel model=auto
  options snd_hda_intel probe_mask=1
  options snd-intel-dspcfg dsp_driver=1

  Under -31 the error messages are not displayed, sound works. If I
  again validate, I get the below:

  root@media2:~# aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 9: HDMI 3 [65Q825]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 11: HDMI 5 [HDMI 5]
Subdevices: 1/1
Subdevice #0: subdevice #0

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pulseaudio 1:16.1+dfsg1-1ubuntu3.1
  ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17
  Uname: Linux 5.19.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:gdm1585 F pipewire
  CasperMD5CheckResult: unknown
  Date: Fri Mar 24 07:45:50 2023
  InstallationDate: Installed on 2019-05-09 (1415 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to kinetic on 2023-01-13 (69 days ago)
  dmi.bios.date: 11/27/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  

[Touch-packages] [Bug 2009502] Re: Enable /dev/sgx_vepc access for the group 'sgx'

[William Wilson]

The verification passed for jammy:

william@william-Latitude-E7470  ~  apt-cache policy udev
udev:
  Installed: 249.11-0ubuntu3.7
  Candidate: 249.11-0ubuntu3.9
  Version table:
 249.11-0ubuntu3.9 500 
500 http://us.archive.ubuntu.com/ubuntu jammy-proposed/main amd64 
Packages
 *** 249.11-0ubuntu3.7 500 
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
100 /var/lib/dpkg/status
 249.11-0ubuntu3 500 
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
 william@william-Latitude-E7470  ~  ls -l /dev/sgx_vepc
crw--- 1 root root 10, 125 Mar 24 12:42 /dev/sgx_vepc
william@william-Latitude-E7470  ~  apt-cache policy udev
udev:
  Installed: 249.11-0ubuntu3.9
  Candidate: 249.11-0ubuntu3.9
  Version table:
 *** 249.11-0ubuntu3.9 500 
500 http://us.archive.ubuntu.com/ubuntu jammy-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 249.11-0ubuntu3.7 500 
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
 249.11-0ubuntu3 500 
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
 william@william-Latitude-E7470  ~  ls -l /dev/sgx_vepc  
crw-rw 1 root sgx 10, 125 Mar 24 12:48 /dev/sgx_vepc
 william@william-Latitude-E7470  ~ 


** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done 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/2009502

Title:
   Enable /dev/sgx_vepc access for the group 'sgx'

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

  On systems where Intel SGX is available, access to a specific device
  node (/dev/sgx_vepc) must be enforced, with a specific permission
  (0660) and group (sgx).

  This allows KVM-based virtual machines to use such feature (the SGX
  "enclaves") in a proper fashion.  Without this, a manual udev rule
  needs to be created.

  [ Test Plan ]

  As the patch itself only tailors the permissions/group to the device
  node, in a system with Intel-SGX enabled, merely `ls -la` against the
  device node should show if the permissions and group are seen as
  expected.

  [ Where problems could occur ]

  N/A.  This seems to be a very straightforward inclusion, very specific
  to access enablement to the SGX reserved memory used for hosting
  enclaves.

  [ Other Info ]

  N/A.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2009502/+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 2012298] Re: PasswordAuthenticaion in sshd_config.d

[Lena Voytek]

Thanks for the update! I managed to reproduce this on my end:

$ lxc launch images:ubuntu/focal test-ssh-focal
$ lxc exec test-ssh-focal bash

# apt update && apt upgrade -y
# apt install openssh-server
# adduser user

> ssh into container from another terminal to show pw auth is available
by default:

$ ssh user@
user@'s password:

> Update /etc/ssh/sshd_config with the following in first terminal

Match User user
  PasswordAuthentication No
Match All

# systemctl restart sshd

> Check again in other terminal

$ ssh user@
user@: Permission denied (publickey).

> Now remove the lines from /etc/ssh/sshd_config and add them to
/etc/ssh/sshd_config.d/username.conf

# systemctl restart sshd

> Check if the other config worked in other terminal (it does not)

$ ssh user@
user@'s password:


I did, however, confirm this works for Jammy and Kinetic, so this is a 
Focal-specific issue. Marking as such




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

** Changed in: openssh (Ubuntu)
   Status: Incomplete => Fix Released

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

** Tags added: server-todo

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

Title:
  PasswordAuthenticaion in sshd_config.d

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Focal:
  Confirmed

Bug description:
  The stanza
  Match User 
PasswordAuthentication no

  in /etc/ssh/sshd_config works as expected.

  The same stanza in /etc/ssh/sshd_config.d/username.conf does not work.

  The Include in /etc/ssh/sshd_config is not commented out, and

  /usr/sbin/sshd -D -ddd

  shows the username.config file being parsed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openssh-server 1:8.2p1-4ubuntu0.5
  ProcVersionSignature: Ubuntu 5.4.0-131.147-generic 5.4.210
  Uname: Linux 5.4.0-131-generic x86_64
  NonfreeKernelModules: falcon_lsm_serviceable falcon_nf_netcontain falcon_kal 
falcon_lsm_pinned_14713
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Mar 20 13:34:14 2023
  InstallationDate: Installed on 2022-11-04 (136 days ago)
  InstallationMedia:
   
  SSHDConfig: Error: command ['pkexec', '/usr/sbin/sshd', '-T'] failed with 
exit code 127: pkexec must be setuid root
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2012298/+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 2002445] Re: udev NIC renaming race with mlx5_core driver

[Nick Rosbrook]

** Changed in: systemd (Ubuntu Focal)
 Assignee: Mustafa Kemal Gilor (mustafakemalgilor) => Nick Rosbrook (enr0n)

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

Title:
  udev NIC renaming race with mlx5_core driver

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Jammy:
  Fix Committed
Status in systemd source package in Kinetic:
  Fix Committed
Status in systemd source package in Lunar:
  Fix Committed

Bug description:
  [Impact]
  On systems with mellanox NICs, udev's NIC renaming races with the mlx5_core 
driver's own configuration of subordinate interfaces. When the kernel wins this 
race, the device cannot be renamed as udev has attempted, and this causes 
systemd-network-online.target to timeout waiting for links to be configured. 
This ultimately results in boot being delayed by about 2 minutes.

  [Test Plan]
  Repeated launches of Standard_D8ds_v5 instance types will generally hit this 
race around 1 in 10 runs. Create a vm snapshot with updated systemd from 
ppa:enr0n/systemd-245. Launch 100 Standard_D8ds_v5 instances with updated 
systemd. Assert not failure in cloud-init status and no 2 minute delay in 
network-online.target.

  To check for failure symptom:
    - Assert that network-online.target isn't the longest pole from 
systemd-analyze blame.

  To assert success condition during net rename busy race:
    - assert when "eth1" is still the primary device name, that two altnames 
are listed (preserving the altname due to the primary NIC rename being hit.

  Sample script uses pycloudlib to create modified base image for test
  and launches 100 VMs of type Standard_D8ds_v5, counting both successes
  and any failures seen.

  #!/usr/bin/env python3
  # This file is part of pycloudlib. See LICENSE file for license information.
  """Basic examples of various lifecycle with an Azure instance."""

  import logging
  import json

  import pycloudlib
  LOG = logging.getLogger()

  base_cfg = """#cloud-config
  ssh-import-id: [chad.smith, enr0n]
  """

  apt_cfg = """
  # Add developer PPA
  apt:
   sources:
     systemd-testing:
   source: "deb [allow-insecure=yes] 
https://ppa.launchpadcontent.net/enr0n/systemd-245/ubuntu focal main"
  # upgrade systemd after cloud-init is nearly done
  runcmd:
   - apt install systemd udev -y --allow-unauthenticated
  """

  debug_systemd_cfg = """
  # Create systemd-udev debug override.conf in base image
  write_files:
  - path: /etc/systemd/system/systemd-networkd.service.d/override.conf
    owner: root:root
    defer: {defer}
    content: |
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug

  - path: /etc/systemd/system/systemd-udevd.service.d/override.conf
    owner: root:root
    defer: {defer}
    content: |
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug
  LogRateLimitIntervalSec=0
  """

  cloud_config = base_cfg + apt_cfg + debug_systemd_cfg
  cloud_config2 = base_cfg + debug_systemd_cfg

  def debug_systemd_image_launch_overlake_v5_with_snapshot():
  """Test overlake v5 timeouts

  test procedure:
  - Launch base focal image
  - enable ppa:enr0n/systemd-245 and systemd/udev debugging
  - cloud-init clean --logs && deconfigure waalinux agent before shutdown
  - snapshot a base image
  - launch v5 system from snapshot
  - check systemd-analyze for expected timeout
  """
  client = pycloudlib.Azure(tag="azure")

  image_id = client.daily_image(release="focal")
  pub_path = "/home/ubuntu/.ssh/id_rsa.pub"
  priv_path = "/home/ubuntu/.ssh/id_rsa"

  client.use_key(pub_path, priv_path)

  base_instance = client.launch(
  image_id=image_id,
  instance_type="Standard_DS1_v2",
  user_data=cloud_config.format(defer="true"),
  )

  LOG.info(f"base instance: ssh ubuntu@{base_instance.ip}")
  base_instance.wait()
  LOG.info(base_instance.execute("apt cache policy systemd"))
  snapshotted_image_id = client.snapshot(base_instance)

  reproducer = False
  tries = 0
  success_count_with_race = 0
  success_count_no_race = 0
  failure_count_network_delay = 0
  failure_count_no_altnames = 0
  TEST_SUMMARY_TMPL = """
  - Test run complete: {tries} attempted -
  Successes without rename race: {success_count_no_race}
  Successes with rename race and preserved altname: 
{success_count_with_race}
  Failures due to network delay: {failure_count_network_delay}
  Failures due to no altnames persisted: {failure_count_no_altnames}
  ===
  """
  while tries < 100 and not reproducer:
  tries += 1
  new_instance = client.launch(
  image_id=snapshotted_image_id,
  

[Touch-packages] [Bug 2012734] Re: no audio after update

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  no audio after update

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 22.10
  Release:  22.10

  
  during normal patching Ubuntu pushed from kernel 5.19.0-31 to 5.19.0-35. 
After this push, I lost audio from my AMD RX570 hdmi. I booted back to -31 
waiting for the next kernel push in the hopes the problem would be caught and 
addressed. It wasn't, and still persists in -38. The card info is below and was 
taken while booted into -38.

  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev ef)
  01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI 
Audio [Radeon RX 470/480 / 570/580/590]

  root@x:~# hwinfo --sound
  35: PCI 100.1: 0403 Audio device
  [Created at pci.386]
  Unique ID: NXNs.TsyFmhFLPLA
  Parent ID: mnDB.fA+tdbAkMSD
  SysFS ID: /devices/pci:00/:00:01.1/:01:00.1
  SysFS BusID: :01:00.1
  Hardware Class: sound
  Model: "ATI Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]"
  Vendor: pci 0x1002 "ATI Technologies Inc"
  Device: pci 0xaaf0 "Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]"
  SubVendor: pci 0x1458 "Gigabyte Technology Co., Ltd"
  SubDevice: pci 0xaaf0
  Driver: "snd_hda_intel"
  Driver Modules: "snd_hda_intel"
  Memory Range: 0xfcf6-0xfcf63fff (rw,non-prefetchable)
  IRQ: 86 (5 events)
  Module Alias: "pci:v1002dAAF0sv1458sdAAF0bc04sc0 3i00"
  Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #31 (PCI bridge)


  The errors I am getting during intialization are:

  [ 4.895282] hdaudio hdaudioC0D0: no AFG or MFG node found
  [ 4.895306] snd_hda_intel :01:00.1: no codecs initialized

  
  and if I try to validate the card

  root@x:~# aplay -l
  aplay: device_list:274: no soundcards found...

  I have tried passing numerous arguments to the module but to no avail.
  Booting back to -31 brings the card right back to fully functioning. I
  believe there has been an update to snd_hda_intel which is causing
  this issue and is most likely a regression situation. Can anyone
  assist? I have searched for a model to be passed specific to AMD
  cards, but can't find one. Any suggestions would be greatly
  appreciated. Additionally, I'm wondering if this should be directed to
  Ubuntu, or should it go to kernel.org the HD-Audio group? Again,
  thanks for your thoughts.

  options snd_hda_intel dmic_detect=0
  options snd_hda_intel model=generic
  options snd_hda_intel model=auto
  options snd_hda_intel probe_mask=1
  options snd-intel-dspcfg dsp_driver=1

  Under -31 the error messages are not displayed, sound works. If I
  again validate, I get the below:

  root@media2:~# aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 9: HDMI 3 [65Q825]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 11: HDMI 5 [HDMI 5]
Subdevices: 1/1
Subdevice #0: subdevice #0

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pulseaudio 1:16.1+dfsg1-1ubuntu3.1
  ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17
  Uname: Linux 5.19.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:gdm1585 F pipewire
  CasperMD5CheckResult: unknown
  Date: Fri Mar 24 07:45:50 2023
  InstallationDate: Installed on 2019-05-09 (1415 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to kinetic on 2023-01-13 (69 days ago)
  dmi.bios.date: 11/27/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 AORUS PRO WIFI-CF
  

[Touch-packages] [Bug 2012734] [NEW] no audio after update

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Description:Ubuntu 22.10
Release:22.10


during normal patching Ubuntu pushed from kernel 5.19.0-31 to 5.19.0-35. After 
this push, I lost audio from my AMD RX570 hdmi. I booted back to -31 waiting 
for the next kernel push in the hopes the problem would be caught and 
addressed. It wasn't, and still persists in -38. The card info is below and was 
taken while booted into -38.

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev ef)
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI 
Audio [Radeon RX 470/480 / 570/580/590]

root@x:~# hwinfo --sound
35: PCI 100.1: 0403 Audio device
[Created at pci.386]
Unique ID: NXNs.TsyFmhFLPLA
Parent ID: mnDB.fA+tdbAkMSD
SysFS ID: /devices/pci:00/:00:01.1/:01:00.1
SysFS BusID: :01:00.1
Hardware Class: sound
Model: "ATI Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]"
Vendor: pci 0x1002 "ATI Technologies Inc"
Device: pci 0xaaf0 "Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]"
SubVendor: pci 0x1458 "Gigabyte Technology Co., Ltd"
SubDevice: pci 0xaaf0
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xfcf6-0xfcf63fff (rw,non-prefetchable)
IRQ: 86 (5 events)
Module Alias: "pci:v1002dAAF0sv1458sdAAF0bc04sc0 3i00"
Driver Info #0:
Driver Status: snd_hda_intel is active
Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #31 (PCI bridge)


The errors I am getting during intialization are:

[ 4.895282] hdaudio hdaudioC0D0: no AFG or MFG node found
[ 4.895306] snd_hda_intel :01:00.1: no codecs initialized


and if I try to validate the card

root@x:~# aplay -l
aplay: device_list:274: no soundcards found...

I have tried passing numerous arguments to the module but to no avail.
Booting back to -31 brings the card right back to fully functioning. I
believe there has been an update to snd_hda_intel which is causing this
issue and is most likely a regression situation. Can anyone assist? I
have searched for a model to be passed specific to AMD cards, but can't
find one. Any suggestions would be greatly appreciated. Additionally,
I'm wondering if this should be directed to Ubuntu, or should it go to
kernel.org the HD-Audio group? Again, thanks for your thoughts.

options snd_hda_intel dmic_detect=0
options snd_hda_intel model=generic
options snd_hda_intel model=auto
options snd_hda_intel probe_mask=1
options snd-intel-dspcfg dsp_driver=1

Under -31 the error messages are not displayed, sound works. If I again
validate, I get the below:

root@media2:~# aplay -l
 List of PLAYBACK Hardware Devices 
card 0: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: HDMI [HDA ATI HDMI], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: HDMI [HDA ATI HDMI], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: HDMI [HDA ATI HDMI], device 9: HDMI 3 [65Q825]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: HDMI [HDA ATI HDMI], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: HDMI [HDA ATI HDMI], device 11: HDMI 5 [HDMI 5]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: pulseaudio 1:16.1+dfsg1-1ubuntu3.1
ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17
Uname: Linux 5.19.0-38-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/seq:gdm1585 F pipewire
CasperMD5CheckResult: unknown
Date: Fri Mar 24 07:45:50 2023
InstallationDate: Installed on 2019-05-09 (1415 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: Upgraded to kinetic on 2023-01-13 (69 days ago)
dmi.bios.date: 11/27/2019
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F50
dmi.board.asset.tag: Default string
dmi.board.name: B450 AORUS PRO WIFI-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSPROWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSPROWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string

[Touch-packages] [Bug 2011751] Re: openbox crashed with SIGABRT

[Launchpad Bug Tracker]

This bug was fixed in the package openbox - 3.6.1-10ubuntu1

---
openbox (3.6.1-10ubuntu1) lunar; urgency=medium

  * Cherry-pick patch from

http://git.openbox.org/?p=mikachu/openbox.git;a=commit;h=d41128e5a1002af41c976c8860f8299cfcd3cd72
to avoid crashing when switching from a fullscreen window (LP: #2011751)
  * Updated copyright file.

 -- Aaron Rainbolt   Thu, 23 Mar 2023 15:47:38
-0500

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

Title:
  openbox crashed with SIGABRT

Status in glib2.0 package in Ubuntu:
  Invalid
Status in openbox package in Ubuntu:
  Fix Released

Bug description:
  Lubuntu lunar (primary box) on
  - dell [optiplex] 7050 (i5-6500, 16gb, intel hd530/i915)

  I experienced a crash yesterday (openbox) but tend to ignore the first
  crashes... Whilst using the machine again today a crash occurred.

  This is my primary box, so my setup is pretty consistent

  - featherpad (restored session)
  - hexchat (irc)
  - qterminal (only single tab today; usually many)
  - firefox (snap, most sites excluding google related)
  - chromium (snap, used for anything google related)
  - telegram (snap)
  - element

  I was using chromium full screen (trying to read my gmail inbox) when
  borders around windows disappeared & I lost the capacity to switch
  between windows; mouse would move, but keyboard appeared mostly dead
  (it wasn't, more I think windows weren't responding, inc. clicks with
  mouse though that's likely inconsistent; I could [not] work out how to
  describe it yesterday, but todays is almost identical).

  I switched to text terminal (ctrl+alt+f4) & explored; returned to GUI and used
  - ctrl+alt+t to open new terminal
  - openbox &

  session returned to what I expect...

  ** expected outcome

  Openbox doesn't crash

  ** actual outcome

  all windows lost borders, and i lost ability to switch between windows
  I appeared to have minimal control (not true, more a fraction of what I 
expect)

  ** How to get crash

  For me,

  - I used chromium (browser)
  - make chromium full screen (ie. F11)
  - click on link/something & right-click to open in new window
  OPENBOX CRASH.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: openbox 3.6.1-10
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: LXQt
  Date: Thu Mar 16 09:46:22 2023
  ExecutablePath: /usr/bin/openbox
  ExecutableTimestamp: 1643543619
  InstallationDate: Installed on 2023-01-25 (49 days ago)
  InstallationMedia: Lubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230124)
  JournalErrors: -- No entries --
  ProcCmdline: /usr/bin/openbox
  ProcCwd: /home/guiverc
  RebootRequiredPkgs: Error: path contained symlinks.
  Signal: 6
  SourcePackage: openbox
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libobt.so.2
    () at /lib/x86_64-linux-gnu/libc.so.6
   client_calc_layer ()
   ()
   () at /lib/x86_64-linux-gnu/libobt.so.2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+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 2006517] Re: Bluetooth works on desktop but not on ubuntu core

[Alex Kaluzhny]

@AceLan,
In the comment #32 you were saying: "removed the beta bluez, and install stable 
bluez"
It looks like you removed bluez that was from 22/beta track (bluez (22/beta) 
5.64-3),
and then installed one from 20/stable track (bluez 5.53-7 334 20/stable). 
You wrote that with that revision of bluez snap "power cycle the machine, and 
then advinfo works".
Can you please confirm that?

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

Title:
  Bluetooth works on desktop but not on ubuntu core

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  We have built a snap that uses some bluetooth functionality.

  The snap runs well when using Ubuntu desktop 22.04 (all updates applied end 
of Jan 2022).
  We have tried using this same snap on Ubuntu Core 22 running on X86_64.

  On some hardware platforms (thinkpad E15 and x86 Mac) everything works as 
expected.
  We can install the snap on Jammy 22.04 or Core 22 on these platforms and get 
expected functionality regardless of OS.

  
  On our targeted platform (a Dell 5570) things are not working.  When running 
22.04 Jammy, everything works.  When running Core 22, some advanced bluetooth 
functionality is not available.
  Since the Core 22 image installs and runs on other X86_64 hardware we suspect 
a device driver issue.

  Attached are several files taken from the Dell 5570
  1) dmesg from Core 22.
  2) dmesg from Jammy 22.04
  3) output of lspci from Jammy 22.04
  4) Output of lsusb from Jammy 22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+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 2012599] Re: tzdata 2023a/2023b release - Egypt restoring DST

[Benjamin Drung]

** Description changed:

  [ Impact ]
  
  Recently the Egyptian authorities decided to restore DST. The first
  switch after the change is expected to take place on last Friday of
  April. The upstream tzdata 2023a release already reflects this change.
  
  The 2023a release contains the following changes:
  
  * Egypt now uses DST again, from April through October.
  * This year Morocco springs forward April 23, not April 30.
  * Palestine delays the start of DST this year.
  * Much of Greenland still uses DST from 2024 on.
  
  [ Test Plan ]
+ 
+ Test cases were added to the autopkgtest to cover the testing:
+ 
+ * python: test_2023a
+ * python: test_2023b
+ * python-icu: test_2023a (only for kinetic, jammy, focal)
+ 
+ So the test plan is to check that the autopkgtest succeeds.
+ 
+ Alternatively the python test_2023a can be run manually:
  
   * Set system timezone to Egypt (e.g. Africa/Cairo).
   * Set system time to 2023-04-27 23:59.
   * Wait and observe what happens at 2023-04-28 0:00
  
  [ Where problems could occur ]
  
   * Systems with incorrect timezone set (e.g. located outside of Egypt
  but still using Egyptian time) may observe unexpected time shift.
  
  [ Other Info ]
  
   * More information with sources:
  
https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023.
  
  The SRUs to the stable include the recent changes for generating the
  debconf template and the timezone mappings in convert_timezone().
  Previous SRUs did forget to update them for the changes from upstream.
  All added tests were also backported.

** Description changed:

  [ Impact ]
  
  Recently the Egyptian authorities decided to restore DST. The first
  switch after the change is expected to take place on last Friday of
  April. The upstream tzdata 2023a release already reflects this change.
  
  The 2023a release contains the following changes:
  
  * Egypt now uses DST again, from April through October.
  * This year Morocco springs forward April 23, not April 30.
  * Palestine delays the start of DST this year.
  * Much of Greenland still uses DST from 2024 on.
  
  [ Test Plan ]
  
  Test cases were added to the autopkgtest to cover the testing:
  
  * python: test_2023a
  * python: test_2023b
  * python-icu: test_2023a (only for kinetic, jammy, focal)
  
  So the test plan is to check that the autopkgtest succeeds.
  
  Alternatively the python test_2023a can be run manually:
  
   * Set system timezone to Egypt (e.g. Africa/Cairo).
   * Set system time to 2023-04-27 23:59.
   * Wait and observe what happens at 2023-04-28 0:00
  
+ [Test Case for releases <= 20.04 LTS]
+ 
+ Additionally, an upstream update of tzdata removed the 'old' SystemV 
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and 
earlier releases. Subsequently, these should be checked for using the following:
+ diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)
+ 
  [ Where problems could occur ]
  
   * Systems with incorrect timezone set (e.g. located outside of Egypt
  but still using Egyptian time) may observe unexpected time shift.
  
  [ Other Info ]
  
   * More information with sources:
  
https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023.
  
  The SRUs to the stable include the recent changes for generating the
  debconf template and the timezone mappings in convert_timezone().
  Previous SRUs did forget to update them for the changes from upstream.
  All added tests were also backported.

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

Title:
  tzdata 2023a/2023b release - Egypt restoring DST

Status in tzdata package in Ubuntu:
  Fix Committed
Status in tzdata source package in Bionic:
  New
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Kinetic:
  Fix Committed
Status in tzdata source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  Recently the Egyptian authorities decided to restore DST. The first
  switch after the change is expected to take place on last Friday of
  April. The upstream tzdata 2023a release already reflects this change.

  The 2023a release contains the following changes:

  * Egypt now uses DST again, from April through October.
  * This year Morocco springs forward April 23, not April 30.
  * Palestine delays the start of DST this year.
  * Much of Greenland still uses DST from 2024 on.

  [ Test Plan ]

  Test cases were added to the autopkgtest to cover the testing:

  * python: test_2023a
  * python: test_2023b
  * python-icu: test_2023a (only for kinetic, jammy, focal)

  So the test plan is to check that the autopkgtest succeeds.

  

[Touch-packages] [Bug 2003797] Re: Pre-1970 timestamps are knowingly wrong

[Benjamin Drung]

** Description changed:

+ [ Impact ]
+ 
  tzdata 2021b says in NEWS: "Merge more location-based Zones whose
  timestamps agree since 1970, as pre-1970 timestamps are out of scope.
  This is part of a process that has been ongoing since 2013.  This does
  not affect post-1970 timestamps, and timezone historians who build with
  'make PACKRATDATA=backzone' should see no changes to pre-1970
  timestamps." tzdata 2022b finished that process: "Finish moving to
  'backzone' the location-based zones whose timestamps since 1970 are
  duplicates; adjust links accordingly. This change ordinarily affects
  only pre-1970 timestamps, and with the new PACKRATLIST option it does
  not affect any timestamps. In this round the affected zones are
  Antarctica/Vostok, Asia/Brunei, Asia/Kuala_Lumpur, Atlantic/Reykjavik,
  Europe/Amsterdam, Europe/Copenhagen, Europe/Luxembourg, Europe/Monaco,
  Europe/Oslo, Europe/Stockholm, Indian/Christmas, Indian/Cocos,
  Indian/Kerguelen, Indian/Mahe, Indian/Reunion, Pacific/Chuuk,
  Pacific/Funafuti, Pacific/Majuro, Pacific/Pohnpei, Pacific/Wake and
  Pacific/Wallis, and the affected links are Arctic/Longyearbyen,
  Atlantic/Jan_Mayen, Iceland, Pacific/Ponape, Pacific/Truk, and
  Pacific/Yap."
  
  The Debian/Ubuntu package builds tzdata with the default settings
  (PACKRATDATA unset) which merges zones whose timestamps agree since
  1970. This leads to timestamps before 1970 being knowingly wrong.
  Example: Europe/Oslo is a link to Europe/Berlin since they are identical
  since 1970, but they differed before 1965. Berlin observed no summertime
  between 1950 and 1980, but Oslo did in 1959 to 1965. So summer 1960 in
  Oslo should be UTC+2 compared to UTC+1 in Berlin:
  
  ```
  $ TZ=Europe/Oslo date -d "1960-07-01 10:00 Z"
  Fri Jul  1 12:00:00 CEST 1960
  $ TZ=Europe/Berlin date -d "1960-07-01 10:00 Z"
  Fri Jul  1 11:00:00 CET 1960
  ```
  
  There was a big debate upstream (see https://lwn.net/Articles/870478/ or
  https://mm.icann.org/pipermail/tz/2021-May/030137.html). The
  Debian/Ubuntu package should ship timezones from backzone. Users that
  care about pre-1970 timestamps will be satisfied and users not caring
  will probably not care about the additional timezones.
  
  The install size will increase by around 20% and the amount of distinct
  (i.e. not symlinked) timezones will increase by 33%:
  
  ```
  $ grep ^Zone africa antarctica asia australasia etcetera europe factory 
northamerica southamerica | wc -l
  352
  $ grep ^Zone backzone | wc -l
  119
  ```
+ 
+ [ Test plan ]
+ 
+ The test case `test_pre_1970_timestamps` was added to the python
+ autopkgtest for testing this change. So the test plan is to check that
+ the autopkgtest succeeds.
+ 
+ [ Where problems could occur ]
+ 
+ Systems with incorrect timezone set may observe unexpected time shift.

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

Title:
  Pre-1970 timestamps are knowingly wrong

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Bionic:
  New
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Kinetic:
  Fix Committed

Bug description:
  [ Impact ]

  tzdata 2021b says in NEWS: "Merge more location-based Zones whose
  timestamps agree since 1970, as pre-1970 timestamps are out of scope.
  This is part of a process that has been ongoing since 2013.  This does
  not affect post-1970 timestamps, and timezone historians who build
  with 'make PACKRATDATA=backzone' should see no changes to pre-1970
  timestamps." tzdata 2022b finished that process: "Finish moving to
  'backzone' the location-based zones whose timestamps since 1970 are
  duplicates; adjust links accordingly. This change ordinarily affects
  only pre-1970 timestamps, and with the new PACKRATLIST option it does
  not affect any timestamps. In this round the affected zones are
  Antarctica/Vostok, Asia/Brunei, Asia/Kuala_Lumpur, Atlantic/Reykjavik,
  Europe/Amsterdam, Europe/Copenhagen, Europe/Luxembourg, Europe/Monaco,
  Europe/Oslo, Europe/Stockholm, Indian/Christmas, Indian/Cocos,
  Indian/Kerguelen, Indian/Mahe, Indian/Reunion, Pacific/Chuuk,
  Pacific/Funafuti, Pacific/Majuro, Pacific/Pohnpei, Pacific/Wake and
  Pacific/Wallis, and the affected links are Arctic/Longyearbyen,
  Atlantic/Jan_Mayen, Iceland, Pacific/Ponape, Pacific/Truk, and
  Pacific/Yap."

  The Debian/Ubuntu package builds tzdata with the default settings
  (PACKRATDATA unset) which merges zones whose timestamps agree since
  1970. This leads to timestamps before 1970 being knowingly wrong.
  Example: Europe/Oslo is a link to Europe/Berlin since they are
  identical since 1970, but they differed before 1965. Berlin observed
  no summertime between 1950 and 1980, but Oslo did in 1959 to 1965. So
  summer 1960 in 

[Touch-packages] [Bug 2012623] Re: 23.04 apparmor package crashed

[Bernard Stafford]

** Changed in: apparmor (Ubuntu)
   Status: New => Opinion

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

Title:
  23.04 apparmor package crashed

Status in apparmor package in Ubuntu:
  Opinion

Bug description:
  Edubuntu 23.04 apparmor package crashed during QA Testing Build 20230323.
  In addition to the crash the mouse pointer/spinner during the
  install did not spin it was stationary.
  Install completed as expected except for the package crash.
  apparmor:
    Installed: 3.0.8-1ubuntu2
    Candidate: 3.0.8-1ubuntu2
    Version table:
   *** 3.0.8-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  100 /var/lib/dpkg/status
  No LSB modules are available.
  Description:  Ubuntu Lunar Lobster (development branch)
  Release:  23.04

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: apparmor 3.0.8-1ubuntu2
  Uname: Linux 6.2.0-18-generic x86_64
  Architecture: amd64
  Date: Thu Mar 23 07:18:57 2023
  ExecutablePath: /usr/sbin/apparmor_parser
  ExecutableTimestamp: 1677622692
  ProcCmdline: apparmor_parser --replace --write-cache -O no-expr-simplify 
--cache-loc=/var/cache/apparmor -j2 --skip-read-cache --quiet 
/var/lib/snapd/apparmor/profiles/snap-update-ns.firefox 
/var/lib/snapd/apparmor/profiles/snap.firefox.firefox 
/var/lib/snapd/apparmor/profiles/snap.firefox.geckodriver 
/var/lib/snapd/apparmor/profiles/snap.firefox.hook.configure 
/var/lib/snapd/apparmor/profiles/snap.firefox.hook.connect-plug-host-hunspell 
/var/lib/snapd/apparmor/profiles/snap.firefox.hook.disconnect-plug-host-hunspell
 /var/lib/snapd/apparmor/profiles/snap.firefox.hook.post-refresh
  ProcCwd: /
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  Signal: 6
  SourcePackage: apparmor
  UserGroups: N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2012623/+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 2012599] Re: tzdata 2023a/2023b release - Egypt restoring DST

[Benjamin Drung]

Attached 2022b SRU for bionic and pushed the changes to
https://code.launchpad.net/~ubuntu-core-
dev/ubuntu/+source/tzdata/+git/tzdata/+ref/ubuntu/bionic

** Patch added: "tzdata_2023b-0ubuntu0.18.04.0.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+attachment/5657283/+files/tzdata_2023b-0ubuntu0.18.04.0.debdiff

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

Title:
  tzdata 2023a/2023b release - Egypt restoring DST

Status in tzdata package in Ubuntu:
  Fix Committed
Status in tzdata source package in Bionic:
  New
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Kinetic:
  Fix Committed
Status in tzdata source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  Recently the Egyptian authorities decided to restore DST. The first
  switch after the change is expected to take place on last Friday of
  April. The upstream tzdata 2023a release already reflects this change.

  The 2023a release contains the following changes:

  * Egypt now uses DST again, from April through October.
  * This year Morocco springs forward April 23, not April 30.
  * Palestine delays the start of DST this year.
  * Much of Greenland still uses DST from 2024 on.

  [ Test Plan ]

   * Set system timezone to Egypt (e.g. Africa/Cairo).
   * Set system time to 2023-04-27 23:59.
   * Wait and observe what happens at 2023-04-28 0:00

  [ Where problems could occur ]

   * Systems with incorrect timezone set (e.g. located outside of Egypt
  but still using Egyptian time) may observe unexpected time shift.

  [ Other Info ]

   * More information with sources:
  
https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023.

  The SRUs to the stable include the recent changes for generating the
  debconf template and the timezone mappings in convert_timezone().
  Previous SRUs did forget to update them for the changes from upstream.
  All added tests were also backported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+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 2012599] Re: tzdata 2023a/2023b release - Egypt restoring DST

[Benjamin Drung]

Attached 2023b SRU for focal and pushed the changes to
https://code.launchpad.net/~ubuntu-core-
dev/ubuntu/+source/tzdata/+git/tzdata/+ref/ubuntu/focal

** Patch added: "tzdata_2023b-0ubuntu0.20.04.0.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+attachment/5657281/+files/tzdata_2023b-0ubuntu0.20.04.0.debdiff

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

Title:
  tzdata 2023a/2023b release - Egypt restoring DST

Status in tzdata package in Ubuntu:
  Fix Committed
Status in tzdata source package in Bionic:
  New
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Kinetic:
  Fix Committed
Status in tzdata source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  Recently the Egyptian authorities decided to restore DST. The first
  switch after the change is expected to take place on last Friday of
  April. The upstream tzdata 2023a release already reflects this change.

  The 2023a release contains the following changes:

  * Egypt now uses DST again, from April through October.
  * This year Morocco springs forward April 23, not April 30.
  * Palestine delays the start of DST this year.
  * Much of Greenland still uses DST from 2024 on.

  [ Test Plan ]

   * Set system timezone to Egypt (e.g. Africa/Cairo).
   * Set system time to 2023-04-27 23:59.
   * Wait and observe what happens at 2023-04-28 0:00

  [ Where problems could occur ]

   * Systems with incorrect timezone set (e.g. located outside of Egypt
  but still using Egyptian time) may observe unexpected time shift.

  [ Other Info ]

   * More information with sources:
  
https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023.

  The SRUs to the stable include the recent changes for generating the
  debconf template and the timezone mappings in convert_timezone().
  Previous SRUs did forget to update them for the changes from upstream.
  All added tests were also backported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+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 2012599] Re: tzdata 2023a/2023b release - Egypt restoring DST

[Benjamin Drung]

Attached 2023b SRU for jammy and pushed the changes to
https://code.launchpad.net/~ubuntu-core-
dev/ubuntu/+source/tzdata/+git/tzdata/+ref/ubuntu/jammy

** Patch added: "tzdata_2023b-0ubuntu0.22.04.0.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+attachment/5657280/+files/tzdata_2023b-0ubuntu0.22.04.0.debdiff

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

Title:
  tzdata 2023a/2023b release - Egypt restoring DST

Status in tzdata package in Ubuntu:
  Fix Committed
Status in tzdata source package in Bionic:
  New
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Kinetic:
  Fix Committed
Status in tzdata source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  Recently the Egyptian authorities decided to restore DST. The first
  switch after the change is expected to take place on last Friday of
  April. The upstream tzdata 2023a release already reflects this change.

  The 2023a release contains the following changes:

  * Egypt now uses DST again, from April through October.
  * This year Morocco springs forward April 23, not April 30.
  * Palestine delays the start of DST this year.
  * Much of Greenland still uses DST from 2024 on.

  [ Test Plan ]

   * Set system timezone to Egypt (e.g. Africa/Cairo).
   * Set system time to 2023-04-27 23:59.
   * Wait and observe what happens at 2023-04-28 0:00

  [ Where problems could occur ]

   * Systems with incorrect timezone set (e.g. located outside of Egypt
  but still using Egyptian time) may observe unexpected time shift.

  [ Other Info ]

   * More information with sources:
  
https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023.

  The SRUs to the stable include the recent changes for generating the
  debconf template and the timezone mappings in convert_timezone().
  Previous SRUs did forget to update them for the changes from upstream.
  All added tests were also backported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+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 2012599] Re: tzdata 2023a/2023b release - Egypt restoring DST

[Benjamin Drung]

Attached 2022b SRU for kinetic and pushed the changes to
https://code.launchpad.net/~ubuntu-core-
dev/ubuntu/+source/tzdata/+git/tzdata/+ref/ubuntu/kinetic

** Patch added: "tzdata_2023b-0ubuntu0.22.10.0.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+attachment/5657279/+files/tzdata_2023b-0ubuntu0.22.10.0.debdiff

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

Title:
  tzdata 2023a/2023b release - Egypt restoring DST

Status in tzdata package in Ubuntu:
  Fix Committed
Status in tzdata source package in Bionic:
  New
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Kinetic:
  Fix Committed
Status in tzdata source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  Recently the Egyptian authorities decided to restore DST. The first
  switch after the change is expected to take place on last Friday of
  April. The upstream tzdata 2023a release already reflects this change.

  The 2023a release contains the following changes:

  * Egypt now uses DST again, from April through October.
  * This year Morocco springs forward April 23, not April 30.
  * Palestine delays the start of DST this year.
  * Much of Greenland still uses DST from 2024 on.

  [ Test Plan ]

   * Set system timezone to Egypt (e.g. Africa/Cairo).
   * Set system time to 2023-04-27 23:59.
   * Wait and observe what happens at 2023-04-28 0:00

  [ Where problems could occur ]

   * Systems with incorrect timezone set (e.g. located outside of Egypt
  but still using Egyptian time) may observe unexpected time shift.

  [ Other Info ]

   * More information with sources:
  
https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023.

  The SRUs to the stable include the recent changes for generating the
  debconf template and the timezone mappings in convert_timezone().
  Previous SRUs did forget to update them for the changes from upstream.
  All added tests were also backported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+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 2000880] Re: systemd-networkd: ActivationPolicy ignored in VLANs

[Timo Aaltonen]

Hello Craig, or anyone else affected,

Accepted systemd into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.9 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.

** Tags removed: verification-done-jammy
** Tags added: verification-needed verification-needed-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/2000880

Title:
  systemd-networkd: ActivationPolicy ignored in VLANs

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Fix Committed
Status in systemd source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  The ActivationPolicy property in .network files is ignored for VLANs.

  [Test Plan]

  * On a Jammy machine with an interface named ens3, create the
  following configs:

  $ cat > /etc/systemd/network/10-vlan18.netdev << EOF
  [NetDev]
  Name=vlan18
  Kind=vlan

  [VLAN]
  Id=18
  EOF

  $ cat > /etc/systemd/network/20-vlan18.network << EOF
  [Match]
  Name=vlan18

  [Network]
  Address=10.10.1.1/24

  [Link]
  ActivationPolicy=manual
  EOF

  $ cat > /etc/systemd/network/30-ens3.network << EOF
  [Match]
  Name=ens3

  [Network]
  DHCP=ipv4
  VLAN=vlan18
  EOF

  * Reboot the machine
  * On an affected machine, the vlan18@ens3 interface will have a configured IP 
at boot, despite the ActivationPolicy=manual setting in 
/etc/systemd/network/20-vlan18.network. On a patched machine, the interface 
should not have a configured IP.

  [Where problems could occur]

  The patch adds a condition where a netdev is not yet ready to be
  created. Specifically, it makes sure stacked netdevs are not created
  before their underlying link is activated. If we saw any problems, it
  would be related to netdev creation.

  [Original Description]

  This has been fixed upstream, see

  Upstream bug: https://github.com/systemd/systemd/issues/22593

  Any chance of a backport of the fix to 22.04?

  Fix: https://github.com/systemd/systemd-stable/pull/211

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

[Timo Aaltonen]

Hello Nick, or anyone else affected,

Accepted systemd into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.9 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.

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

Title:
  udev NIC renaming race with mlx5_core driver

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Jammy:
  Fix Committed
Status in systemd source package in Kinetic:
  Fix Committed
Status in systemd source package in Lunar:
  Fix Committed

Bug description:
  [Impact]
  On systems with mellanox NICs, udev's NIC renaming races with the mlx5_core 
driver's own configuration of subordinate interfaces. When the kernel wins this 
race, the device cannot be renamed as udev has attempted, and this causes 
systemd-network-online.target to timeout waiting for links to be configured. 
This ultimately results in boot being delayed by about 2 minutes.

  [Test Plan]
  Repeated launches of Standard_D8ds_v5 instance types will generally hit this 
race around 1 in 10 runs. Create a vm snapshot with updated systemd from 
ppa:enr0n/systemd-245. Launch 100 Standard_D8ds_v5 instances with updated 
systemd. Assert not failure in cloud-init status and no 2 minute delay in 
network-online.target.

  To check for failure symptom:
    - Assert that network-online.target isn't the longest pole from 
systemd-analyze blame.

  To assert success condition during net rename busy race:
    - assert when "eth1" is still the primary device name, that two altnames 
are listed (preserving the altname due to the primary NIC rename being hit.

  Sample script uses pycloudlib to create modified base image for test
  and launches 100 VMs of type Standard_D8ds_v5, counting both successes
  and any failures seen.

  #!/usr/bin/env python3
  # This file is part of pycloudlib. See LICENSE file for license information.
  """Basic examples of various lifecycle with an Azure instance."""

  import logging
  import json

  import pycloudlib
  LOG = logging.getLogger()

  base_cfg = """#cloud-config
  ssh-import-id: [chad.smith, enr0n]
  """

  apt_cfg = """
  # Add developer PPA
  apt:
   sources:
     systemd-testing:
   source: "deb [allow-insecure=yes] 
https://ppa.launchpadcontent.net/enr0n/systemd-245/ubuntu focal main"
  # upgrade systemd after cloud-init is nearly done
  runcmd:
   - apt install systemd udev -y --allow-unauthenticated
  """

  debug_systemd_cfg = """
  # Create systemd-udev debug override.conf in base image
  write_files:
  - path: /etc/systemd/system/systemd-networkd.service.d/override.conf
    owner: root:root
    defer: {defer}
    content: |
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug

  - path: /etc/systemd/system/systemd-udevd.service.d/override.conf
    owner: root:root
    defer: {defer}
    content: |
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug
  LogRateLimitIntervalSec=0
  """

  cloud_config = base_cfg + apt_cfg + debug_systemd_cfg
  cloud_config2 = base_cfg + debug_systemd_cfg

  def debug_systemd_image_launch_overlake_v5_with_snapshot():
  """Test overlake v5 timeouts

  test procedure:
  - Launch base focal image
  - enable ppa:enr0n/systemd-245 and systemd/udev debugging
  - cloud-init clean --logs && deconfigure waalinux agent before shutdown
  - snapshot a base image
  - launch v5 system from snapshot
  - check systemd-analyze for expected timeout
  """
  client = pycloudlib.Azure(tag="azure")

  image_id = client.daily_image(release="focal")
  pub_path = "/home/ubuntu/.ssh/id_rsa.pub"
  priv_path = "/home/ubuntu/.ssh/id_rsa"

  client.use_key(pub_path, priv_path)

  base_instance = client.launch(
  

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

[Timo Aaltonen]

Hello Tuetuopay, or anyone else affected,

Accepted systemd into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.9 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.

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

Title:
  systemd-networkd's dhcp4 client ignores local subnet routes

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Fix Committed
Status in systemd source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]

  If a DHCP server pushes down a local subnet route with a null gateway,
  the systemd-networkd DHCP client does not correctly install the route.
  Instead, the route is ignored.

  [Test Plan]

  Taken from
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2004478/comments/2.

  * Start a Jammy LXD container:

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

  * Create a veth pair:

  $ ip link add veth0 up type veth peer name veth1
  $ ip addr add 172.20.0.1/24 dev veth0
  $ cat > /etc/netplan/60-veth1.yaml 

[Touch-packages] [Bug 2002445] Re: udev NIC renaming race with mlx5_core driver

[Timo Aaltonen]

Hello Nick, or anyone else affected,

Accepted systemd into kinetic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/systemd/251.4-1ubuntu7.3 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: systemd (Ubuntu Kinetic)
   Status: In Progress => Fix Committed

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

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

** Tags removed: verification-failed-jammy
** Tags added: verification-needed-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/2002445

Title:
  udev NIC renaming race with mlx5_core driver

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Jammy:
  Fix Committed
Status in systemd source package in Kinetic:
  Fix Committed
Status in systemd source package in Lunar:
  Fix Committed

Bug description:
  [Impact]
  On systems with mellanox NICs, udev's NIC renaming races with the mlx5_core 
driver's own configuration of subordinate interfaces. When the kernel wins this 
race, the device cannot be renamed as udev has attempted, and this causes 
systemd-network-online.target to timeout waiting for links to be configured. 
This ultimately results in boot being delayed by about 2 minutes.

  [Test Plan]
  Repeated launches of Standard_D8ds_v5 instance types will generally hit this 
race around 1 in 10 runs. Create a vm snapshot with updated systemd from 
ppa:enr0n/systemd-245. Launch 100 Standard_D8ds_v5 instances with updated 
systemd. Assert not failure in cloud-init status and no 2 minute delay in 
network-online.target.

  To check for failure symptom:
    - Assert that network-online.target isn't the longest pole from 
systemd-analyze blame.

  To assert success condition during net rename busy race:
    - assert when "eth1" is still the primary device name, that two altnames 
are listed (preserving the altname due to the primary NIC rename being hit.

  Sample script uses pycloudlib to create modified base image for test
  and launches 100 VMs of type Standard_D8ds_v5, counting both successes
  and any failures seen.

  #!/usr/bin/env python3
  # This file is part of pycloudlib. See LICENSE file for license information.
  """Basic examples of various lifecycle with an Azure instance."""

  import logging
  import json

  import pycloudlib
  LOG = logging.getLogger()

  base_cfg = """#cloud-config
  ssh-import-id: [chad.smith, enr0n]
  """

  apt_cfg = """
  # Add developer PPA
  apt:
   sources:
     systemd-testing:
   source: "deb [allow-insecure=yes] 
https://ppa.launchpadcontent.net/enr0n/systemd-245/ubuntu focal main"
  # upgrade systemd after cloud-init is nearly done
  runcmd:
   - apt install systemd udev -y --allow-unauthenticated
  """

  debug_systemd_cfg = """
  # Create systemd-udev debug override.conf in base image
  write_files:
  - path: /etc/systemd/system/systemd-networkd.service.d/override.conf
    owner: root:root
    defer: {defer}
    content: |
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug

  - path: /etc/systemd/system/systemd-udevd.service.d/override.conf
    owner: root:root
    defer: {defer}
    content: |
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug
  LogRateLimitIntervalSec=0
  """

  cloud_config = base_cfg + apt_cfg + debug_systemd_cfg
  cloud_config2 = base_cfg + debug_systemd_cfg

  def debug_systemd_image_launch_overlake_v5_with_snapshot():
  """Test overlake v5 timeouts

  test procedure:
  - Launch base focal image
  - enable ppa:enr0n/systemd-245 and systemd/udev debugging
  - cloud-init clean --logs && deconfigure waalinux agent before shutdown
  - snapshot a base image
  - launch v5 system from 

[Touch-packages] [Bug 2004478] Re: systemd-networkd's dhcp4 client ignores local subnet routes

[Timo Aaltonen]

Hello Tuetuopay, or anyone else affected,

Accepted systemd into kinetic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/systemd/251.4-1ubuntu7.3 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.

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

** Tags removed: verification-done-jammy
** Tags added: verification-needed-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/2004478

Title:
  systemd-networkd's dhcp4 client ignores local subnet routes

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Fix Committed
Status in systemd source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]

  If a DHCP server pushes down a local subnet route with a null gateway,
  the systemd-networkd DHCP client does not correctly install the route.
  Instead, the route is ignored.

  [Test Plan]

  Taken from
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2004478/comments/2.

  * Start a Jammy LXD container:

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

  * Create a veth pair:

  $ ip link add veth0 up type veth peer name veth1
  $ ip addr add 172.20.0.1/24 dev veth0
  $ cat > /etc/netplan/60-veth1.yaml 

[Touch-packages] [Bug 2009502] Re: Enable /dev/sgx_vepc access for the group 'sgx'

[Timo Aaltonen]

Hello Pedro, or anyone else affected,

Accepted systemd into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.9 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.

** Tags removed: verification-done verification-done-jammy
** Tags added: verification-needed verification-needed-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/2009502

Title:
   Enable /dev/sgx_vepc access for the group 'sgx'

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

  On systems where Intel SGX is available, access to a specific device
  node (/dev/sgx_vepc) must be enforced, with a specific permission
  (0660) and group (sgx).

  This allows KVM-based virtual machines to use such feature (the SGX
  "enclaves") in a proper fashion.  Without this, a manual udev rule
  needs to be created.

  [ Test Plan ]

  As the patch itself only tailors the permissions/group to the device
  node, in a system with Intel-SGX enabled, merely `ls -la` against the
  device node should show if the permissions and group are seen as
  expected.

  [ Where problems could occur ]

  N/A.  This seems to be a very straightforward inclusion, very specific
  to access enablement to the SGX reserved memory used for hosting
  enclaves.

  [ Other Info ]

  N/A.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2009502/+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 2002445] Re: udev NIC renaming race with mlx5_core driver

[Mustafa Kemal Gilor]

** Changed in: systemd (Ubuntu Focal)
 Assignee: (unassigned) => Mustafa Kemal Gilor (mustafakemalgilor)

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

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

Title:
  udev NIC renaming race with mlx5_core driver

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Jammy:
  In Progress
Status in systemd source package in Kinetic:
  In Progress
Status in systemd source package in Lunar:
  Fix Committed

Bug description:
  [Impact]
  On systems with mellanox NICs, udev's NIC renaming races with the mlx5_core 
driver's own configuration of subordinate interfaces. When the kernel wins this 
race, the device cannot be renamed as udev has attempted, and this causes 
systemd-network-online.target to timeout waiting for links to be configured. 
This ultimately results in boot being delayed by about 2 minutes.

  [Test Plan]
  Repeated launches of Standard_D8ds_v5 instance types will generally hit this 
race around 1 in 10 runs. Create a vm snapshot with updated systemd from 
ppa:enr0n/systemd-245. Launch 100 Standard_D8ds_v5 instances with updated 
systemd. Assert not failure in cloud-init status and no 2 minute delay in 
network-online.target.

  To check for failure symptom:
    - Assert that network-online.target isn't the longest pole from 
systemd-analyze blame.

  To assert success condition during net rename busy race:
    - assert when "eth1" is still the primary device name, that two altnames 
are listed (preserving the altname due to the primary NIC rename being hit.

  Sample script uses pycloudlib to create modified base image for test
  and launches 100 VMs of type Standard_D8ds_v5, counting both successes
  and any failures seen.

  #!/usr/bin/env python3
  # This file is part of pycloudlib. See LICENSE file for license information.
  """Basic examples of various lifecycle with an Azure instance."""

  import logging
  import json

  import pycloudlib
  LOG = logging.getLogger()

  base_cfg = """#cloud-config
  ssh-import-id: [chad.smith, enr0n]
  """

  apt_cfg = """
  # Add developer PPA
  apt:
   sources:
     systemd-testing:
   source: "deb [allow-insecure=yes] 
https://ppa.launchpadcontent.net/enr0n/systemd-245/ubuntu focal main"
  # upgrade systemd after cloud-init is nearly done
  runcmd:
   - apt install systemd udev -y --allow-unauthenticated
  """

  debug_systemd_cfg = """
  # Create systemd-udev debug override.conf in base image
  write_files:
  - path: /etc/systemd/system/systemd-networkd.service.d/override.conf
    owner: root:root
    defer: {defer}
    content: |
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug

  - path: /etc/systemd/system/systemd-udevd.service.d/override.conf
    owner: root:root
    defer: {defer}
    content: |
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug
  LogRateLimitIntervalSec=0
  """

  cloud_config = base_cfg + apt_cfg + debug_systemd_cfg
  cloud_config2 = base_cfg + debug_systemd_cfg

  def debug_systemd_image_launch_overlake_v5_with_snapshot():
  """Test overlake v5 timeouts

  test procedure:
  - Launch base focal image
  - enable ppa:enr0n/systemd-245 and systemd/udev debugging
  - cloud-init clean --logs && deconfigure waalinux agent before shutdown
  - snapshot a base image
  - launch v5 system from snapshot
  - check systemd-analyze for expected timeout
  """
  client = pycloudlib.Azure(tag="azure")

  image_id = client.daily_image(release="focal")
  pub_path = "/home/ubuntu/.ssh/id_rsa.pub"
  priv_path = "/home/ubuntu/.ssh/id_rsa"

  client.use_key(pub_path, priv_path)

  base_instance = client.launch(
  image_id=image_id,
  instance_type="Standard_DS1_v2",
  user_data=cloud_config.format(defer="true"),
  )

  LOG.info(f"base instance: ssh ubuntu@{base_instance.ip}")
  base_instance.wait()
  LOG.info(base_instance.execute("apt cache policy systemd"))
  snapshotted_image_id = client.snapshot(base_instance)

  reproducer = False
  tries = 0
  success_count_with_race = 0
  success_count_no_race = 0
  failure_count_network_delay = 0
  failure_count_no_altnames = 0
  TEST_SUMMARY_TMPL = """
  - Test run complete: {tries} attempted -
  Successes without rename race: {success_count_no_race}
  Successes with rename race and preserved altname: 
{success_count_with_race}
  Failures due to network delay: {failure_count_network_delay}
  Failures due to no altnames persisted: {failure_count_no_altnames}
  ===
  """
  while tries < 100 and not reproducer:
  tries += 1
  new_instance = client.launch(
  

[Touch-packages] [Bug 2011628] Re: Apparmor Disallows Disabling Dhclient Scripts

[Robie Basak]

I wondered if this needed an FFe, but then I considered that we're
fixing an Apparmor profile to do what the command would allow anyway,
and I think that fixing Apparmor profiles is not something that
generally would violate feature freeze. So I'm not bothering the release
team with this one and am instead documenting why :-)

** Merge proposal linked:
   
https://code.launchpad.net/~holmanb/ubuntu/+source/isc-dhcp/+git/isc-dhcp/+merge/439186

** Changed in: isc-dhcp (Ubuntu)
   Status: New => Triaged

** Changed in: isc-dhcp (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Apparmor Disallows Disabling Dhclient Scripts

Status in isc-dhcp package in Ubuntu:
  Triaged

Bug description:
  In some cases, it may be desirable to disable dhclient scripts. By
  default /sbin/dhclient-script is used, and some others are allowed by
  the apparmor profile.

  Without Apparmor, disabling hook scripts can be accomplished with
  flags -sf /bin/true, but with apparmor enabled this gets blocked:

  execve (/bin/true, ...): Permission denied

  Unfortunately dhclient doesn't appear to provide any other mechanism
  for disabling hook scripts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/2011628/+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 2012540] Re: Please merge tiff 4.5.0-5 from Debian unstable

[Sebastien Bacher]

Thanks Nathan!

** Changed in: tiff (Ubuntu)
   Importance: Undecided => High

** Changed in: tiff (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  Please merge tiff 4.5.0-5 from Debian unstable

Status in tiff package in Ubuntu:
  Fix Committed

Bug description:
  Please merge tiff 4.5.0-5 from Debian unstable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/2012540/+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 2006633] Re: Merge librsvg 2.54.5+dfsg-1 (main) from Debian unstable (main)

[Launchpad Bug Tracker]

This bug was fixed in the package librsvg - 2.54.5+dfsg-1ubuntu2

---
librsvg (2.54.5+dfsg-1ubuntu2) lunar; urgency=medium

  * Don't fail the build on tests issues on s390x

 -- Sebastien Bacher   Tue, 21 Mar 2023 15:45:43
+0100

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

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

Title:
  Merge librsvg 2.54.5+dfsg-1 (main) from Debian unstable (main)

Status in librsvg package in Ubuntu:
  Fix Released

Bug description:
  Please merge librsvg 2.54.5+dfsg-1 (main) from Debian unstable (main)

  Changelog entries since current lunar version 2.54.4+dfsg-1ubuntu1:

  librsvg (2.54.5+dfsg-1) unstable; urgency=medium

* New upstream release
* debian/librsvg2-2.docs: NEWS.md -> NEWS

   -- Jeremy Bicha   Thu, 22 Sep 2022 17:00:54 -0400

  Remaining differences with librsvg from Debian unstable:

* Don't fail the build on tests error for i386

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/2006633/+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 2012599] Re: tzdata 2023a/2023b release - Egypt restoring DST

[Benjamin Drung]

** Summary changed:

- tzdata 2023a release - Egypt restoring DST
+ tzdata 2023a/2023b release - Egypt restoring DST

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

Title:
  tzdata 2023a/2023b release - Egypt restoring DST

Status in tzdata package in Ubuntu:
  Fix Committed
Status in tzdata source package in Bionic:
  New
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Kinetic:
  Fix Committed
Status in tzdata source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  Recently the Egyptian authorities decided to restore DST. The first
  switch after the change is expected to take place on last Friday of
  April. The upstream tzdata 2023a release already reflects this change.

  The 2023a release contains the following changes:

  * Egypt now uses DST again, from April through October.
  * This year Morocco springs forward April 23, not April 30.
  * Palestine delays the start of DST this year.
  * Much of Greenland still uses DST from 2024 on.

  [ Test Plan ]

   * Set system timezone to Egypt (e.g. Africa/Cairo).
   * Set system time to 2023-04-27 23:59.
   * Wait and observe what happens at 2023-04-28 0:00

  [ Where problems could occur ]

   * Systems with incorrect timezone set (e.g. located outside of Egypt
  but still using Egyptian time) may observe unexpected time shift.

  [ Other Info ]

   * More information with sources:
  
https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023.

  The SRUs to the stable include the recent changes for generating the
  debconf template and the timezone mappings in convert_timezone().
  Previous SRUs did forget to update them for the changes from upstream.
  All added tests were also backported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+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 2003797] Autopkgtest regression report (tzdata/2023a-0ubuntu0.22.04.0)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted tzdata (2023a-0ubuntu0.22.04.0) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

chrony/4.2-2ubuntu2 (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#tzdata

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Pre-1970 timestamps are knowingly wrong

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Bionic:
  New
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Kinetic:
  Fix Committed

Bug description:
  tzdata 2021b says in NEWS: "Merge more location-based Zones whose
  timestamps agree since 1970, as pre-1970 timestamps are out of scope.
  This is part of a process that has been ongoing since 2013.  This does
  not affect post-1970 timestamps, and timezone historians who build
  with 'make PACKRATDATA=backzone' should see no changes to pre-1970
  timestamps." tzdata 2022b finished that process: "Finish moving to
  'backzone' the location-based zones whose timestamps since 1970 are
  duplicates; adjust links accordingly. This change ordinarily affects
  only pre-1970 timestamps, and with the new PACKRATLIST option it does
  not affect any timestamps. In this round the affected zones are
  Antarctica/Vostok, Asia/Brunei, Asia/Kuala_Lumpur, Atlantic/Reykjavik,
  Europe/Amsterdam, Europe/Copenhagen, Europe/Luxembourg, Europe/Monaco,
  Europe/Oslo, Europe/Stockholm, Indian/Christmas, Indian/Cocos,
  Indian/Kerguelen, Indian/Mahe, Indian/Reunion, Pacific/Chuuk,
  Pacific/Funafuti, Pacific/Majuro, Pacific/Pohnpei, Pacific/Wake and
  Pacific/Wallis, and the affected links are Arctic/Longyearbyen,
  Atlantic/Jan_Mayen, Iceland, Pacific/Ponape, Pacific/Truk, and
  Pacific/Yap."

  The Debian/Ubuntu package builds tzdata with the default settings
  (PACKRATDATA unset) which merges zones whose timestamps agree since
  1970. This leads to timestamps before 1970 being knowingly wrong.
  Example: Europe/Oslo is a link to Europe/Berlin since they are
  identical since 1970, but they differed before 1965. Berlin observed
  no summertime between 1950 and 1980, but Oslo did in 1959 to 1965. So
  summer 1960 in Oslo should be UTC+2 compared to UTC+1 in Berlin:

  ```
  $ TZ=Europe/Oslo date -d "1960-07-01 10:00 Z"
  Fri Jul  1 12:00:00 CEST 1960
  $ TZ=Europe/Berlin date -d "1960-07-01 10:00 Z"
  Fri Jul  1 11:00:00 CET 1960
  ```

  There was a big debate upstream (see https://lwn.net/Articles/870478/
  or https://mm.icann.org/pipermail/tz/2021-May/030137.html). The
  Debian/Ubuntu package should ship timezones from backzone. Users that
  care about pre-1970 timestamps will be satisfied and users not caring
  will probably not care about the additional timezones.

  The install size will increase by around 20% and the amount of
  distinct (i.e. not symlinked) timezones will increase by 33%:

  ```
  $ grep ^Zone africa antarctica asia australasia etcetera europe factory 
northamerica southamerica | wc -l
  352
  $ grep ^Zone backzone | wc -l
  119
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2003797/+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 2012599] Autopkgtest regression report (tzdata/2023a-0ubuntu0.22.04.0)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted tzdata (2023a-0ubuntu0.22.04.0) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

chrony/4.2-2ubuntu2 (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#tzdata

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  tzdata 2023a release - Egypt restoring DST

Status in tzdata package in Ubuntu:
  Fix Committed
Status in tzdata source package in Bionic:
  New
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Kinetic:
  Fix Committed
Status in tzdata source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  Recently the Egyptian authorities decided to restore DST. The first
  switch after the change is expected to take place on last Friday of
  April. The upstream tzdata 2023a release already reflects this change.

  The 2023a release contains the following changes:

  * Egypt now uses DST again, from April through October.
  * This year Morocco springs forward April 23, not April 30.
  * Palestine delays the start of DST this year.
  * Much of Greenland still uses DST from 2024 on.

  [ Test Plan ]

   * Set system timezone to Egypt (e.g. Africa/Cairo).
   * Set system time to 2023-04-27 23:59.
   * Wait and observe what happens at 2023-04-28 0:00

  [ Where problems could occur ]

   * Systems with incorrect timezone set (e.g. located outside of Egypt
  but still using Egyptian time) may observe unexpected time shift.

  [ Other Info ]

   * More information with sources:
  
https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023.

  The SRUs to the stable include the recent changes for generating the
  debconf template and the timezone mappings in convert_timezone().
  Previous SRUs did forget to update them for the changes from upstream.
  All added tests were also backported.

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