[Touch-packages] [Bug 2063094] Re: unattended-upgrades is running forever

[Brian Murray]

It also seemed rather unkillable.

** Tags added: rls-nn-incoming

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

Title:
  unattended-upgrades is running forever

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
28433 root  39  19  354904 111480  71296 R  99.7   0.7 107:29.26
  unattended-upgr

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: unattended-upgrades 2.9.1+nmu4ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1
  Uname: Linux 6.8.0-28-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 22 10:27:34 2024
  InstallationDate: Installed on 2022-01-07 (836 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: Upgraded to noble on 2024-04-10 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2063094/+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 2063094] [NEW] unattended-upgrades is running forever

[Brian Murray]

Public bug reported:

  28433 root  39  19  354904 111480  71296 R  99.7   0.7 107:29.26
unattended-upgr

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: unattended-upgrades 2.9.1+nmu4ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1
Uname: Linux 6.8.0-28-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 22 10:27:34 2024
InstallationDate: Installed on 2022-01-07 (836 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
PackageArchitecture: all
SourcePackage: unattended-upgrades
UpgradeStatus: Upgraded to noble on 2024-04-10 (12 days ago)

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  unattended-upgrades is running forever

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
28433 root  39  19  354904 111480  71296 R  99.7   0.7 107:29.26
  unattended-upgr

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: unattended-upgrades 2.9.1+nmu4ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1
  Uname: Linux 6.8.0-28-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 22 10:27:34 2024
  InstallationDate: Installed on 2022-01-07 (836 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: Upgraded to noble on 2024-04-10 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2063094/+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 2063003] Re: package manager could not make changes to the installed system

[Brian Murray]

** Also affects: calamares (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  package manager could not make changes to the installed system

Status in apt package in Ubuntu:
  New
Status in calamares package in Ubuntu:
  New

Bug description:
  This is the cause of Ubuntu Unity failing to install. Test case
  requires system to be offline.

  The full error message is:
  The package manager could not make changes to the installed system. The 
command apt-get --purge -q -y remove ^live-* 
calamares-settings-ubuntu-unity calamares zram-config cifs-utils returned 
error code 100.

  There are no logs in /var/log/installer or /var/crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2063003/+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 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

[Brian Murray]

** Changed in: systemd (Ubuntu Noble)
Milestone: None => ubuntu-24.04

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

Title:
  Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

Status in Native ZFS for Linux:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress
Status in zfs-linux package in Ubuntu:
  In Progress
Status in systemd source package in Noble:
  In Progress
Status in zfs-linux source package in Noble:
  In Progress

Bug description:
  As per https://github.com/openzfs/zfs/issues/15930

  ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
  copy_file_range, breaking a multitude of applications.

  Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
  2.2.2.

  One notable issue is when running Root on ZFS: systemd-sysusers will
  always fail to create users/groups with the error "Failed to backup
  /etc/{group,passwd}: Operation not supported" due to the call to
  copy_file_range.

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+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 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

[Brian Murray]

** Also affects: systemd (Ubuntu Noble)
   Importance: Medium
   Status: Triaged

** Also affects: zfs-linux (Ubuntu Noble)
   Importance: Undecided
   Status: Confirmed

** Changed in: zfs-linux (Ubuntu Noble)
Milestone: None => ubuntu-24.04

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

Title:
  Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

Status in Native ZFS for Linux:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged
Status in zfs-linux package in Ubuntu:
  Confirmed
Status in systemd source package in Noble:
  Triaged
Status in zfs-linux source package in Noble:
  Confirmed

Bug description:
  As per https://github.com/openzfs/zfs/issues/15930

  ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
  copy_file_range, breaking a multitude of applications.

  Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
  2.2.2.

  One notable issue is when running Root on ZFS: systemd-sysusers will
  always fail to create users/groups with the error "Failed to backup
  /etc/{group,passwd}: Operation not supported" due to the call to
  copy_file_range.

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+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 2061214] Re: Software sources not correctly updated after upgrade

[Brian Murray]

** Tags added: dist-upgrade jammy-to-noble

** Tags added: rls-nn-incmong

** Tags removed: rls-nn-incmong
** Tags added: rls-nn-incoming

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

Title:
  Software sources not correctly updated after upgrade

Status in software-properties package in Ubuntu:
  New

Bug description:
  Upgrading Lubuntu Jammy to Lubuntu Noble using TUI results in
  "Software sources" not correctly updated after upgrade. Prompt= shows
  normal and not LTS

  Used command sudo do-release-upgrade -d

  Otherwise the upgrade is good

  see attached screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: software-properties-common 0.99.46
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Sat Apr 13 11:44:28 2024
  InstallationDate: Installed on 2024-04-13 (0 days ago)
  InstallationMedia: Lubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240331)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago)
  mtime.conffile..etc.init.d.apport: 2024-02-22T14:20:00

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2061214/+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 2061316] Re: first screen refers to Noble Numbat (development branch)

[Brian Murray]

This'll be addressed next week as a part of the 24.04 Final Release
checklist.

https://warthogs.atlassian.net/browse/RTMP-1560

** Changed in: base-files (Ubuntu Noble)
   Status: New => Triaged

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

Title:
  first screen refers to Noble Numbat (development branch)

Status in base-files package in Ubuntu:
  Triaged
Status in base-files source package in Noble:
  Triaged

Bug description:
  While Noble is still in development and this screen is currently
  accurate, what will make it change to say Ubuntu 24.04? This should be
  done by the end of the week / early next week as we will be building
  candidate images for the final release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2061316/+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 2060311] Re: Setting "optional: true" to overcome he timeout "Job systemd-networkd-wait-online" does no longer work with latest noble image

[Brian Murray]

** Also affects: systemd (Ubuntu Noble)
   Importance: High
   Status: Confirmed

** Also affects: netplan.io (Ubuntu Noble)
   Importance: Undecided
   Status: New

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

Title:
  Setting "optional: true" to overcome he timeout "Job systemd-networkd-
  wait-online" does no longer work with latest noble image

Status in Netplan:
  In Progress
Status in Ubuntu on IBM z Systems:
  New
Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Confirmed
Status in netplan.io source package in Noble:
  New
Status in systemd source package in Noble:
  Confirmed

Bug description:
  Especially on s390x (but not limited to s390x) it's often the case that a 
system has network devices that are not necessarily connected during boot-up 
and one gets such a 2 min timeout:
  "Job systemd-networkd-wait-online. Start running (1min 59s / no limit)"

  In the past I could avoid that by setting "optional: true" post-install (no 
perfect, but worked),
  but this does no longer seem to work using the latest noble ISO image (Apr 
5th).

  Setting 'optional: true' in /etc/netplan/50-cloud-init.yaml looks like
  this for me:

  # 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:
  ethernets:
  enP1p0s0:
  optional: true
  dhcp4: true
  enP1p0s0d1:
  optional: true
  dhcp4: true
  enP2p0s0:
  optional: true
  dhcp4: true
  enP2p0s0d1:
  optional: true
  dhcp4: true
  encc000: {}
  version: 2
  vlans:
  encc000.2653:
  addresses:
  - 10.11.12.15/24
  gateway4: 10.11.12.1
  id: 2653
  link: encc000
  nameservers:
  addresses:
  - 10.11.12.1

  ... can be set fine (also --dry-run does not moan, except about
  dhcp4).

  This worked in the past on noble, but also on older Ubuntu releases
  like jammy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2060311/+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 2060898] Re: Trying to install gimp-help-en threatens to install wslu

[Brian Murray]

I see chromium-browser in the manifest for Ubuntu Studio so that's why
seeded-in-ubuntu thinks it is seeded.

https://cdimage.ubuntu.com/ubuntustudio/dvd/current/noble-dvd-
amd64.manifest

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

Title:
  Trying to install gimp-help-en threatens to install wslu

Status in edubuntu-meta package in Ubuntu:
  Triaged
Status in kubuntu-meta package in Ubuntu:
  Triaged
Status in lubuntu-meta package in Ubuntu:
  In Progress
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-mate-meta package in Ubuntu:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  Invalid
Status in ubuntustudio-meta package in Ubuntu:
  Triaged
Status in wslu package in Ubuntu:
  Invalid
Status in edubuntu-meta source package in Noble:
  Triaged
Status in kubuntu-meta source package in Noble:
  Triaged
Status in lubuntu-meta source package in Noble:
  In Progress
Status in ubuntu-budgie-meta source package in Noble:
  Fix Committed
Status in ubuntu-mate-meta source package in Noble:
  Triaged
Status in ubuntu-meta source package in Noble:
  Invalid
Status in ubuntustudio-meta source package in Noble:
  Triaged
Status in wslu source package in Noble:
  Invalid

Bug description:
  Filing this against ubuntu-meta since I believe this is a seed problem
  that potentially affects all variants of Ubuntu (flavors or
  otherwise).

  wslu is "a collection of utilities for the Windows 10 Linux Subsystem,
  such as for converting Linux paths to a Windows paths or creating
  Linux application shortcuts on the Windows 10 Desktop." Obviously this
  package should *never* be installed on a desktop or even on most VMs,
  but only within WSL instances. However...

  wslu provides the virtual package www-browser, as one of its features
  is to open links in Windows 10 using the default browser set there.
  This means that if a package depends or recommends www-browser, it may
  attempt to pull in one of several packages, wslu included. In the
  past, this hasn't been a problem because Firefox was present on all
  flavor images, and Firefox provides www-browser as well. However, now
  that Firefox is a Snap, it is possible for Firefox to be installed
  without the firefox transitional apt package being installed. (This is
  the case in a default installation of Kubuntu Noble Beta.) As it turns
  out, Kubuntu Noble Beta ships with *no* packages that provide www-
  browser, meaning that any package that depends on it will have to
  install a new browser.

  Due to some stroke of misfortune, apt is picking wslu out of all
  packages as the package for this use case. Installing gimp-help-en
  will also install www-browser, which results in wslu becoming
  installed.

  wslu causes quite a few problems when installed on a desktop system -
  among them, the syslog is spammed with errors due to the system not in
  fact being a WSL VM, audio breaks in weird ways, and application
  launchers sometimes fail. Why this happens is unclear, but the issues
  appear to resolve once wslu is removed from the system. It is
  therefore probably a good idea to avoid wslu becoming installed on
  accident in this way.

  Probably the best way to resolve this is to ensure that some package
  that provides www-browser is available on every Ubuntu image. This
  could be done via seeding or by adding a package to ubuntu-minimal.
  Alternatively, wslu could be set to no longer provide www-browser,
  though it's unclear if that would break its functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/edubuntu-meta/+bug/2060898/+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 2060679] Re: No icons for gtk4 applications under noble

[Brian Murray]

** Changed in: mesa (Ubuntu Noble)
Milestone: None => ubuntu-24.04

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

Title:
  No icons for gtk4 applications under noble

Status in mesa package in Ubuntu:
  In Progress
Status in mesa source package in Noble:
  In Progress

Bug description:
  While testing the Ubuntu noble (24.04) desktop for Raspberry Pi beta,
  I noticed that all GTK4 applications appear to be missing various
  icons. All lack the minimize / maximize / close icons (which are left
  as three empty circles on the window), and others lack icons within
  the windows, e.g. on various controls like radio buttons, or folder
  icons in nautilus. GTK3 applications appear unaffected. I'll attach
  some screenshots demonstrating the issue.

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

[Brian Murray]

Hello John, or anyone else affected,

Accepted apparmor into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apparmor/2.13.3-7ubuntu5.4 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 apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1597017

Title:
  mount rules grant excessive permissions

Status in AppArmor:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Focal:
  Fix Committed
Status in apparmor source package in Jammy:
  Fix Committed

Bug description:
  SRU Team; the packages for focal-proposed and jammy-proposed are
  intended as security updates prepared by the Ubuntu Security team (and
  have built in a ppa with only the security pockets enabled). However,
  because the fix makes mount rules in apparmor policy be treated more
  restrictively than they were prior to this update, we would like these
  packages to gain more widespread testing.

  Risk of Regression:

  The update for this issue causes the apparmor parser, the tool that
  translates written policy into the enforcement data structures used by
  the kernel, to generate more strict policy for mount rules, like the
  example below. They are not common in apparmor policy generally, but
  can appear in policies written for container managers to restrict
  containers, and thus can potentially break container startup.

  The packages prepared for focal-proposed and jammy-proposed have
  tested with the versions of snapd, lxc, libvirt, and docker in the
  ubuntu archive, but container managers outside of the ubuntu archive
  may run into issues, hence the need for testing and policy
  adjustments.

  Original Report:

  The rule
    mount options=(rw,make-slave) -> **,

  ends up allowing
    mount -t proc proc /mnt

  which it shouldn't as it should be restricted to commands with a make-
  slave flag

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1597017/+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 1597017] Re: mount rules grant excessive permissions

[Brian Murray]

Hello John, or anyone else affected,

Accepted apparmor into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apparmor/3.0.4-2ubuntu2.4 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.

** Description changed:

  SRU Team; the packages for focal-proposed and jammy-proposed are
  intended as security updates prepared by the Ubuntu Security team (and
  have built in a ppa with only the security pockets enabled). However,
  because the fix makes mount rules in apparmor policy be treated more
  restrictively than they were prior to this update, we would like these
  packages to gain more widespread testing.
  
  Risk of Regression:
  
  The update for this issue causes the apparmor parser, the tool that
  translates written policy into the enforcement data structures used by
  the kernel, to generate more strict policy for mount rules, like the
  example below. They are not common in apparmor policy generally, but can
  appear in policies written for container managers to restrict
  containers, and thus can potentially break container startup.
  
  The packages prepared for focal-proposed and jammy-proposed have tested
  with the versions of snapd, lxc, libvirt, and docker in the ubuntu
- archive, but conainter managers outside of the ubunty archive may run
+ archive, but container managers outside of the ubuntu archive may run
  into issues, hence the need for testing and policy adjustments.
  
  Original Report:
  
  The rule
    mount options=(rw,make-slave) -> **,
  
  ends up allowing
    mount -t proc proc /mnt
  
  which it shouldn't as it should be restricted to commands with a make-
  slave flag

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

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

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

** Tags added: verification-needed-focal

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

Title:
  mount rules grant excessive permissions

Status in AppArmor:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Focal:
  Fix Committed
Status in apparmor source package in Jammy:
  Fix Committed

Bug description:
  SRU Team; the packages for focal-proposed and jammy-proposed are
  intended as security updates prepared by the Ubuntu Security team (and
  have built in a ppa with only the security pockets enabled). However,
  because the fix makes mount rules in apparmor policy be treated more
  restrictively than they were prior to this update, we would like these
  packages to gain more widespread testing.

  Risk of Regression:

  The update for this issue causes the apparmor parser, the tool that
  translates written policy into the enforcement data structures used by
  the kernel, to generate more strict policy for mount rules, like the
  example below. They are not common in apparmor policy generally, but
  can appear in policies written for container managers to restrict
  containers, and thus can potentially break container startup.

  The packages prepared for focal-proposed and jammy-proposed have
  tested with the versions of snapd, lxc, libvirt, and docker in the
  ubuntu archive, but container managers outside of the ubuntu archive
  may run into issues, hence the need for testing and policy
  adjustments.

  Original Report:

  The rule
    mount options=(rw,make-slave) -> **,

  ends up allowing
    mount -t proc proc /mnt

  which it shouldn't as it should be restricted to commands with a make-
  slave flag

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


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

[Touch-packages] [Bug 2060581] [NEW] stop shipping debian-installer package hook

[Brian Murray]

Public bug reported:

I don't remember when we stopped producing installer images with debian-
installer but it should be long enough ago that people won't be
reporting bugs about it on Noble. So let's drop that from the apport
package.

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


** Tags: rls-nn-incoming

** Changed in: apport (Ubuntu)
Milestone: None => ubuntu-24.04

** Tags added: rls-nn-incoming

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

Title:
  stop shipping debian-installer package hook

Status in apport package in Ubuntu:
  New

Bug description:
  I don't remember when we stopped producing installer images with
  debian-installer but it should be long enough ago that people won't be
  reporting bugs about it on Noble. So let's drop that from the apport
  package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2060581/+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 2051672] Re: Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)

[Brian Murray]

** Changed in: iproute2 (Ubuntu)
Milestone: ubuntu-24.04-feature-freeze => ubuntu-24.04-beta

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

Title:
  Merge iproute2 with the latest Debian version: 6.8.0-1 from
  testing/unstable (main)

Status in iproute2 package in Ubuntu:
  Confirmed

Bug description:
  A few versions have been released and Ubuntu Noble still has the 6.1
  version (6.1.0-1ubuntu2) from one year ago. Could it be possible to
  import the latest version from Debian unstable fixing a bunch of
  issues and supporting features from more recent kernels?

  Please note that Ubuntu Noble 24.04 will probably be shipped with the
  v6.8 kernel [1]. IPRoute v6.1 supports features added up to the v6.1
  kernel, so missing the ones added to earlier versions. Switching to
  the v6.7 now should ease the upgrade to the v6.8 later.

  [1] https://discourse.ubuntu.com/t/introducing-kernel-6-8-for-
  the-24-04-noble-numbat-release/41958

  Upstream ChangeLog:

  - 6.2: https://lore.kernel.org/netdev/20230220105811.674bd304@hermes.local/
  - 6.3: https://lore.kernel.org/netdev/20230427090253.7a92616b@hermes.local/
  - 6.4: https://lore.kernel.org/netdev/20230626093137.2f302acc@hermes.local/
  - 6.5: https://lore.kernel.org/netdev/20230906093918.394a1b1d@hermes.local/
  - 6.6: https://lore.kernel.org/netdev/20231106090325.07092c87@hermes.local/
  - 6.7: https://lore.kernel.org/netdev/20240108094709.050e22bc@hermes.local/
  - 6.8: https://lore.kernel.org/netdev/20240311094432.16bf9516@hermes.local/

  (Previous changelog:
  
https://lore.kernel.org/netdev/?q=s%3A%22%5BANNOUNCE%5D+iproute2%22+AND+NOT+s%3A%22Re%3A%22
  )

  ChangeLog from Debian:

  iproute2 (6.8.0-1) unstable; urgency=medium

[ Ceppo ]
* Update Italian po-debconf translation (Closes: #1063002)

[ Luca Boccassi ]
* Add build dependency on libnsl-dev (Closes: #1065214)
* Switch to pkgconf
* Update upstream source from tag 'upstream/6.8.0'
* Drop 0002-ss-show-extra-info-when-processes-is-not-used.patch, merged
  upstream
* Drop iproute2-doc package
* Drop tc/m_xt.so and tc/m_ipt.so, removed upstream

   -- Luca Boccassi <>  Tue, 12 Mar 2024 14:02:38 +

  iproute2 (6.7.0-2) unstable; urgency=medium

    * Backport fix for 'ss' output

   -- Luca Boccassi <>  Mon, 22 Jan 2024 12:24:29 +

  iproute2 (6.7.0-1) unstable; urgency=medium

    * Add Italian debconf translation (Closes: #1056582)
    * Update upstream source from tag 'upstream/6.7.0'
    * Bump copyright year ranges in d/copyright
    * Drop 0002-Revert-Makefile-ensure-CONF_USR_DIR-honours-the-libd.patch,
  merged upstream
    * Default config files moved from /usr/lib to /usr/share

   -- Luca Boccassi <>  Fri, 12 Jan 2024 21:47:59 +

  iproute2 (6.6.0-1) unstable; urgency=medium

    * Update upstream source from tag 'upstream/6.6.0'
    * Backport patch to fix configuration installation
    * Remove handling of qt_atm.so, dropped upstream

   -- Luca Boccassi <>  Sun, 05 Nov 2023 22:46:20 +

  iproute2 (6.5.0-5) unstable; urgency=medium

    * Use dh-sequence-movetousr

   -- Luca Boccassi <>  Tue, 24 Oct 2023 15:24:01 +0100

  iproute2 (6.5.0-4) unstable; urgency=medium

    * postinst: handle legacy config files only when upgrading from previous
  versions that shipped them
    * postinst: ensure that locally modified legacy config files are
  preserved as overrides on upgrade (Closes: #1051577)
    * Note configuration files location changes in NEWS

   -- Luca Boccassi <>  Sat, 16 Sep 2023 18:58:51 +0100

  iproute2 (6.5.0-3) unstable; urgency=medium

    * Remove further leftovers as part of upstream's move of config to /usr
  (Closes: #1051577)

   -- Luca Boccassi <>  Mon, 11 Sep 2023 09:42:12 +0100

  iproute2 (6.5.0-2) unstable; urgency=medium

    * Add maintscript to remove conffiles that upstream has moved to /usr
  (Closes: #1051577)

   -- Luca Boccassi <>  Sun, 10 Sep 2023 21:28:28 +0100

  iproute2 (6.5.0-1) unstable; urgency=medium

    [ Luca Boccassi ]
    * Use wildcard for Lintian overrides

    [ Peter Kvillegård ]
    * Add Swedish translation of debconf messages (Closes: #1050442)

    [ Luca Boccassi ]
    * Update upstream source from tag 'upstream/6.5.0'
    * Use cap_bpf instead of cap_sys_admin for ip vrf-exec
    * Package-provided config files are now shipped in /usr/iproute2 instead
  of /etc/iproute2

   -- Luca Boccassi <>  Sat, 09 Sep 2023 16:32:54 +0100

  iproute2 (6.4.0-1) unstable; urgency=medium

    * Fix patch header Forwarded field
    * Enable ELF metadata stamping
    * Update upstream source from tag 'upstream/6.4.0'
    * Update Lintian overrides

   -- Luca Boccassi <>  Fri, 30 Jun 2023 12:16:40 +0100

  iproute2 (6.3.0-1) unstable; urgency=medium

    * Drop obsolete conflicts/replaces
    * Update upstream source from tag 

[Touch-packages] [Bug 2059078] Re: proposed-migration for faketime 0.9.10-2.1ubuntu1

[Brian Murray]

** Changed in: faketime (Ubuntu)
Milestone: None => ubuntu-24.04-beta

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

Title:
  proposed-migration for faketime 0.9.10-2.1ubuntu1

Status in bash package in Ubuntu:
  New
Status in faketime package in Ubuntu:
  New

Bug description:
  faketime 0.9.10-2.1ubuntu1 is stuck in -proposed with build failures
  on armhf.

  On armhf, the testsuite confusingly fails with a stack smash error.
  But this error happens in bash, which isn't even meant to be the
  process under test.

  Minimal reproducer:
  # LD_PRELOAD=./src/libfaketime.so.1 bash -c 'exit 0'
  *** stack smashing detected ***: terminated
  Aborted (core dumped)
  #

  Confusingly, ltrace shows different results for the newly-built binary
  than from one built without 64-bit time_t.

  # LD_PRELOAD=./src/libfaketime.so.1 ltrace --library '*faketime*' bash -c 
'exit 0'
  bash->getrandom(0x1f3bf08, 1, 0x9683b0, 0)   = 0xc8202
  bash->getrandom(0xc8203, 0xf7fad53c, 1023, 0xf7eef801) = 0xc8202
  *** stack smashing detected ***: terminated
  --- SIGABRT (Aborted) ---
  +++ killed by SIGABRT +++
  # LD_PRELOAD=/usr/lib/arm-linux-gnueabihf/faketime/libfaketime.so.1 ltrace 
--library '*faketime*' bash -c 'exit 0' 
  bash->gettimeofday(0x8b07a0, 0)  = 0
  bash->getpid()   = 819717
  bash->gettimeofday(0xffb88714, 0)= 0
  bash->getpid()   = 819717
  bash->gettimeofday(0xffb8871c, 0)= 0
  bash->getpid()   = 819717
  +++ exited (status 0) +++
  #

  Unsetting -DFAKE_RANDOM in debian/rules does not fix the problem
  however.

  So simply loading the LD_PRELOAD library without executing it seems to
  be enough to break bash.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/2059078/+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 2058800] Re: [needs-packaging] Add systemd-bsod

[Brian Murray]

*** This is an automated message ***

This bug is tagged needs-packaging which identifies it as a request for
a new package in Ubuntu.  As a part of the managing needs-packaging bug
reports specification,
https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs-
packaging bug reports have Wishlist importance.  Subsequently, I'm
setting this bug's status to Wishlist.

** Summary changed:

- Add systemd-bsod
+ [needs-packaging] Add systemd-bsod

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

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

Title:
  [needs-packaging] Add systemd-bsod

Status in systemd package in Ubuntu:
  New

Bug description:
  One of the components of systemd 255 and later.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2058800/+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 2058693] Re: NetworkManager crashed with SIGABRT in g_assertion_message_expr()

[Brian Murray]

I looked at the log files on the server which does the retracing of
these crashes and I did not find anything informative. If you still have
the .crash file available on your system (its located in /var/crash/) I
might be able to have a look at it.  You may want to make the bug
private again if you do upload the core dump as it could contain
personal information.

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

Title:
  NetworkManager crashed with SIGABRT in g_assertion_message_expr()

Status in network-manager package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: network-manager 1.45.90-1ubuntu1
  Uname: Linux 6.8.1 x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar 20 23:12:46 2024
  ExecutablePath: /usr/sbin/NetworkManager
  InstallationDate: Installed on 2024-02-14 (37 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240212)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcAttrCurrent: Error: [Errno 22] Invalid argument
  ProcCmdline: /usr/sbin/NetworkManager --no-daemon
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  Signal: 6
  SignalName: SIGABRT
  SourcePackage: network-manager
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? ()
  Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2024-02-18T15:43:08.117195
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.45.90  connected  started  full  enabled enabled  
enabled  missing  enabled
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2058693/+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 2054319] Re: System installed from jammy point release iso cannot upgrade to noble

[Brian Murray]

I broke out the policykit failure, with an apport-package bug, into
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2054716

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

Title:
  System installed from jammy point release iso cannot upgrade to noble

Status in gnome-shell package in Ubuntu:
  New
Status in policykit-1 package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  We have different crashes being encountered. In our auto-upgrade-
  testing, we see gnome-shell crash, however, when testing locally, I
  didn't experience this. @hyask did experience the gnome-shell crash
  though.

  When running an upgrade from jammy to noble in a virsh vm, about
  halfway through the upgrade process my gui dies. I then ran the
  upgrade from a console, to which it revealed that just the gui dies -
  the upgrade process, for me, continues and then laterally fails.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: ubuntu-release-upgrader-core 1:24.04.7
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu7
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CrashReports:
   640:1000:124:1592041:2024-02-19 14:26:22.564354912 +:2024-02-19 
14:51:56.318947066 +:/var/crash/_usr_libexec_tracker-extract-3.1000.crash
   600:0:124:833806:2024-02-19 14:34:18.370597600 +:2024-02-19 
14:34:19.370597600 +:/var/crash/polkitd.0.crash
  Date: Mon Feb 19 14:53:39 2024
  InstallationDate: Installed on 2024-02-19 (0 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to noble on 2024-02-19 (0 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: pkexec must be setuid root
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  mtime.conffile..etc.init.d.apport: 2024-02-14T15:51:44

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2054319/+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 2054716] Re: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1

[Brian Murray]

** Changed in: policykit-1 (Ubuntu)
Milestone: None => ubuntu-24.04-beta

** Tags added: need-duplicate-check rls-nn-incoming

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

Title:
  package polkitd 124-1 failed to install/upgrade: installed polkitd
  package post-installation script subprocess returned error exit status
  1

Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  I was working on recreating bug 2054319 and did so by modifying my
  /etc/apt/sources.list file from jammy to noble and installing polkit
  and all its dependencies.

  bdmurray@clean-jammy-amd64:~$ sudo apt-get install gir1.2-polkit-1.0 
libpolkit-agent-1-0:amd64 libpolkit-gobject-1-0:amd64 pkexec policykit-1 polkitd
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
linux-headers-6.2.0-26-generic linux-headers-6.2.0-36-generic 
linux-headers-6.5.0-14-generic
linux-hwe-6.2-headers-6.2.0-26 linux-hwe-6.2-headers-6.2.0-36 
linux-hwe-6.5-headers-6.5.0-14 linux-image-6.2.0-26-generic
linux-image-6.2.0-36-generic linux-image-6.5.0-14-generic 
linux-modules-6.2.0-26-generic linux-modules-6.2.0-36-generic
linux-modules-6.5.0-14-generic linux-modules-extra-6.2.0-26-generic 
linux-modules-extra-6.2.0-36-generic
linux-modules-extra-6.5.0-14-generic
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libduktape207 
libgcrypt20 libglib2.0-0 libglib2.0-bin
libnss-systemd libpam-systemd libsystemd-shared libsystemd0 libudev1 
libzstd1 locales systemd systemd-dev systemd-oomd
systemd-resolved systemd-sysv systemd-timesyncd udev
  Suggested packages:
glibc-doc rng-tools low-memory-monitor polkitd-pkla systemd-container 
systemd-homed systemd-userdbd systemd-boot
libqrencode4 libtss2-rc0
  Recommended packages:
libnss-nis libnss-nisplus
  The following NEW packages will be installed:
libduktape207 libsystemd-shared systemd-dev systemd-resolved
  The following packages will be upgraded:
gir1.2-polkit-1.0 libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg 
libc6-dev libgcrypt20 libglib2.0-0 libglib2.0-bin
libnss-systemd libpam-systemd libpolkit-agent-1-0 libpolkit-gobject-1-0 
libsystemd0 libudev1 libzstd1 locales pkexec
policykit-1 polkitd systemd systemd-oomd systemd-sysv systemd-timesyncd udev
  26 upgraded, 4 newly installed, 0 to remove and 1407 not upgraded.
  Need to get 34.9 MB of archives.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: polkitd 124-1
  ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  Date: Thu Feb 22 08:46:48 2024
  ErrorMessage: installed polkitd package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2023-11-02 (112 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.11
  SourcePackage: policykit-1
  Title: package polkitd 124-1 failed to install/upgrade: installed polkitd 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2054716/+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 1881504] Re: cross-testing essential packages fails

[Brian Murray]

** Tags added: adt-494

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

Title:
  cross-testing essential packages fails

Status in apt package in Ubuntu:
  Won't Fix
Status in autopkgtest package in Ubuntu:
  Confirmed
Status in gzip package in Ubuntu:
  New

Bug description:
  Testing gzip on i386 fails at replacing gzip(:amd64) with gzip:i386.

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-
  groovy/groovy/i386/g/gzip/20200528_195150_89f08@/log.gz

  ...
  autopkgtest [19:51:38]: testing package gzip version 1.10-2ubuntu1
  autopkgtest [19:51:38]: build not needed
  autopkgtest [19:51:38]: test simple-gzip: preparing testbed
  Note, using file '/tmp/autopkgtest.1PbIQv/1-autopkgtest-satdep.dsc' to get 
the build dependencies
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Starting pkgProblemResolver with broken count: 0
  Starting 2 pkgProblemResolver with broken count: 0
  Done
  The following packages will be REMOVED:
gzip
  The following NEW packages will be installed:
build-essential cpp cpp-9 g++ g++-9 gcc gcc-10-base:i386 gcc-9 gcc-9-base
gzip:i386 libasan5 libatomic1 libc-dev-bin libc6:i386 libc6-dev libcc1-0
libcrypt-dev libcrypt1:i386 libgcc-9-dev libgcc-s1:i386 libgomp1 libisl22
libitm1 liblsan0 libmpc3 libquadmath0 libstdc++-9-dev libtsan0 libubsan1
linux-libc-dev
  WARNING: The following essential packages will be removed.
  This should NOT be done unless you know exactly what you are doing!
gzip
  0 upgraded, 30 newly installed, 1 to remove and 0 not upgraded.
  E: Essential packages were removed and -y was used without 
--allow-remove-essential.
  E: Failed to process build dependencies
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1881504/+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 2054716] Re: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1

[Brian Murray]

** Tags added: cuqa-automated-testing need-duplicate-check

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

Title:
  package polkitd 124-1 failed to install/upgrade: installed polkitd
  package post-installation script subprocess returned error exit status
  1

Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  I was working on recreating bug 2054319 and did so by modifying my
  /etc/apt/sources.list file from jammy to noble and installing polkit
  and all its dependencies.

  bdmurray@clean-jammy-amd64:~$ sudo apt-get install gir1.2-polkit-1.0 
libpolkit-agent-1-0:amd64 libpolkit-gobject-1-0:amd64 pkexec policykit-1 polkitd
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
linux-headers-6.2.0-26-generic linux-headers-6.2.0-36-generic 
linux-headers-6.5.0-14-generic
linux-hwe-6.2-headers-6.2.0-26 linux-hwe-6.2-headers-6.2.0-36 
linux-hwe-6.5-headers-6.5.0-14 linux-image-6.2.0-26-generic
linux-image-6.2.0-36-generic linux-image-6.5.0-14-generic 
linux-modules-6.2.0-26-generic linux-modules-6.2.0-36-generic
linux-modules-6.5.0-14-generic linux-modules-extra-6.2.0-26-generic 
linux-modules-extra-6.2.0-36-generic
linux-modules-extra-6.5.0-14-generic
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libduktape207 
libgcrypt20 libglib2.0-0 libglib2.0-bin
libnss-systemd libpam-systemd libsystemd-shared libsystemd0 libudev1 
libzstd1 locales systemd systemd-dev systemd-oomd
systemd-resolved systemd-sysv systemd-timesyncd udev
  Suggested packages:
glibc-doc rng-tools low-memory-monitor polkitd-pkla systemd-container 
systemd-homed systemd-userdbd systemd-boot
libqrencode4 libtss2-rc0
  Recommended packages:
libnss-nis libnss-nisplus
  The following NEW packages will be installed:
libduktape207 libsystemd-shared systemd-dev systemd-resolved
  The following packages will be upgraded:
gir1.2-polkit-1.0 libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg 
libc6-dev libgcrypt20 libglib2.0-0 libglib2.0-bin
libnss-systemd libpam-systemd libpolkit-agent-1-0 libpolkit-gobject-1-0 
libsystemd0 libudev1 libzstd1 locales pkexec
policykit-1 polkitd systemd systemd-oomd systemd-sysv systemd-timesyncd udev
  26 upgraded, 4 newly installed, 0 to remove and 1407 not upgraded.
  Need to get 34.9 MB of archives.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: polkitd 124-1
  ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  Date: Thu Feb 22 08:46:48 2024
  ErrorMessage: installed polkitd package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2023-11-02 (112 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.11
  SourcePackage: policykit-1
  Title: package polkitd 124-1 failed to install/upgrade: installed polkitd 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2054716/+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 2054716] [NEW] package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1

[Brian Murray]

Public bug reported:

I was working on recreating bug 2054319 and did so by modifying my
/etc/apt/sources.list file from jammy to noble and installing polkit and
all its dependencies.

bdmurray@clean-jammy-amd64:~$ sudo apt-get install gir1.2-polkit-1.0 
libpolkit-agent-1-0:amd64 libpolkit-gobject-1-0:amd64 pkexec policykit-1 polkitd
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  linux-headers-6.2.0-26-generic linux-headers-6.2.0-36-generic 
linux-headers-6.5.0-14-generic
  linux-hwe-6.2-headers-6.2.0-26 linux-hwe-6.2-headers-6.2.0-36 
linux-hwe-6.5-headers-6.5.0-14 linux-image-6.2.0-26-generic
  linux-image-6.2.0-36-generic linux-image-6.5.0-14-generic 
linux-modules-6.2.0-26-generic linux-modules-6.2.0-36-generic
  linux-modules-6.5.0-14-generic linux-modules-extra-6.2.0-26-generic 
linux-modules-extra-6.2.0-36-generic
  linux-modules-extra-6.5.0-14-generic
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libduktape207 
libgcrypt20 libglib2.0-0 libglib2.0-bin
  libnss-systemd libpam-systemd libsystemd-shared libsystemd0 libudev1 libzstd1 
locales systemd systemd-dev systemd-oomd
  systemd-resolved systemd-sysv systemd-timesyncd udev
Suggested packages:
  glibc-doc rng-tools low-memory-monitor polkitd-pkla systemd-container 
systemd-homed systemd-userdbd systemd-boot
  libqrencode4 libtss2-rc0
Recommended packages:
  libnss-nis libnss-nisplus
The following NEW packages will be installed:
  libduktape207 libsystemd-shared systemd-dev systemd-resolved
The following packages will be upgraded:
  gir1.2-polkit-1.0 libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg 
libc6-dev libgcrypt20 libglib2.0-0 libglib2.0-bin
  libnss-systemd libpam-systemd libpolkit-agent-1-0 libpolkit-gobject-1-0 
libsystemd0 libudev1 libzstd1 locales pkexec
  policykit-1 polkitd systemd systemd-oomd systemd-sysv systemd-timesyncd udev
26 upgraded, 4 newly installed, 0 to remove and 1407 not upgraded.
Need to get 34.9 MB of archives.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: polkitd 124-1
ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8
Uname: Linux 6.5.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckMismatches: ./boot/grub/grub.cfg
CasperMD5CheckResult: fail
Date: Thu Feb 22 08:46:48 2024
ErrorMessage: installed polkitd package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2023-11-02 (112 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.2
 apt  2.4.11
SourcePackage: policykit-1
Title: package polkitd 124-1 failed to install/upgrade: installed polkitd 
package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: policykit-1 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy need-duplicate-check third-party-packages

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

Title:
  package polkitd 124-1 failed to install/upgrade: installed polkitd
  package post-installation script subprocess returned error exit status
  1

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  I was working on recreating bug 2054319 and did so by modifying my
  /etc/apt/sources.list file from jammy to noble and installing polkit
  and all its dependencies.

  bdmurray@clean-jammy-amd64:~$ sudo apt-get install gir1.2-polkit-1.0 
libpolkit-agent-1-0:amd64 libpolkit-gobject-1-0:amd64 pkexec policykit-1 polkitd
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
linux-headers-6.2.0-26-generic linux-headers-6.2.0-36-generic 
linux-headers-6.5.0-14-generic
linux-hwe-6.2-headers-6.2.0-26 linux-hwe-6.2-headers-6.2.0-36 
linux-hwe-6.5-headers-6.5.0-14 linux-image-6.2.0-26-generic
linux-image-6.2.0-36-generic linux-image-6.5.0-14-generic 
linux-modules-6.2.0-26-generic linux-modules-6.2.0-36-generic
linux-modules-6.5.0-14-generic linux-modules-extra-6.2.0-26-generic 
linux-modules-extra-6.2.0-36-generic
linux-modules-extra-6.5.0-14-generic
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libduktape207 
libgcrypt20 libglib2.0-0 

[Touch-packages] [Bug 2019026] Re: systemd /tmp cleaning is suboptimal

[Brian Murray]

It looks like something on our autopkgtest-cloud-worker may also be
regularly changing the contents of /tmp but we've set up an experiment
for over the weekend and will report back.

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

Title:
  systemd /tmp cleaning is suboptimal

Status in systemd package in Ubuntu:
  Confirmed

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

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

  This is suboptimal for two reasons.

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

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

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

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

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

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

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


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

[Touch-packages] [Bug 2053165] Re: [noble] Version 2.7.5 causes software-properties to crash

[Brian Murray]

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

** This bug has been marked a duplicate of bug 2053228
   software-properties-gtk does not start

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

Title:
  [noble] Version 2.7.5 causes software-properties to crash

Status in python-apt package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Only since recent 2.7.5 update along with 0.99.42 for software-properties.
  Crash on start-up.

  $ software-properties-gtk 
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)

^^^
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 163, in __init__
  SoftwareProperties.__init__(self, options=options, datadir=datadir,
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
109, in __init__
  self.backup_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
437, in backup_sourceslist
  source_bkp = SourceEntry(line=source.line,file=source.file)
   ^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509, 
in __init__
  raise ValueError("Classic SourceEntry cannot be written to .sources file")
  ValueError: Classic SourceEntry cannot be written to .sources file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2053165/+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 2053228] Re: software-properties-gtk does not start

[Brian Murray]

** Tags added: rls-nn-incoming

** Changed in: software-properties (Ubuntu)
Milestone: None => ubuntu-24.04-beta

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  software-properties-gtk does not start

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  On a new install with the new format sources.list software-properties-gtk 
does not start:
  corrado@corrado-n4-nn-0215:~$ software-properties-gtk
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)

^^^
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 163, in __init__
  SoftwareProperties.__init__(self, options=options, datadir=datadir,
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
109, in __init__
  self.backup_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
437, in backup_sourceslist
  source_bkp = SourceEntry(line=source.line,file=source.file)
   ^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509, 
in __init__
  raise ValueError("Classic SourceEntry cannot be written to .sources file")
  ValueError: Classic SourceEntry cannot be written to .sources file
  corrado@corrado-n4-nn-0215:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: software-properties-gtk 0.99.42
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 15 10:07:43 2024
  InstallationDate: Installed on 2024-02-15 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2053228/+subscriptions


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

[Touch-packages] [Bug 2019026] Re: systemd /tmp cleaning is suboptimal

[Brian Murray]

The Ubuntu QA team encountered an issue where our autopkgtest-cloud-
workers in the prod-proposed-migration environment ran out of free space
in /tmp because these are production servers which are rebooted very
infrequently. Due to some bug in the autopkgtest-cloud or autopkgtest
code there were left over log files from late November, December, and
January in /tmp. These log files can be quite large and our 200G /tmp
partition ended up being full quite regularly.

I too would expect /tmp to be cleaned up regularly and remember the days
when it was.

It be interesting to see what other server administrators do about
cleaning up /tmp. Does everyone modify /usr/lib/tmpfiles.d/tmp.conf ?

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

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

Title:
  systemd /tmp cleaning is suboptimal

Status in systemd package in Ubuntu:
  Confirmed

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

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

  This is suboptimal for two reasons.

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

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

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

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

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

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

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


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

[Touch-packages] [Bug 2052535] Re: Blocked by pycountry autopkgtest

[Brian Murray]

** Tags removed: update-excuse

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

Title:
  Blocked by pycountry autopkgtest

Status in iso-codes package in Ubuntu:
  New

Bug description:
  https://bugs.launchpad.net/ubuntu/+source/pycountry/+bug/2052318
  currently prevents iso-codes to migrate from 4.15.0-1 to 4.16.0-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iso-codes/+bug/2052535/+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 2011628] Re: Apparmor Disallows Disabling Dhclient Scripts

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: isc-dhcp (Ubuntu Lunar)
   Status: New => Won't Fix

-- 
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:
  Fix Released
Status in isc-dhcp source package in Focal:
  New
Status in isc-dhcp source package in Jammy:
  New
Status in isc-dhcp source package in Lunar:
  Won't Fix
Status in isc-dhcp package in Debian:
  New

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 2026273] Re: SRU e2fsprogs v1.47.0 for HWE reasons

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

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

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

Title:
  SRU e2fsprogs v1.47.0 for HWE reasons

Status in e2fsprogs package in Ubuntu:
  Confirmed
Status in focal package in Ubuntu:
  New
Status in e2fsprogs source package in Jammy:
  Confirmed
Status in focal source package in Jammy:
  New
Status in e2fsprogs source package in Kinetic:
  Won't Fix
Status in focal source package in Kinetic:
  New
Status in e2fsprogs source package in Lunar:
  Won't Fix
Status in focal source package in Lunar:
  Won't Fix

Bug description:
  [ Impact ]

   * orphan_file ext4 feature is available in Jammy v5.15 GA kernel
   * It is to be enabled by default in Mantic
   * fsck utility in jammy doesn't support orphan_file feature
   * as part of forwards-compatibility support it would be useful for Jammy 
22.04 LTS to be able to fsck future releases (i.e. 23.10 / 24.04)
   * as part of HWE support, users may opt-in and choose to use orphan_file in 
Jammy today, when they do so they currently loose support to fsck a given 
filesystem.

  [ Test Plan ]

   * Create new ext4 filesystem with GA version of e2fsprogs and with proposed 
one
   * Ensure that default feature set enabled is the same (i.e. orphan_file & 
metadata_csum features are OFF)
   * Ensure that either fsck can fsck both filesystems
   * Use tune2fs to enable orphan_file feature
   * Ensure that new fsck can check such a filesystem, and that GA (v5.15) 
kernel can mount it

   * do test rebuilds of reverse-build-depends of e2fsprogs to verify to
  change of API and ABI, none should FTBFS and none should gain any new
  dependencies on the 1.47 symbols

  [ Where problems could occur ]

   * library api/abi changes:

  struct ext2_super_block size is unchanged, s_orphan_file_inum consumes
  one of the s_reserved fields.

  orphan_file related public APIs are added.

   * default features:

  Ensure that config files are unchanged, to ensure that no new features
  are enabled by default, meaning filesystems created with the upgraded
  e2fsprogs in a given Ubuntu release will keep the same feature level.

  [ Other Info ]
   
   * Anything else you think is useful to include
   * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
   * and address these questions in advance

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2026273/+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 2026273] Re: SRU e2fsprogs v1.47.0 for HWE reasons

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: e2fsprogs (Ubuntu Lunar)
   Status: Confirmed => Won't Fix

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

Title:
  SRU e2fsprogs v1.47.0 for HWE reasons

Status in e2fsprogs package in Ubuntu:
  Confirmed
Status in focal package in Ubuntu:
  New
Status in e2fsprogs source package in Jammy:
  Confirmed
Status in focal source package in Jammy:
  New
Status in e2fsprogs source package in Kinetic:
  Won't Fix
Status in focal source package in Kinetic:
  New
Status in e2fsprogs source package in Lunar:
  Won't Fix
Status in focal source package in Lunar:
  Won't Fix

Bug description:
  [ Impact ]

   * orphan_file ext4 feature is available in Jammy v5.15 GA kernel
   * It is to be enabled by default in Mantic
   * fsck utility in jammy doesn't support orphan_file feature
   * as part of forwards-compatibility support it would be useful for Jammy 
22.04 LTS to be able to fsck future releases (i.e. 23.10 / 24.04)
   * as part of HWE support, users may opt-in and choose to use orphan_file in 
Jammy today, when they do so they currently loose support to fsck a given 
filesystem.

  [ Test Plan ]

   * Create new ext4 filesystem with GA version of e2fsprogs and with proposed 
one
   * Ensure that default feature set enabled is the same (i.e. orphan_file & 
metadata_csum features are OFF)
   * Ensure that either fsck can fsck both filesystems
   * Use tune2fs to enable orphan_file feature
   * Ensure that new fsck can check such a filesystem, and that GA (v5.15) 
kernel can mount it

   * do test rebuilds of reverse-build-depends of e2fsprogs to verify to
  change of API and ABI, none should FTBFS and none should gain any new
  dependencies on the 1.47 symbols

  [ Where problems could occur ]

   * library api/abi changes:

  struct ext2_super_block size is unchanged, s_orphan_file_inum consumes
  one of the s_reserved fields.

  orphan_file related public APIs are added.

   * default features:

  Ensure that config files are unchanged, to ensure that no new features
  are enabled by default, meaning filesystems created with the upgraded
  e2fsprogs in a given Ubuntu release will keep the same feature level.

  [ Other Info ]
   
   * Anything else you think is useful to include
   * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
   * and address these questions in advance

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2026273/+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 2033967] Re: Laptop screen blinked, no tty works and 200 dmesg errors per second

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

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

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

Title:
  Laptop screen blinked, no tty works and 200 dmesg errors per second

Status in Mesa:
  Fix Released
Status in linux-hwe-6.2 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-hwe-6.2 source package in Jammy:
  Invalid
Status in mesa source package in Jammy:
  New
Status in linux-hwe-6.2 source package in Lunar:
  Invalid
Status in mesa source package in Lunar:
  Won't Fix
Status in linux-hwe-6.2 source package in Mantic:
  Invalid
Status in mesa source package in Mantic:
  Fix Released

Bug description:
  I was using my laptop and suddenly the screen blinked. After that, all
  I could do was to move the mouse, no interaction worked. Trying to
  change to a TTY would open the black screen but the text cursor wasn't
  blinking and nothing happened.

  I accessed the laptop via SSH and used:

  screen env DISPLAY=:0 xfwm4 --vblank=xpresent --replace

  To reload xfwm4. After that, the graphical interface started working
  again. However, no TTY is accessible and there are 200 dmesg errors
  per second. These are the errors that repeat endlessly:

  [43959.444682] amdgpu :06:00.0: amdgpu: couldn't schedule ib on ring 

  [43959.444688] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs 
(-22)

  And while I was writing this report, another problem happened:

  [44566.016330] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring vcn_enc0 
timeout, signaled seq=2, emitted seq=6
  [44566.016553] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process 
information: process obs pid 38687 thread obs:cs0 pid 38694
  [44566.016748] amdgpu :06:00.0: amdgpu: GPU reset begin!
  [44566.317039] [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 
0x0001 != 0x0002
  [44566.525640] [drm] Register(0) [mmUVD_RB_RPTR] failed to reach value 
0x0100 != 0x
  [44566.728577] [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 
0x0001 != 0x0002
  [44566.731204] [ cut here ]
  [44566.731205] WARNING: CPU: 15 PID: 29333 at 
drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c:600 amdgpu_irq_put+0xa4/0xc0 [amdgpu]
  [44566.731429] Modules linked in: tls wireguard curve25519_x86_64 
libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libcurve25519_generic 
libchacha ip6_udp_tunnel udp_tunnel nvme_fabrics veth bridge stp llc zfs(PO) 
zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) 
rfcomm snd_seq_dummy snd_hrtimer vhost_vsock vmw_vsock_virtio_transport_common 
vhost vhost_iotlb vsock cmac algif_hash algif_skcipher af_alg bnep zram 
binfmt_misc nls_iso8859_1 nft_masq snd_sof_amd_rembrandt snd_sof_amd_renoir 
snd_hda_codec_realtek snd_sof_amd_acp snd_hda_codec_generic snd_sof_pci 
ledtrig_audio snd_sof_xtensa_dsp snd_hda_codec_hdmi snd_sof snd_hda_intel 
snd_sof_utils snd_intel_dspcfg snd_soc_core snd_intel_sdw_acpi snd_compress 
nft_limit snd_hda_codec intel_rapl_msr ac97_bus intel_rapl_common snd_hda_core 
snd_pcm_dmaengine snd_hwdep edac_mce_amd snd_pci_ps btusb snd_seq_midi btrtl 
snd_rpl_pci_acp6x kvm_amd snd_seq_midi_event btbcm snd_acp_pci btintel btmtk 
snd_rawmidi uvcvideo
  [44566.731465]  snd_pci_acp6x nf_log_syslog rtw89_8852ae kvm 
videobuf2_vmalloc bluetooth snd_pcm videobuf2_memops snd_seq rtw89_8852a 
irqbypass snd_pci_acp5x videobuf2_v4l2 ecdh_generic snd_seq_device 
snd_rn_pci_acp3x joydev nft_log input_leds rapl videobuf2_common serio_raw 
snd_timer wmi_bmof hid_multitouch ecc snd_acp_config rtw89_pci snd_soc_acpi snd 
k10temp rtw89_core snd_pci_acp3x soundcore ideapad_laptop ccp sparse_keymap 
platform_profile mac_hid nft_ct nvidia_uvm(PO) nft_chain_nat nf_nat 
sch_fq_codel nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 cuse msr parport_pc 
nf_tables ppdev lp nfnetlink parport ramoops pstore_blk reed_solomon 
pstore_zone efi_pstore autofs4 btrfs blake2b_generic dm_crypt raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear overlay v4l2loopback(O) videodev mc 
virt_wifi virtio_net net_failover failover virtio_gpu virtio_dma_buf 
drm_shmem_helper z3fold rndis_host cdc_ether usbnet bfq at
 h10k_pci
  [44566.731504]  ath10k_core ath mac80211 libarc4 cfg80211 usb_storage nbd mii 
nvidia_drm(PO) nvidia_modeset(PO) usbhid nvidia(PO) amdgpu iommu_v2 drm_buddy 
gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_display_helper cec rc_core 
drm_kms_helper crct10dif_pclmul syscopyarea crc32_pclmul polyval_clmulni 
sysfillrect polyval_generic hid_generic nvme sysimgblt ghash_clmulni_intel drm 
sha512_ssse3 aesni_intel i2c_hid_acpi crypto_simd xhci_pci nvme_core cryptd 
r8169 

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

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

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

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

Title:
  Update ubuntu cloud info

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

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

  [ Test Plan ]

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

  verification scriptlet (attached):

  #!/bin/bash
  set -ex

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

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

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

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

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

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

  done

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

  [ Other Info ]

  [Original description]

  Issues:
   - Using the presence of cloud-init to flag an image as a cloud image is 
incorrect now that ubuntu-server includes cloud-init (and ubuntu-core images)
   - Using the presence of EC2 metadata source is incorrect as many non-EC2 
clouds provide EC2 metadata.  Thus we have bugs like bug #1722946 that are 
tagged as an 'ec2-images' bug which are clearly on openstack
   - Marking all bugs that have cloud-init but no EC2 metadata source as an 
'uec-images' bug uses a name that no longer has 

[Touch-packages] [Bug 1971425] Re: The "look" cli dictionary only sees capitalized words

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: util-linux (Ubuntu Lunar)
   Status: Triaged => Won't Fix

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

Title:
  The "look" cli dictionary only sees capitalized words

Status in util-linux package in Ubuntu:
  Triaged
Status in util-linux source package in Jammy:
  Triaged
Status in util-linux source package in Lunar:
  Won't Fix
Status in util-linux package in Debian:
  Confirmed

Bug description:
  In Ubuntu 20.04;
  ~ > look accident
  accident
  accident's
  accidental
  accidental's
  accidentally
  accidentals
  accidents
  In Ubuntu 22.04;
  ~ > look accident
  (nothing)
  ~ > look acc
  Accenture
  Accenture's
  Accra
  Accra's
  Digging deeper; the dictionary at /usr/share/dict/words seems OK.
  If I copy the "look" binary from Ubuntu 20.04 and use it on Ubuntu 22.04 it 
works;
  ~ > ./look accident
  accident
  accidental
  accidentally
  accidental's
  accidentals
  accident's
  accidents

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bsdextrautils 2.37.2-4ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Tue May  3 14:19:57 2022
  InstallationDate: Installed on 2018-09-07 (1334 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to jammy on 2022-05-01 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1971425/+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 1980991] Re: /usr/sbin/on_ac_power incorrectly reporting ac power status

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: powermgmt-base (Ubuntu Lunar)
   Status: Triaged => Won't Fix

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

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

Status in powermgmt-base package in Ubuntu:
  Triaged
Status in powermgmt-base source package in Kinetic:
  Won't Fix
Status in powermgmt-base source package in Lunar:
  Won't Fix

Bug description:
  Good afternoon, folks.

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

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

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

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

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

  Thanks!
  -Kevin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1980991/+subscriptions


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

[Touch-packages] [Bug 1997912] Re: /usr/share/apport/whoopsie-upload-all:binascii.Error:/usr/share/apport/whoopsie-upload-all@249:main:collect_info:process_report:load:_decompress_line:b64decode

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

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

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

Title:
  /usr/share/apport/whoopsie-upload-
  all:binascii.Error:/usr/share/apport/whoopsie-upload-
  all@249:main:collect_info:process_report:load:_decompress_line:b64decode

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Kinetic:
  Won't Fix
Status in apport source package in Lunar:
  Won't Fix

Bug description:
  Impact
  ==

  apport-unpack and whoopsie-upload-all can crash when fed with a
  malformed problem report. They should print a proper error message
  instead of crashing.

  Test Plan
  =

  1. Create malformed report:
  ```
  printf "CoreDump: base64\n H4sICAAC/0NvcmVEdW1wAA==\n 7Z0LYFPV/cdP0rQ\n" 
> malformed.crash
  ```
  2. Try to unpack it:
  ```
  apport-unpack malformed.crash unpack
  ```

  It should print an error message instead of a stack trace.

  Where problems could occur
  ==

  The patch touches the problem report handling and therefore can affect
  apport-unpack, apport-bug, whoopsie-upload-all. The change is covered
  with tests and apport has a test suite running during build and as
  autopkgtest.

  Original report
  ===

  ```
  Traceback (most recent call last):
    File "/usr/share/apport/whoopsie-upload-all", line 249, in 
  main()
    File "/usr/share/apport/whoopsie-upload-all", line 231, in main
  stamps = collect_info()
    File "/usr/share/apport/whoopsie-upload-all", line 162, in collect_info
  res = process_report(r)
    File "/usr/share/apport/whoopsie-upload-all", line 76, in process_report
  r.load(f, binary="compressed")
    File "/usr/lib/python3/dist-packages/problem_report.py", line 139, in load
  bd, value = self._decompress_line(line, bd, value)
    File "/usr/lib/python3/dist-packages/problem_report.py", line 276, in 
_decompress_line
  block = base64.b64decode(line)
    File "/usr/lib/python3.10/base64.py", line 87, in b64decode
  return binascii.a2b_base64(s)
  binascii.Error: Incorrect padding
  ```

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.23.1-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/dd58c8169d2ec8468b8b37471dfb701ac31c 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1997912/+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 2015380] Re: slapd crash when using pwdMinDelay of ppolicy

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

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

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

Title:
  slapd crash when using pwdMinDelay of ppolicy

Status in openldap package in Ubuntu:
  Fix Released
Status in openldap source package in Jammy:
  Fix Released
Status in openldap source package in Kinetic:
  Won't Fix
Status in openldap source package in Lunar:
  Won't Fix
Status in openldap source package in Mantic:
  Fix Released

Bug description:
  Bug reported upstream[1], and confirmed in the mailing list[2].

  PR at [3].

  From the mailing list post[2], we can see that slapd crashes:
  """
  But if I test with a wrong password ( yyy) I got:
  root@zeus:/usr/lib/python3/dist-packages# ldapsearch -xLLLZZD
  uid=pauloric,ou=users,dc=contatogs,dc=com,dc=br -w yyy |wc -l
  ldap_result: Can't contact LDAP server (-1)
  0

  my openldap stop working.Active: inactive (dead)

  root@zeus:/usr/lib/python3/dist-packages# systemctl status -l slapd
  ○ slapd.service - LSB: OpenLDAP standalone server (Lightweight Director>
   Loaded: loaded (/etc/init.d/slapd; generated)
  Drop-In: /usr/lib/systemd/system/slapd.service.d
   └─slapd-remain-after-exit.conf
   Active: inactive (dead) since Tue 2023-04-04 14:44:49 -03; 20s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 986673 ExecStart=/etc/init.d/slapd start (code=exited, sta>
  Process: 986688 ExecStop=/etc/init.d/slapd stop (code=exited, statu>
  CPU: 47ms
  """


  1. https://bugs.openldap.org/show_bug.cgi?id=10028
  2. 
https://lists.openldap.org/hyperkitty/list/openldap-techni...@openldap.org/thread/3LYIPMT6TYJM4C7NUFXVYJS7YMODB5ZH/
  3. https://git.openldap.org/openldap/openldap/-/merge_requests/609

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2015380/+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 2018293] Re: [UBUNTU 20.04] Crash in zlib deflateBound() function on s390x

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

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

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

Title:
  [UBUNTU 20.04] Crash in zlib deflateBound() function on s390x

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  Fix Released
Status in zlib source package in Focal:
  New
Status in zlib source package in Jammy:
  New
Status in zlib source package in Lunar:
  Won't Fix
Status in zlib source package in Mantic:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [ Impact ]

   * The zlib deflateBound() function can crash on s390x,
     if called before deflateInit().

   * The solution is that zlib on s390x needs to support
     calling deflateBound() always before deflateInit().

  [ Test Plan ]

   * It's suggested to do a more overall or e2e test
 and run the zlib-ng test suite against the system zlib
 as follows:
 $ git clone https://github.com/zlib-ng/zlib-ng.git
 $ cd zlib-ng
 $ cmake -DZLIB_COMPAT=ON -DZLIBNG_ENABLE_TESTS=OFF -DBUILD_SHARED_LIBS=ON 
-DWITH_DFLTCC_DEFLATE=ON -DWITH_DFLTCC_INFLATE=ON .
 $ make gtest_zlib
 $ ldd gtest_zlib
   libz.so.1 => /lib/s390x-linux-gnu/libz.so.1 (0x03fff7e0)
 $ ./gtest_zlib

  [ Where problems could occur ]

   * The only (single line) modification is in the if condition
     of the define DEFLATE_BOUND_ADJUST_COMPLEN statement in
     deflate.c.

   * Things can go wrong if the condition (or logic) is wrong,

   * or if other parts of the code are coded against the old behavior
     and are still expecting it.

   * The likely outcome would be still a crash
     or an unexpected behavior.

  [ Other Info ]

   * Getting this into mantic first,
     before the SRU down to focal is done.
  __

  Problem Description:
  zlib deflateBound() function can crash on s390x when called before 
deflateInit().

  Solution:
  zlib on s390x needs to support calling deflateBound() before deflateInit().

  The fix is squashed into the latest DFLTCC PR:
  https://github.com/madler/zlib/pull/410

  Diff:
  
https://github.com/madler/zlib/compare/113203437eda67261848b14b6c80a33ff7e33d34..f6d382a91a4e7d88b9b12ce0ecdffb1783878160

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2018293/+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 2024599] Re: linux-image-5.15.0-1032-realtime locks up under scheduler test load

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

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

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

Title:
  linux-image-5.15.0-1032-realtime locks up under scheduler test load

Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in apparmor source package in Jammy:
  New
Status in linux source package in Jammy:
  Incomplete
Status in apparmor source package in Kinetic:
  New
Status in linux source package in Kinetic:
  New
Status in apparmor source package in Lunar:
  Won't Fix
Status in linux source package in Lunar:
  Won't Fix
Status in apparmor source package in Mantic:
  New
Status in linux source package in Mantic:
  Incomplete

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

  uname -a
  Linux jammie-amd64-efi 5.15.0-1032-realtime #35-Ubuntu SMP PREEMPT_RT Tue Jan 
24 11:45:03 UTC 2023 x86_64
  x86_64 x86_64 GNU/Linux

  free
     totalusedfree  shared  buff/cache   
available
  Mem: 4013888  200984 34390121204  373892 
3744628
  Swap:4014076   0 4014076

  Running in a kvm-qemu, 8 cpus, cpu Intel Core Processor (Skylake,
  IBRS):

  how to reproduce issue:

  git clone https://github.com/ColinIanKing/stress-ng
  sudo apt-get update
  sudo apt-get build-dep stress-ng
  sudo apt-get install libeigen3-dev libmpfr-dev libkmod-dev libxxhash-dev 
libglvnd-dev libgbm-dev
  cd stress-ng
  make clean
  make -j 8
  sudo ./stress-ng --class scheduler --all 1 -v --vmstat 1 -t 30m

  ..wait for all the stressors to get invoked, system becomes
  unresponsive, can't ^C stress-ng, can't swap consoles on the VM,
  appears to be hard locked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2024599/+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 2024599] Re: linux-image-5.15.0-1032-realtime locks up under scheduler test load

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

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

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

Title:
  linux-image-5.15.0-1032-realtime locks up under scheduler test load

Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in apparmor source package in Jammy:
  New
Status in linux source package in Jammy:
  Incomplete
Status in apparmor source package in Kinetic:
  New
Status in linux source package in Kinetic:
  New
Status in apparmor source package in Lunar:
  Won't Fix
Status in linux source package in Lunar:
  Won't Fix
Status in apparmor source package in Mantic:
  New
Status in linux source package in Mantic:
  Incomplete

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

  uname -a
  Linux jammie-amd64-efi 5.15.0-1032-realtime #35-Ubuntu SMP PREEMPT_RT Tue Jan 
24 11:45:03 UTC 2023 x86_64
  x86_64 x86_64 GNU/Linux

  free
     totalusedfree  shared  buff/cache   
available
  Mem: 4013888  200984 34390121204  373892 
3744628
  Swap:4014076   0 4014076

  Running in a kvm-qemu, 8 cpus, cpu Intel Core Processor (Skylake,
  IBRS):

  how to reproduce issue:

  git clone https://github.com/ColinIanKing/stress-ng
  sudo apt-get update
  sudo apt-get build-dep stress-ng
  sudo apt-get install libeigen3-dev libmpfr-dev libkmod-dev libxxhash-dev 
libglvnd-dev libgbm-dev
  cd stress-ng
  make clean
  make -j 8
  sudo ./stress-ng --class scheduler --all 1 -v --vmstat 1 -t 30m

  ..wait for all the stressors to get invoked, system becomes
  unresponsive, can't ^C stress-ng, can't swap consoles on the VM,
  appears to be hard locked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2024599/+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 2025382] Re: 22.04 DHCPv6 IPv6 broken (at least on Oracle OCI)

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

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

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

Title:
  22.04 DHCPv6 IPv6 broken (at least on Oracle OCI)

Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Jammy:
  Triaged
Status in systemd source package in Lunar:
  Won't Fix

Bug description:
  Ubuntu 22.04.2 LTS
  kernel 5.15.0-1038-oracle
  systemd 249.11-0ubuntu3.9

  After an update a couple weeks ago, Ubuntu 22.04 can no longer get
  IPv6 via DHCPv6 systemd-networkd, at least on Oracle OCI, but there
  are also other similar reports, e.g.

  https://ubuntuforums.org/showthread.php?t=2487465=14146758

  Oracle seems to be aware of the issue but they claim it's a Ubuntu
  22.04 bug:

  https://community.oracle.com/customerconnect/discussion/687610/oci-
  ipv6-address-not-assigned-to-oci-ubuntu-instance-by-dhcp

  The workaround to assign a static IPv6 is not great when managing
  multiple cloud instances.

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


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

[Touch-packages] [Bug 2026307] Re: ssh-askpass-gnome pops up for every sudo command

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

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

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

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

Status in openssh package in Ubuntu:
  New
Status in openssh source package in Jammy:
  Triaged
Status in openssh source package in Kinetic:
  Won't Fix
Status in openssh source package in Lunar:
  Won't Fix

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

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

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

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

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

  thanks

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


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

[Touch-packages] [Bug 1842439] Re: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0) from gtk_css_value_icon_theme_compute() from gtk_css_static_style_compute_value()

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: gtk+3.0 (Ubuntu Lunar)
   Status: Triaged => Won't Fix

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

Title:
  apport-gtk crashed with SIGSEGV in
  _gtk_settings_get_screen(settings=0x0) from
  gtk_css_value_icon_theme_compute() from
  gtk_css_static_style_compute_value()

Status in apport package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in apport source package in Focal:
  Invalid
Status in gtk+3.0 source package in Focal:
  Triaged
Status in apport source package in Lunar:
  Invalid
Status in gtk+3.0 source package in Lunar:
  Won't Fix

Bug description:
  Steps to reproduce
  --

  1. Use GNOME with GNOME shell
  2. killall -11 gnome-shell

  Suspicious Apport log:

  gdbus call error: Error:
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.gnome.SessionManager was not provided by any .service files

  Error tracker
  -
  https://errors.ubuntu.com/problem/815a179408135a894bbb5921adef3757563c75c5
  https://errors.ubuntu.com/problem/276759c7bf0b6628977c63ca70d26b53c9defd22

  Stack trace
  ---

  Python:

  ```
File "apport-gtk", line 703, in 
  app = GTKUserInterface(sys.argv)
File "apport-gtk", line 68, in GTKUserInterface.__init__
  self.widgets.add_from_file(
  os.path.join(os.path.dirname(argv[0]), "apport-gtk.ui")
  )
  ```

  StacktraceTop:
   _gtk_settings_get_screen (settings=0x0) at ../../../../gtk/gtksettings.c:3319
   gtk_css_value_icon_theme_compute (icon_theme=, 
property_id=, provider=, style=, 
parent_style=) at ../../../../gtk/gtkcssiconthemevalue.c:84
   gtk_css_static_style_compute_value (style=0x1e7c320, provider=0x0, 
parent_style=0x0, id=3, specified=0x7f53258b9b20 , section=0x0) at 
../../../../gtk/gtkcssstaticstyle.c:237
   _gtk_css_lookup_resolve (lookup=lookup@entry=0x1e7e790, 
provider=provider@entry=0x0, style=style@entry=0x1e7c320, 
parent_style=parent_style@entry=0x0) at ../../../../gtk/gtkcsslookup.c:122
   gtk_css_static_style_new_compute (provider=provider@entry=0x0, 
matcher=matcher@entry=0x0, parent=parent@entry=0x0) at 
../../../../gtk/gtkcssstaticstyle.c:195

  Original report
  ---
  Session suddenly stopped and came back to login screen, all opened windows 
lost.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: apport-gtk 2.20.11-0ubuntu7
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:117:7292709:2019-09-03 16:20:13.909392833 +0200:2019-09-03 
16:20:14.909392833 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   640:1000:117:48937942:2019-09-03 16:20:11.681426286 +0200:2019-09-03 
16:20:12.681426286 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:1000:117:32054:2019-08-27 17:39:07.125607490 +0200:2019-08-28 
12:36:17.087672961 +0200:/var/crash/_usr_bin_dbus-daemon.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  3 16:20:13 2019
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2018-06-16 (443 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.7, Python 3.7.4, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1
  SegvAnalysis:
   Segfault happened at: 0x7f532548f8c4:mov0x18(%rdi),%rax
   PC (0x7f532548f8c4) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV
  UpgradeStatus: Upgraded to eoan on 2019-06-10 (84 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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


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

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

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

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

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

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

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

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

  Attached is an image of the hang

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


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

[Touch-packages] [Bug 2036467] Re: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: e2fsprogs (Ubuntu Lunar)
   Status: In Progress => Won't Fix

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

Title:
  Resizing cloud-images occasionally fails due to superblock checksum
  mismatch in resize2fs

Status in cloud-images:
  New
Status in e2fsprogs package in Ubuntu:
  In Progress
Status in e2fsprogs source package in Trusty:
  Won't Fix
Status in e2fsprogs source package in Xenial:
  Won't Fix
Status in e2fsprogs source package in Bionic:
  Won't Fix
Status in e2fsprogs source package in Focal:
  In Progress
Status in e2fsprogs source package in Jammy:
  In Progress
Status in e2fsprogs source package in Lunar:
  Won't Fix
Status in e2fsprogs source package in Mantic:
  In Progress

Bug description:
  [Impact]

  This is a long running bug plaguing cloud-images, where on a rare
  occasion resize2fs would fail and the image would not resize to fit
  the entire disk.

  Online resizes would fail due to a superblock checksum mismatch, where
  the superblock in memory differs from what is currently on disk due to
  changes made to the image.

  $ resize2fs /dev/nvme1n1p1
  resize2fs 1.47.0 (5-Feb-2023)
  resize2fs: Superblock checksum does not match superblock while trying to open 
/dev/nvme1n1p1
  Couldn't find valid filesystem superblock.

  Changing the read of the superblock to Direct I/O solves the issue.

  [Testcase]

  Start an c5.large instance on AWS, and attach a 60gb gp3 volume for
  use as a scratch disk.

  Run the following script, courtesy of Krister Johansen and his team:

     #!/usr/bin/bash
     set -euxo pipefail

     while true
     do
     parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s
     sleep .5
     mkfs.ext4 /dev/nvme1n1p1
     mount -t ext4 /dev/nvme1n1p1 /mnt
     stress-ng --temp-path /mnt -D 4 &
     STRESS_PID=$!
     sleep 1
     growpart /dev/nvme1n1 1
     resize2fs /dev/nvme1n1p1
     kill $STRESS_PID
     wait $STRESS_PID
     umount /mnt
     wipefs -a /dev/nvme1n1p1
     wipefs -a /dev/nvme1n1
     done

  Test packages are available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test

  If you install the test packages, the race no longer occurs.

  [Where problems could occur]

  We are changing how resize2fs reads the superblock from underlying
  disks.

  If a regression were to occur, resize2fs could fail to resize offline
  or online volumes. As all cloud-images are online resized during their
  initial boot, this could have a large impact to public and private
  clouds should a regression occur.

  [Other info]

  Upstream mailing list discussion:
  https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/
  https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/

  This was fixed in the below commit upstream:

  commit 43a498e938887956f393b5e45ea6ac79cc5f4b84
  Author: Theodore Ts'o 
  Date: Thu, 15 Jun 2023 00:17:01 -0400
  Subject: resize2fs: use Direct I/O when reading the superblock for
   online resizes
  Link: 
https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84

  The commit has not been tagged to any release. All supported Ubuntu
  releases require this fix, and need to be published in standard non-
  ESM archives to be picked up in cloud images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2036467/+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 2050836] [NEW] apport should prevent crash reporting for unsupported python versions

[Brian Murray]

Public bug reported:

The following bucket in the Ubuntu Error Tracker was brought to my
attention because a package update stopped phasing because of it.

https://errors.ubuntu.com/problem/51d4468e0e9096398f852e3aed0e51658b6ca603

Looking at the individual crashes, e.g.
https://errors.ubuntu.com/oops/2b3117f0-b6ea-11ee-b9e6-fa163e171f02,
we can see that the InterpreterPath is /usr/bin/python3.9 and that this
also appears in Python3Details.

I don't see an UnreportableReason in the report so these would likely
get sent to Launchpad also. Anyway, I don't think these types of crashes
(using an unsupported python version) should be reportable because there
isn't anything we as Ubuntu Developers can do to resolve this problem.

** Affects: apport (Ubuntu)
 Importance: Low
 Status: New

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

** Description changed:

  The following bucket in the Ubuntu Error Tracker was brought to my
  attention because a package update stopped phasing because of it.
  
  https://errors.ubuntu.com/problem/51d4468e0e9096398f852e3aed0e51658b6ca603
  
- Looking at the individual crashes,
- e.g.https://errors.ubuntu.com/oops/2b3117f0-b6ea-11ee-b9e6-fa163e171f02,
+ Looking at the individual crashes, e.g.
+ https://errors.ubuntu.com/oops/2b3117f0-b6ea-11ee-b9e6-fa163e171f02,
  we can see that the InterpreterPath is /usr/bin/python3.9 and that this
  also appears in Python3Details.
  
  I don't see an UnreportableReason in the report so these would likely
  get sent to Launchpad also. Anyway, I don't think these types of crashes
  (using an unsupported python version) should be reportable because there
  isn't anything we as Ubuntu Developers can do to resolve this problem.

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

Title:
  apport should prevent crash reporting for unsupported python versions

Status in apport package in Ubuntu:
  New

Bug description:
  The following bucket in the Ubuntu Error Tracker was brought to my
  attention because a package update stopped phasing because of it.

  https://errors.ubuntu.com/problem/51d4468e0e9096398f852e3aed0e51658b6ca603

  Looking at the individual crashes, e.g.
  https://errors.ubuntu.com/oops/2b3117f0-b6ea-11ee-b9e6-fa163e171f02,
  we can see that the InterpreterPath is /usr/bin/python3.9 and that
  this also appears in Python3Details.

  I don't see an UnreportableReason in the report so these would likely
  get sent to Launchpad also. Anyway, I don't think these types of
  crashes (using an unsupported python version) should be reportable
  because there isn't anything we as Ubuntu Developers can do to resolve
  this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2050836/+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 2041396] Re: gdb 12.1 generates SIGILL on armhf

[Brian Murray]

Given the current size of the queues that might take some time. Could
you run the test locally on the same device which you verified the fix
on?

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

Title:
  gdb 12.1 generates SIGILL on armhf

Status in gdb:
  Fix Released
Status in gdb package in Ubuntu:
  Fix Released
Status in gdb source package in Jammy:
  Incomplete

Bug description:
  [ Impact ]

   * GDB 12.1 introduced a regression where it will break program execution 
when the program contains mixed ARM code and THUMB code.
   * Upstream stated they tested the changes on Ubuntu 20.04 and it went okay.

  [ Test Plan ]

  Considering the following C program:

  ```
  __attribute__((target("arm"), noinline))
  int thumb_func() {
    return 42;
  }

  __attribute__((target("thumb")))
  int main() { return thumb_func(); }
  ```

  If you build it using `gcc repro.c -ggdb3 -Og -o repro` and run the
  GDB using the following commands ...

  ```
  b 3
  r
  c
  ```

  (you can save the contents above to a file and run GDB using `gdb -x
  script ./repro`)

  ... you will notice GDB broke the program and threw SIGILL.
  If you run the program without GDB, the program exits normally.

  [ Where problems could occur ]

   * GDB is a complex software. As the patch suggests, it may break other use 
cases (like single-stepping) entirely.
   * Since this is an ARM-only patch, it's unlikely to affect other CPU 
architectures. However, it is possible that this fix may break ARM64 execution.

  [ Other Info ]
   
   * This bug has been fixed in GDB 13, but the fix was never backported to GDB 
12. You can find the upstream bug in the remote bug watch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/2041396/+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 2045455] Re: add-apt-repository crashed with --- in _request()

[Brian Murray]

** Information type changed from Private to Public

** Changed in: software-properties (Ubuntu)
Milestone: None => ubuntu-24.04-beta

** Tags added: rls-nn-incoming

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

Title:
  add-apt-repository crashed with --- in _request()

Status in software-properties package in Ubuntu:
  New

Bug description:
  Error encountered during first boot after installing ubuntu-unity-
  desktop on Live Server 24.04 Daily Build.

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: software-properties-common 0.99.40
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Nov 30 02:20:48 2023
  ExecutablePath: /usr/bin/add-apt-repository
  InstallationDate: Installed on 2023-11-30 (2 days ago)
  InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily amd64 (20231129)
  InterpreterPath: /usr/bin/python3.11
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/add-apt-repository ppa:relan/exfat -y
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=linux
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonArgs: ['/usr/bin/add-apt-repository', 'ppa:relan/exfat', '-y']
  PythonDetails: N/A
  SourcePackage: software-properties
  Title: add-apt-repository crashed with --- in _request()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2045455/+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 2041396] Re: gdb 12.1 generates SIGILL on armhf

[Brian Murray]

The where problems could occur section says "it is possible that this
fix may break ARM64 execution". How was it verified that this is not
broken?

** Changed in: gdb (Ubuntu Jammy)
   Status: Fix Committed => Incomplete

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

Title:
  gdb 12.1 generates SIGILL on armhf

Status in gdb:
  Fix Released
Status in gdb package in Ubuntu:
  Fix Released
Status in gdb source package in Jammy:
  Incomplete

Bug description:
  [ Impact ]

   * GDB 12.1 introduced a regression where it will break program execution 
when the program contains mixed ARM code and THUMB code.
   * Upstream stated they tested the changes on Ubuntu 20.04 and it went okay.

  [ Test Plan ]

  Considering the following C program:

  ```
  __attribute__((target("arm"), noinline))
  int thumb_func() {
    return 42;
  }

  __attribute__((target("thumb")))
  int main() { return thumb_func(); }
  ```

  If you build it using `gcc repro.c -ggdb3 -Og -o repro` and run the
  GDB using the following commands ...

  ```
  b 3
  r
  c
  ```

  (you can save the contents above to a file and run GDB using `gdb -x
  script ./repro`)

  ... you will notice GDB broke the program and threw SIGILL.
  If you run the program without GDB, the program exits normally.

  [ Where problems could occur ]

   * GDB is a complex software. As the patch suggests, it may break other use 
cases (like single-stepping) entirely.
   * Since this is an ARM-only patch, it's unlikely to affect other CPU 
architectures. However, it is possible that this fix may break ARM64 execution.

  [ Other Info ]
   
   * This bug has been fixed in GDB 13, but the fix was never backported to GDB 
12. You can find the upstream bug in the remote bug watch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/2041396/+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 2049529] Re: Extra ZFS-related log line with `useradd -m -R /path`

[Brian Murray]

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

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

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

Title:
  Extra ZFS-related log line with `useradd -m -R /path`

Status in shadow package in Ubuntu:
  Confirmed
Status in shadow source package in Noble:
  Confirmed

Bug description:
  Hi,

  I was digging into fixing `autopkgtest`'s `unshare` testsuite, and the
  rabbit hole led me here.

  Here is a very quick reproducer, first:

  Start a fresh Ubuntu VM. Here is a quick path, but other ways should do fine:
  ```
  $ cd /tmp
  $ autopkgtest-buildvm-ubuntu-cloud -a amd64 -r noble
  $ kvm -m 1G -snapshot -hda autopkgtest-noble-amd64.img
  ```

  Now in the VM:
  ```
  $ sudo apt install -y mmdebstrap
  $ mmdebstrap noble /tmp/rootfs
  [...]
  $ sudo useradd --create-home --root /tmp/rootfs user1
  can't open /dev/null: No such file or directory
  ```

  The line `can't open /dev/null: No such file or directory` is printed
  on `stderr`, and that's unexpected by the part of the code I was
  debugging in the first place.

  Digging a bit led me to that line that does the printing:
  
https://git.launchpad.net/ubuntu/+source/shadow/tree/debian/patches/1015_add_zsys_support.patch#n69

  There seem to me that there are multiple issues with that patch:
  * Why try to call `zsysctl` in every case without first checking that it 
would be relevant: ZFS is not even installed on the VM we just created, less 
alone it has any ZFS volume/pool/whatever.
  * Obviously, when creating a user in a `chroot`, `/dev/null` won't exist 
unless mapped, and `useradd` is perfectly aware of that, because it even does 
the `chroot` call itself! But why even try to mess with ZFS in the `chroot` 
case in the first place?

  From what history @brian-murray told me, this patch was part of some
  ZFS experimentation in the past. Maybe that experimentation is now
  finished, and that patch could be dropped? At the very least it needs
  improvements, imho.

  EDIT: Just for context on why this issue appears only now: I was
  trying to fix the `unshare` testsuite in `autopkgtest`, which is
  pretty recent (2022) (https://salsa.debian.org/ci-
  team/autopkgtest/-/commit/d1671f94f68bce9a0c6793310a9f8b79b4e919a5)
  even upstream on Debian, and has never worked yet on Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2049529/+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 2047314] Update Released

[Brian Murray]

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

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

Title:
  tzdata 2023d release (leap-second.list expiring this week)

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released
Status in tzdata source package in Jammy:
  Fix Released
Status in tzdata source package in Lunar:
  Fix Released
Status in tzdata source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

  leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023.

  The 2023d release contains the following changes:

     Briefly:
   Ittoqqortoormiit, Greenland changes time zones on 2024-03-31.
   Vostok, Antarctica changed time zones on 2023-12-18.
   Casey, Antarctica changed time zones five times since 2020.
   Code and data fixes for Palestine timestamps starting in 2072.
   A new data file zonenow.tab for timestamps starting now.

     Changes to future timestamps

   Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of
   the rest of Greenland's timekeeping practice on 2024-03-31, by
   changing its time zone from -01/+00 to -02/-01 at the same moment
   as the spring-forward transition.  Its clocks will therefore not
   spring forward as previously scheduled.  The time zone change
   reverts to its common practice before 1981.

   Fix predictions for DST transitions in Palestine in 2072-2075,
   correcting a typo introduced in 2023a.

     Changes to past and future timestamps

   Vostok, Antarctica changed to +05 on 2023-12-18.  It had been at
   +07 (not +06) for years.  (Thanks to Zakhary V. Akulov.)

   Change data for Casey, Antarctica to agree with timeanddate.com,
   by adding five time zone changes since 2020.  Casey is now at +08
   instead of +11.

     Changes to past tm_isdst flags

   Much of Greenland, represented by America/Nuuk, changed its
   standard time from -03 to -02 on 2023-03-25, not on 2023-10-28.
   This does not affect UTC offsets, only the tm_isdst flag.
   (Thanks to Thomas M. Steenholdt.)

     New data file

   A new data file zonenow.tab helps configure applications that use
   timestamps dated from now on.  This simplifies configuration,
   since users choose from a smaller Zone set.  The file's format is
   experimental and subject to change.

  [ Test Plan ]

  Test cases were added to autopkgtest to cover the testing:

  * python: test_2023d

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

  [ Other Info ]

  The autopkgtest for chrony is flaky on jammy and newer (see bug
  #2002910).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+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 2047314] Re: tzdata 2023d release (leap-second.list expiring this week)

[Brian Murray]

** Tags removed: verification-needed-focal verification-needed-jammy 
verification-needed-lunar verification-needed-mantic
** Tags added: verification-done-focal verification-done-jammy 
verification-done-lunar verification-done-mantic

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

Title:
  tzdata 2023d release (leap-second.list expiring this week)

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released
Status in tzdata source package in Jammy:
  Fix Released
Status in tzdata source package in Lunar:
  Fix Released
Status in tzdata source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

  leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023.

  The 2023d release contains the following changes:

     Briefly:
   Ittoqqortoormiit, Greenland changes time zones on 2024-03-31.
   Vostok, Antarctica changed time zones on 2023-12-18.
   Casey, Antarctica changed time zones five times since 2020.
   Code and data fixes for Palestine timestamps starting in 2072.
   A new data file zonenow.tab for timestamps starting now.

     Changes to future timestamps

   Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of
   the rest of Greenland's timekeeping practice on 2024-03-31, by
   changing its time zone from -01/+00 to -02/-01 at the same moment
   as the spring-forward transition.  Its clocks will therefore not
   spring forward as previously scheduled.  The time zone change
   reverts to its common practice before 1981.

   Fix predictions for DST transitions in Palestine in 2072-2075,
   correcting a typo introduced in 2023a.

     Changes to past and future timestamps

   Vostok, Antarctica changed to +05 on 2023-12-18.  It had been at
   +07 (not +06) for years.  (Thanks to Zakhary V. Akulov.)

   Change data for Casey, Antarctica to agree with timeanddate.com,
   by adding five time zone changes since 2020.  Casey is now at +08
   instead of +11.

     Changes to past tm_isdst flags

   Much of Greenland, represented by America/Nuuk, changed its
   standard time from -03 to -02 on 2023-03-25, not on 2023-10-28.
   This does not affect UTC offsets, only the tm_isdst flag.
   (Thanks to Thomas M. Steenholdt.)

     New data file

   A new data file zonenow.tab helps configure applications that use
   timestamps dated from now on.  This simplifies configuration,
   since users choose from a smaller Zone set.  The file's format is
   experimental and subject to change.

  [ Test Plan ]

  Test cases were added to autopkgtest to cover the testing:

  * python: test_2023d

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

  [ Other Info ]

  The autopkgtest for chrony is flaky on jammy and newer (see bug
  #2002910).

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

[Brian Murray]

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

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

Title:
  [SRU] Segfault in dnsmasq when using certain static domain entries +
  DoH (bugfix possibly exists upstream)

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

Bug description:
  [ Impact ]

  Some users may face an unpleasant segmentation fault if they combine 
configurations options like
  server=/domain/# with server|address=/domain/ since the domain matching 
functionality was rewritten in
  version 2.86.

  The  special server address ’#’ means "use the standard servers". The SEGV 
occurs due to the struct server
  datastructure associated with it is passed to forward_query() call without 
been properly reserved and filled
  due to resolvconf servers didn't belong to the priority list.

  Without resolving this, dnsmasq stops running due to the SEGV and
  (non-experienced) users might not notice it.

  
  [ Test Plan ]

  #0.Prepare a VM or Container. i.e:
  # lxc launch ubuntu-daily:jammy Jdnsmasq

  #1. Install dnsmasq
  # apt update && apt upgrade -y
  # apt install -y dnsmasq

  #2. Disable systemd-resolved service and enabling resolution through
  dnsmasq, configuring DNS servers through it.

  # systemctl disable --now systemd-resolved.service
  # rm -f /etc/resolv.conf
  # cat > /etc/resolv.conf << __EOF__
  nameserver 127.0.0.1
  __EOF__
  # echo "server=8.8.8.8" >> /etc/dnsmasq.conf (or edit the file to add it if 
you prefer)
  # (Optional) echo "log-queries" >> /etc/dnsmasq.conf
  # (optional) echo "log-debug" >> /etc/dnsmasq.conf
  # systemctl start dnsmasq.service

  3. Copy netflix-nov6.conf into /etc/dnsmasq.d/
  # cat > /etc/dnsmasq.d/netflix-nov6.conf << __EOF__
  # Null  response on these domains
  server=/netflix.com/#
  address=/netflix.com/::
  server=/netflix.net/#
  address=/netflix.net/::
  server=/nflxext.com/#
  address=/nflxext.com/::
  server=/example.com/#
  address=/example.com/::
  __EOF__

  #4. Restart/reload dnsmasq
  # systemctl restart dnsmasq

  #5. Verify that dnsmasq resolves domains correctly:

  root@Jdnsmasq:~# dig +short -tA ubuntu.com @127.0.0.1
  185.125.190.21
  185.125.190.20
  185.125.190.29
  root@Jdnsmasq:~# dig +short -t ubuntu.com @127.0.0.1
  2620:2d:4000:1::28
  2620:2d:4000:1::26
  2620:2d:4000:1::27

  #6. Perform a type65 / HTTPS recordtype query for netflix.com towards
  the dnsmasq server twice:

  root@Jdnsmasq:~# dig A netflix.com @127.0.0.1

  ; <<>> DiG 9.18.18-0ubuntu0.22.04.1-Ubuntu <<>> A netflix.com @127.0.0.1
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 48730
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 1232
  ; EDE: 23 (Network Error)
  ;; QUESTION SECTION:
  ;netflix.com. IN  A

  ;; Query time: 23 msec
  ;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP)
  ;; WHEN: Wed Nov 15 16:46:19 UTC 2023
  ;; MSG SIZE  rcvd: 46

  root@Jdnsmasq-checking:~# dig A netflix.com @127.0.0.1
  ;; communications error to 127.0.0.1#53: timed out
  ;; communications error to 127.0.0.1#53: connection refused
  ;; communications error to 127.0.0.1#53: connection refused

  #7. Check logs to verify segfault:
  # journalctl -u dnsmasq

  Apr 27 11:22:52 Jdnsmasq systemd[1]: Started dnsmasq - A lightweight DHCP and 
caching DNS server.
  Apr 27 11:22:53 Jdnsmasq dnsmasq[111585]: query[type=65] netflix.com from 
127.0.0.1
  Apr 27 11:22:53 Jdnsmasq dnsmasq[111585]: config error is REFUSED (EDE: 
network error)
  Apr 27 11:22:54 Jdnsmasq dnsmasq[111585]: query[type=65] netflix.com from 
127.0.0.1
  Apr 27 11:22:54 Jdnsmasq systemd[1]: dnsmasq.service: Main process exited, 
code=dumped, status=11/SEGV
  Apr 27 11:22:54 Jdnsmasq systemd[1]: dnsmasq.service: Failed with result 
'core-dump'.


  [ Where problems could occur ]

   This cherry picked commit from upstream incorporates a rewrite of the server 
priority list in the dnsmasq header file.
   Fortunately, that headers are not exported outside dnsmasq, so it cannot 
impact other third-party pieces of software.
   However, it can lend to think about the matching domain functionality that 
is being patched: could it be affect in
   some way to other types of server displaced on that list? Does anything 
change for the rest? In other words... Is the
   

[Touch-packages] [Bug 2024009] Re: [PATCH] systemd-resolved can't follow more than 8 CNAMEs

[Brian Murray]

Hello Vincent, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.23 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: systemd (Ubuntu Focal)
   Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  [PATCH] systemd-resolved can't follow more than 8 CNAMEs

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

Bug description:
  [Impact]

  Using systemd-resolved to resolve a hostname which has more than 8
  CNAME redirects will fail because of the hard-coded limit. While this
  case is somewhat rare, the original reporter demonstrated a real-world
  scenario where this happened (although that particular hostname seems
  to be fixed now).

  [Test Plan]

  This test plan uses a LXC container to test systemd-resolved on Focal.
  If LXD has not been configured on your system, start with:

  $ lxd init --auto

  Then, create a Focal container with:

  $ lxc launch ubuntu-daily:focal focal

  Install dnsmasq-base if needed:

  $ apt install dnsmasq-base

  Stop other DNS servers:

  $ systemctl stop systemd-resolved
  $ kill -9 $(pgrep dnsmasq)

  Now, on the host start a new DNS server that listens on lxdbr0, and
  sets up an A record, and many CNAME records which ultimately redirect
  to the A record:

  $ dnsmasq \
  --cname=test10.lan,test9.lan \
  --cname=test9.lan,test8.lan \
  --cname=test8.lan,test7.lan \
  --cname=test7.lan,test6.lan \
  --cname=test6.lan,test5.lan \
  --cname=test5.lan,test4.lan \
  --cname=test4.lan,test3.lan \
  --cname=test3.lan,test2.lan \
  --cname=test2.lan,test1.lan \
  --cname=test1.lan,test0.lan \
  -k -i lxdbr0 -z -I lo --host-record=test0.lan,$IP

  where $IP is any host on your network.

  Now, obtain a shell in the Focal container:

  $ lxc exec focal bash

  Attempt to resolve test10.lan:

  $ resolvectl query test10.lan
  test10.lan: resolve call failed: CNAME loop detected, or CNAME resolving 
disabled on 'test2.lan'

  On an affected system, the above error will be seen. On a patched
  system, the hostname should be resolved.

  [Where problems could occur]

  The patch simply increases the maximum CNAME redirects that are
  allowed from 8 to 16, so a reasonable limit is still imposed. If an
  application specifically relied on systemd-resolved's limit being at
  8, then that application would potentially see new behavior.

  [Original Description]

  On Ubuntu 20.04 (systemd v245.4-4ubuntu3.21), hostname resolution only
  follows 8 CNAME redirections maximum.

  So when using a service like Azure Virtual Desktop that has between 9
  and 12 redirections, name resolution fails.

  $ host client.wvd.microsoft.com
  Host client.wvd.microsoft.com not found: 2(SERVFAIL)
  $ resolvectl query client.wvd.microsoft.com
  client.wvd.microsoft.com: resolve call failed: CNAME loop detected, or CNAME 
resolving disabled on 'waws-prod-zrh-ff7172dd.sip.p.azurewebsites.windows.net'

  On the other hand it's working fine on Ubuntu 20.04 because CNAME loop
  limit has been raised from 8 to 16.

  $ host client.wvd.microsoft.com
  client.wvd.microsoft.com is an alias for 
client.privatelink-global.wvd.microsoft.com.
  client.privatelink-global.wvd.microsoft.com is an alias for 
client.privatelink.wvd.microsoft.com.
  client.privatelink.wvd.microsoft.com is an alias for rdweb.wvd.microsoft.com.
  rdweb.wvd.microsoft.com is an alias for 
rdweb.privatelink-global.wvd.microsoft.com.
  rdweb.privatelink-global.wvd.microsoft.com is an alias for 
rdweb.privatelink.wvd.microsoft.com.
  rdweb.privatelink.wvd.microsoft.com is an alias for 

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

[Brian Murray]

Hello Dan, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.23 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: systemd (Ubuntu Focal)
   Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  focal: backport kexec fallback patch

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

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

  [Impact]

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

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

  [Test Plan]

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

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

  4) `reboot`

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

  [Where problems could occur]

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

  [Other info]

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

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

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


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

[Touch-packages] [Bug 2029352] Re: systemd/ 245.4-4ubuntu3.22 ADT test failure with linux/5.4.0-156.173

[Brian Murray]

Hello Roxana, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.23 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: systemd (Ubuntu Focal)
   Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  systemd/ 245.4-4ubuntu3.22  ADT test failure with linux/5.4.0-156.173

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  The armhf autopkgtest fails for focal and ultimately leads to less
  test coverage because other packages now won't block on these
  failures, and may not notice new regressions.

  [Test Plan]

  The test-execute test within root-unittests should pass.

  [Where problems could occur]

  The patch only changes a service file in the test tree of systemd, so
  this is not a change that will be seen on real Ubuntu systems. Hence
  any further problems would be seen only in the test-execute test.

  [Original Description]

  This is a scripted bug report about ADT failures while running systemd tests 
for linux/5.4.0-156.173 on focal. Whether this is caused by the dep8 tests of 
the tested source or the kernel has yet to be determined.
  root-unittests fails.

  Testing failed on:
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20230727_150132_9cd77@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2029352/+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 1837227] Re: systemd mount units fail during boot, while file system is correctly mounted

[Brian Murray]

Hello Guillaume, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.23 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: systemd (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  systemd mount units fail during boot, while file system is correctly
  mounted

Status in systemd:
  New
Status in Ubuntu Pro:
  In Progress
Status in Ubuntu Pro 18.04 series:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in systemd source package in Bionic:
  Won't Fix
Status in linux source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Released
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  systemd mount units fail during boot, and the system boots into emergency mode

  [Test Plan]
  This issue seems to happen randomly, and doesn't seem related to a specific 
mount unit.

  We've used a test script with good results during investigation to
  reproduce similar mount failures in a running system, and have seen a
  strong correlation between the script failures and the boot time mount
  failures.

  The attached 'rep-tmpfs.sh' script should be used to validate that
  mount points are working correctly under stress. One can run through
  the different variants as below:

  # ./rep-tmpfs.sh --variant-0
  # ./rep-tmpfs.sh --variant-1
  # ./rep-tmpfs.sh --variant-2
  # ./rep-tmpfs.sh --variant-3
  # ./rep-tmpfs.sh --variant-4

  All of these should run successfully without any reported errors.

  [Where problems could occur]
  The patches change the way systemd tracks and handles mount points in 
general, so potential regressions could affect other mount units. We should 
keep an eye out for any issues with mounting file systems, as well as rapid 
mount/unmount operations. Successful test runs with the reproducer script 
should increase reliability in having no new regressions.

  [Other Info]
  This has been tackled upstream with several attempts, which have resulted in 
the final patch from 2022:
    01400460ae16 core/mount: adjust deserialized state based on 
/proc/self/mountinfo

  For Bionic, systemd requires several dependency patches as below:
    6a1d4d9fa6b9 core: properly reset all ExecStatus structures when entering a 
new unit cycle
    7eba1463dedc mount: flush out cycle state on DEAD→MOUNTED only, not the 
other way round
    350804867dbc mount: rescan /proc/self/mountinfo before processing waitid() 
results
    1d086a6e5972 mount: mark an existing "mounting" unit from 
/proc/self/mountinfo as "just_mounted"

  Additionally, the kernel also requires the following patches:
    28ca0d6d39ab list: introduce list_for_each_continue()
    9f6c61f96f2d proc/mounts: add cursor

  [Original Description]
  In Ubuntu 18.04 at least, we sometimes get a random server in emergency mode 
with a failed mount unit (ext4 file system), while the corresponding file 
system is in fact correctly mounted. It happens roughly once every 1000 reboots.

  It seems to be related with this bug :
  https://github.com/systemd/systemd/issues/10872

  Is it possible to apply the fix
  
(https://github.com/systemd/systemd/commit/350804867dbcc9b7ccabae1187d730d37e2d8a21)
  in Ubuntu 18.04 ?

  Thanks in advance.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 2037281] Re: Shutdown when triggering daemon-reload early in boot

[Brian Murray]

Hello Valentin, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.23 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: systemd (Ubuntu Focal)
   Status: New => Fix Committed

** Tags added: verification-needed-focal

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

Title:
  Shutdown when triggering daemon-reload early in boot

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

Bug description:
  In Ubuntu Core 20, and Ubuntu Core 22, we are encountering an issue
  where if a service, started earlier than devices are processed by
  udev, does `systemctl daemon-reload`, the system shuts down. This is
  due to devices for mounted filesystem temporarily taken dead, which
  pulls most units down.

  This was fixed by upstream in
  https://github.com/systemd/systemd/pull/23218.

  But this was not backported to the versions used by Ubuntu packages
  for focal and jammy. The needed commit from that PR is the one with
  message `core/device: ignore DEVICE_FOUND_UDEV bit on switching root`.

  This patch applies to 245.4-4ubuntu3.22 (focal) without rebasing
  needed. And I suppose it does also for jammy.

  I have manually tested the fix with Ubuntu Core 20, and this fixes our
  issue.

  We would like this patch to be backported to focal-updates and jammy-
  updates.

  Thank you in advance.

  [ Impact ]

  If a user adds a service that calls `systemctl daemon-reload`, and if
  this service is started before systemd-udevd. And if the initrd is
  systemd (the case of Ubuntu Core), then most service will be stopped
  or cancel, and the machine will mostly shutdown everything and hang.

  The fix has been backported down to 250 upstream. It is already on
  kinetic and later.

  The fix only affects systems where systemd is used in initrd.

  [ Test Plan ]

  On Ubuntu Core 20 (with Core 22 kernel) or on Ubuntu Core 22. Or on
  any system that uses systemd in initrd.

  Add a systemd service that calls `systemctl daemon-reload`.
  The service should have `DefaultDependencies=no` in order to start as soon as 
possible and be enabled.

  Restart the machine.

  If fix is not applied, after the service is started, most of units
  with be shutdown, and the system will be unusable.

  [ Where problems could occur ]

  This should affect systems with systemd in initrd.

  There are risks on systems that have an udev rule in initrd not
  present in the main system.

  There are risks on systems that use db_persist in initrd where the
  device can potentially get dead state. Though this does not seem to
  happen on Ubuntu Core 22, even though we use db_persist for dev mapper
  devices. Regression is upstream bug #23429. Commits named
  "core/device: device_coldplug(): don't set DEVICE_DEAD" and
  "core/device: do not downgrade device state if it is already
  enumerated" could be applied as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2037281/+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 2035122] Re: Under ubuntu core/core-desktop, /etc/default/locale is not modifiable

[Brian Murray]

While the test plan now has information about changing the locale there
is nothing which covers the keyboard changes. I'm going to accept this
today but please update the test case to include testing the keyboard
changes and ensure that is also tested.

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

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

Title:
  Under ubuntu core/core-desktop, /etc/default/locale is not modifiable

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Jammy:
  Fix Committed
Status in systemd source package in Lunar:
  Won't Fix
Status in systemd source package in Mantic:
  Won't Fix

Bug description:
  [Impact]

  When working with ubuntu core or ubuntu core desktop, neither
  */etc/default/locale* nor */etc/default/keyboard* are modifiable, so
  it's not possible to set the global keyboard or the global language.
  This is required to allow to set the GDM language, and the default one
  during installation.

  The first half of the solution is to create the folder
  */etc/writable/default*, and make soft-links from
  */etc/default/locale* to */etc/writable/default/locale* and from
  */etc/default/keyboard* to */etc/writable/default/keyboard*, just like
  it is already being done with */etc/hostname*, */etc/issue*,
  */etc/localtime*, */etc/motd* and , */etc/timezone*.

  This solution, unfortunately, isn't complete. Although any application
  that just reads the files will work, not all of the applications that
  write to them will; specifically the systemd utilities that set the
  contents for those files, because they don't open the file directly;
  instead, they create first the new file in the same folder than the
  old one, fill its contents, and only then delete the old one and
  rename the new one. To solve this, systemd in Ubuntu already has
  several patches that detect if a file is a soft-link, in which case it
  replaces the old path with the destination one.

  Currently I have in place a patch for Ubuntu Core Desktop that
  implements both changes for both */etc/default/locale* and
  */etc/default/keyboard*.

  [Test plan]

  Using *sudo localectl set-lang LANG="xx_YY.UTF-8"* in an Ubuntu Core
  or Ubuntu Core Desktop admin terminal must change the locale to the
  specified one, which can be checked by reading the
  */etc/default/locale* file. Also, *localectl* must return the new
  locale.

  [Where problems could occur]

  In general, applications just read the content of the file and use the
  DBus interface to set the locale, so only those applications that
  modify by themselves the */etc/default/keyboard* and/or
  */etc/default/locale* would present a problem, in which case they
  would require specific patches. Anyway, those applications neither
  would work with the current state (with those files in a read-only
  filesystem).

  [Other info]

  For Noble, this will be addressed when we merge systemd v255 from
  Debian. This is only needed on core, so we don't need to fix for
  Mantic or Lunar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035122/+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 2037281] Re: Shutdown when triggering daemon-reload early in boot

[Brian Murray]

Hello Valentin, 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.12 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

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

Title:
  Shutdown when triggering daemon-reload early in boot

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

Bug description:
  In Ubuntu Core 20, and Ubuntu Core 22, we are encountering an issue
  where if a service, started earlier than devices are processed by
  udev, does `systemctl daemon-reload`, the system shuts down. This is
  due to devices for mounted filesystem temporarily taken dead, which
  pulls most units down.

  This was fixed by upstream in
  https://github.com/systemd/systemd/pull/23218.

  But this was not backported to the versions used by Ubuntu packages
  for focal and jammy. The needed commit from that PR is the one with
  message `core/device: ignore DEVICE_FOUND_UDEV bit on switching root`.

  This patch applies to 245.4-4ubuntu3.22 (focal) without rebasing
  needed. And I suppose it does also for jammy.

  I have manually tested the fix with Ubuntu Core 20, and this fixes our
  issue.

  We would like this patch to be backported to focal-updates and jammy-
  updates.

  Thank you in advance.

  [ Impact ]

  If a user adds a service that calls `systemctl daemon-reload`, and if
  this service is started before systemd-udevd. And if the initrd is
  systemd (the case of Ubuntu Core), then most service will be stopped
  or cancel, and the machine will mostly shutdown everything and hang.

  The fix has been backported down to 250 upstream. It is already on
  kinetic and later.

  The fix only affects systems where systemd is used in initrd.

  [ Test Plan ]

  On Ubuntu Core 20 (with Core 22 kernel) or on Ubuntu Core 22. Or on
  any system that uses systemd in initrd.

  Add a systemd service that calls `systemctl daemon-reload`.
  The service should have `DefaultDependencies=no` in order to start as soon as 
possible and be enabled.

  Restart the machine.

  If fix is not applied, after the service is started, most of units
  with be shutdown, and the system will be unusable.

  [ Where problems could occur ]

  This should affect systems with systemd in initrd.

  There are risks on systems that have an udev rule in initrd not
  present in the main system.

  There are risks on systems that use db_persist in initrd where the
  device can potentially get dead state. Though this does not seem to
  happen on Ubuntu Core 22, even though we use db_persist for dev mapper
  devices. Regression is upstream bug #23429. Commits named
  "core/device: device_coldplug(): don't set DEVICE_DEAD" and
  "core/device: do not downgrade device state if it is already
  enumerated" could be applied as well.

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

[Brian Murray]

Hello Sergio, 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.12 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/2035122

Title:
  Under ubuntu core/core-desktop, /etc/default/locale is not modifiable

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Jammy:
  Fix Committed
Status in systemd source package in Lunar:
  Won't Fix
Status in systemd source package in Mantic:
  Won't Fix

Bug description:
  [Impact]

  When working with ubuntu core or ubuntu core desktop, neither
  */etc/default/locale* nor */etc/default/keyboard* are modifiable, so
  it's not possible to set the global keyboard or the global language.
  This is required to allow to set the GDM language, and the default one
  during installation.

  The first half of the solution is to create the folder
  */etc/writable/default*, and make soft-links from
  */etc/default/locale* to */etc/writable/default/locale* and from
  */etc/default/keyboard* to */etc/writable/default/keyboard*, just like
  it is already being done with */etc/hostname*, */etc/issue*,
  */etc/localtime*, */etc/motd* and , */etc/timezone*.

  This solution, unfortunately, isn't complete. Although any application
  that just reads the files will work, not all of the applications that
  write to them will; specifically the systemd utilities that set the
  contents for those files, because they don't open the file directly;
  instead, they create first the new file in the same folder than the
  old one, fill its contents, and only then delete the old one and
  rename the new one. To solve this, systemd in Ubuntu already has
  several patches that detect if a file is a soft-link, in which case it
  replaces the old path with the destination one.

  Currently I have in place a patch for Ubuntu Core Desktop that
  implements both changes for both */etc/default/locale* and
  */etc/default/keyboard*.

  [Test plan]

  Using *sudo localectl set-lang LANG="xx_YY.UTF-8"* in an Ubuntu Core
  or Ubuntu Core Desktop admin terminal must change the locale to the
  specified one, which can be checked by reading the
  */etc/default/locale* file. Also, *localectl* must return the new
  locale.

  [Where problems could occur]

  In general, applications just read the content of the file and use the
  DBus interface to set the locale, so only those applications that
  modify by themselves the */etc/default/keyboard* and/or
  */etc/default/locale* would present a problem, in which case they
  would require specific patches. Anyway, those applications neither
  would work with the current state (with those files in a read-only
  filesystem).

  [Other info]

  For Noble, this will be addressed when we merge systemd v255 from
  Debian. This is only needed on core, so we don't need to fix for
  Mantic or Lunar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035122/+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 2040273] Update Released

[Brian Murray]

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

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

Title:
  [SRU] Enable support for Caracal Cloud Archive

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Jammy:
  Fix Committed
Status in software-properties source package in Noble:
  Fix Released

Bug description:
  Please add support for:

 cloud-archive:caracal
 cloud-archive:caracal-proposed

  This will also need to be SRU'd back to jammy.

  [Impact]
  End users have to manually enable the caracal cloud archive pockets.

  [Test case]
  sudo add-apt-repository cloud-archive:caracal
  sudo add-apt-repository cloud-archive:caracal-proposed

  [Regression potential]
  Limited - just a data item addition

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2040273/+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 1881504] Re: cross-testing essential packages fails

[Brian Murray]

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

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

Title:
  cross-testing essential packages fails

Status in apt package in Ubuntu:
  Won't Fix
Status in autopkgtest package in Ubuntu:
  Confirmed
Status in gzip package in Ubuntu:
  New

Bug description:
  Testing gzip on i386 fails at replacing gzip(:amd64) with gzip:i386.

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-
  groovy/groovy/i386/g/gzip/20200528_195150_89f08@/log.gz

  ...
  autopkgtest [19:51:38]: testing package gzip version 1.10-2ubuntu1
  autopkgtest [19:51:38]: build not needed
  autopkgtest [19:51:38]: test simple-gzip: preparing testbed
  Note, using file '/tmp/autopkgtest.1PbIQv/1-autopkgtest-satdep.dsc' to get 
the build dependencies
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Starting pkgProblemResolver with broken count: 0
  Starting 2 pkgProblemResolver with broken count: 0
  Done
  The following packages will be REMOVED:
gzip
  The following NEW packages will be installed:
build-essential cpp cpp-9 g++ g++-9 gcc gcc-10-base:i386 gcc-9 gcc-9-base
gzip:i386 libasan5 libatomic1 libc-dev-bin libc6:i386 libc6-dev libcc1-0
libcrypt-dev libcrypt1:i386 libgcc-9-dev libgcc-s1:i386 libgomp1 libisl22
libitm1 liblsan0 libmpc3 libquadmath0 libstdc++-9-dev libtsan0 libubsan1
linux-libc-dev
  WARNING: The following essential packages will be removed.
  This should NOT be done unless you know exactly what you are doing!
gzip
  0 upgraded, 30 newly installed, 1 to remove and 0 not upgraded.
  E: Essential packages were removed and -y was used without 
--allow-remove-essential.
  E: Failed to process build dependencies
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1881504/+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 2039328] Update Released

[Brian Murray]

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

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

Title:
  Update ubuntu-meta with promotions done between last ubuntu-meta build
  & release

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-meta source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

   * ubuntu-seeds were changed since last meta update
   * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes 
done before release

  [ Test Plan ]

   * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to
  mantic install newly recommended packages.

  [ Where problems could occur ]

   * This is automatically generated change based on ubuntu-seeds commit
  [1].

   * Theoretically, regressions would occur if new desktop-minimal-recommends
     dependencies on arm64 (flash-kernel, protection-domain-mapper, qrtr-tools):
     - have issues on install during release-upgrade;
     - have issues on regular system usage (after installed).

  [ Other Info ]

   * ubuntu-meta was not uploaded during final freeze, to prevent
  rebuilding all images as changes affect arm64 only, which is a brand
  new release image

   * protection-domain-mapper [2] and qrtr [3] moved from universe to main in 
Mantic.
   * flash-kernel is/was already in main.

  [1] 
https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=afe820cd49514896e96d02303298ed873d8d7f8a
  [2] 
https://launchpad.net/ubuntu/+source/protection-domain-mapper/1.0-4ubuntu2/+publishinghistory
  [3] https://launchpad.net/ubuntu/+source/qrtr/1.0-2ubuntu1/+publishinghistory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2039328/+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 2028082] Update Released

[Brian Murray]

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

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

Title:
  Update glib to 2.76.4

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Lunar:
  Fix Released

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 2.76 series

  The current release in Ubuntu 23.04 is 2.76.1

  https://gitlab.gnome.org/GNOME/glib/-/blob/2.76.4/NEWS

  Test Case 1
  ---
  glib has an extensive test suite.

  Failing tests will fail the build.
  This update will also trigger a lot of autopkgtests.

  Ensure that there aren't autopkgtest regressions triggered by this
  update and that the builds complete successfully

  Test Case 2
  ---
  Pretty much all parts of GNOME use GLib, so test anything in the desktop that 
you can. If you reboot the machine and can get to the desktop, that's already 
tested GLib extensively. But also run applications like the terminal, the file 
browser and epiphany-browser

  What Could Go Wrong
  ---
  This update contains fixes in multiple places so multiple apps could be 
affected. The consequences of a broken GLib can range from some functions 
returning bad results sometimes, which have minimal runtime implications, up to 
the system simply crashing all the time.

  Other Info
  --
  The upstream gnome-remote-desktop maintainer requested that we do this update 
to fix a frequent gnome-remote-desktop crash that shows on errors.ubuntu.com

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2028082/+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 1831747] Re: fixrtc hook requires e2fsprogs package, but that is not a dependency

[Brian Murray]

** Tags added: rls-nn-incoming

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

Title:
  fixrtc hook requires e2fsprogs package, but that is not a dependency

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Package "initramfs-tools-core" provides "/usr/share/initramfs-
  tools/hooks/fixrtc" which runs during the update or regeneration of
  the initramfs and requires the file "/sbin/dumpe2fs" (available from
  "e2fsprogs") to be present, otherwise it fails and aborts the whole
  process, leading e.g. to an inconsistent package system.

  The problem/cause seems to be that "initramfs-tools-core" package has
  no direct or indirect hard dependency on "e2fsprogs".

  I believe either the package dependency should be added, or the fixrtc
  hook script should be rewritten so that it just outputs a warning
  instead of aborting with a failure if missing "dumpe2fs" is not a
  critical problem.

  This issue seems to affect at least Ubuntu 16.04 and 18.04. It has
  been brought to my attention at https://askubuntu.com/q/1148791/367990

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1831747/+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 2032851] Update Released

[Brian Murray]

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

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

Title:
  package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new
  apparmor package pre-installation script subprocess returned error
  exit status 1

Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

   * During an apparmor package upgrade, the cache files were
 deleted, but there could also be directories under
 /etc/apparmor.d/cache/ which the pre installation scripts did
 not account for. The upgrade would then fail with the
 following error message because it would not be able to remove
 the directories:

   package:apparmor:2.12-4ubuntu5.3
   Preparing to unpack .../16-apparmor_2.13.3-7ubuntu5.2_amd64.deb ...
   rm: cannot remove '/etc/apparmor.d/cache/bf9d6da9.0': Is a directory
   dpkg: error processing archive 
/tmp/apt-dpkg-install-InP0fz/16-apparmor_2.13.3-7ubuntu5.2_amd64.deb (--unpack):
new apparmor package pre-installation script subprocess returned error exit 
status 1
  ErrorMessage: new apparmor package pre-installation script subprocess 
returned error exit status 1

  [ Test Plan ]

   * On a bionic machine, create a directory under
  /etc/apparmor.d/cache

  sudo mkdir /etc/apparmor.d/cache/test

   * To simulate a system upgrade to focal, you can run the following
  steps

  1. Add the focal archive

  sudo bash -c "cat 

[Touch-packages] [Bug 1981103] Update Released

[Brian Murray]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


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

[Touch-packages] [Bug 1907878] Update Released

[Brian Murray]

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

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

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

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

Bug description:
  Syslog error:

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

  I think it's because of this line:

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

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

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

  SRU for Jammy:

  [ Impact ]

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

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

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

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

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


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

[Touch-packages] [Bug 2040113] Update Released

[Brian Murray]

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

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

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

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

Bug description:
  [ Impact ]

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

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

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

  [ Test Plan ]

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

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

  [ Where problems could occur ]

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

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

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


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

[Touch-packages] [Bug 2042710] Update Released

[Brian Murray]

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

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

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

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

Bug description:
  [ Impact ]

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

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

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

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

  spi_pxa2xx_platform
  intel_lpss_pci

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

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

  [ Test Plan ]

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

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

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

  [ Where problems could occur ]

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

  [ Remaining original report ]

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

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

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

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

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


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

[Touch-packages] [Bug 2007050] Update Released

[Brian Murray]

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

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

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

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

Bug description:
  [ Impact ]

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

  The keyboard works fine on the fully booted system.

  Secure boot is disabled on this system.

  [ Test Plan ]

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

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

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

  [ Where problems could occur ]

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

  [ Apport report ]

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

[Touch-packages] [Bug 2042397] Re: /usr/sbin/cupsd:corrupted double-linked list

[Brian Murray]

There are a few thousand crashes in the Error Tracker about this and I
encountered it a couple of times while at an event where I guess there
was a printer on the network.

** Tags added: rls-mm-incoming

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

Title:
  /usr/sbin/cupsd:corrupted double-linked list

Status in cups package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
cups.  This problem was most recently seen with package version 2.4.6-0ubuntu3, 
the problem page at 
https://errors.ubuntu.com/problem/a8a50d83f4b4d9621dd706ee4b339b096aa86a70 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2042397/+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 2041396] Re: gdb 12.1 generates SIGILL on armhf

[Brian Murray]

** Also affects: gdb (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: gdb (Ubuntu Jammy)
Milestone: None => jammy-updates

** Changed in: gdb (Ubuntu)
Milestone: jammy-updates => None

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

Title:
  gdb 12.1 generates SIGILL on armhf

Status in gdb:
  Fix Released
Status in gdb package in Ubuntu:
  New
Status in gdb source package in Jammy:
  New

Bug description:
  [ Impact ]

   * GDB 12.1 introduced a regression where it will break program execution 
when the program contains mixed ARM code and THUMB code.
   * Upstream stated they tested the changes on Ubuntu 20.04 and it went okay.

  [ Test Plan ]

  Considering the following C program:

  ```
  __attribute__((target("arm"), noinline))
  int thumb_func() {
    return 42;
  }

  __attribute__((target("thumb")))
  int main() { return thumb_func(); }
  ```

  If you build it using `gcc repro.c -ggdb3 -Og -o repro` and run the
  GDB using the following commands ...

  ```
  b 3
  r
  c
  ```

  (you can save the contents above to a file and run GDB using `gdb -x
  script ./repro`)

  ... you will notice GDB broke the program and threw SIGILL.
  If you run the program without GDB, the program exits normally.

  [ Where problems could occur ]

   * GDB is a complex software. As the patch suggests, it may break other use 
cases (like single-stepping) entirely.
   * Since this is an ARM-only patch, it's unlikely to affect other CPU 
architectures. However, it is possible that this fix may break ARM64 execution.

  [ Other Info ]
   
   * This bug has been fixed in GDB 13, but the fix was never backported to GDB 
12. You can find the upstream bug in the remote bug watch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/2041396/+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 2040153] Re: Network Manager will not remove Netplan YAMLs when connections are deleted

[Brian Murray]

Hello Danilo, or anyone else affected,

Accepted network-manager into mantic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.44.2-1ubuntu1.2 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-
mantic to verification-done-mantic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-mantic. 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: network-manager (Ubuntu Mantic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-mantic

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

Title:
  Network Manager will not remove Netplan YAMLs when connections are
  deleted

Status in netplan.io package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  In Progress
Status in netplan.io source package in Mantic:
  Invalid
Status in network-manager source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

  Desktop users, or any users with YAML files in /usr/lib/netplan, can't delete
  Network Manager connections persistently. That means that, when the 
connection is
  deliberately deleted by the user, it will re-appear when the system is 
rebooted or
  netplan apply is executed.

  This is happening because the systemd service unit is setting the property 
"ProtectSystem"
  to true. Because of that, /usr is being presented to the Network Manager 
daemon as read-only.
  When connections are deleted, libnetplan will try to open its YAML files with 
writing permissions
  and will fail for files from /usr/lib/netplan. Even if the user hasn't added 
any files there manually,
  the file /usr/lib/netplan/00-network-manager-all.yaml will be installed by 
the package ubuntu-settings.

  This issue is fixed by allow-listing /usr/lib/netplan with 
ReadWritePaths=/usr/lib/netplan in systemd
  so the Network Manager's daemon will be able to write to that directory.

  This upload also improves the autopkgtests related to Netplan. Network 
Manager will be
  started by systemd, which ensures we are testing in the same environment 
conditions
  used by a desktop installation. It also adds a few more instances of 
connections deletions so
  we can test a bit more that YAML files are being removed. It also adds all 
the dependencies
  required by the test script (which sadly was causing the nm_netplan.py tests 
to be skipped).

  [ Test Plan ]

  Launch a new Mantic VM:

  $ lxc launch ubuntu:mantic --vm

  Install network-manager and ubuntu-settings:

  # apt install network-manager ubuntu-settings

  Run Netplan

  # netplan apply

  Create a dummy connection via nmcli:

  # nmcli con add type dummy connection.interface-name dummy0

  Check a new YAML will be created in /etc/netplan

  Delete the connection with nmcli

  # nmcli con del dummy-dummy0

  Check the YAML WAS NOT removed from /etc/netplan

  You will see the error below in the NetworkManager's journal

  netplan_delete_connection: Cannot write output state: Read-only file
  system

  Add the PPA containing the fix and run the same test described above

  # add-apt-repository ppa:danilogondolfo/network-manager
  # apt update
  # apt upgrade

  Check that the YAML will be created when the connection is added and
  deleted and the connection is removed.

  [ Where problems could occur ]

  As the only change is a relaxation of the restrictions applied by systemd on 
the environment where Network Manager
  runs, we are not expecting any regression.

  As for the changes in the autopkgtest related to Netplan, they are
  passing on all architectures.

  Autopkgtests

  amd64 - 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/amd64/n/network-manager/20231023_175203_b2798@/log.gz
  ppc64 - 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/ppc64el/n/network-manager/20231023_182332_f0497@/log.gz
  s390x - 

[Touch-packages] [Bug 2038650] Update Released

[Brian Murray]

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

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

Title:
  crash reports not sent to the Error Tracker

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Lunar:
  Fix Released
Status in apport source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

  Crash reports aren't sent in when going through the UI, unless the
  user looks at the crash details.

  [ Test Plan ]

  0) Make sure that error reporting is set to manual in the system settings (in 
Privacy screen)
  1) Launch xeyes
  2) pkill -11 xeyes
  3) Click send in the apport dialog. DO NOT look at the details of the report.
  4) ls -lh /var/crash/*xeyes*

  There should be 3 files:

  -rw-r- 1 bdmurray whoopsie  3370567 Oct  6 11:53 _usr_bin_xeyes.1000.crash
  -rw-rw-r-- 1 bdmurray bdmurray0 Oct  6 11:53 
_usr_bin_xeyes.1000.upload
  -rw--- 1 whoopsie whoopsie   37 Oct  6 11:53 
_usr_bin_xeyes.1000.uploaded

  [ Where problems could occur ]

  If the patch is wrong, we actually see similar bugs for other UI
  paths, e.g. ticking the "Remember this" box, etc. I tried to cover
  them during manual testing but I might have missed some.

  [ Other Info ]
   
  If possible I'd like for us not to wait too long for this to mature in 
-proposed, as this would affect crashes during the upgrade.

  [ Original report ]
  From what I can tell when I click the send button to send a crash report to 
the Error Tracker the crash doesn't actually get sent. My testing process 
follows:

  1) Launch xeyes
  2) pkill -11 xeyes
  3) Click send in the apport dialog
  4) ls -lh /var/crash

  I would expect there to be three files in /var/crash:

  -rw-r- 1 bdmurray whoopsie  3370567 Oct  6 11:53 _usr_bin_xeyes.1000.crash
  -rw-rw-r-- 1 bdmurray bdmurray0 Oct  6 11:53 
_usr_bin_xeyes.1000.upload
  -rw--- 1 whoopsie whoopsie   37 Oct  6 11:53 
_usr_bin_xeyes.1000.uploaded

  However, after step #4 I'm only seeing the .crash file and not a
  .upload or .uploaded.  I was able to get the .upload and .uploaded
  files created if I chose to "View Report" and then click "Send".

  It's worth noting though that I did notice the size of the .crash file
  increase after clicking "Send" so some post-processing was done.

  ProblemType: BugDistroRelease: Ubuntu 23.10
  Package: apport 2.27.0-0ubuntu4
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports: 640:1000:123:20944237:2023-10-06 12:10:47.809248208 
+0100:2023-10-06 12:11:23.340030509 +0100:/var/crash/_usr_bin_mpv.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  6 12:12:46 2023
  InstallationDate: Installed on 2022-01-07 (637 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: allSourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2038650/+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 2039503] Update Released

[Brian Murray]

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

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

Title:
  package network-manager 1.44.2-1ubuntu1 failed to install/upgrade:
  installed network-manager package post-installation script subprocess
  returned error exit status 10

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

   * A failure to query nmcli will fail the network-manager.postinst
  maintainer script (using "set -e")

   * This will make the package installation/upgrade fail

   * The fix catches the error on "ORIG_NAME=$(nmcli --get-values
  connection.id con show "$UUID")" and skips the corresponding keyfile
  with a warning message

  [ Test Plan ]

  $ sudo vim /etc/NetworkManager/system-connections/UPTOWN.guests # bad file
  [connection]
  id=UPTOWN.guests
  uuid=491fa5c8-68ef-4140-8679-dca422f5c262
  type=wifi

  [wifi]
  ssid=UPTOWN.guests
  mode=infrastructure
  mac-address=E0:9D:31:09:84:54

  [ipv6]
  method=auto

  [ipv4]
  method=auto

  $ sudo vim /etc/NetworkManager/system-connections/aaaUPTOWN # good file
  [connection]
  id=aaaUPTOWN
  uuid=491fa5c8-68ef---dca422f5c262
  type=wifi

  [wifi]
  ssid=aaaUPTOWN
  mode=infrastructure
  mac-address=E0:9D:31:09:84:54

  [ipv6]
  method=auto

  [ipv4]
  method=auto

  $ sudo chmod 600 /etc/NetworkManager/system-connections/*UPTOWN*
  $ sudo nmcli con reload
  $ ls -la /etc/NetworkManager/system-connections/
  total 32
  drwxr-xr-x 2 root root 12288 Oct 17 17:51 ./
  drwxr-xr-x 7 root root 12288 Oct 17 17:46 ../
  -rw--- 1 root root   199 Oct 17 17:05 UPTOWN.guests
  -rw--- 1 root root   191 Oct 17 17:46 aaaUPTOWN

  # Install network-manager from proposed
  $ apt update && apt install -t mantic-proposed network-manager # version 
1.44.2-1ubuntu1.1

  # Verify you don't see an error like this, breaking the pkg install
  Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile.
  dpkg: error processing package network-manager (--configure):
   installed network-manager package post-installation script subprocess 
returned error exit status 10

  # Verify you see a migration log like this and the package installation is 
successful:
  Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile.
  SKIP: UPTOWN.guests (491fa5c8-68ef-4140-8679-dca422f5c262) unknown to 
NetworkManager.
  Migrating aaaUPTOWN (491fa5c8-68ef---dca422f5c262) to /etc/netplan
  $ echo $?
  0

  # Verify the good profile got migrated, while the bad one remains:
  $ sudo grep -RH UPTOWN /etc/netplan/
  /etc/netplan/90-NM-491fa5c8-68ef---dca422f5c262.yaml:
"aaaUPTOWN":
  /etc/netplan/90-NM-491fa5c8-68ef---dca422f5c262.yaml:
name: "aaaUPTOWN"
  /etc/netplan/90-NM-491fa5c8-68ef---dca422f5c262.yaml:name: 
"aaaUPTOWN"
  $ ls -la /etc/NetworkManager/system-connections/
  insgesamt 28
  drwxr-xr-x 2 root root 12288 Okt 17 18:03 .
  drwxr-xr-x 7 root root 12288 Okt 17 17:46 ..
  -rw--- 1 root root   199 Okt 17 17:05 UPTOWN.guests

  [ Where problems could occur ]

   * This is touching NetworkManager's maintainer script
   * Breaking it could lead to a broken/unconfigured NetworkManager package
   * This could render a machine's networking unusable
   * It could break distribution upgrades on package install/configure failure

  [ Other Info ]

   * Linting was used to validate the maintainer script:
     shellcheck --shell=sh debian/network-manager.postinst

  === original bug description ===

  lunar to mantic upgrade, exciting to see output from network-manager
  postinst migrating connections to /etc/netplan one by one.  But then:

  Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile.
  dpkg: error processing package network-manager (--configure):
   installed network-manager package post-installation script subprocess 
returned error exit status 10

  That UUID appears in a file /etc/NetworkManager/system-
  connections/UPTOWN.guests that hasn't been touched since 2015.

  Contents of the file were:

  [connection]
  id=UPTOWN.guests
  uuid=491fa5c8-68ef-4140-8679-dca422f5c262
  type=wifi

  [wifi]
  ssid=UPTOWN.guests
  mode=infrastructure
  mac-address=E0:9D:31:09:84:54

  [ipv6]
  method=auto

  [ipv4]
  method=auto

  I've removed it from disk and the migration continued to 

[Touch-packages] [Bug 2039252] Re: [needs-packaging] The packages ntp and ntpsec are not equivalent

[Brian Murray]

*** This is an automated message ***

This bug is tagged needs-packaging which identifies it as a request for
a new package in Ubuntu.  As a part of the managing needs-packaging bug
reports specification,
https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs-
packaging bug reports have Wishlist importance.  Subsequently, I'm
setting this bug's status to Wishlist.

** Summary changed:

- The packages ntp and ntpsec are not equivalent
+ [needs-packaging] The packages ntp and ntpsec are not equivalent

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

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

Title:
  [needs-packaging] The packages ntp and ntpsec are not equivalent

Status in ntp package in Ubuntu:
  Confirmed
Status in ntp package in Debian:
  Confirmed

Bug description:
  I recently did an install of Ubuntu 23.04 and then configured ntp as I have 
been doing so for more than 8 years.
  With previous versions of Debian and Ubuntu using the real ntp package, the 
details at https://wiki.ubuntu.com/JonathanFerguson/NTP?action=recall=38 
created the desired results.
  I updated the details at https://wiki.ubuntu.com/JonathanFerguson/NTP with 
the new location of ntp.conf, after restarting I noticed that the resultant 
output was missing requisite details.

  
  Compare the following and the lack of ".MCST." and ".ACST.":

  Original ntp on Apollo-Lake-N3150
  jonathan@Apollo-Lake-N3450:~$ lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04
  jonathan@Apollo-Lake-N3450:~$ ntpq -p
   remote   refid  st t when poll reach   delay   offset  jitter
  ==
   0.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   1.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   2.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   3.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   ntp.ubuntu.com  .POOL.  16 p-   6400.000   +0.000   0.000
   ntp.mcast.net   .MCST.  16 M-   6400.000   +0.000   0.000
   ff0e::101   .MCST.  16 M-   6400.000   +0.000   0.000
   ntp.mcast.net   .ACST.  16 a-   6400.000   +0.000   0.000
   ff0e::101   .ACST.  16 a-   6400.000   +0.000   0.000
  *time.cloudflare 10.242.8.77  3 u  469 1024  367  234.691   -0.929  67.380
  +2001-44b8-2100- 42.3.115.79  2 u  581 1024  377  487.209  +55.669  57.154
  +2001-44b8-2100- 4.179.66.17  3 u  215 1024  377  489.637  +57.002  35.399
  jonathan@Apollo-Lake-N3450:~$

  NTPsec on Braswell-N3150
  jonathan@Braswell-N3150:~$ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 23.04
  Release:23.04
  jonathan@Braswell-N3150:~$ ntpq -p
   remote   refid  st t when poll reach 
  delay   offset   jitter
  
===
   0.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
   1.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
   2.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
   3.ubuntu.pool.ntp.org   .POOL.  16 p-   640  
 0.   0.   0.0002
  +prod-ntp-5.ntp1.ps5.canonical.com   37.15.221.1892 u  141 1024  367 
383.4932 -19.6895  35.0534
  *time.tfmcloud.au203.35.83.2422 u  325 1024  367 
325.9317  -0.1496  43.0522
  +any.time.nl 133.243.238.243  2 u  158 1024  373 
300.7941 -20.8962 136.1422
  +ntp2.its.waikato.ac.nz  .GPS.1 u  363 1024  377 
356.5361 -18.2740 140.5984
  +2001-44b8-2100-3f00---007b-0004 42.3.115.79  2 u  214 1024  367 
490.3898  28.3416   2.7728
  +tic.ntp.telstra.net 203.35.83.2422 u   13 1024  367 
566.0744 -14.1332   6.0377
  +863xqmprtfqv69pv7nwc.ip6.superloop.au   192.168.1.1  2 u   79 1024  367 
330.2658 -14.3483  16.2172
  +gps-ads.10mrlp.juneks.com.au.PPS.1 u  271 1024  367 
443.4812 -71.8020  44.6332
  +x.ns.gin.ntt.net129.250.35.222   2 u   57 1024  367  
22.4974  41.3055   6.0639
  jonathan@Braswell-N3150:~$

  
  This behaviour will affect the following:
  Ubuntu 22.10, 23.04 and 23.10
  Debian 12, 13 and 14

  NTPsec have documented their reasoning for lacking support.
  https://docs.ntpsec.org/latest/discover.html
  https://docs.ntpsec.org/latest/ntpsec.html
  https://docs.ntpsec.org/latest/assoc.html#broad
  

[Touch-packages] [Bug 2034986] Update Released

[Brian Murray]

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

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

Title:
  some text became unreadable during a distribution upgrade

Status in Cinnamon:
  New
Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress
Status in ubuntu-release-upgrader source package in Jammy:
  Fix Committed
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Released
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  In Progress

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+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 2038650] Re: crash reports not sent to the Error Tracker

[Brian Murray]

Hello Brian, or anyone else affected,

Accepted apport into lunar-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.26.1-0ubuntu2.1 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
lunar to verification-done-lunar. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-lunar. 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: apport (Ubuntu Lunar)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed verification-needed-lunar

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

Title:
  crash reports not sent to the Error Tracker

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Lunar:
  Fix Committed
Status in apport source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

  Crash reports aren't sent in when going through the UI, unless the
  user looks at the crash details.

  [ Test Plan ]

  0) Make sure that error reporting is set to manual in the system settings (in 
Privacy screen)
  1) Launch xeyes
  2) pkill -11 xeyes
  3) Click send in the apport dialog. DO NOT look at the details of the report.
  4) ls -lh /var/crash/*xeyes*

  There should be 3 files:

  -rw-r- 1 bdmurray whoopsie  3370567 Oct  6 11:53 _usr_bin_xeyes.1000.crash
  -rw-rw-r-- 1 bdmurray bdmurray0 Oct  6 11:53 
_usr_bin_xeyes.1000.upload
  -rw--- 1 whoopsie whoopsie   37 Oct  6 11:53 
_usr_bin_xeyes.1000.uploaded

  [ Where problems could occur ]

  If the patch is wrong, we actually see similar bugs for other UI
  paths, e.g. ticking the "Remember this" box, etc. I tried to cover
  them during manual testing but I might have missed some.

  [ Other Info ]
   
  If possible I'd like for us not to wait too long for this to mature in 
-proposed, as this would affect crashes during the upgrade.

  [ Original report ]
  From what I can tell when I click the send button to send a crash report to 
the Error Tracker the crash doesn't actually get sent. My testing process 
follows:

  1) Launch xeyes
  2) pkill -11 xeyes
  3) Click send in the apport dialog
  4) ls -lh /var/crash

  I would expect there to be three files in /var/crash:

  -rw-r- 1 bdmurray whoopsie  3370567 Oct  6 11:53 _usr_bin_xeyes.1000.crash
  -rw-rw-r-- 1 bdmurray bdmurray0 Oct  6 11:53 
_usr_bin_xeyes.1000.upload
  -rw--- 1 whoopsie whoopsie   37 Oct  6 11:53 
_usr_bin_xeyes.1000.uploaded

  However, after step #4 I'm only seeing the .crash file and not a
  .upload or .uploaded.  I was able to get the .upload and .uploaded
  files created if I chose to "View Report" and then click "Send".

  It's worth noting though that I did notice the size of the .crash file
  increase after clicking "Send" so some post-processing was done.

  ProblemType: BugDistroRelease: Ubuntu 23.10
  Package: apport 2.27.0-0ubuntu4
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports: 640:1000:123:20944237:2023-10-06 12:10:47.809248208 
+0100:2023-10-06 12:11:23.340030509 +0100:/var/crash/_usr_bin_mpv.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  6 12:12:46 2023
  InstallationDate: Installed on 2022-01-07 (637 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: allSourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2038650/+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 2034986] Re: some text became unreadable during a distribution upgrade

[Brian Murray]

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

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

Title:
  some text became unreadable during a distribution upgrade

Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Jammy:
  Fix Committed
Status in ubuntu-meta source package in Lunar:
  Confirmed
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Committed
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/2034986/+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 2034986] Re: some text became unreadable during a distribution upgrade

[Brian Murray]

I've tested an upgrade of Ubuntu MATE (running Lunar) with -proposed
enabled with version 1:23.04.7 installed and the fonts in the body of
the ubuntu-release-upgrader were legible, however the title bar was
corrupted but that's fine.

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

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

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

Title:
  some text became unreadable during a distribution upgrade

Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Lunar:
  New
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Committed
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/2034986/+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 2034986] Re: some text became unreadable during a distribution upgrade

[Brian Murray]

Hello Brian, or anyone else affected,

Accepted ubuntu-release-upgrader into lunar-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-release-upgrader/1:23.04.7
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-
lunar to verification-done-lunar. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-lunar. 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: ubuntu-release-upgrader (Ubuntu Lunar)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-lunar

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

Title:
  some text became unreadable during a distribution upgrade

Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Lunar:
  New
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Committed
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - 

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Brian Murray]

** Also affects: ubuntu-meta (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-release-upgrader (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-release-upgrader (Ubuntu Lunar)
   Status: New => In Progress

** Changed in: ubuntu-release-upgrader (Ubuntu Lunar)
   Importance: Undecided => Critical

** Changed in: ubuntu-release-upgrader (Ubuntu Lunar)
 Assignee: (unassigned) => Nick Rosbrook (enr0n)

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

Title:
  some text became unreadable during a distribution upgrade

Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Lunar:
  New
Status in ubuntu-release-upgrader source package in Lunar:
  In Progress
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/2034986/+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 2038650] Re: crash reports not sent to the Error Tracker

[Brian Murray]

** Changed in: apport (Ubuntu Lunar)
Milestone: None => lunar-updates

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

** Changed in: apport (Ubuntu Lunar)
 Assignee: (unassigned) => Benjamin Drung (bdrung)

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

Title:
  crash reports not sent to the Error Tracker

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Lunar:
  Confirmed
Status in apport source package in Mantic:
  Fix Released

Bug description:
  From what I can tell when I click the send button to send a crash
  report to the Error Tracker the crash doesn't actually get sent. My
  testing process follows:

  1) Launch xeyes
  2) pkill -11 xeyes
  3) Click send in the apport dialog
  4) ls -lh /var/crash

  I would expect there to be three files in /var/crash:

  -rw-r- 1 bdmurray whoopsie  3370567 Oct  6 11:53 _usr_bin_xeyes.1000.crash
  -rw-rw-r-- 1 bdmurray bdmurray0 Oct  6 11:53 
_usr_bin_xeyes.1000.upload
  -rw--- 1 whoopsie whoopsie   37 Oct  6 11:53 
_usr_bin_xeyes.1000.uploaded

  However, after step #4 I'm only seeing the .crash file and not a
  .upload or .uploaded.  I was able to get the .upload and .uploaded
  files created if I chose to "View Report" and then click "Send".

  It's worth noting though that I did notice the size of the .crash file
  increase after clicking "Send" so some post-processing was done.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: apport 2.27.0-0ubuntu4
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports: 640:1000:123:20944237:2023-10-06 12:10:47.809248208 
+0100:2023-10-06 12:11:23.340030509 +0100:/var/crash/_usr_bin_mpv.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  6 12:12:46 2023
  InstallationDate: Installed on 2022-01-07 (637 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2038650/+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 2038834] Re: GPU acceleration via VirGL is broken in qemu

[Brian Murray]

** Also affects: ubuntu-release-notes
   Importance: Undecided
   Status: New

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

Title:
  GPU acceleration via VirGL is broken in qemu

Status in Release Notes for Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  This was reported by someone else upstream and is already fixed by
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038834/+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 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems

[Brian Murray]

** Changed in: ubuntu-release-notes
   Status: New => Invalid

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

Title:
  mantic images after 20230917 are failing to deploy with failure to
  mount root and kernel filesystems

Status in cloud-images:
  New
Status in maas-images:
  Confirmed
Status in The Ubuntu-power-systems project:
  Invalid
Status in Release Notes for Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in util-linux package in Ubuntu:
  Fix Released
Status in linux source package in Mantic:
  Invalid
Status in systemd source package in Mantic:
  Invalid
Status in util-linux source package in Mantic:
  Fix Released

Bug description:
  Mantic arm64 deploys started failing on Sept 18th with:

  [   41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root 
and Kernel File Systems...
   Starting systemd-remount-f鈥t Root and Kernel File 
Systems...
  [   41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug 
All udev Devices...
   Starting systemd-udev-trig鈥0m - Coldplug All udev 
Devices...
  [   41.964758] systemd[1]: Started systemd-journald.service - Journal Service.
  [  OK  ] Started systemd-journald.service - Journal 
Service.
  [  OK  ] Mounted dev-hugepages.mount - Huge Pages 
File System.
  [  OK  ] Mounted dev-mqueue.mount[鈥�- POSIX Message 
Queue File System.
  [  OK  ] Mounted sys-kernel-debug.m鈥t - Kernel Debug 
File System.
  [  OK  ] Mounted sys-kernel-tracing鈥t - Kernel Trace 
File System.
  [  OK  ] Finished keyboard-setup.se鈥�- Set the console 
keyboard layout.
  [  OK  ] Finished kmod-static-nodes鈥eate List of Static 
Device Nodes.
  [  OK  ] Finished lvm2-monitor.serv鈥ing dmeventd or 
progress polling.
  [  OK  ] Finished modprobe@configfs鈥0m - Load Kernel 
Module configfs.
  [  OK  ] Finished modprobe@dm_mod.s鈥 - Load Kernel 
Module dm_mod.
  [  OK  ] Finished modprobe@drm.service - Load Kernel 
Module drm.
  [  OK  ] Finished modprobe@efi_psto鈥 - Load Kernel 
Module efi_pstore.
  [  OK  ] Finished modprobe@fuse.service - Load Kernel 
Module fuse.
  [  OK  ] Finished modprobe@loop.service - Load Kernel 
Module loop.
  [  OK  ] Finished systemd-modules-l鈥ervice - Load 
Kernel Modules.
  [FAILED] Failed to start systemd-re鈥unt Root and 
Kernel File Systems.
  See 'systemctl status systemd-remount-fs.service' for details.

  After this many other services and cloud-init fails. See the full
  kopter-0918.log. For comparison, a log from the prior day's test is
  also attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2037417/+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 2038765] Re: df: /sys/firmware/efi/efivars: Invalid argument causes installation crash

[Brian Murray]

The log messages specifically refer to lightdm,
"2023-10-08T16:35:59.205065+00:00 ubuntu-budgie lightdm[1890]: df:
/sys/firmware/efi/efivars: Invalid argument", and I noticed this patch
in lightdm:

https://git.launchpad.net/ubuntu/+source/lightdm/tree/debian/patches/04_language_handling.patch?h=applied/ubuntu/devel#n79


** Also affects: lightdm (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  df: /sys/firmware/efi/efivars: Invalid argument causes installation
  crash

Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  df: /sys/firmware/efi/efivars: Invalid argument appears on first
  display of the  live session - I note subsequently that at the end of
  the installation curtin fails due to an efivars error - looking at
  syslog I saw various efivars errors so I'm filing this with the kernel
  since this is the first instance.

  i.e. running grep efivars /var/log/*

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-7-generic 6.5.0-7.7
  ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
  Uname: Linux 6.5.0-7-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu-budgie   2077 F wireplumber
   /dev/snd/seq:ubuntu-budgie   2074 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CasperVersion: 1.486
  CurrentDesktop: Budgie:GNOME
  Date: Sun Oct  8 16:27:29 2023
  LiveMediaBuild: Ubuntu-Budgie 23.10 "Mantic Minotaur" - Daily amd64 
(20231008.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
layerfs-path=minimal.standard.live.squashfs --- quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-7-generic N/A
   linux-backports-modules-6.5.0-7-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP91.88Z.00D9.B00.1802021100
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-6F01561E16C75D06
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro9,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-6F01561E16C75D06
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP91.88Z.00D9.B00.1802021100:bd02/02/2018:br0.1:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:skuSystemSKU#:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro9,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/2038765/+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 2038650] Re: crash reports not sent to the Error Tracker

[Brian Murray]

** Changed in: apport (Ubuntu)
 Assignee: (unassigned) => Simon Chopin (schopin)

** Changed in: apport (Ubuntu)
Milestone: None => ubuntu-23.10

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

Title:
  crash reports not sent to the Error Tracker

Status in apport package in Ubuntu:
  New

Bug description:
  From what I can tell when I click the send button to send a crash
  report to the Error Tracker the crash doesn't actually get sent. My
  testing process follows:

  1) Launch xeyes
  2) pkill -11 xeyes
  3) Click send in the apport dialog
  4) ls -lh /var/crash

  I would expect there to be three files in /var/crash:

  -rw-r- 1 bdmurray whoopsie  3370567 Oct  6 11:53 _usr_bin_xeyes.1000.crash
  -rw-rw-r-- 1 bdmurray bdmurray0 Oct  6 11:53 
_usr_bin_xeyes.1000.upload
  -rw--- 1 whoopsie whoopsie   37 Oct  6 11:53 
_usr_bin_xeyes.1000.uploaded

  However, after step #4 I'm only seeing the .crash file and not a
  .upload or .uploaded.  I was able to get the .upload and .uploaded
  files created if I chose to "View Report" and then click "Send".

  It's worth noting though that I did notice the size of the .crash file
  increase after clicking "Send" so some post-processing was done.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: apport 2.27.0-0ubuntu4
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports: 640:1000:123:20944237:2023-10-06 12:10:47.809248208 
+0100:2023-10-06 12:11:23.340030509 +0100:/var/crash/_usr_bin_mpv.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  6 12:12:46 2023
  InstallationDate: Installed on 2022-01-07 (637 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2038650/+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 2038650] Re: crash reports not sent to the Error Tracker

[Brian Murray]

** Tags removed: rls-mm-incoming
** Tags added: foundations-todo

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

Title:
  crash reports not sent to the Error Tracker

Status in apport package in Ubuntu:
  New

Bug description:
  From what I can tell when I click the send button to send a crash
  report to the Error Tracker the crash doesn't actually get sent. My
  testing process follows:

  1) Launch xeyes
  2) pkill -11 xeyes
  3) Click send in the apport dialog
  4) ls -lh /var/crash

  I would expect there to be three files in /var/crash:

  -rw-r- 1 bdmurray whoopsie  3370567 Oct  6 11:53 _usr_bin_xeyes.1000.crash
  -rw-rw-r-- 1 bdmurray bdmurray0 Oct  6 11:53 
_usr_bin_xeyes.1000.upload
  -rw--- 1 whoopsie whoopsie   37 Oct  6 11:53 
_usr_bin_xeyes.1000.uploaded

  However, after step #4 I'm only seeing the .crash file and not a
  .upload or .uploaded.  I was able to get the .upload and .uploaded
  files created if I chose to "View Report" and then click "Send".

  It's worth noting though that I did notice the size of the .crash file
  increase after clicking "Send" so some post-processing was done.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: apport 2.27.0-0ubuntu4
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports: 640:1000:123:20944237:2023-10-06 12:10:47.809248208 
+0100:2023-10-06 12:11:23.340030509 +0100:/var/crash/_usr_bin_mpv.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  6 12:12:46 2023
  InstallationDate: Installed on 2022-01-07 (637 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2038650/+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 2038650] [NEW] crash reports not sent to the Error Tracker

[Brian Murray]

Public bug reported:

>From what I can tell when I click the send button to send a crash report
to the Error Tracker the crash doesn't actually get sent. My testing
process follows:

1) Launch xeyes
2) pkill -11 xeyes
3) Click send in the apport dialog
4) ls -lh /var/crash

I would expect there to be three files in /var/crash:

-rw-r- 1 bdmurray whoopsie  3370567 Oct  6 11:53 _usr_bin_xeyes.1000.crash
-rw-rw-r-- 1 bdmurray bdmurray0 Oct  6 11:53 _usr_bin_xeyes.1000.upload
-rw--- 1 whoopsie whoopsie   37 Oct  6 11:53 
_usr_bin_xeyes.1000.uploaded

However, after step #4 I'm only seeing the .crash file and not a .upload
or .uploaded.  I was able to get the .upload and .uploaded files created
if I chose to "View Report" and then click "Send".

It's worth noting though that I did notice the size of the .crash file
increase after clicking "Send" so some post-processing was done.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: apport 2.27.0-0ubuntu4
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CrashReports: 640:1000:123:20944237:2023-10-06 12:10:47.809248208 
+0100:2023-10-06 12:11:23.340030509 +0100:/var/crash/_usr_bin_mpv.1000.crash
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct  6 12:12:46 2023
InstallationDate: Installed on 2022-01-07 (637 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: apport (Ubuntu)
 Importance: High
 Status: New


** Tags: amd64 apport-bug mantic rls-mm-incoming wayland-session

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

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

Title:
  crash reports not sent to the Error Tracker

Status in apport package in Ubuntu:
  New

Bug description:
  From what I can tell when I click the send button to send a crash
  report to the Error Tracker the crash doesn't actually get sent. My
  testing process follows:

  1) Launch xeyes
  2) pkill -11 xeyes
  3) Click send in the apport dialog
  4) ls -lh /var/crash

  I would expect there to be three files in /var/crash:

  -rw-r- 1 bdmurray whoopsie  3370567 Oct  6 11:53 _usr_bin_xeyes.1000.crash
  -rw-rw-r-- 1 bdmurray bdmurray0 Oct  6 11:53 
_usr_bin_xeyes.1000.upload
  -rw--- 1 whoopsie whoopsie   37 Oct  6 11:53 
_usr_bin_xeyes.1000.uploaded

  However, after step #4 I'm only seeing the .crash file and not a
  .upload or .uploaded.  I was able to get the .upload and .uploaded
  files created if I chose to "View Report" and then click "Send".

  It's worth noting though that I did notice the size of the .crash file
  increase after clicking "Send" so some post-processing was done.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: apport 2.27.0-0ubuntu4
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports: 640:1000:123:20944237:2023-10-06 12:10:47.809248208 
+0100:2023-10-06 12:11:23.340030509 +0100:/var/crash/_usr_bin_mpv.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  6 12:12:46 2023
  InstallationDate: Installed on 2022-01-07 (637 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2038650/+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 2037642] Re: [FFe] Raspberry Pi 5 support

[Brian Murray]

** Also affects: ubuntu-release-notes
   Importance: Undecided
   Status: New

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

Title:
  [FFe] Raspberry Pi 5 support

Status in Release Notes for Ubuntu:
  New
Status in libcamera package in Ubuntu:
  Triaged
Status in linux-meta-raspi package in Ubuntu:
  Fix Released
Status in linux-raspi package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in pipewire package in Ubuntu:
  Invalid
Status in rpi-eeprom package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

   * HWE for Raspberry Pi 5 https://raspberrypi.com/5

  [ Test Plan ]

   * Private builds tested on all existing/supported Raspberry Pi SKUs
  in armhf & arm64 variants

   * No regressions on any existing SKUs

   * Test that Raspberry Pi 5 boards work

  [ Where problems could occur ]

   * Mesa is upgraded, and there are patches to mesa, the raspberry-pi
  specific provider this has been tested but not as extensively.
  Separately there is mesa FFe granted to upgrade to latest release,
  thus these changes piggy-back on top of it.

   * libcamera has new build-depends on new package libpisp for the
  raspberry-pi specific provider which also affects pipewire to provide
  full webcam support.

   * These dependencies, will need to make their way into gnome platform
  snaps to be usable by default in Firefox.

  [ Other Info ]

   * The proposed code changes have been tested in private, prior to
  public announcement

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2037642/+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 2036440] Re: Choosing "Try Ubuntu" on daily-legacy image produced a crash

[Brian Murray]

Could the gnome-shell crash be a consequence of how we are booting the
Legacy image and starting the desktop environment? I noticed the
following in the crash report "gnome-shell --sm-disable
--mode=ubiquity".

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

Title:
  Choosing "Try Ubuntu" on daily-legacy image produced a crash

Status in apport package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  New

Bug description:
  I was booting up a daily-legacy image from 20230918 and received a
  crash report after choosing "Try Ubuntu".

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~rc-0ubuntu3
  Uname: Linux 6.5.0-5-generic x86_64
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 18 15:20:58 2023
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1694375959
  ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
  ProcCwd: /home/ubuntu
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: gnome-shell
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2036440/+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 2036440] Re: Choosing "Try Ubuntu" on daily-legacy image produced a crash

[Brian Murray]

We could create an /etc/apport/report-ignore/ file with the contents
'/usr/bin/gnome-shell' so then at least the crash report dialog would
not appear. However, after choosing try Ubuntu you presented with a
black screen and some console output so its still not a great
experience.

** Also affects: ubiquity (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubiquity (Ubuntu)
Milestone: None => ubuntu-23.10

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

Title:
  Choosing "Try Ubuntu" on daily-legacy image produced a crash

Status in apport package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  New

Bug description:
  I was booting up a daily-legacy image from 20230918 and received a
  crash report after choosing "Try Ubuntu".

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~rc-0ubuntu3
  Uname: Linux 6.5.0-5-generic x86_64
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 18 15:20:58 2023
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1694375959
  ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
  ProcCwd: /home/ubuntu
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: gnome-shell
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2036440/+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 2036440] Re: Choosing "Try Ubuntu" on daily-legacy image produced a crash

[Brian Murray]

The gnome-shell crash is easily reproducible by choosing Try Ubuntu when
using a mantic desktop legacy image.

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2036440/+attachment/5703615/+files/journal.txt

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

Title:
  Choosing "Try Ubuntu" on daily-legacy image produced a crash

Status in apport package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I was booting up a daily-legacy image from 20230918 and received a
  crash report after choosing "Try Ubuntu".

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~rc-0ubuntu3
  Uname: Linux 6.5.0-5-generic x86_64
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 18 15:20:58 2023
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1694375959
  ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
  ProcCwd: /home/ubuntu
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: gnome-shell
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2036440/+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 2037004] [NEW] warnings in terminal with software-properties-gtk

[Brian Murray]

Public bug reported:

When running software-properties-gtk and switching to the "Additional
Drivers" tab I saw the following warnings in my terminal:

 $ software-properties-gtk 
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
...

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: software-properties-gtk 0.99.39
ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
Uname: Linux 6.5.0-4-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 21 11:49:24 2023
InstallationDate: Installed on 2018-08-10 (1868 days ago)
InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
PackageArchitecture: all
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: software-properties
UpgradeStatus: Upgraded to mantic on 2023-09-06 (15 days ago)

** Affects: software-properties (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-bug mantic rls-nn-incoming

** Tags added: rls-nn-incoming

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  warnings in terminal with software-properties-gtk

Status in software-properties package in Ubuntu:
  New

Bug description:
  When running software-properties-gtk and switching to the "Additional
  Drivers" tab I saw the following warnings in my terminal:

   $ software-properties-gtk 
  udevadm hwdb is deprecated. Use systemd-hwdb instead.
  udevadm hwdb is deprecated. Use systemd-hwdb instead.
  udevadm hwdb is deprecated. Use systemd-hwdb instead.
  udevadm hwdb is deprecated. Use systemd-hwdb instead.
  udevadm hwdb is deprecated. Use systemd-hwdb instead.
  udevadm hwdb is deprecated. Use systemd-hwdb instead.
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: software-properties-gtk 0.99.39
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 21 11:49:24 2023
  InstallationDate: Installed on 2018-08-10 (1868 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2037004/+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 2031899] Re: File system layers missing - unable to boot live cd Ubuntu Mantic Desktop

[Brian Murray]

This was sorted out a few weeks ago, but I don't have the primary bug at
hand.

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

** Changed in: ubuntu-desktop-installer
   Status: New => Invalid

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

Title:
  File system layers missing - unable to boot live cd Ubuntu Mantic
  Desktop

Status in ubuntu-desktop-installer:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  Testing Ubuntu Mantic desktop daily iso 18-08-2023 the folling error
  reported when attempting to boot live installation media -

  File system layers missing:\n
  '/cdrom/casper/minimal.standard.live.squashfs .. see attached
  screenshot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2031899/+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 2034986] Re: some text became unreadable during a distribution upgrade

[Brian Murray]

I think we'd want to put it in a "quirk" and those are found in
DistUpgradeQuirks.py:

https://git.launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/tree/DistUpgrade/DistUpgradeQuirks.py?h=ubuntu/mantic

I think a "StartUpgrade" quirk is likely the best time for this but
there should be a check to ensure that we are using the gtk frontend or
some other check to ensure that we really need to modify the font.

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

Title:
  some text became unreadable during a distribution upgrade

Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in ubuntu-meta source package in Mantic:
  Confirmed
Status in ubuntu-release-upgrader source package in Mantic:
  Confirmed

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2034986/+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 2036440] Re: Choosing "Try Ubuntu" on daily-legacy image produced a crash

[Brian Murray]

Oh, in that case you'll want to look at /usr/share/apport/general-
hooks/ubuntu.py which is provided by the apport package.

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

Title:
  Choosing "Try Ubuntu" on daily-legacy image produced a crash

Status in apport package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I was booting up a daily-legacy image from 20230918 and received a
  crash report after choosing "Try Ubuntu".

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~rc-0ubuntu3
  Uname: Linux 6.5.0-5-generic x86_64
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 18 15:20:58 2023
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1694375959
  ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
  ProcCwd: /home/ubuntu
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: gnome-shell
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2036440/+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 2036440] Re: Choosing "Try Ubuntu" on daily-legacy image produced a crash

[Brian Murray]

gnome-shell already ships an apport package hook which is installed in
/usr/share/apport/package-hooks/source_gnome-shell.py and that seems to
be debian/source_gnome-shell.py from the source package. It should be
relatively straight forward to modify that and an update to it is
something the SRU team would likely (I say likely due to the install
base of gnome-shell) as an stable release update to the package. It is
something the Ubuntu Release team would definitely accept as an update
post Feature Freeze.

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

Title:
  Choosing "Try Ubuntu" on daily-legacy image produced a crash

Status in apport package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I was booting up a daily-legacy image from 20230918 and received a
  crash report after choosing "Try Ubuntu".

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~rc-0ubuntu3
  Uname: Linux 6.5.0-5-generic x86_64
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 18 15:20:58 2023
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1694375959
  ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
  ProcCwd: /home/ubuntu
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: gnome-shell
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2036440/+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 2036440] Re: Choosing "Try Ubuntu" on daily-legacy image produced a crash

[Brian Murray]

Couldn't we modify the apport hook for gnome-shell to gather the
relevant log file when ever there is a 'Signal: 6' in the crash report?

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

Title:
  Choosing "Try Ubuntu" on daily-legacy image produced a crash

Status in apport package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I was booting up a daily-legacy image from 20230918 and received a
  crash report after choosing "Try Ubuntu".

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~rc-0ubuntu3
  Uname: Linux 6.5.0-5-generic x86_64
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 18 15:20:58 2023
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1694375959
  ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
  ProcCwd: /home/ubuntu
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: gnome-shell
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users

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