[Touch-packages] [Bug 1974456] Re: regression: apt.postint fails if never previously configured

2022-05-31 Thread Chris Halse Rogers
Hello David, or anyone else affected,

Accepted apt into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.0.9 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
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: apt (Ubuntu Focal)
   Status: Confirmed => 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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1974456

Title:
  regression: apt.postint fails if never previously configured

Status in apt package in Ubuntu:
  Confirmed
Status in apt source package in Bionic:
  Confirmed
Status in apt source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  bootstrapping a system with apt that fixes #1968154 fails in focal and 
bionic, as they try to execute the config file that is being removed.

  This is not a problem on updates, only on new installs, so impact is
  limited to bootstrapping tools that enable -updates, such as
  mmdebstrap.

  [Test case]

  bootstrapping with -updates enabled can easily be tested with
  mmdebstrap:

  mmdebstrap -v focal ~/Projects/Ubuntu/Scratch/focal

  for example, on focal:

  Setting up apt (2.0.8) ...
  /var/lib/dpkg/info/apt.postinst: 65: /etc/kernel/postinst.d/apt-auto-removal: 
not found
  dpkg: error processing package apt (--configure):
   installed apt package post-installation script subprocess returned error 
exit status 127

  [Regression potential]
  We remove 5 lines from the shell postinst script, there could be syntax 
errors? But then we'd see those during upgrades, so practically none.

  [Original bug report]
  #1968154 removed `/etc/kernel/postinst.d/apt-auto-removal` in this patch:
  
https://git.launchpad.net/ubuntu/+source/apt/commit/?id=f9d2d993687c0d5223c241956ef6a0aabcf15bf0

  ...but `apt.postinst` still tries to run it:

  # create kernel autoremoval blacklist on update
  if dpkg --compare-versions "$2" lt 0.9.9.3; then
  /etc/kernel/postinst.d/apt-auto-removal
  fi

  If I understand correctly, "$2" is the most-recently-configured-
  version, and if it's empty `dpkg --compare-versions lt` will evaluate
  to true.

  This fails when I'm building a focal (20.04) userspace from scratch:

  $ dpkg --configure -a
  [...]
  Setting up apt (2.0.8) ...
  /var/lib/dpkg/info/apt.postinst: 65: 
/etc/kernel/postinst.d/apt-auto-removal: not found
  dpkg: error processing package apt (--configure):
   installed apt package post-installation script subprocess returned error 
exit status 127

  It works with apt 2.0.6.

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

2022-05-31 Thread Chris Halse Rogers
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/1974428

Title:
  Update to the current 1.36 stable version

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Jammy:
  Fix Released

Bug description:
  * Impact

  It's a stable update from upstream, the changes are listed in the NEWS
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS

  * Test Case

  Since it's an update with several fixes the testing should focus on a
  specific point but rather by validating that the testplan is green,
  https://wiki.ubuntu.com/NetworkManager/DistroTesting

  * Regression potential

  There are fixes around IPv6 handling, VPN connections and the hotspot
  feature, verify that those configurations are still working as
  expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1974428/+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 1913775] Re: Copy from Firefox Wayland fails to be pasted anywhere else

2022-05-17 Thread Chris Halse Rogers
Yeah, ok.

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

Title:
  Copy from Firefox Wayland fails to be pasted anywhere else

Status in GTK+:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Impish:
  Fix Released

Bug description:
  * Impact

  The clipboard copies from GTK based software sometime stop working
  under wayland

  * Test Case

  - in a wayland session try to copy text between software, from firefox
  to gedit for example, it should work in a consistent manner

  alternative testcase inspired from the gitlab ticket
  - install wl-clipboard
  - use evince to open a pdf
  - select and copy some content
  - on a cmdline do 
  $ wl-paste -t TEXT
  - try to paste then in another software, gedit for example

  the copied text should be pasted

  
  * Regression potential

  The changes are in the wayland selection source so the impact should
  only be for wayland users and limited to clipboard interactions

  
  --

  
  Running Firefox 84.0.2 for Ubuntu Canonical-1.0 on Ubuntu 20.04.1 LTS, on 
Wayland native

  Version   84.0.2
  Build ID  20210105180113

  Window Protocol   wayland
  Desktop Environment   gnome

  DESCRIPTION OF THE PROBLEM:

  If I copy text from a web page and try to paste it into another
  Firefox page, the text is pasted correctly.

  If I copy text from a web page and try to paste it in [gedit,
  libreoffice, thunderbird, terminal, slack (electron)] nothing happens.
  The Gnome Clipboard extension stays empty when content is copied from
  Firefox Wayland.

  Pasting *from* another app *to* Firefox works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1913775/+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 1913775] Update Released

2022-05-17 Thread Chris Halse Rogers
The verification of the Stable Release Update for gtk+3.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 gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1913775

Title:
  Copy from Firefox Wayland fails to be pasted anywhere else

Status in GTK+:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Impish:
  Fix Released

Bug description:
  * Impact

  The clipboard copies from GTK based software sometime stop working
  under wayland

  * Test Case

  - in a wayland session try to copy text between software, from firefox
  to gedit for example, it should work in a consistent manner

  alternative testcase inspired from the gitlab ticket
  - install wl-clipboard
  - use evince to open a pdf
  - select and copy some content
  - on a cmdline do 
  $ wl-paste -t TEXT
  - try to paste then in another software, gedit for example

  the copied text should be pasted

  
  * Regression potential

  The changes are in the wayland selection source so the impact should
  only be for wayland users and limited to clipboard interactions

  
  --

  
  Running Firefox 84.0.2 for Ubuntu Canonical-1.0 on Ubuntu 20.04.1 LTS, on 
Wayland native

  Version   84.0.2
  Build ID  20210105180113

  Window Protocol   wayland
  Desktop Environment   gnome

  DESCRIPTION OF THE PROBLEM:

  If I copy text from a web page and try to paste it into another
  Firefox page, the text is pasted correctly.

  If I copy text from a web page and try to paste it in [gedit,
  libreoffice, thunderbird, terminal, slack (electron)] nothing happens.
  The Gnome Clipboard extension stays empty when content is copied from
  Firefox Wayland.

  Pasting *from* another app *to* Firefox works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1913775/+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 1959047] Update Released

2022-05-17 Thread Chris Halse Rogers
The verification of the Stable Release Update for lxd 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1959047

Title:
  systemd ignores RootDirectory option in .service units

Status in lxd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed
Status in lxd source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Confirmed
Status in systemd source package in Focal:
  Confirmed
Status in systemd source package in Impish:
  Confirmed

Bug description:
  [Impact]

  Ubuntu carries a patch on top of systemd [a] to silence
  namespace set up failures. This is meant as a workaround
  for a bug in the LXD version shipped in Ubuntu 18.04.

  Masking namespace set up failures creates a false sense of
  security for the user/admin.

  As mentioned in comment #1, systemd upstream explains that silencing
  this kind of error is dangerous and should be avoided.

  Backporting the LXD fix [b] to Ubuntu 18.04 would allow namespaces
  to work inside containers. This is the goal of this SRU.

  Ultimately, once LXD in Ubuntu 18.04 includes the fix [b], it would
  be possible to drop the Ubuntu-specific patch for systemd [a]. This
  is however *not an immediate concern for this SRU*.

  [Test Plan]

  1) Create a 18.04 VM:
  $ lxc launch images:ubuntu/18.04 lp1959047 --vm
  $ sleep 30  # give it time to boot

  1.5) Enable bionic-proposed:
  $ echo "deb http://archive.ubuntu.com/ubuntu bionic-proposed main restricted 
universe multiverse" | lxc file push - 
lp1959047/etc/apt/sources.list.d/proposed.list

  2) Install and initialize LXD in it:
  $ lxc exec lp1959047 -- apt-get update
  $ lxc exec lp1959047 -- apt-get install -y lxd
  $ lxc exec lp1959047 -- lxd init --auto

  3) Create a Jammy container and enable systemd debugging:
  $ lxc exec lp1959047 -- lxc init images:ubuntu/22.04 c1
  $ lxc exec lp1959047 -- lxc config set c1 raw.lxc 'lxc.init.cmd = /sbin/init 
systemd.log_level=debug'
  $ lxc exec lp1959047 -- lxc start c1

  4) Check if namespace set up failures are logged:
  $ lxc exec lp1959047 --  lxc exec c1 -- journalctl -b0 --grep 'Failed to set 
up namespace'
  Mar 24 23:29:19 c1 systemd[99]: systemd-udevd.service: Failed to set up 
namespace, assuming containerized execution, ignoring: Permission denied
  Mar 24 23:29:19 c1 systemd[132]: systemd-networkd.service: Failed to set up 
namespace, assuming containerized execution, ignoring: Permission denied
  Mar 24 23:29:19 c1 systemd[131]: systemd-logind.service: Failed to set up 
namespace, assuming containerized execution, ignoring: Permission denied
  Mar 24 23:29:20 c1 systemd[136]: systemd-resolved.service: Failed to set up 
namespace, assuming containerized execution, ignoring: Permission denied
  Mar 24 23:29:20 c1 systemd[128]: e2scrub_reap.service: Failed to set up 
namespace, assuming containerized execution, ignoring: Permission denied
  Mar 24 23:29:23 c1 systemd[243]: systemd-hostnamed.service: Failed to set up 
namespace, assuming containerized execution, ignoring: Permission denied

  If LXD in Ubuntu 18.04 has the patch, the "Failed to set up namespace"
  messages wouldn't be there.

  [Where problems could occur]

  The LXD fix changes the Apparmor profile used for containers. This essentially
  loosen the mount restrictions applied to containers.

  Weakening the Apparmor profile could make it easier for a process in the 
container
  to do damage that would have otherwise been blocked. On the other hand, this
  allows making use of namespaces/sandboxing inside the container.

  Upstream LXD has the fix since 2019 which make it less likely to run into
  problems with the backport.

  The backported fix was also tested manually to ensure LXD still behaved 
normally
  and that it avoided the namespace set up failures in Jammy containers.

  [a]: 
https://git.launchpad.net/ubuntu/+source/systemd/tree/debian/patches/debian/UBUNTU-Revert-namespace-be-more-careful-when-handling-namespacin.patch?h=ubuntu/jammy
  [b]: 
https://github.com/lxc/lxd/commit/a6b780703350faff8328f3d565f6bac7b6dcf59f

  [Initial bug description]

  The version of systemd (249.5-2ubuntu4) currently packaged for the
  Ubuntu development version (22.04 Jammy Jellyfish) totally ignores the
  RootDirectory= option in systemd service files. With RootDirectory,
  systemd should start the service after calling chroot() on the
  supplied directory.

  To test/reproduce, create a test service file with the 

[Touch-packages] [Bug 1959375] Update Released

2022-05-17 Thread Chris Halse Rogers
The verification of the Stable Release Update for shadow 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 shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1959375

Title:
  [SRU] Please support group manipulation with "extrausers"

Status in shadow package in Ubuntu:
  Fix Released
Status in shadow source package in Bionic:
  Fix Committed
Status in shadow source package in Focal:
  Fix Committed
Status in shadow source package in Impish:
  Won't Fix
Status in shadow source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  * In order to use the microk8s snap in Ubuntu Core, one currently
  needs to be root. This is far from optimal, since normally (on desktop
  and server installations) this is not necessary.

  * This make it hard to provide consistent documentation on microk8s
  across all supported device, if we have to take the "sudo" command
  into account, and how file permissions for generated files might be
  affected.

  
  [Test Plan]

  The issue can be reproduced on Ubuntu Core 18, 20 and 22. The steps
  are as following (replace "" with the actual path of your
  Ubuntu Core image file:

  qemu-system-x86_64 -enable-kvm -smp 2 -m 1500 \
  -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \
  -device virtio-net-pci,netdev=mynet0 \
  -drive file=,format=raw

  After configuring your account, connect to youd device via SSH:

  ssh @localhost -p 8022

  And issue these commands

  sudo snap install microk8s --channel=latest/edge/stable

  # microk8s is going to eat up all your disk space, so stop it as soon
  # as the prompt comes back:
  sudo microk8s stop

  # Add your user to the microk8s group
  sudo usermod -G snap_microk8s $(whoami)

  The last command will fail unless this bug is fixed. If the bug is
  fixed, the command will succeed, and after logging out and in again,
  you can verify that you've been added to the snap_microk8s group by
  running the "groups" command.

  
  [Where problems could occur]

  * The patch only touches error code paths and adds a fallback
  mechanism in them. Therefore, "normal" operations, where these
  commands would have succeeded before, will not be affected at all.

  * In those cases when usermod fails because it failed to find or load
  the requested user/group, we reset the user/group database paths to
  our writable user/group databases, and retry the operation. Note that
  the path for our database is hardcoded in the program source, so the
  security risk seems contained. We do not add additional command-line
  parameters.

  
  [Other Info]

  Original bug description
  

  Currently doing something like:

  sudo usermod -a -G snap_microk8s dbeamonte

  on a Ubuntu Core system will fail with

  usermod: /etc/group.15965: Read-only file system

  This is because the existing usermod patches to detect
  the extrausers file do not cover this case. Attached
  a simple patch that enables it. I will give this patch
  a test run in our image PPA for jammy and if things look
  good I would like upload to 22.04 and SRU for 20.04 and
  18.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+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 1959375] Re: [SRU] Please support group manipulation with "extrausers"

2022-05-17 Thread Chris Halse Rogers
Yeeah, ok.

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

Title:
  [SRU] Please support group manipulation with "extrausers"

Status in shadow package in Ubuntu:
  Fix Released
Status in shadow source package in Bionic:
  Fix Committed
Status in shadow source package in Focal:
  Fix Committed
Status in shadow source package in Impish:
  Won't Fix
Status in shadow source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  * In order to use the microk8s snap in Ubuntu Core, one currently
  needs to be root. This is far from optimal, since normally (on desktop
  and server installations) this is not necessary.

  * This make it hard to provide consistent documentation on microk8s
  across all supported device, if we have to take the "sudo" command
  into account, and how file permissions for generated files might be
  affected.

  
  [Test Plan]

  The issue can be reproduced on Ubuntu Core 18, 20 and 22. The steps
  are as following (replace "" with the actual path of your
  Ubuntu Core image file:

  qemu-system-x86_64 -enable-kvm -smp 2 -m 1500 \
  -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \
  -device virtio-net-pci,netdev=mynet0 \
  -drive file=,format=raw

  After configuring your account, connect to youd device via SSH:

  ssh @localhost -p 8022

  And issue these commands

  sudo snap install microk8s --channel=latest/edge/stable

  # microk8s is going to eat up all your disk space, so stop it as soon
  # as the prompt comes back:
  sudo microk8s stop

  # Add your user to the microk8s group
  sudo usermod -G snap_microk8s $(whoami)

  The last command will fail unless this bug is fixed. If the bug is
  fixed, the command will succeed, and after logging out and in again,
  you can verify that you've been added to the snap_microk8s group by
  running the "groups" command.

  
  [Where problems could occur]

  * The patch only touches error code paths and adds a fallback
  mechanism in them. Therefore, "normal" operations, where these
  commands would have succeeded before, will not be affected at all.

  * In those cases when usermod fails because it failed to find or load
  the requested user/group, we reset the user/group database paths to
  our writable user/group databases, and retry the operation. Note that
  the path for our database is hardcoded in the program source, so the
  security risk seems contained. We do not add additional command-line
  parameters.

  
  [Other Info]

  Original bug description
  

  Currently doing something like:

  sudo usermod -a -G snap_microk8s dbeamonte

  on a Ubuntu Core system will fail with

  usermod: /etc/group.15965: Read-only file system

  This is because the existing usermod patches to detect
  the extrausers file do not cover this case. Attached
  a simple patch that enables it. I will give this patch
  a test run in our image PPA for jammy and if things look
  good I would like upload to 22.04 and SRU for 20.04 and
  18.04.

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

2022-05-10 Thread Chris Halse Rogers
The verification of the Stable Release Update for glibc 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 pam in Ubuntu.
https://bugs.launchpad.net/bugs/1892825

Title:
  update-locale not perform correctly sanity checks

Status in glibc package in Ubuntu:
  In Progress
Status in pam package in Ubuntu:
  New
Status in glibc source package in Bionic:
  New
Status in pam source package in Bionic:
  New
Status in glibc source package in Focal:
  Fix Released
Status in pam source package in Focal:
  New
Status in glibc source package in Hirsute:
  Won't Fix
Status in pam source package in Hirsute:
  New
Status in glibc source package in Impish:
  New
Status in pam source package in Impish:
  New

Bug description:
  [impact]
  A simple typo using the update-locale script can render a system inoperable 
without booting into single user mode or similar:

  $ sudo update-locale LANGUAGE = en_US.UTF-8
  $ sudo -s
  sudo: pam_open_session: Bad item passed to pam_*_item()
  sudo: policy plugin failed session initialization

  [test case]
  $ cp /etc/default/locale /tmp/locale
  $ update-locale --locale-file /tmp/locale LANGUAGE = en_US.UTF-8

  "diff -u /etc/default/locale /tmp/locale" should be empty.

  $ update-locale --locale-file /tmp/locale LANGUAGE=en_US.UTF-8

  The LANGUAGE=en_US.UTF-8 line should have been replaced by
  LANGUAGE=en_GB.UTF-8.

  $ update-locale --locale-file /tmp/locale LANGUAGE

  The LANGUAGE setting is now commented out.

  [regression potential]
  Apart from the general concerns about a glibc rebuild, this is a simple 
change to a simple script. Performing the test as in the test case section is 
enough to ensure it still works.

  [original description]
  By passing wrong input as following:
   sudo update-locale LANGUAGE = en_US.UTF-8
  result is:
  ...
  #LANGUAGE=en
  =

  This "equal" sign that was added makes system completely
  unusable(can't run sudo anymore):

  bentzy@bentzy-nb:~$ sudo vim /etc/default/locale
  sudo: pam_open_session: Bad item passed to pam_*_item()
  sudo: policy plugin failed session initialization

  Fixed it booting from installation disk and fixing corrupted
  /etc/default/locale

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: locales 2.31-0ubuntu9
  Uname: Linux 5.5.4-050504-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Aug 25 09:36:03 2020
  InstallationDate: Installed on 2020-08-17 (7 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: glibc
  UpgradeStatus: No upgrade log present (probably fresh install)

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

2022-03-23 Thread Chris Halse Rogers
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/1965791

Title:
  Update tzdata to version 2022a

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Bionic:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released
Status in tzdata source package in Impish:
  Fix Released
Status in tzdata source package in Jammy:
  Fix Released

Bug description:
  New upstream version affecting the following timestamp:

  $region/$timezone = Asia/Gaza

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with 'zdump -v
  $region/$timezone_that_changed' (this needs to be greped for in
  /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
  compared to the same output after the updated package got installed.
  If those are different the verification is considered done.

  [Test Case for all releases]
  1) zdump -v Asia/Gaza | grep 'Mar.*2022'

  With the version of the package from -proposed this will show Mar 26
  not Mar 25.

  For releases with ICU timezone data verification is done using the following 
with dates before and after the change:
  [Test Case for releases >= 20.04 LTS]
  1) sudo apt-get install python3-icu
  2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.createTimeZone('Asia/Gaza')); 
print(str(tz.utcoffset(datetime(2022, 3, 26'

  Additionally, an upstream update of tzdata removed the 'old' SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  [Test Case for releases <= 20.04 LTS]
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  Nothing should be returned by the above command.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1965791/+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 1962135] Re: [SRU] gstreamer 1.16.3 series

2022-03-15 Thread Chris Halse Rogers
Hello kunal, or anyone else affected,

Accepted gst-plugins-bad1.0 into focal-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/gst-
plugins-bad1.0/1.16.3-0ubuntu1 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: gst-plugins-bad1.0 (Ubuntu Focal)
   Status: Triaged => Fix Committed

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

Title:
  [SRU] gstreamer 1.16.3 series

Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 source package in Focal:
  Fix Committed
Status in gst-plugins-base1.0 source package in Focal:
  Fix Committed
Status in gst-plugins-good1.0 source package in Focal:
  Fix Committed
Status in gstreamer1.0 source package in Focal:
  Fix Committed

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.16 series
  that 20.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  If one of the fixes is bad then it might break video or audio
  playback, or could crash any application that tries to use gstreamer.

  ---


  On ubuntu-20.04 "apt-get" default installs gstreamer version 1.16.2,
  though gstreamer has subsequent minor version gst-1.16.3 with fixes
  incorporated.

  Hence, Ideally default gstreamer-1.16 minor version support with
  ubuntu-20.04 should be upgraded to use gstreamer version 1.16.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1962135/+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 1962135] Re: [SRU] gstreamer 1.16.3 series

2022-03-08 Thread Chris Halse Rogers
Hello kunal, or anyone else affected,

Accepted gst-plugins-base1.0 into focal-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/gst-
plugins-base1.0/1.16.3-0ubuntu1 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: gst-plugins-base1.0 (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  [SRU] gstreamer 1.16.3 series

Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 source package in Focal:
  Triaged
Status in gst-plugins-base1.0 source package in Focal:
  Fix Committed
Status in gst-plugins-good1.0 source package in Focal:
  Fix Committed
Status in gstreamer1.0 source package in Focal:
  Fix Committed

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.16 series
  that 20.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  If one of the fixes is bad then it might break video or audio
  playback, or could crash any application that tries to use gstreamer.

  ---


  On ubuntu-20.04 "apt-get" default installs gstreamer version 1.16.2,
  though gstreamer has subsequent minor version gst-1.16.3 with fixes
  incorporated.

  Hence, Ideally default gstreamer-1.16 minor version support with
  ubuntu-20.04 should be upgraded to use gstreamer version 1.16.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1962135/+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 1962135] Re: [SRU] gstreamer 1.16.3 series

2022-03-08 Thread Chris Halse Rogers
Hello kunal, or anyone else affected,

Accepted gst-plugins-good1.0 into focal-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/gst-
plugins-good1.0/1.16.3-0ubuntu1 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: gst-plugins-good1.0 (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  [SRU] gstreamer 1.16.3 series

Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 source package in Focal:
  Triaged
Status in gst-plugins-base1.0 source package in Focal:
  In Progress
Status in gst-plugins-good1.0 source package in Focal:
  Fix Committed
Status in gstreamer1.0 source package in Focal:
  Fix Committed

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.16 series
  that 20.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  If one of the fixes is bad then it might break video or audio
  playback, or could crash any application that tries to use gstreamer.

  ---


  On ubuntu-20.04 "apt-get" default installs gstreamer version 1.16.2,
  though gstreamer has subsequent minor version gst-1.16.3 with fixes
  incorporated.

  Hence, Ideally default gstreamer-1.16 minor version support with
  ubuntu-20.04 should be upgraded to use gstreamer version 1.16.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1962135/+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 1962135] Re: [SRU] gstreamer 1.16.3 series

2022-03-08 Thread Chris Halse Rogers
Hello kunal, or anyone else affected,

Accepted gstreamer1.0 into focal-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/gstreamer1.0/1.16.3-0ubuntu1 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: gstreamer1.0 (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 gst-plugins-base1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/1962135

Title:
  [SRU] gstreamer 1.16.3 series

Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 source package in Focal:
  Triaged
Status in gst-plugins-base1.0 source package in Focal:
  In Progress
Status in gst-plugins-good1.0 source package in Focal:
  In Progress
Status in gstreamer1.0 source package in Focal:
  Fix Committed

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.16 series
  that 20.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  If one of the fixes is bad then it might break video or audio
  playback, or could crash any application that tries to use gstreamer.

  ---


  On ubuntu-20.04 "apt-get" default installs gstreamer version 1.16.2,
  though gstreamer has subsequent minor version gst-1.16.3 with fixes
  incorporated.

  Hence, Ideally default gstreamer-1.16 minor version support with
  ubuntu-20.04 should be upgraded to use gstreamer version 1.16.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1962135/+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 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications

2022-03-01 Thread Chris Halse Rogers
Ok. So it seems that the bug *exists* in Focal, so now we just need to
verify that the bug is *fixed* by the proposed package.

@angie78 - as you seem to suffer from the bug, can you try to verify
that the proposed packages (from
https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1782984/comments/106
) fix the bug? Once we've got verification that the bug is fixed, we can
release the packages into -updates and everyone can benefit!

Anyone else is also welcome to verify!

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

Title:
  Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
  applications

Status in libx11 package in Ubuntu:
  Fix Released
Status in libx11 source package in Bionic:
  Fix Committed
Status in libx11 source package in Focal:
  Fix Committed
Status in libx11 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  There is a race in libx11 causing applications to randomly abort. It's
  not trivial to reproduce, but there are enough duplicates that this
  deserves an SRU to bionic & focal.

  [Fix]

  Backport a commit from upstream:

  From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001
  From: Frediano Ziglio 
  Date: Wed, 29 Jan 2020 09:06:54 +
  Subject: [PATCH] Fix poll_for_response race condition

  In poll_for_response is it possible that event replies are skipped
  and a more up to date message reply is returned.
  This will cause next poll_for_event call to fail aborting the program.

  This was proved using some slow ssh tunnel or using some program
  to slow down server replies (I used a combination of xtrace and strace).

  How the race happens:
  - program enters into poll_for_response;
  - poll_for_event is called but the server didn't still send the reply;
  - pending_requests is not NULL because we send a request (see call
to  append_pending_request in _XSend);
  - xcb_poll_for_reply64 is called from poll_for_response;
  - xcb_poll_for_reply64 will read from server, at this point
server reply with an event (say sequence N) and the reply to our
last request (say sequence N+1);
  - xcb_poll_for_reply64 returns the reply for the request we asked;
  - last_request_read is set to N+1 sequence in poll_for_response;
  - poll_for_response returns the response to the request;
  - poll_for_event is called (for instance from another poll_for_response);
  - event with sequence N is retrieved;
  - the N sequence is widen, however, as the "new" number computed from
last_request_read is less than N the number is widened to N + 2^32
(assuming last_request_read is still contained in 32 bit);
  - poll_for_event enters the nested if statement as req is NULL;
  - we compare the widen N (which now does not fit into 32 bit) with
request (which fits into 32 bit) hitting the throw_thread_fail_assert.

  To avoid the race condition and to avoid the sequence to go back
  I check again for new events after getting the response and
  return this last event if present saving the reply to return it
  later.

  To test the race and the fix it's helpful to add a delay (I used a
  "usleep(5000)") before calling xcb_poll_for_reply64.

  Original patch written by Frediano Ziglio, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34

  Reworked primarily for readability by Peter Hutterer, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53

  Signed-off-by: Peter Hutterer 

  bionic needs another commit so that the real fix applies.

  [Test case]

  It's a race condition, the SRU sponsor (tjaalton) does not have a test
  case for this, but the bug subscribers seem to.

  
  [Where things could go wrong]

  In theory there might be a case where a race still happens, but since
  this has been upstream for a year now with no follow-up commits, it's
  safe to assume that there are no regressions.

  
  --

  STEPS TO REPRODUCE
  ==
  The bug seems to occur when clicking on a file or folder. It is random and 
difficult to provide clear steps to reproduce. It is, however, a common 
situation.

  EXPECTED RESULTS
  
  pcmanfm works without problem.

  ACTUAL RESULTS
  ==
  All pcmanfm windows become unresponsive, though background processes (e.g. 
copying) may continue without problem. with the same error message in 
~/.cache/lxsession/LXDE/run.log:

  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not 
been called
  [xcb] Aborting, sorry about that.
  pcmanfm: xcb_io.c:259: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.
  ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6
  ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload

  (note the timestamp on the message will vary)

  

[Touch-packages] [Bug 1958594] Re: Boot error: libgcc_s.so.1 must be installed for pthread_exit to work

2022-02-02 Thread Chris Halse Rogers
Are you guaranteed to be able to know the set of architecture(s) of
libgcc_s needed? That's what's prevented me from suggesting a patch like
that.

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

Title:
  Boot error: libgcc_s.so.1 must be installed for pthread_exit to work

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in initramfs-tools source package in Jammy:
  Confirmed

Bug description:
  [Bug description]

  On a jammy installation, which was upgraded from focal, after a full-
  upgrade and a reboot,

  I enter the LUKS password to decrypt the disk. Then I get the
  following error:

  libgcc_s.so.1 must be installed for pthread_exit to work

  After the error is shown, the system asks for the password again
  (which never works, always throwing the same error).

  [Root cause]

  I was able to decrypt the disk with the same password by booting from
  a live usb. Which allowed further investigation.

  The error shown in the LUKS password prompt menu comes from
  https://github.com/bminor/glibc/blob/glibc-2.34/nptl/pthread_exit.c#L31-L32, 
which indeed shows that pthread_exit fails when libgcc_s.so.1 is missing.

  From
  
https://git.launchpad.net/ubuntu/+source/initramfs-tools/tree/hook-functions?h=import/0.140ubuntu10#n260,
  we noticed that libgcc_s.so.1 is only copied if

  1) copy_exec is called for a binary directly linked to libgcc_s.so.1, or
  2) copy_exec is called for a binary linked to libpthread

  The cryptsetup initramfs hook, calls copy_exec for /sbin/cryptsetup,
  which is linked to libargon2.so.1, which is linked to libpthread.so.0.
  This covers case (2) above. As a consequence, libgcc_s.so.1 is copied
  to the initrd image and the error reported here is not seen.

  However, since glibc 2.34, libpthread is shipped within glibc, and the
  binaries are no longer linked to libpthread.so.0. As a consequence, an
  argon2 package built with glibc 2.32 will no longer be linked to
  libpthread.so.0 and libgcc_s.so.1 will no longer be copied to the
  initrd image. Triggering the reported error.

  This can be verified in these two argon2 builds, from the same
  sources, but with different glibc versions:

  
https://launchpad.net/ubuntu/+source/argon2/0~20171227-0.2build21.04.0/+build/21066610
  
https://launchpad.net/ubuntu/+source/argon2/0~20171227-0.2build22/+build/22255217

  Still lvm2 is a seeded package, which Recommends thin-provisioning-
  tools. thin-provisioning-tools ships a initramfs hook that calls
  copy_exec for /usr/sbin/pdata_tools, which is directly linked to
  libgcc_s.so.1. This covers the case (1) above and should suffice to
  ensure the boot process works properly.

  Since thin-provisioning-tools is just a recommends for lvm2, it could
  be removed from the system (and indeed, for some reason, was not
  present in my focal=>jammy installation). In this case, a new kernel
  installation should trigger the reported error.

  [Reproducer]

  - Install jammy with a LUKS encrypted disk
  - remove thin-provisioning-tools
  - perform a full-upgrade (make sure the kernel was upgraded or run 
update-initramfs manually)
  - reboot and verify you can no longer get past the decrypt password prompt 
screen

  [Workaround]

  A workaround for anyone affected would be to install thin-
  provisioning-tools and run update-initramfs.

  [Impact]

  Users upgrading from focal to jammy will eventually be locked out of
  their systems in case they are using LUKS encryption.

  [Additional information]

  While this issue is similar to
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1861757,
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950254, and
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950551,
  This is a different bug, with a different root cause.

  Thanks to sergiodj for the pairing session on the root cause analysis.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958594/+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 1958806] [NEW] Fails to include libgcc, resulting in cryptsetup failures

2022-01-23 Thread Chris Halse Rogers
Public bug reported:

I recently rebooted my laptop, and couldn't unlock my (cryptsetup-
managed) root filesystem; after entering my passphrase, the plymouth
prompt would always say “unable to unlock /dev/nvme0n1p3_crypt”.

Dropping to text mode, I can see that cryptsetup is failing with a message like:
"libgcc_s: missing library, needed for pthread_exit”.

Indeed, in the recovery console cryptsetup will immediately crash with
that message.

I note that initramfs-tools already has some logic for detecting when
libgcc_s is needed but isn't in DT_NEEDED, but this seems to have gone
out of date.

Adding an initramfs hook to manually add libgcc_s to the initramfs
results in a bootable system again.

I don't reboot this laptop often, so I unfortunately can't narrow down
*when* this started failing better than “sometime in the last 2 months”.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: initramfs-tools 0.140ubuntu10
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu75
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 24 12:08:34 2022
InstallationDate: Installed on 2021-06-26 (211 days ago)
InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
PackageArchitecture: all
SourcePackage: initramfs-tools
UpgradeStatus: Upgraded to jammy on 2021-10-28 (87 days ago)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  Fails to include libgcc, resulting in cryptsetup failures

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I recently rebooted my laptop, and couldn't unlock my (cryptsetup-
  managed) root filesystem; after entering my passphrase, the plymouth
  prompt would always say “unable to unlock /dev/nvme0n1p3_crypt”.

  Dropping to text mode, I can see that cryptsetup is failing with a message 
like:
  "libgcc_s: missing library, needed for pthread_exit”.

  Indeed, in the recovery console cryptsetup will immediately crash with
  that message.

  I note that initramfs-tools already has some logic for detecting when
  libgcc_s is needed but isn't in DT_NEEDED, but this seems to have gone
  out of date.

  Adding an initramfs hook to manually add libgcc_s to the initramfs
  results in a bootable system again.

  I don't reboot this laptop often, so I unfortunately can't narrow down
  *when* this started failing better than “sometime in the last 2
  months”.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: initramfs-tools 0.140ubuntu10
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 24 12:08:34 2022
  InstallationDate: Installed on 2021-06-26 (211 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: Upgraded to jammy on 2021-10-28 (87 days ago)

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

2022-01-18 Thread Chris Halse Rogers
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/1927192

Title:
  gdb ftbfs on armhf, testsuite timeouts

Status in gdb:
  Incomplete
Status in gdb package in Ubuntu:
  Fix Released
Status in glibc package in Ubuntu:
  Fix Released
Status in gdb source package in Focal:
  Fix Released
Status in glibc source package in Focal:
  Fix Committed
Status in gdb source package in Groovy:
  Won't Fix
Status in glibc source package in Groovy:
  Won't Fix
Status in gdb source package in Hirsute:
  Won't Fix
Status in glibc source package in Hirsute:
  Won't Fix
Status in gdb source package in Impish:
  Fix Released
Status in glibc source package in Impish:
  Fix Released

Bug description:
  [Impact]

  * Gdb can't set some breakpoints in ld.so on armhf when libc6-dbg is
  not installed.

  [Test Plan]

  * Check that ld.so is not stripped on armhf:
  $  /lib/*/ld-2.31.so
  libc6/lib/arm-linux-gnueabihf/ld-2.31.so: ELF 32-bit LSB shared object, ARM, 
EABI5 version 1 (SYSV), dynamically linked, 
BuildID[sha1]=e20a43bff0c4d2aa7f508c93eadad973ea0c0af9, with debug_info, not 
stripped

  * Check that ld.so is stripped on amd64:

  $ file /lib/x86_64-linux-gnu/ld-2.31.so
  /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, 
version 1 (SYSV), dynamically linked, 
BuildID[sha1]=ea85fcb25ee4c4c9e7b180924ab4a44257a9547a, stripped

  [Where problems could occur]

  * The fix is not stripping ld.so on armhf. Not stripping it comes with
  a notable increase in file size and it may be performance critical
  109K stripped vs 1.3M unstripped. Accidentally ld.so could be left
  unstripped on other architectures, but the test plan covers checking
  that, at least on amd64. Other than those not stripping ld.so should
  not cause any issue.

  [Original Bug Text]

  see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3

  $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep 
'(timeout)'|wc -l
  10451

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1927192/+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 1952421] Re: Issue on sshd finds correct private key for a certificate when using ssh-agent

2022-01-04 Thread Chris Halse Rogers
For SRU verification we require that the actual package from the
-proposed archive is tested. This is to avoid the chance that the patch
is mis-applied in the package uploaded to the archive, or that the
archive build environment differs in a way that affects the patch.

We'll also need this to be verified for Hirsute and Impish before we can
release it for Focal, to ensure that upgrades do not regress this bug.

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

Title:
  Issue on sshd finds correct private key for a certificate when using
  ssh-agent

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Focal:
  Fix Committed
Status in openssh source package in Hirsute:
  Fix Committed
Status in openssh source package in Impish:
  Fix Committed

Bug description:
  Reported as https://bugzilla.mindrot.org/show_bug.cgi?id=3254 upstream

  [Impact]

   * HostCertificate and HostKeyAgent are not working together in sshd due 
 to a mismatched certificate's public key and private key. The function `  
`sshkey_equal_public()`` incorrectly compares the certificate's public 
key with a private key, never finding a match. The impact is that sshd 
cannot use said certificate *even though* its private key is indeed in 
ssh-agent.

  * What it should do is compare the certificate's public key with a
  public key in `sensitive_data`.

  * Having this SRU-ed is a direct ask from one of the major cloud partners. 
They are currently using a customised version of the package to work 
around this issue, and we would like them to use a package directly from 
our own archive.

   * Looping through sensitive_data.host_pubkeys[j] *instead* of 
 sensitive_data.host_keys[j] fixes the issue

  [https://github.com/openssh/openssh-portable/blob/V_8_4/sshd.c#L1936]

  /* Find matching private key */
   for (j = 0; j < options.num_host_key_files; j++) {
    if (sshkey_equal_public(key,
     sensitive_data.host_keys[j])) {
     sensitive_data.host_certificates[j] = key;
  break;
     }
   }

  vs.

  /* Find matching private key */
   for (j = 0; j < options.num_host_key_files; j++) {
    if (sshkey_equal_public(key,
     sensitive_data.host_pubkeys[j])) {
     sensitive_data.host_certificates[j] = key;
  break;
     }
   }
   

  [Test Plan]

   * Due to the empirical nature of this bug, the test is quite straight 
 forward. *Without* the fix, one cannot use certificates to authenticate 
 successfully (e.g. ``sshd -c /path/to/certificate.pem``)
 whereas with the fix (assuming the certificate matches a host key) you 
 can create a channel.
 
  [Where problems could occur]

   * This has already been fixed both upstream and in Jammy without issue. 
 However, if a regression where to happen it would probably be in one of 
 two ways:
   
   * A dependency/reverse-dependency issue stemming from the version 
 bump that will happen if this fix is ported. We mitigate this risk 
 by testing for these exact types of regression, 
 and by selecting carefully what to label this new version.
 
   * Accidentally breaking a set up that was made to work around this 
 bug in the first place. The risk of this is lower, as the most 
 likely fix is the one being implemented here anyway.  Though
 to mitigate this more we can describe exactly what is happening 
 with the fix in the changelog.

  
  This affects every version of openssh back until Focal, at least.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1952421/+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 1927192] Re: gdb ftbfs on armhf, testsuite timeouts

2021-12-14 Thread Chris Halse Rogers
The gdb upload looks fine; I presume it wants to be marked block-
proposed, though?

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

Title:
  gdb ftbfs on armhf, testsuite timeouts

Status in gdb:
  Incomplete
Status in gdb package in Ubuntu:
  Fix Released
Status in glibc package in Ubuntu:
  Fix Released
Status in gdb source package in Focal:
  Fix Committed
Status in glibc source package in Focal:
  Fix Committed
Status in gdb source package in Groovy:
  Won't Fix
Status in glibc source package in Groovy:
  Won't Fix
Status in gdb source package in Hirsute:
  Won't Fix
Status in glibc source package in Hirsute:
  Won't Fix
Status in gdb source package in Impish:
  Fix Released
Status in glibc source package in Impish:
  Fix Released

Bug description:
  [Impact]

  * Gdb can't set some breakpoints in ld.so on armhf when libc6-dbg is
  not installed.

  [Test Plan]

  * Check that ld.so is not stripped on armhf:
  $  /lib/*/ld-2.31.so
  libc6/lib/arm-linux-gnueabihf/ld-2.31.so: ELF 32-bit LSB shared object, ARM, 
EABI5 version 1 (SYSV), dynamically linked, 
BuildID[sha1]=e20a43bff0c4d2aa7f508c93eadad973ea0c0af9, with debug_info, not 
stripped

  * Check that ld.so is stripped on amd64:

  $ file /lib/x86_64-linux-gnu/ld-2.31.so
  /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, 
version 1 (SYSV), dynamically linked, 
BuildID[sha1]=ea85fcb25ee4c4c9e7b180924ab4a44257a9547a, stripped

  [Where problems could occur]

  * The fix is not stripping ld.so on armhf. Not stripping it comes with
  a notable increase in file size and it may be performance critical
  109K stripped vs 1.3M unstripped. Accidentally ld.so could be left
  unstripped on other architectures, but the test plan covers checking
  that, at least on amd64. Other than those not stripping ld.so should
  not cause any issue.

  [Original Bug Text]

  see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3

  $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep 
'(timeout)'|wc -l
  10451

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1927192/+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 1927192] Re: gdb ftbfs on armhf, testsuite timeouts

2021-12-14 Thread Chris Halse Rogers
Hello Matthias, or anyone else affected,

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

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

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

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

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

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

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

Title:
  gdb ftbfs on armhf, testsuite timeouts

Status in gdb:
  Incomplete
Status in gdb package in Ubuntu:
  Fix Released
Status in glibc package in Ubuntu:
  Fix Released
Status in gdb source package in Focal:
  Fix Committed
Status in glibc source package in Focal:
  Fix Committed
Status in gdb source package in Groovy:
  Won't Fix
Status in glibc source package in Groovy:
  Won't Fix
Status in gdb source package in Hirsute:
  Won't Fix
Status in glibc source package in Hirsute:
  Won't Fix
Status in gdb source package in Impish:
  Fix Released
Status in glibc source package in Impish:
  Fix Released

Bug description:
  [Impact]

  * Gdb can't set some breakpoints in ld.so on armhf when libc6-dbg is
  not installed.

  [Test Plan]

  * Check that ld.so is not stripped on armhf:
  $  /lib/*/ld-2.31.so
  libc6/lib/arm-linux-gnueabihf/ld-2.31.so: ELF 32-bit LSB shared object, ARM, 
EABI5 version 1 (SYSV), dynamically linked, 
BuildID[sha1]=e20a43bff0c4d2aa7f508c93eadad973ea0c0af9, with debug_info, not 
stripped

  * Check that ld.so is stripped on amd64:

  $ file /lib/x86_64-linux-gnu/ld-2.31.so
  /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, 
version 1 (SYSV), dynamically linked, 
BuildID[sha1]=ea85fcb25ee4c4c9e7b180924ab4a44257a9547a, stripped

  [Where problems could occur]

  * The fix is not stripping ld.so on armhf. Not stripping it comes with
  a notable increase in file size and it may be performance critical
  109K stripped vs 1.3M unstripped. Accidentally ld.so could be left
  unstripped on other architectures, but the test plan covers checking
  that, at least on amd64. Other than those not stripping ld.so should
  not cause any issue.

  [Original Bug Text]

  see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3

  $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep 
'(timeout)'|wc -l
  10451

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1927192/+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 1951470] Update Released

2021-12-07 Thread Chris Halse Rogers
The verification of the Stable Release Update for qtwebkit-opensource-
src 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 qtwebkit-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1951470

Title:
  webkit javascript segmentation fault

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in qtwebkit-opensource-src package in Ubuntu:
  Fix Released
Status in qtwebkit-opensource-src source package in Focal:
  Fix Released
Status in qtwebkit-opensource-src source package in Hirsute:
  Fix Released
Status in qtwebkit-opensource-src source package in Impish:
  Fix Released
Status in qtwebkit-opensource-src source package in Jammy:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]

   * WebKit Javascript engine is causing a segmentation fault on big
  endian (s390x) systems.

   * This happens for example when transferring an html to a pdf file
  using wkhtmltopdf.

   * The fix is relatively simple with changing loadisFromInstruction to 
loadpFromInstruction
 in macro getProperty(slow), which solves this unpleasant situation.

   * The JIT ocde is 32bit (even on 64bit systems),
 hence is crucial to make sure the lower part of a 64bit value is taken on 
big endian systems.

  [Test Plan]

   * Testing is very straight forward by following these steps:

   * install the following packages (incl. their dependencies):
 $ sudo apt install libqt5webkit5 wkhtmltopdf

   * create an html file like this:
 $ vi index.html
 $ cat index.html
 
 
   
   
 
   
 
   
 

   * create a JavaScript file like this:
 $ vi min.js
 $ cat min.js
 var i = Math.max

   * call wkhtmltopdf to process the local files:
 $ wkhtmltopdf --enable-local-file-access index.html test.pdf

   * if it's broken one gets this output:
 Loading page (1/2)
 Segmentation fault (core dumped) ] 50%
 and no pdf file was generated:
 $ ls *.pdf
 ls: cannot access '*.pdf': No such file or directory

   * in case it's fixed one gets this output:
 Loading page (1/2)
 Printing pages (2/2)   
 Done   
 and a pdf file was generated and in placed in the current directory (with 
more than 0 bytes size):
 $ ls -l ./*.pdf
 -rw-rw-r-- 1 ubuntu ubuntu 1339 Nov 24 11:48 ./test.pdf

  [Where problems could occur]

   * While this issue only affects big endian systems (like s390x),
 a bad fix may have an impact on little endian systems, too
 for example in case the wrong function got used in the macro.

   * But loadpFromInstruction is known to work for LE and BE systems;

   * and on top cross-architecture builds were done:
 https://launchpad.net/~fheimes/+archive/ubuntu/lp1951470

   * and tested on s390x (if the fix works) and on non-s390x (regression
  testing).

   * The changes are otherwise very limited, just:
 macro getProperty(slow)
 -loadisFromInstruction(6, t1)
 +loadpFromInstruction(6, t1)
 hence I think there is not much more to say.

  [Other Info]
   
   * The maintainer of the Debian packages (Dmitry Shachnev)
 is going to add this to the Debian package, too.

   * This issue affects Ubuntu jammy, impish, hirsute and focal - SRUs
  are ongoing.

   * The issue does not occur with the very latest upstream version anymore,
 and was fixed in a similar way as part of a commit
 that fixes numerous other CLoop issues on top:
 "Fix all CLoop JSC test failures (including some LLInt bugs due to recent 
bytecode format change)."
 commit 3fdde71c7d95d758a61fcbc4c58168616794c102

  __

  == Comment: #0 - Andreas Krebbel  - 2021-11-15 
09:29:44 ==
  ---Problem Description---
  Segmentation fault from WebKit Javascript engine

  Contact Information = andreas.kreb...@de.ibm.com

  ---uname output---
  Linux 193438490afd 5.8.15-301.fc33.s390x #1 SMP Thu Oct 15 15:55:57 UTC 2020 
s390x s390x s390x GNU/Linux

  Machine Type = IBM Z

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   index.html:
  
  
    
    

    
  
    
  

  min.js:
  var i = Math.max

  wkhtmltopdf index.html test.pdf
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
  Loading page (1/2)
  Segmentation fault (core dumped) ] 17%

  Userspace tool common name: wkhtmltopdf

  The userspace tool has the 

[Touch-packages] [Bug 1942685] Re: pulseaudio crashed with SIGSEGV in _IceTransClose()

2021-11-30 Thread Chris Halse Rogers
Checking
https://errors.ubuntu.com/problem/877172e07ed9f86b0674cd458a5aaf24b37fb01e
I see that there are no reports of this for 1:15.0+dfsg1-1ubuntu2.1 in
Impish and, reassuringly, no reports of this for 1:15.0+dfsg1-1ubuntu3
in Jammy, either.

I think that's sufficient to mark this as verified.

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

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

Title:
  pulseaudio crashed with SIGSEGV in _IceTransClose()

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Impish:
  Fix Released

Bug description:
  * Impact

  The pulseaudio service sometime segfaults on session closing which
  trigger a bug report dialog

  * Test plan

  Log out of a desktop session and back in, there should be no error
  prompt

  The issue isn't triggered only randomly it seems so it might be easier to 
check that reports stop on
  https://errors.ubuntu.com/problem/877172e07ed9f86b0674cd458a5aaf24b37fb01e

  * Where problems could occur

  The change is in the X session closing handling so shouldn't impact on
  normal use, if incorrect the fix could lead to increase the chance of
  hitting the segfault when an Xsession is closed

  
  ---

  Installing Xubuntu Impish daily ISO 04092021

  After install I rebooted - applied updates and then rebooted again-

  the errors (pulseaudio crashed with SIGSEGV in _IceTransClose() )
  occurred after logging in.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
  Uname: Linux 5.13.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kx  847 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Sat Sep  4 16:43:45 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-09-04 (0 days ago)
  InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210904)
  ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal
  Signal: 11
  SourcePackage: pulseaudio
  StacktraceTop:
   _IceTransClose () from /lib/x86_64-linux-gnu/libICE.so.6
   _IceFreeConnection () from /lib/x86_64-linux-gnu/libICE.so.6
   IceCloseConnection () from /lib/x86_64-linux-gnu/libICE.so.6
   SmcCloseConnection () from /lib/x86_64-linux-gnu/libSM.so.6
   ?? () from /usr/lib/pulse-15.0+dfsg1/modules/module-x11-xsmp.so
  Title: pulseaudio crashed with SIGSEGV in _IceTransClose()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 12/23/2020
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DKCN51WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo V14-IIL
  dmi.ec.firmware.release: 1.51
  dmi.modalias: 
dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:skuLENOVO_MT_82C4_BU_idea_FM_V14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL:
  dmi.product.family: V14-IIL
  dmi.product.name: 82C4
  dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL
  dmi.product.version: Lenovo V14-IIL
  dmi.sys.vendor: LENOVO
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1942685/+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 1942685] Update Released

2021-11-30 Thread Chris Halse Rogers
The verification of the Stable Release Update for pulseaudio 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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1942685

Title:
  pulseaudio crashed with SIGSEGV in _IceTransClose()

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Impish:
  Fix Released

Bug description:
  * Impact

  The pulseaudio service sometime segfaults on session closing which
  trigger a bug report dialog

  * Test plan

  Log out of a desktop session and back in, there should be no error
  prompt

  The issue isn't triggered only randomly it seems so it might be easier to 
check that reports stop on
  https://errors.ubuntu.com/problem/877172e07ed9f86b0674cd458a5aaf24b37fb01e

  * Where problems could occur

  The change is in the X session closing handling so shouldn't impact on
  normal use, if incorrect the fix could lead to increase the chance of
  hitting the segfault when an Xsession is closed

  
  ---

  Installing Xubuntu Impish daily ISO 04092021

  After install I rebooted - applied updates and then rebooted again-

  the errors (pulseaudio crashed with SIGSEGV in _IceTransClose() )
  occurred after logging in.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
  Uname: Linux 5.13.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kx  847 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Sat Sep  4 16:43:45 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-09-04 (0 days ago)
  InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210904)
  ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal
  Signal: 11
  SourcePackage: pulseaudio
  StacktraceTop:
   _IceTransClose () from /lib/x86_64-linux-gnu/libICE.so.6
   _IceFreeConnection () from /lib/x86_64-linux-gnu/libICE.so.6
   IceCloseConnection () from /lib/x86_64-linux-gnu/libICE.so.6
   SmcCloseConnection () from /lib/x86_64-linux-gnu/libSM.so.6
   ?? () from /usr/lib/pulse-15.0+dfsg1/modules/module-x11-xsmp.so
  Title: pulseaudio crashed with SIGSEGV in _IceTransClose()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 12/23/2020
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DKCN51WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo V14-IIL
  dmi.ec.firmware.release: 1.51
  dmi.modalias: 
dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:skuLENOVO_MT_82C4_BU_idea_FM_V14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL:
  dmi.product.family: V14-IIL
  dmi.product.name: 82C4
  dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL
  dmi.product.version: Lenovo V14-IIL
  dmi.sys.vendor: LENOVO
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1942685/+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 1951667] Re: [SRU] pulseaudio: restore hdmi audio be active output after resume

2021-11-30 Thread Chris Halse Rogers
Hello Hui, or anyone else affected,

Accepted pulseaudio into focal-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu3.13 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.

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

Title:
  [SRU] pulseaudio: restore hdmi audio be active output after resume

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Hirsute:
  Won't Fix
Status in pulseaudio source package in Impish:
  Fix Committed
Status in pulseaudio source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  On the machines with legacy HDA audio driver, when users plug a hdmi/dp 
monitor, the active output device is still speaker, need users to manually 
select the hdmi, then the hdmi audio will be the users' preference, once it is 
plugged, it should become the active output automatically. But with the current 
PA, after reboot and suspend/resume, the hdmi can't change to be active output 
automatically anymore.

  [Fix]
  Backport an upstream fix, this will fix the issue of "preferred ports being 
cleaned by a mistake"

  [Test]
  On a machine with legacy HDA audio driver, install the patched pulseaudio, 
then run 'rm ~/.config/pulse/*; reboot', plug a hdmi monitor, select the hdmi 
audio to be active, with the hdmi monitor plugged and reboot, suspend and 
resume, check what is the active output, it is still the hdmi audio.

  [Where problems could occur]
  This patch is in the card-restore.c, if it could introduce regression, it 
will be on the default active input/output devices, for example, users select a 
input or output device to be active, after reboot, if those devices are 
available, they should be active, but they could be replaced by other devices 
if a regression is introduced. But this possibility is very low since we tested 
the patch on a couple of desktop and laptop machines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1951667/+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 1949553] Please test proposed package

2021-11-30 Thread Chris Halse Rogers
Hello Timo, or anyone else affected,

Accepted libdrm into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libdrm/2.4.107-8ubuntu1~20.04.1 in
a few hours, and then in the -proposed repository.

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

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

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

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

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

Title:
  Backport packages for 20.04.4 HWE stack

Status in libdrm package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libdrm source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  In Progress
Status in xorg-server source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 20.04.4 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  libdrm: adds some new api, no changes to old stuff

  llvm-13: a new package, no regression potential on it's own

  mesa: a new major release, but we'll pull the final stable release of
  21.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release, 1.20.x series is in deep maintenance
  mode, so there should be little chance of breakage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1949553/+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 1949553] Re: Backport packages for 20.04.4 HWE stack

2021-11-30 Thread Chris Halse Rogers
Well, that's a compelling reason.

** Changed in: libdrm (Ubuntu Focal)
   Status: Incomplete => Fix Committed

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

Title:
  Backport packages for 20.04.4 HWE stack

Status in libdrm package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libdrm source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  In Progress
Status in xorg-server source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 20.04.4 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  libdrm: adds some new api, no changes to old stuff

  llvm-13: a new package, no regression potential on it's own

  mesa: a new major release, but we'll pull the final stable release of
  21.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release, 1.20.x series is in deep maintenance
  mode, so there should be little chance of breakage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1949553/+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 1952083] Re: Add support for Beige Goby

2021-11-25 Thread Chris Halse Rogers
Hello Timo, or anyone else affected,

Accepted mesa into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/21.0.3-0ubuntu0.3~20.04.5 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: mesa (Ubuntu Focal)
   Status: New => 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 mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1952083

Title:
  Add support for Beige Goby

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

Bug description:
  Impact]

  New hardware support for AMD's Beige Goby needs a commit backported to
  mesa. This is only needed on focal, skipping hirsute (no kernel
  support there). Fixed in impish and up.

  [Test plan]

  Install updates, boot a BG machine and check that the desktop has full
  hardware acceleration.

  [Where problems could occur]

  Mesa adds a single commit for enabling BEIGE_GOBY, hard to see what
  could go wrong.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1952083/+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 1949553] Re: Backport packages for 20.04.4 HWE stack

2021-11-23 Thread Chris Halse Rogers
@Timo: I notice the libdrm backport drops the valgrind integration. I
know it's disabled in (at least) impish, but is there any particular
reason for it to be disabled in the focal backport?

It seems pretty unlikely that anyone would notice, but the diff required
to keep the valgrind annotations enabled also looks small, so maybe we
should?

** Changed in: libdrm (Ubuntu Focal)
   Status: In Progress => Incomplete

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

Title:
  Backport packages for 20.04.4 HWE stack

Status in libdrm package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libdrm source package in Focal:
  Incomplete
Status in mesa source package in Focal:
  In Progress
Status in xorg-server source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 20.04.4 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  libdrm: adds some new api, no changes to old stuff

  llvm-13: a new package, no regression potential on it's own

  mesa: a new major release, but we'll pull the final stable release of
  21.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release, 1.20.x series is in deep maintenance
  mode, so there should be little chance of breakage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1949553/+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 1949553] Re: Backport packages for 20.04.4 HWE stack

2021-11-23 Thread Chris Halse Rogers
Hello Timo, or anyone else affected,

Accepted xorg-server into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:1.20.13-1ubuntu1~20.04.1 in a few hours, and then in the
-proposed repository.

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

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

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

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

** Changed in: xorg-server (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 libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1949553

Title:
  Backport packages for 20.04.4 HWE stack

Status in libdrm package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libdrm source package in Focal:
  In Progress
Status in mesa source package in Focal:
  In Progress
Status in xorg-server source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 20.04.4 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  libdrm: adds some new api, no changes to old stuff

  llvm-13: a new package, no regression potential on it's own

  mesa: a new major release, but we'll pull the final stable release of
  21.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release, 1.20.x series is in deep maintenance
  mode, so there should be little chance of breakage

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

2021-11-16 Thread Chris Halse Rogers
The verification of the Stable Release Update for rsync 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 rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1896251

Title:
  rsync --delete-missing-args fails with "error: protocol
  incompatibility"

Status in rsync package in Ubuntu:
  Fix Released
Status in rsync source package in Xenial:
  Won't Fix
Status in rsync source package in Bionic:
  Fix Committed
Status in rsync source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  Rsync crashes when using --delete-missing-args on a file with a
  missing parent folder.

  Backporting this fix will allow users to delete missing source args
  when some files in the list have missing parent folders without
  interruption.

  This is fixed by patching in an upstream commit that allows files with
  missing parent folders to be handled without aborting.

  [Test Plan]

  # lxc launch images:ubuntu/focal builder
  # lxc exec builder bash
  # apt update
  # apt dist-upgrade
  # apt install -y rsync
  # mkdir -p a/1 b/1; echo "/1/2/3" > list
  # rsync --dry-run --stats -Pav --delete-missing-args --files-from=list a b

  * This should crash with exit code 2 after printing the following:

  building file list ...
   0 files...
  file has vanished: "/root/a/1/2"
  2 files to consider
  ABORTING due to invalid path from sender: 1/2/3
  rsync error: protocol incompatibility (code 2) at generator.c(1278) 
[generator=3.1.3]

  [Where problems could occur]

  Since the remove operation will now continue when files in the list
  have missing parent folders, other errors and warnings with different
  behaviors could arise instead.

  A warning that may arise the most often in these situations is the
  following:

  warning: some files vanished before they could be transferred (code
  24) at main.c(1207) [sender=3.1.3]

  This appears at the end of the above test case with the new code. The
  behavior is expected, but it may cause regressions due to changes in
  the output of certain use cases.

  [Original Description]

  Running

 rsync --delete-missing-args --files-from=...

  fails with error message like

  ABORTING due to invalid path from sender: dir1/dir2/dir3
  rsync error: protocol incompatibility (code 2) at generator.c(1271) 
[generator=3.1.2]

  if the listed directories are trying to delete full subtree of files.

  According to https://bugzilla.samba.org/show_bug.cgi?id=12569 this has
  been fixed in version 3.2.2.

  See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863334

  Could you update the rsync package or backport the fix?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: rsync 3.1.2-2.1ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-lowlatency 5.4.55
  Uname: Linux 5.4.0-47-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Sep 18 18:27:53 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-01-05 (621 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1896251/+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 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.

2021-10-26 Thread Chris Halse Rogers
Ok. For clarity, my understanding of these patches are that they do the 
following things:
1) Add a feature to ModemManager to support uploading firmware to these modems
2) Increase a timeout that was found to be insufficient when doing a firmware 
update
3) Add a bunch of mappings from SIM->Carrier

And then in response to potential concerns:
(1) is a straight feature addition, and the associated code will only be called 
if an external component connects to modemmanager requesting a firmware upload. 
This is not expected to change any existing behaviours.
(2) is low-risk

It's not clear to me whether (3) is expected to change existing
behaviours at all.

Is this understanding correct?

Assuming (3) is not expected to change existing behaviour this looks
like it would be acceptable under the hardware-enablement SRU policy.

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

Title:
  Support manual firmware upgrading for Foxconn and Quectel modems.

Status in OEM Priority Project:
  In Progress
Status in modemmanager package in Ubuntu:
  New

Bug description:
  [Impact]

  The modem certification requires that different modem firmware is used for 
different network carrier.
  This needs the firmware upgrading capability during the modem certification 
process.

  The modem manufacture vendors (Foxconn and Quectel) provided utilities to do 
modem's firmware upgrading manually.(LP#1943774, LP#1943780)
  These utilities are verified to be working when the recent versions(> v 
1.18.2) of ModemManager are used with.

  To support manual firmware upgrading on the current Focal release which is 
using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2.
  The requested upstream patches are listed as below:
  * for Quectel EM160 4G
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2
  * for Foxconn T99W175
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9
    
**https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154

  The firmware upgrading was verified using the patched ModemManager v 1.16.6 
with the following 2 modems:
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem

  [Test Plan]

  1. Install the Ubuntu image.
  2. Boot and login the system.
  3. Prepare the modem’s firmware and install the firmware upgrading 
application provided by Foxconn and Quectel
  4. Using the firmware upgrading application to upgrade the modem’s firmware
  5. Verify if the modem’s firmware upgrading is successful
  6. Reboot
  7. Verify if the upgraded modem firmware is still working

  [Where problems could occur]

  The requested upstream patches are for these 2 specific modems.
  This should not affect existing generic functions and other modems.

  [Other Info]

  The firmware and the upgrading utilities can be downloaded from the following 
link:
  * LP#1943774 for Quectel modems
  * LP#1943780 for Foxconn modems

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1946096/+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 1662620] Re: "ip addr add" permits illegal labels

2021-10-19 Thread Chris Halse Rogers
Hm. It's not clear what the actual user impact of this is?

Reading from the original description, it seems that if a user uses an
invalid label to set one address and *also* uses a valid label to set
another address *then* tools can be confused?

“Our parser is actually more lenient than the manpage states” on its own
is definitely not SRU-worthy, but if it breaks other tools then maybe?

On the other hand, from the bug it looks like if you *don't* mix valid
and invalid labels then everything actually works? So this would
potentially be breaking currently working setups?

I think we need more information before determining whether this should
be accepted as an SRU.

** Changed in: iproute2 (Ubuntu Bionic)
   Status: Triaged => Incomplete

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

Title:
  "ip addr add" permits illegal labels

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Incomplete

Bug description:
  [Impact]

   * The filter on label names does not match the intention
 by upstream nor the description in the man page

   * Fix by backporting upstream fix that strengthens the check

  [Test Plan]

  Bad case:
  root@b:~# ip addr add 1.1.1.1 label test1 dev eth0
  "dev" (eth0) must match "label" (test1).
  root@b:~# ip addr add 1.1.1.1 label eth0-test dev eth0
  root@b:~# ip addr show dev eth0 | grep test
  inet 1.1.1.1/32 scope global eth0-test

  With the fix it should look like:
  root@i:~# ip addr add 1.1.1.1 label test1 dev eth0
  "label" (test1) must match "dev" (eth0) or be prefixed by "dev" with a colon.
  root@i:~# ip addr add 1.1.1.1 label eth0-test dev eth0
  "label" (eth0-test) must match "dev" (eth0) or be prefixed by "dev" with a 
colon.
  root@i:~# ip addr show dev eth0 | grep test

  [Where problems could occur]

   * While the fix indeed "corrects" behavior I must say that if someone 
 relied on the non-intended behavior it would now break e.g. his 
 scripting or automation.

  [Other Info]
   
   * It was too easy to fix and too long dormant to ignore it further,
 but if the SRU team says this is too much regression risk relative to 
 the gain we will mark it Won't Fix based on that decision.

  
  ---

  ip-address(8) manpage states:

    label NAME
  Each address may be tagged with a label string.  In order to preserve 
compatibility with Linux-2.0 net aliases, this string must coincide with the 
name of the device or must be prefixed with the device name followed by colon.

  But you can omit the colon, "ip addr add" is ONLY checking the label
  is prefixed with the device:

  # ip addr add 1.1.1.1 label test1 dev eth0
  "dev" (eth0) must match "label" (test1).

  # ip addr add 1.1.1.2 label eth0-test2 dev eth0

  # ip addr add 1.1.1.3 label eth0:test3 dev eth0

  Now ifconfig becomes confused about eth0-test2:

  # ifconfig eth0-test2
  eth0-test2: error fetching interface information: Device not found

  # ifconfig eth0:test3
  eth0:test3 Link encap:Ethernet  HWaddr b0:d5:cc:fe:1d:7c
    inet addr:1.1.1.3  Bcast:0.0.0.0  Mask:255.255.255.255
    UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
    Interrupt:171

  And daemons like ntpd also log errors about the interface with the
  illegal label:

  ntpd[7570]: eth0-test3: getting interface flags: No such device
    ## => many of this error per minute until:
  ntpd[7570]: Too many errors.  Shutting up.

  So, I think ip addr show disallow adding address with illegal (as
  stated by his own documentation) labels, it must also check for the
  colon following the dev name.

  Version: 4.3.0-1ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1662620/+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 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications

2021-10-19 Thread Chris Halse Rogers
Has anyone tried PCManFM or Inkscape on focal? It seems that this update
doesn't fix GNOME Shell on focal, but *maybe* that's because Shell is
hitting a different bug?

If this can be verified to fix PCManFM, Inkscape, or something on focal
we can release it and open a new bug for GNOME Shell on Focal.

If this *doesn't* fix something on focal, we need to work out why -
maybe it needs more changes backported, like bionic did?

If FCManFM & Inkscape don't hang on focal *without* this update then I
think we can release the bionic update and close the focal task.

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

Title:
  Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
  applications

Status in libx11 package in Ubuntu:
  Fix Released
Status in libx11 source package in Bionic:
  Fix Committed
Status in libx11 source package in Focal:
  Fix Committed
Status in libx11 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  There is a race in libx11 causing applications to randomly abort. It's
  not trivial to reproduce, but there are enough duplicates that this
  deserves an SRU to bionic & focal.

  [Fix]

  Backport a commit from upstream:

  From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001
  From: Frediano Ziglio 
  Date: Wed, 29 Jan 2020 09:06:54 +
  Subject: [PATCH] Fix poll_for_response race condition

  In poll_for_response is it possible that event replies are skipped
  and a more up to date message reply is returned.
  This will cause next poll_for_event call to fail aborting the program.

  This was proved using some slow ssh tunnel or using some program
  to slow down server replies (I used a combination of xtrace and strace).

  How the race happens:
  - program enters into poll_for_response;
  - poll_for_event is called but the server didn't still send the reply;
  - pending_requests is not NULL because we send a request (see call
to  append_pending_request in _XSend);
  - xcb_poll_for_reply64 is called from poll_for_response;
  - xcb_poll_for_reply64 will read from server, at this point
server reply with an event (say sequence N) and the reply to our
last request (say sequence N+1);
  - xcb_poll_for_reply64 returns the reply for the request we asked;
  - last_request_read is set to N+1 sequence in poll_for_response;
  - poll_for_response returns the response to the request;
  - poll_for_event is called (for instance from another poll_for_response);
  - event with sequence N is retrieved;
  - the N sequence is widen, however, as the "new" number computed from
last_request_read is less than N the number is widened to N + 2^32
(assuming last_request_read is still contained in 32 bit);
  - poll_for_event enters the nested if statement as req is NULL;
  - we compare the widen N (which now does not fit into 32 bit) with
request (which fits into 32 bit) hitting the throw_thread_fail_assert.

  To avoid the race condition and to avoid the sequence to go back
  I check again for new events after getting the response and
  return this last event if present saving the reply to return it
  later.

  To test the race and the fix it's helpful to add a delay (I used a
  "usleep(5000)") before calling xcb_poll_for_reply64.

  Original patch written by Frediano Ziglio, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34

  Reworked primarily for readability by Peter Hutterer, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53

  Signed-off-by: Peter Hutterer 

  bionic needs another commit so that the real fix applies.

  [Test case]

  It's a race condition, the SRU sponsor (tjaalton) does not have a test
  case for this, but the bug subscribers seem to.

  
  [Where things could go wrong]

  In theory there might be a case where a race still happens, but since
  this has been upstream for a year now with no follow-up commits, it's
  safe to assume that there are no regressions.

  
  --

  STEPS TO REPRODUCE
  ==
  The bug seems to occur when clicking on a file or folder. It is random and 
difficult to provide clear steps to reproduce. It is, however, a common 
situation.

  EXPECTED RESULTS
  
  pcmanfm works without problem.

  ACTUAL RESULTS
  ==
  All pcmanfm windows become unresponsive, though background processes (e.g. 
copying) may continue without problem. with the same error message in 
~/.cache/lxsession/LXDE/run.log:

  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not 
been called
  [xcb] Aborting, sorry about that.
  pcmanfm: xcb_io.c:259: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.
  ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6
  ** Message: 19:58:49.268: app.vala:148: 

[Touch-packages] [Bug 1945227] Update Released

2021-10-12 Thread Chris Halse Rogers
The verification of the Stable Release Update for linux-firmware 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 mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1945227

Title:
  drm/amdgpu: Add support for Yellow Carp

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Released
Status in mesa source package in Focal:
  Fix Released

Bug description:
  [Impact]

  New hardware support for AMD's Yellow Carp need five commits
  backported to mesa and new firmware. This is only needed on focal,
  skipping hirsute (no kernel support there).

  [Test plan]

  Install updates, boot a YC machine and check that the desktop has full
  hardware acceleration.

  [Where problems could occur]

  The firmware is new, so it will simply add new files to l-f without
  any impact on others.

  Mesa adds five commits in total, and while some affect other chips,
  they mostly fix hw bugs or add a helper and such, hard to see what
  could go wrong.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945227/+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 1945227] Re: drm/amdgpu: Add support for Yellow Carp

2021-09-28 Thread Chris Halse Rogers
Hello Timo, or anyone else affected,

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

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
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: mesa (Ubuntu Focal)
   Status: New => 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 mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1945227

Title:
  drm/amdgpu: Add support for Yellow Carp

Status in linux-firmware package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  New
Status in mesa source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  New hardware support for AMD's Yellow Carp need five commits
  backported to mesa and new firmware. This is only needed on focal,
  skipping hirsute/impish (no kernel support there).

  [Test plan]

  Install updates, boot a YC machine and check that the desktop has full
  hardware acceleration.

  [Where problems could occur]

  The firmware is new, so it will simply add new files to l-f without
  any impact on others.

  Mesa adds five commits in total, and while some affect other chips,
  they mostly fix hw bugs or add a helper and such, hard to see what
  could go wrong.

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

2021-09-14 Thread Chris Halse Rogers
The verification of the Stable Release Update for systemd 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1937238

Title:
  systemd-time-wait-sync.service stuck in "activating" state after boot,
  blocks timers from starting

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

Bug description:
  [impact]

  systemd-time-wait-sync service sometimes misses sync completed event
  and remains in 'activating' state

  [test case]

  this isn't consistently reproducable, see original description for
  test case

  [regression potential]

  possible problems with the systemd-time-wait-sync service completing
  too early or not completing on time

  [scope]

  this is needed only for f

  this is fixed upstream with commit
  f6f4f5fe5395a57f10dd446c7266c53f0673eaac which is in v246, so this is
  fixed in h and later already

  the service does not exist in b so this does not apply there

  [original description]

  When I start my server running Ubuntu 20.04 the systemd-time-wait-
  sync.service is stuck in "activating" state. I noticed this because
  none of the systemd timer units triggered, because all the timers
  depend on systemd-time-wait-sync.service. Running "systemctl restart
  systemd-time-wait-sync.service" manually works around the problem.

  Some logs and command outputs:

  raek@mizar:~$ lsb_release -rd
  Description:Ubuntu 20.04.2 LTS
  Release:20.04

  raek@mizar:~$ systemctl | grep systemd-time-wait-sync.service
    systemd-time-wait-sync.service  
 loaded activating start start Wait Until Kernel Time 
Synchronized

  raek@mizar:~$ systemctl status systemd-time-wait-sync.service
  ● systemd-time-wait-sync.service - Wait Until Kernel Time Synchronized
   Loaded: loaded (/lib/systemd/system/systemd-time-wait-sync.service; 
enabled; vendor preset: enabled)
   Active: activating (start) since Thu 2021-07-22 11:06:52 CEST; 27min ago
     Docs: man:systemd-time-wait-sync.service(8)
     Main PID: 514 (systemd-time-wa)
    Tasks: 1 (limit: 9415)
   Memory: 972.0K
   CGroup: /system.slice/systemd-time-wait-sync.service
   └─514 /lib/systemd/systemd-time-wait-sync

  Jul 22 11:06:52 mizar systemd-time-wait-sync[514]: adjtime state 5 status 40 
time Thu 2021-07-22 09:06:52.216338 UTC
  Warning: journal has been rotated since unit was started, output may be 
incomplete.

  raek@mizar:~$ journalctl -b -u systemd-time-wait-sync.service
  -- Logs begin at Wed 2020-07-08 16:34:13 CEST, end at Thu 2021-07-22 11:36:44 
CEST. --
  Jul 22 11:06:52 mizar systemd-time-wait-sync[514]: adjtime state 5 status 40 
time Thu 2021-07-22 09:06:52.216338 UTC

  raek@mizar:~$ dpkg -S /lib/systemd/system/systemd-time-wait-sync.service
  systemd: /lib/systemd/system/systemd-time-wait-sync.service

  raek@mizar:~$ apt-cache policy systemd
  systemd:
    Installed: 245.4-4ubuntu3.11
    Candidate: 245.4-4ubuntu3.11
    Version table:
   *** 245.4-4ubuntu3.11 500
  500 http://se.archive.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   245.4-4ubuntu3.10 500
  500 http://se.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
   245.4-4ubuntu3.8 400
  400 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 
Packages
   245.4-4ubuntu3 500
  500 http://se.archive.ubuntu.com/ubuntu focal/main amd64 Packages

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

2021-09-14 Thread Chris Halse Rogers
The verification of the Stable Release Update for systemd 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1914740

Title:
  IPs are not assigned for Hipersockets in DHCP mode

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in netplan.io source package in Focal:
  New
Status in systemd source package in Focal:
  Fix Released
Status in netplan.io source package in Hirsute:
  New
Status in systemd source package in Hirsute:
  Fix Released
Status in netplan.io source package in Impish:
  Confirmed
Status in systemd source package in Impish:
  Fix Committed

Bug description:
  ---Problem Description---
  IPs are not getting assigned for Hipersockets in DHCP mode
   
  Contact Information = Asha Shekharappa(ashsh...@in.ibm.com)  
Sankar(sankar...@in.ibm.com) 
   
  ---uname output---
  52-Ubuntu SMP Thu Sep 10 10:59:04 UTC 2020 s390x s390x s390x GNU/Linux
   
  Machine Type = s390x 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Ubuntu 20.04
  Netplan with systemd-networkd as renderer

  Creating ethernet connection on Hipersockets device in DHCP mode fails
  to assign IPs

  1. Configure a Hipersockets device
 chzdev -e 0.0.8f00

  2. Create a .yaml file with the below details

  network:
  version: 2
  ethernets:
  enc8f00:
  dhcp4: yes

  3. netplan apply

  
  4. The IP is not assigned as seen below

  root@M96SANKAR:/etc/netplan# ip a s

  enc8f00:  mtu 32768 qdisc mq state UP 
group default qlen 1000
  link/ether fe:da:af:44:08:02 brd ff:ff:ff:ff:ff:ff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+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 1853164] Update Released

2021-09-14 Thread Chris Halse Rogers
The verification of the Stable Release Update for systemd 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1853164

Title:
  systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error

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

Bug description:
  [impact]

  with systemd-resolved disabled, dhclient doesn't correctly notify
  resolvconf about dns server(s)

  [test case]

  install resolvconf and ifupdown and disable systemd-resolved and
  systemd-networkd, use ifupdown to get a dhcp address where the lease
  includes a dns nameserver, verify resolvconf is using that dhcp-
  provided nameserver

  [regression potential]

  failure to correctly notify systemd-resolved about new dhclient-
  provided nameserver(s)

  [scope]

  this is needed for f and earlier

  in g and later the hook script is moved to the isc-dhcp package, and
  edited to correctly check is-enabled systemd-resolved instead of only
  checking for the existence of the binary

  [original description]

  The functionality exists to allow users to revert to the traditional ifupdown
  package for network configuration. Alongside this, systemd's often-buggy
  resolver can be disabled. However, there's a logic error in the systemd-
  supplied /etc/dhcp/dhclient-enter-hooks.d/resolved that prevents the system
  from populating /etc/resolv.conf properly when systemd-resolved is disabled.
  The issue is here:

  if [ -x /lib/systemd/systemd-resolved ] ; then

  Instead of checking to see if the systemd-resolved service is enabled or
  active, which would be the correct behaviour, this checks for the existence of
  a binary, assuming that if it exists it's supposed to be used.

  I've not tested this in the absence of resolvconf, but if systemd-resolved
  isn't enabled, it's difficult to imagine this code wanting to run. I've tested
  this with resolvconf and ifupdown driving dhclient, and it corrects the
  behaviour that was broken with the introduction of systemd-resolved.

  I'm attaching a patch, and am also including it here for easy access:

  *** resolved.broken 2019-11-19 15:01:28.785588838 +
  --- resolved2019-11-19 15:08:06.519430073 +
  ***
  *** 14,20 
    #   (D) = master script downs interface
    #   (-) = master script does nothing with this

  ! if [ -x /lib/systemd/systemd-resolved ] ; then
    # For safety, first undefine the nasty default make_resolv_conf()
    make_resolv_conf() { : ; }
    case "$reason" in
  --- 14,21 
    #   (D) = master script downs interface
    #   (-) = master script does nothing with this

  ! systemctl is-active systemd-resolved > /dev/null 2>&1
  ! if [ $? -eq 0 ]; then
    # For safety, first undefine the nasty default make_resolv_conf()
    make_resolv_conf() { : ; }
    case "$reason" in

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

2021-09-14 Thread Chris Halse Rogers
The verification of the Stable Release Update for systemd 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1934981

Title:
  systemctl suspend-then-hibernate attempts hybrid-sleep instead

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in systemd source package in Groovy:
  Won't Fix
Status in systemd source package in Hirsute:
  Fix Released
Status in systemd source package in Impish:
  Fix Committed

Bug description:
  [impact]

  suspend-then-hibernate not possible using systemctl

  [test case]

  configure a system (that has enough swap to be able to hibernate) to
  allow suspend-then-hibernate but not hybrid-sleep, e.g. by editing
  /etc/systemd/sleep.conf to set AllowSuspendThenHibernate=yes and
  AllowHybridSleep=no, then try it:

  $ sudo systemctl suspend-then-hibernate
  Failed to suspend system, hibernate later via logind: Sleep verb 
"hybrid-sleep" not supported

  note that on bionic, the Allow...= params do not exist, instead we can
  reproduce the error by setting one of the hybrid parameters to an
  invalid value, e.g. HybridSleepState=bugverification

  
  [regression potential]

  failure to correctly enter hybrid-sleep and/or suspend-then-hibernate,
  or other issues around suspending/hibernating

  [scope]

  This is needed in b and later.

  The bug appears to have been introduced by a typo in the original
  suspend-then-hibernate commit c58493c00af, and then fixed with larger
  changes in commit c8cd8ca3986.

  this is also present in b, by a backport of the functionality

  [other info]

  note that if hybrid-sleep is allowed/possible, then calling 'systemctl
  suspend-then-hibernate' does actually perform suspend-then-hibernate;
  this typo only controls what suspend action logind checks for support
  of, not what suspend action it actually performs.

  [original description]

  ```
  systemctl suspend-then-hibernate
  Failed to suspend system, hibernate later via logind: Sleep verb 
"hybrid-sleep" not supported
  ```

  Note the verb change!

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: systemd 247.3-3ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  8 08:54:01 2021
  InstallationDate: Installed on 2021-07-06 (1 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. XPS 13 9300
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic 
root=/dev/mapper/username-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-localed.service → 
/usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf

   3 overridden configuration files found.
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/03/2021
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0PP9G2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd02/03/2021:br1.5:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0PP9G2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.systemd.sleep.conf: 2021-07-08T08:51:57.213321

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

2021-09-14 Thread Chris Halse Rogers
The verification of the Stable Release Update for systemd 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1934221

Title:
  systemd-resolve segfault

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in systemd source package in Hirsute:
  Fix Released
Status in systemd source package in Impish:
  Fix Released

Bug description:
  [Impact]

   * systemd-resolved stops replying to clients on the local LAN.
   * logging segfault crashes in dmesg:
  [836786.046514] systemd-resolve[872009]: segfault at 399 ip 
0399 sp 7ffd7959a6d8 error 14 in 
systemd-resolved[556398695000+9000]
  [836786.046524] Code: Bad RIP value.
  [840887.303994] traps: systemd-resolve[877019] general protection fault 
ip:55ba402e2594 sp:7ffe8cb6bbb0 error:0 in systemd-resolved[55ba402b5000+4]
  [844395.313421] systemd-resolve[878503]: segfault at 208 ip 5557a249f5fa 
sp 7ffe686f5a90 error 6 in systemd-resolved[5557a2472000+4]
  [844395.313431] Code: 48 85 c0 74 0e 48 8b 8d 00 01 00 00 48 89 88 00 01 00 
00 48 8b 85 00 01 00 00 48 85 c0 0f 84 1d 01 00 00 48 8b 95 f8 00 00 00 <48> 89 
90 f8 00 00 00 48 c7 85 00 01 00 00 00 00 00 00 48 c7 85 f8

   * The upload backports the upstream fix
  (https://github.com/systemd/systemd/pull/18832) to Focal & Hirsute.

  [Test Plan]

   * Setup /etc/systemd/resolved.conf:
  [Resolve]
  DNS=46.182.19.48#dns2.digitalcourage.de 1.1.1.1#cloudflare-dns.com 
9.9.9.9#dns.quad9.net
  DNSSEC=yes
  DNSOverTLS=opportunistic
  MulticastDNS=no
  LLMNR=no
  Cache=yes
  DNSStubListener=yes
  Domains=~.

   * wait for ~24-48 hours and observe if any crash happens

  [Where problems could occur]

   * Any regression would likely cause crashes in systemd-resolved,
  making it unresponsive to DNS network name requests to local
  applications.

  [Other Info]
   
   * Reported upstream: https://github.com/systemd/systemd/issues/18427
   * Fixed upstream in v248: https://github.com/systemd/systemd/pull/18832

  === Original description ===

  
  systemd-resolve keep crashing and it is very annoying as sometimes it 
severely interrupt normal dns resolving.

  Last uploaded report is 2d9e7378-d89b-11eb-9e14-fa163ee63de6
  Typical error in dmesg:
  systemd-resolve[1792202]: segfault at 564ff982f3e0 ip 564ff982f3e0 sp 
7ffe2fd0b758 error 15

  apport hints me that problem is related to mdns

  #3  0x7f3e903c2f11 in sd_event_dispatch () from
  /lib/systemd/libsystemd-shared-245.so

  It might be (or not) related that some hosts with mdns in my network
  have ipv6 enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.7
  ProcVersionSignature: Ubuntu 5.4.0-75.84-generic 5.4.119
  Uname: Linux 5.4.0-75-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  1 08:22:51 2021
  InstallationDate: Installed on 2018-12-05 (938 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-75-generic 
root=UUID=54b80d5c-3d61-4919-873f-0d308083e3b9 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2020-05-22 (405 days ago)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1205
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX X399-E GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1205:bd05/12/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX399-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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

[Touch-packages] [Bug 1934147] Update Released

2021-09-14 Thread Chris Halse Rogers
The verification of the Stable Release Update for systemd 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1934147

Title:
  systemd leaks abandoned session scopes

Status in snapd:
  New
Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in systemd source package in Groovy:
  Won't Fix
Status in systemd source package in Hirsute:
  Fix Released
Status in systemd source package in Impish:
  Fix Committed

Bug description:
  [impact]

  systemd may leak sessions, leaving empty cgroups around as well as
  abandoned session scopes.

  [test case]

  on a system where the user has a ssh key that allows noninteractive
  login to localhost, and also has noninteractive sudo, run:

  $ for i in {1..100}; do sudo -b -i -u ubuntu ssh localhost -- sleep 1;
  done; for i in {1..20}; do echo 'Reloading...'; sudo systemctl daemon-
  reload; done

  check the sessions to see there have been leaked sessions:

  $ loginctl list-sessions

  SESSION  UID USER   SEAT TTY
1 1000 ubuntu  ttyS0
  350 1000 ubuntu  
  351 1000 ubuntu  
  360 1000 ubuntu  
  ...

  to verify the sessions were leaked, clear them out with:

  $ echo '' | sudo tee
  
/sys/fs/cgroup/unified/user.slice/user-1000.slice/session-*.scope/cgroup.events

  that should result in all the leaked sessions being cleaned up.

  [regression potential]

  issues during systemd pid1 reexec/reload, or issues while cleaning up
  sessions, including leaking sessions/cgroups

  [scope]

  this is needed for all releases

  upstream bug linked above, and upstream PR:
  https://github.com/systemd/systemd/pull/20199

  [original description]

  On a system that is monitored via telegraf I found many abandoned
  systemd session which I believe are created by a potential race where
  systemd is reloading unit files and at the same time a user is
  connecting to the system via ssh or is executing the su command.

  The simple reproducer

  $ for i in {1..100}; do sleep 0.2; ssh localhost sudo systemctl
  daemon-reload & ssh localhost sleep 1 & done

  Wait > 1 second

  $ jobs -p | xargs --verbose --no-run-if-empty kill -KILL

  To clean out STOPPED jobs and

  $ systemctl status --all 2> /dev/null | grep --before-context 3
  abandoned

  will produce something similar to

     │ ├─  175 su - ubuntu
     │ ├─  178 -su
     │ ├─62375 systemctl status --all
     │ └─62376 grep --color=auto --before-context 3 abandoned
  --
  ● session-273.scope - Session 273 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-273.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
  --
  ● session-274.scope - Session 274 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-274.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
  --
  ● session-30.scope - Session 30 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-30.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 10:05:56 UTC; 3h 30min ago
  --
  ● session-302.scope - Session 302 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-302.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 13:32:04 UTC; 4min 6s ago
  --
     │ ├─  175 su - ubuntu
     │ ├─  178 -su
     │ ├─62375 systemctl status --all
     │ └─62376 grep --color=auto --before-context 3 abandoned

  The system in question is running Bionic, systemd-237-3ubuntu10.48

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1934147/+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 1939255] Update Released

2021-09-14 Thread Chris Halse Rogers
The verification of the Stable Release Update for systemd 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1939255

Title:
  dhclient triggers systemd-resolved start limit when processing more
  than 5 interfaces at once

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

Bug description:
  [impact]

  on a system where systemd-resolved is running, if dhclient is used on
  more than 5 interfaces, it calls the '/etc/dhcp/dhclient-enter-
  hooks.d/resolved' script multiple times, which then restarts systemd-
  resolved multiple times, triggering the unit's start-limit throttle
  which results in the unit entering failed state

  [test case]

  on a system with more than 5 available interfaces to run dhclient on
  (where all the interfaces will get a dhcp response), run dhclient with
  the interfaces:

  $ dhclient ens8 ens9 ens10 ens11 ens12 ens13 ens14 ens15

  check if systemd-resolved failed:

  $ journalctl -b -1 -u systemd-resolved
  ...
  Aug 09 00:38:08 sf316232-b systemd[1]: systemd-resolved.service: Start 
request repeated too quickly.
  Aug 09 00:38:08 sf316232-b systemd[1]: systemd-resolved.service: Failed with 
result 'start-limit-hit'.
  Aug 09 00:38:08 sf316232-b systemd[1]: Failed to start Network Name 
Resolution.

  [regression potential]

  failure to start/stop/restart systemd-resolved, or problems adding
  dhclient-provided DNS nameservers to systemd-resolved

  [scope]

  this is needed only for b/f

  the dhclient 'hook' script is provided by the systemd package in focal
  and earlier, and needs fixing in those releases

  in h and later, the 'hook' script is included in the isc-dhcp-client
  package and notifies systemd-resolved in a more direct way without
  requiring restarting, and so doesn't trigger the restart limiting.

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

2021-09-14 Thread Chris Halse Rogers
The verification of the Stable Release Update for systemd 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1935051

Title:
  systemd pid 1 memory leak

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

Bug description:
  [impact]

  pid1 leaks memory when rebuilding unit path cache

  [test case]

  see original description.

  also, the patch contains an example of how to reproduce:

  $ for i in {1..300}; do cp ~/.config/systemd/user/test0001.service
  ~/.config/systemd/user/test$(printf %04d $i).service; systemctl --user
  start test$(printf %04d $i).service;done

  [regression]

  any problems would occur when rebuilding the path cache, possibly
  resulting in memory leaks or pid1 crashes.

  [scope]

  this is needed only in f

  fixed upstream by 3fb2326f3ed87aa0b26078d307ebfb299e36286d which is
  included in v246, so fixed in h and later

  the code in b is very different and doesn't appear to have the leak,
  per original report

  [original description]

  Hi everybody.

  We've meet a memory leak of pid1 process on the focal release.
  When we launch chef-client, several systemd .service and .timers are checked 
for state.
  Every time of this run pid1 increase VSZ/RSS on ~ 232 Kb, this don't happen 
on xenial and bionic releases.
  I straced pid1 when that leak happen and found brk call.
  On pmap view of pid 1 it's anon memory grow on the same address and all 
marked as dirty.
  All that leak memory can be freed by calling systemctl daemon-reexec.

  Searching in systemd github repo i found this commit
  
https://github.com/systemd/systemd/commit/3fb2326f3ed87aa0b26078d307ebfb299e36286d
  - it may be related to this leak.

  

  Environment:
    Distributor ID: Ubuntu
    Description:Ubuntu 20.04.2 LTS
    Release:20.04
    Codename:   focal
    Uname:  5.4.0-77-generic #83-Ubuntu SMP Sat May 8 02:35:39 UTC 2021 
x86_64

  Package:
    systemd:
  Installed: 245.4-4ubuntu3.7

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

2021-09-14 Thread Chris Halse Rogers
The verification of the Stable Release Update for systemd 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1942899

Title:
  Revert Add ACCEL_LOCATION=base property for Dell clamshell models

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

Bug description:
  [impact]

  initial patch for LP: #1938259 was incorrect.

  [test case]

  this bug is only to revert the previous patch

  the upstream commit
  
is:https://github.com/systemd/systemd/pull/20314/commits/55b29d8f130684bf1fd9fdfaef3bcca64b66930e

  checking for lack of the new 'sku' lines, and presence of the old
  lines, should be enough to verify this revert is correct

  [regression potential]

  any regression would likely be restricted to dell clamshell models
  matching the modified config settings

  [scope]

  the incorrect patch was added in f/h/i so only those need the patch
  removed/reverted

  [other info]

  this only reverts the patch that was added for bug 1938259, as the bug
  reporter indicated in that bug in comment 15 that the patch did not
  actually work correctly.

  a correct patch will need to go upstream first, so this bug is just to
  revert the last patch and respin systemd for all releases

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1942899/+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 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications

2021-09-14 Thread Chris Halse Rogers
That seems like we should be able to extract a verification from the
errors.ubuntu.com results. Is it possible to query crashes with a
specific dependency version? Seeing no crash reports with libx11
2:1.6.9-2ubuntu1.3 would suggest this is fixed.

On the other hand,
https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1782984/comments/110
suggests that this may *not* be fixed in focal.

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

Title:
  Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
  applications

Status in libx11 package in Ubuntu:
  Fix Released
Status in libx11 source package in Bionic:
  Fix Committed
Status in libx11 source package in Focal:
  Fix Committed
Status in libx11 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  There is a race in libx11 causing applications to randomly abort. It's
  not trivial to reproduce, but there are enough duplicates that this
  deserves an SRU to bionic & focal.

  [Fix]

  Backport a commit from upstream:

  From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001
  From: Frediano Ziglio 
  Date: Wed, 29 Jan 2020 09:06:54 +
  Subject: [PATCH] Fix poll_for_response race condition

  In poll_for_response is it possible that event replies are skipped
  and a more up to date message reply is returned.
  This will cause next poll_for_event call to fail aborting the program.

  This was proved using some slow ssh tunnel or using some program
  to slow down server replies (I used a combination of xtrace and strace).

  How the race happens:
  - program enters into poll_for_response;
  - poll_for_event is called but the server didn't still send the reply;
  - pending_requests is not NULL because we send a request (see call
to  append_pending_request in _XSend);
  - xcb_poll_for_reply64 is called from poll_for_response;
  - xcb_poll_for_reply64 will read from server, at this point
server reply with an event (say sequence N) and the reply to our
last request (say sequence N+1);
  - xcb_poll_for_reply64 returns the reply for the request we asked;
  - last_request_read is set to N+1 sequence in poll_for_response;
  - poll_for_response returns the response to the request;
  - poll_for_event is called (for instance from another poll_for_response);
  - event with sequence N is retrieved;
  - the N sequence is widen, however, as the "new" number computed from
last_request_read is less than N the number is widened to N + 2^32
(assuming last_request_read is still contained in 32 bit);
  - poll_for_event enters the nested if statement as req is NULL;
  - we compare the widen N (which now does not fit into 32 bit) with
request (which fits into 32 bit) hitting the throw_thread_fail_assert.

  To avoid the race condition and to avoid the sequence to go back
  I check again for new events after getting the response and
  return this last event if present saving the reply to return it
  later.

  To test the race and the fix it's helpful to add a delay (I used a
  "usleep(5000)") before calling xcb_poll_for_reply64.

  Original patch written by Frediano Ziglio, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34

  Reworked primarily for readability by Peter Hutterer, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53

  Signed-off-by: Peter Hutterer 

  bionic needs another commit so that the real fix applies.

  [Test case]

  It's a race condition, the SRU sponsor (tjaalton) does not have a test
  case for this, but the bug subscribers seem to.

  
  [Where things could go wrong]

  In theory there might be a case where a race still happens, but since
  this has been upstream for a year now with no follow-up commits, it's
  safe to assume that there are no regressions.

  
  --

  STEPS TO REPRODUCE
  ==
  The bug seems to occur when clicking on a file or folder. It is random and 
difficult to provide clear steps to reproduce. It is, however, a common 
situation.

  EXPECTED RESULTS
  
  pcmanfm works without problem.

  ACTUAL RESULTS
  ==
  All pcmanfm windows become unresponsive, though background processes (e.g. 
copying) may continue without problem. with the same error message in 
~/.cache/lxsession/LXDE/run.log:

  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not 
been called
  [xcb] Aborting, sorry about that.
  pcmanfm: xcb_io.c:259: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.
  ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6
  ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload

  (note the timestamp on the message will vary)

  AFFECTED VERSIONS
  =
  1.2.5-3ubuntu1
  NOT 1.2.4-1ubuntu0.1

  UPSTREAM BUG

[Touch-packages] [Bug 1934147] Re: systemd leaks abandoned session scopes

2021-08-31 Thread Chris Halse Rogers
Hello Nicolas, or anyone else affected,

Accepted systemd into hirsute-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/systemd/247.3-3ubuntu3.5 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-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. 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 Hirsute)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-hirsute

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

Title:
  systemd leaks abandoned session scopes

Status in snapd:
  New
Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  Won't Fix
Status in systemd source package in Hirsute:
  Fix Committed
Status in systemd source package in Impish:
  Fix Committed

Bug description:
  [impact]

  systemd may leak sessions, leaving empty cgroups around as well as
  abandoned session scopes.

  [test case]

  on a system where the user has a ssh key that allows noninteractive
  login to localhost, and also has noninteractive sudo, run:

  $ for i in {1..100}; do sudo -b -i -u ubuntu ssh localhost -- sleep 1;
  done; for i in {1..20}; do echo 'Reloading...'; sudo systemctl daemon-
  reload; done

  check the sessions to see there have been leaked sessions:

  $ loginctl list-sessions

  SESSION  UID USER   SEAT TTY
1 1000 ubuntu  ttyS0
  350 1000 ubuntu  
  351 1000 ubuntu  
  360 1000 ubuntu  
  ...

  to verify the sessions were leaked, clear them out with:

  $ echo '' | sudo tee
  
/sys/fs/cgroup/unified/user.slice/user-1000.slice/session-*.scope/cgroup.events

  that should result in all the leaked sessions being cleaned up.

  [regression potential]

  issues during systemd pid1 reexec/reload, or issues while cleaning up
  sessions, including leaking sessions/cgroups

  [scope]

  this is needed for all releases

  upstream bug linked above, and upstream PR:
  https://github.com/systemd/systemd/pull/20199

  [original description]

  On a system that is monitored via telegraf I found many abandoned
  systemd session which I believe are created by a potential race where
  systemd is reloading unit files and at the same time a user is
  connecting to the system via ssh or is executing the su command.

  The simple reproducer

  $ for i in {1..100}; do sleep 0.2; ssh localhost sudo systemctl
  daemon-reload & ssh localhost sleep 1 & done

  Wait > 1 second

  $ jobs -p | xargs --verbose --no-run-if-empty kill -KILL

  To clean out STOPPED jobs and

  $ systemctl status --all 2> /dev/null | grep --before-context 3
  abandoned

  will produce something similar to

     │ ├─  175 su - ubuntu
     │ ├─  178 -su
     │ ├─62375 systemctl status --all
     │ └─62376 grep --color=auto --before-context 3 abandoned
  --
  ● session-273.scope - Session 273 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-273.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
  --
  ● session-274.scope - Session 274 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-274.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
  --
  ● session-30.scope - Session 30 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-30.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 10:05:56 UTC; 3h 30min ago
  --
  ● session-302.scope - Session 302 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-302.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 13:32:04 UTC; 4min 6s ago
  --
     │ ├─  175 

[Touch-packages] [Bug 1934221] Re: systemd-resolve segfault

2021-08-31 Thread Chris Halse Rogers
Hello Denys, or anyone else affected,

Accepted systemd into hirsute-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/systemd/247.3-3ubuntu3.5 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-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. 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 Hirsute)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed verification-needed-hirsute

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

Title:
  systemd-resolve segfault

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Confirmed
Status in systemd source package in Hirsute:
  Fix Committed
Status in systemd source package in Impish:
  Fix Released

Bug description:
  [Impact]

   * systemd-resolved stops replying to clients on the local LAN.
   * logging segfault crashes in dmesg:
  [836786.046514] systemd-resolve[872009]: segfault at 399 ip 
0399 sp 7ffd7959a6d8 error 14 in 
systemd-resolved[556398695000+9000]
  [836786.046524] Code: Bad RIP value.
  [840887.303994] traps: systemd-resolve[877019] general protection fault 
ip:55ba402e2594 sp:7ffe8cb6bbb0 error:0 in systemd-resolved[55ba402b5000+4]
  [844395.313421] systemd-resolve[878503]: segfault at 208 ip 5557a249f5fa 
sp 7ffe686f5a90 error 6 in systemd-resolved[5557a2472000+4]
  [844395.313431] Code: 48 85 c0 74 0e 48 8b 8d 00 01 00 00 48 89 88 00 01 00 
00 48 8b 85 00 01 00 00 48 85 c0 0f 84 1d 01 00 00 48 8b 95 f8 00 00 00 <48> 89 
90 f8 00 00 00 48 c7 85 00 01 00 00 00 00 00 00 48 c7 85 f8

   * The upload backports the upstream fix
  (https://github.com/systemd/systemd/pull/18832) to Focal & Hirsute.

  [Test Plan]

   * Setup /etc/systemd/resolved.conf:
  [Resolve]
  DNS=46.182.19.48#dns2.digitalcourage.de 1.1.1.1#cloudflare-dns.com 
9.9.9.9#dns.quad9.net
  DNSSEC=yes
  DNSOverTLS=opportunistic
  MulticastDNS=no
  LLMNR=no
  Cache=yes
  DNSStubListener=yes
  Domains=~.

   * wait for ~24-48 hours and observe if any crash happens

  [Where problems could occur]

   * Any regression would likely cause crashes in systemd-resolved,
  making it unresponsive to DNS network name requests to local
  applications.

  [Other Info]
   
   * Reported upstream: https://github.com/systemd/systemd/issues/18427
   * Fixed upstream in v248: https://github.com/systemd/systemd/pull/18832

  === Original description ===

  
  systemd-resolve keep crashing and it is very annoying as sometimes it 
severely interrupt normal dns resolving.

  Last uploaded report is 2d9e7378-d89b-11eb-9e14-fa163ee63de6
  Typical error in dmesg:
  systemd-resolve[1792202]: segfault at 564ff982f3e0 ip 564ff982f3e0 sp 
7ffe2fd0b758 error 15

  apport hints me that problem is related to mdns

  #3  0x7f3e903c2f11 in sd_event_dispatch () from
  /lib/systemd/libsystemd-shared-245.so

  It might be (or not) related that some hosts with mdns in my network
  have ipv6 enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.7
  ProcVersionSignature: Ubuntu 5.4.0-75.84-generic 5.4.119
  Uname: Linux 5.4.0-75-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  1 08:22:51 2021
  InstallationDate: Installed on 2018-12-05 (938 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-75-generic 
root=UUID=54b80d5c-3d61-4919-873f-0d308083e3b9 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2020-05-22 (405 days ago)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1205
  dmi.board.asset.tag: Default string
  

[Touch-packages] [Bug 1934981] Re: systemctl suspend-then-hibernate attempts hybrid-sleep instead

2021-08-31 Thread Chris Halse Rogers
Hello Robert, or anyone else affected,

Accepted systemd into hirsute-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/systemd/247.3-3ubuntu3.5 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-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. 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 Hirsute)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-hirsute

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

Title:
  systemctl suspend-then-hibernate attempts hybrid-sleep instead

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  Won't Fix
Status in systemd source package in Hirsute:
  Fix Committed
Status in systemd source package in Impish:
  Fix Committed

Bug description:
  [impact]

  suspend-then-hibernate not possible using systemctl

  [test case]

  configure a system to allow suspend-then-hibernate but not hybrid-
  sleep, e.g. by editing /etc/systemd/sleep.conf to set
  AllowSuspendThenHibernate=yes and AllowHybridSleep=no, then try it:

  $ sudo systemctl suspend-then-hibernate
  Failed to suspend system, hibernate later via logind: Sleep verb 
"hybrid-sleep" not supported

  [regression potential]

  failure to correctly enter hybrid-sleep and/or suspend-then-hibernate,
  or other issues around suspending/hibernating

  [scope]

  This is needed in b and later.

  The bug appears to have been introduced by a typo in the original
  suspend-then-hibernate commit c58493c00af, and then fixed with larger
  changes in commit c8cd8ca3986.

  this is also present in b, by a backport of the functionality

  [other info]

  note that if hybrid-sleep is allowed/possible, then calling 'systemctl
  suspend-then-hibernate' does actually perform suspend-then-hibernate;
  this typo only controls what suspend action logind checks for support
  of, not what suspend action it actually performs.

  [original description]

  ```
  systemctl suspend-then-hibernate
  Failed to suspend system, hibernate later via logind: Sleep verb 
"hybrid-sleep" not supported
  ```

  Note the verb change!

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: systemd 247.3-3ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  8 08:54:01 2021
  InstallationDate: Installed on 2021-07-06 (1 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. XPS 13 9300
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic 
root=/dev/mapper/username-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-localed.service → 
/usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf

   3 overridden configuration files found.
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/03/2021
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0PP9G2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Touch-packages] [Bug 1914740] Re: IPs are not assigned for Hipersockets in DHCP mode

2021-08-31 Thread Chris Halse Rogers
Hello bugproxy, or anyone else affected,

Accepted systemd into hirsute-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/systemd/247.3-3ubuntu3.5 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-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. 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 Hirsute)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-hirsute

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

Title:
  IPs are not assigned for Hipersockets in DHCP mode

Status in Ubuntu on IBM z Systems:
  In Progress
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  In Progress
Status in netplan.io source package in Focal:
  New
Status in systemd source package in Focal:
  In Progress
Status in netplan.io source package in Hirsute:
  New
Status in systemd source package in Hirsute:
  Fix Committed
Status in netplan.io source package in Impish:
  Confirmed
Status in systemd source package in Impish:
  In Progress

Bug description:
  ---Problem Description---
  IPs are not getting assigned for Hipersockets in DHCP mode
   
  Contact Information = Asha Shekharappa(ashsh...@in.ibm.com)  
Sankar(sankar...@in.ibm.com) 
   
  ---uname output---
  52-Ubuntu SMP Thu Sep 10 10:59:04 UTC 2020 s390x s390x s390x GNU/Linux
   
  Machine Type = s390x 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Ubuntu 20.04
  Netplan with systemd-networkd as renderer

  Creating ethernet connection on Hipersockets device in DHCP mode fails
  to assign IPs

  1. Configure a Hipersockets device
 chzdev -e 0.0.8f00

  2. Create a .yaml file with the below details

  network:
  version: 2
  ethernets:
  enc8f00:
  dhcp4: yes

  3. netplan apply

  
  4. The IP is not assigned as seen below

  root@M96SANKAR:/etc/netplan# ip a s

  enc8f00:  mtu 32768 qdisc mq state UP 
group default qlen 1000
  link/ether fe:da:af:44:08:02 brd ff:ff:ff:ff:ff:ff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+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 1938259] Re: Add ACCEL_LOCATION=base property for Dell clamshell models

2021-08-31 Thread Chris Halse Rogers
Hello Yao, or anyone else affected,

Accepted systemd into hirsute-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/systemd/247.3-3ubuntu3.5 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-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. 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 Hirsute)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-hirsute

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

Title:
  Add ACCEL_LOCATION=base property for Dell clamshell models

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Hirsute:
  Fix Committed
Status in systemd source package in Impish:
  Fix Committed

Bug description:
  We are planning to do SRU to systemd in focal, to avoid unwanted
  screen rotations on some Dell laptop models.

  [Impact]

   * This fixes unwanted rotations on certain Dell clamshell laptop
  models with accelerometer.

  [Test Plan]

   * On Dell laptops with model SKU 0A3E or 0E0E, install this package and 
kernel 5.13, or kernel with this patch backported:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e26f023e01ef26b4138bc1099af309bdc4523d23
   * Rotate the laptop and the display should not be rotated.

  [Where problems could occur]

   * This is to add parameters for certain models in hwdb, and does not
  affect any other part of systemd.

   * This fix would only take effect with kernel 5.13 or the above patch
  backported.

  [scope]

  this is needed for all releases

  this is being fixed upstream by
  https://github.com/systemd/systemd/pull/20314

  [Other info]

   * The patch mentioned above is going to have a separated SRU for
  linux-oem-5.10 and linux-hwe-5.11 (LP: #1938143)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1938259/+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 1939255] Re: dhclient triggers systemd-resolved start limit when processing more than 5 interfaces at once

2021-08-31 Thread Chris Halse Rogers
Hello Dan, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.52 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed verification-needed-bionic

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

Title:
  dhclient triggers systemd-resolved start limit when processing more
  than 5 interfaces at once

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  In Progress

Bug description:
  [impact]

  on a system where systemd-resolved is running, if dhclient is used on
  more than 5 interfaces, it calls the '/etc/dhcp/dhclient-enter-
  hooks.d/resolved' script multiple times, which then restarts systemd-
  resolved multiple times, triggering the unit's start-limit throttle
  which results in the unit entering failed state

  [test case]

  on a system with more than 5 available interfaces to run dhclient on
  (where all the interfaces will get a dhcp response), run dhclient with
  the interfaces:

  $ dhclient ens8 ens9 ens10 ens11 ens12 ens13 ens14 ens15

  check if systemd-resolved failed:

  $ journalctl -b -1 -u systemd-resolved
  ...
  Aug 09 00:38:08 sf316232-b systemd[1]: systemd-resolved.service: Start 
request repeated too quickly.
  Aug 09 00:38:08 sf316232-b systemd[1]: systemd-resolved.service: Failed with 
result 'start-limit-hit'.
  Aug 09 00:38:08 sf316232-b systemd[1]: Failed to start Network Name 
Resolution.

  [regression potential]

  failure to start/stop/restart systemd-resolved, or problems adding
  dhclient-provided DNS nameservers to systemd-resolved

  [scope]

  this is needed only for b/f

  the dhclient 'hook' script is provided by the systemd package in focal
  and earlier, and needs fixing in those releases

  in h and later, the 'hook' script is included in the isc-dhcp-client
  package and notifies systemd-resolved in a more direct way without
  requiring restarting, and so doesn't trigger the restart limiting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1939255/+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 1934147] Re: systemd leaks abandoned session scopes

2021-08-31 Thread Chris Halse Rogers
Hello Nicolas, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.52 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed verification-needed-bionic

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

Title:
  systemd leaks abandoned session scopes

Status in snapd:
  New
Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  Won't Fix
Status in systemd source package in Hirsute:
  In Progress
Status in systemd source package in Impish:
  Fix Committed

Bug description:
  [impact]

  systemd may leak sessions, leaving empty cgroups around as well as
  abandoned session scopes.

  [test case]

  on a system where the user has a ssh key that allows noninteractive
  login to localhost, and also has noninteractive sudo, run:

  $ for i in {1..100}; do sudo -b -i -u ubuntu ssh localhost -- sleep 1;
  done; for i in {1..20}; do echo 'Reloading...'; sudo systemctl daemon-
  reload; done

  check the sessions to see there have been leaked sessions:

  $ loginctl list-sessions

  SESSION  UID USER   SEAT TTY
1 1000 ubuntu  ttyS0
  350 1000 ubuntu  
  351 1000 ubuntu  
  360 1000 ubuntu  
  ...

  to verify the sessions were leaked, clear them out with:

  $ echo '' | sudo tee
  
/sys/fs/cgroup/unified/user.slice/user-1000.slice/session-*.scope/cgroup.events

  that should result in all the leaked sessions being cleaned up.

  [regression potential]

  issues during systemd pid1 reexec/reload, or issues while cleaning up
  sessions, including leaking sessions/cgroups

  [scope]

  this is needed for all releases

  upstream bug linked above, and upstream PR:
  https://github.com/systemd/systemd/pull/20199

  [original description]

  On a system that is monitored via telegraf I found many abandoned
  systemd session which I believe are created by a potential race where
  systemd is reloading unit files and at the same time a user is
  connecting to the system via ssh or is executing the su command.

  The simple reproducer

  $ for i in {1..100}; do sleep 0.2; ssh localhost sudo systemctl
  daemon-reload & ssh localhost sleep 1 & done

  Wait > 1 second

  $ jobs -p | xargs --verbose --no-run-if-empty kill -KILL

  To clean out STOPPED jobs and

  $ systemctl status --all 2> /dev/null | grep --before-context 3
  abandoned

  will produce something similar to

     │ ├─  175 su - ubuntu
     │ ├─  178 -su
     │ ├─62375 systemctl status --all
     │ └─62376 grep --color=auto --before-context 3 abandoned
  --
  ● session-273.scope - Session 273 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-273.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
  --
  ● session-274.scope - Session 274 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-274.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
  --
  ● session-30.scope - Session 30 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-30.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 10:05:56 UTC; 3h 30min ago
  --
  ● session-302.scope - Session 302 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-302.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 13:32:04 UTC; 4min 6s ago
  --
   

[Touch-packages] [Bug 1853164] Re: systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error

2021-08-31 Thread Chris Halse Rogers
Hello Mason, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.52 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

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

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

Title:
  systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error

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

Bug description:
  [impact]

  with systemd-resolved disabled, dhclient doesn't correctly notify
  resolvconf about dns server(s)

  [test case]

  install resolvconf and ifupdown and disable systemd-resolved and
  systemd-networkd, use ifupdown to get a dhcp address where the lease
  includes a dns nameserver, verify resolvconf is using that dhcp-
  provided nameserver

  [regression potential]

  failure to correctly notify systemd-resolved about new dhclient-
  provided nameserver(s)

  [scope]

  this is needed for f and earlier

  in g and later the hook script is moved to the isc-dhcp package, and
  edited to correctly check is-enabled systemd-resolved instead of only
  checking for the existence of the binary

  [original description]

  The functionality exists to allow users to revert to the traditional ifupdown
  package for network configuration. Alongside this, systemd's often-buggy
  resolver can be disabled. However, there's a logic error in the systemd-
  supplied /etc/dhcp/dhclient-enter-hooks.d/resolved that prevents the system
  from populating /etc/resolv.conf properly when systemd-resolved is disabled.
  The issue is here:

  if [ -x /lib/systemd/systemd-resolved ] ; then

  Instead of checking to see if the systemd-resolved service is enabled or
  active, which would be the correct behaviour, this checks for the existence of
  a binary, assuming that if it exists it's supposed to be used.

  I've not tested this in the absence of resolvconf, but if systemd-resolved
  isn't enabled, it's difficult to imagine this code wanting to run. I've tested
  this with resolvconf and ifupdown driving dhclient, and it corrects the
  behaviour that was broken with the introduction of systemd-resolved.

  I'm attaching a patch, and am also including it here for easy access:

  *** resolved.broken 2019-11-19 15:01:28.785588838 +
  --- resolved2019-11-19 15:08:06.519430073 +
  ***
  *** 14,20 
    #   (D) = master script downs interface
    #   (-) = master script does nothing with this

  ! if [ -x /lib/systemd/systemd-resolved ] ; then
    # For safety, first undefine the nasty default make_resolv_conf()
    make_resolv_conf() { : ; }
    case "$reason" in
  --- 14,21 
    #   (D) = master script downs interface
    #   (-) = master script does nothing with this

  ! systemctl is-active systemd-resolved > /dev/null 2>&1
  ! if [ $? -eq 0 ]; then
    # For safety, first undefine the nasty default make_resolv_conf()
    make_resolv_conf() { : ; }
    case "$reason" in

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853164/+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 1934981] Re: systemctl suspend-then-hibernate attempts hybrid-sleep instead

2021-08-31 Thread Chris Halse Rogers
Hello Robert, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.52 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed verification-needed-bionic

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

Title:
  systemctl suspend-then-hibernate attempts hybrid-sleep instead

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  Won't Fix
Status in systemd source package in Hirsute:
  In Progress
Status in systemd source package in Impish:
  Fix Committed

Bug description:
  [impact]

  suspend-then-hibernate not possible using systemctl

  [test case]

  configure a system to allow suspend-then-hibernate but not hybrid-
  sleep, e.g. by editing /etc/systemd/sleep.conf to set
  AllowSuspendThenHibernate=yes and AllowHybridSleep=no, then try it:

  $ sudo systemctl suspend-then-hibernate
  Failed to suspend system, hibernate later via logind: Sleep verb 
"hybrid-sleep" not supported

  [regression potential]

  failure to correctly enter hybrid-sleep and/or suspend-then-hibernate,
  or other issues around suspending/hibernating

  [scope]

  This is needed in b and later.

  The bug appears to have been introduced by a typo in the original
  suspend-then-hibernate commit c58493c00af, and then fixed with larger
  changes in commit c8cd8ca3986.

  this is also present in b, by a backport of the functionality

  [other info]

  note that if hybrid-sleep is allowed/possible, then calling 'systemctl
  suspend-then-hibernate' does actually perform suspend-then-hibernate;
  this typo only controls what suspend action logind checks for support
  of, not what suspend action it actually performs.

  [original description]

  ```
  systemctl suspend-then-hibernate
  Failed to suspend system, hibernate later via logind: Sleep verb 
"hybrid-sleep" not supported
  ```

  Note the verb change!

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: systemd 247.3-3ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  8 08:54:01 2021
  InstallationDate: Installed on 2021-07-06 (1 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. XPS 13 9300
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic 
root=/dev/mapper/username-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-localed.service → 
/usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf

   3 overridden configuration files found.
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/03/2021
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0PP9G2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Touch-packages] [Bug 1934995] Re: Broken on ppc64el (toolchain bug?)

2021-07-27 Thread Chris Halse Rogers
** Also affects: mir (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

Title:
  Broken on ppc64el (toolchain bug?)

Status in glibc package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  New
Status in umockdev package in Ubuntu:
  Invalid

Bug description:
  umockdev appears to be broken on ppc64el in impish. Running it on one
  of Mir's umockdev-using tests results in:

  (impish-ppc64el)root@juju-deb017-porterbox-1:/build/mir-Xn1VqE/umockdev# 
umockdev-run ../mir-2.4.1/build-ppc64el/bin/mir_umock_unit_tests
  MIR_CLIENT_PLATFORM_PATH=../mir-2.4.1/build-ppc64el/bin/../lib/client-modules/
  MIR_SERVER_PLATFORM_PATH=../mir-2.4.1/build-ppc64el/bin/../lib/server-modules/
  LD_LIBRARY_PATH=../mir-2.4.1/build-ppc64el/bin/../lib
  exec=../mir-2.4.1/build-ppc64el/bin/mir_umock_unit_tests.bin
  *** stack smashing detected ***: terminated
  umockdev-run: unable to propagate signal 6 to child 15833: No such process

  (You can also see this in the Mir 2.4.1-0ubuntu1 build log:
  https://launchpadlibrarian.net/546972958/buildlog_ubuntu-impish-
  ppc64el.mir_2.4.1-0ubuntu1_BUILDING.txt.gz )

  Installing umockdev 0.15.4-1 and libumockdev0 0.15.4-1 from hirsute
  results in those tests passing.

  Strangely, rebuilding umockdev 0.15.4-1 in a hirsute sbuild
  environment results in packages that do *not* pass those tests,
  suggesting a toolchain change might be responsible.

  Unfortunately, I've tried rebuilding umockdev with gcc-9, gcc-11, and
  vala 0.48.12-1 in Impish and none of these appear to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: umockdev 0.16.1-1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  8 16:04:15 2021
  InstallationDate: Installed on 2021-06-26 (11 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
  SourcePackage: umockdev
  UpgradeStatus: No upgrade log present (probably fresh install)

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

2021-07-22 Thread Chris Halse Rogers
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/1930359

Title:
  glib2.0: Uninitialised memory is written to gschema.compiled, failure
  to parse this file leads to gdm, gnome-shell failing to start

Status in GLib:
  Unknown
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Focal:
  Fix Released

Bug description:
  [Impact]

  A recent SRU of mutter 3.36.9-0ubuntu0.20.04.1 caused an outage for a
  user with 300 VDIs running Focal, where GNOME applications would fail
  to start, and if you reboot, gdm and gnome-shell both fail to start,
  and you are left with a black screen and a blinking cursor.

  After much investigation, mutter was not at fault. Instead, mutter-
  common calls the libglib2.0-0 hook on upgrade:

  Processing triggers for libglib2.0-0:amd64 (2.64.6-1~ubuntu20.04.3)
  ...

  This in turn calls glib-compile-schemas to recompile the gsettings
  gschema cache, from the files in /usr/share/glib-2.0/schemas/. The
  result is a binary gschemas.compiled file, which is loaded by
  libglib2.0 on every invocation of a GNOME application, or gdm or
  gnome-shell to fetch application default settings.

  Now, glib2.0 2.64.6-1~ubuntu20.04.3 in Focal has some non-
  deterministic behaviour when calling glib-compile-schemas, causing
  generated gschemas.compiled files to have differing contents on each
  run:

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 D0
  3771 A4 DB

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 C3
  3771 A4 98

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 68
  3771 A4 30
  3772 55 56

  The bytes on the left are from a corrupted gschemas.compiled provided
  by an affected user. The changing bytes on the right are non-
  deterministic.

  I ran valgrind over glib-compile-schemas, and found that we are
  writing to uninitialised memory.

  https://paste.ubuntu.com/p/hvZccwdzxz/

  What is happening is that a submodule of glib, gvdb, contains the
  logic for serialising the gschema data structures, and when it
  allocates a buffer to store the eventual gschemas.compiled file, it
  does not initialise it.

  When we populate the fields in the buffer, some bytes are never
  overwritten, and these junk bytes find themselves written to
  gschemas.compiled.

  On boot, when gdm and gnome-shell attempt to parse and load this
  corrupted gschemas.compiled file, it can't parse the junk bytes, and
  raises and error, which propagates up to a breakpoint in glib logging,
  but no debugger is present, so the kernel traps the breakpoint, and
  terminates the library, and the calling application, e.g. gdm.

  The result is that the user is left starting at a black screen with a
  blinking pointer.

  [Testcase]

  On a Focal system, simply run valgrind over glib-compile-schemas:

  # valgrind glib-compile-schemas /usr/share/glib-2.0/schemas

  You will get output like this, with the warning "Syscall param
  write(buf) points to uninitialised byte(s)":

  https://paste.ubuntu.com/p/hvZccwdzxz/

  If you happen to have a large amount of gschema overrides present on
  your system, like my affected user does, you can save a copy of a
  generated gschema.compiled to your home directory and bindiff it
  against recompiles:

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cp /usr/share/glib-2.0/schemas/gschema.compiled 
/home/ubuntu/schemas/gschemas.compiled
  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 C3
  3771 A4 98

  If you install the test package from the following ppa:

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

  When you run valgrind, it will report a clean run with no writing to
  

[Touch-packages] [Bug 1934995] Re: Broken on ppc64el (toolchain bug?)

2021-07-20 Thread Chris Halse Rogers
Ok: A list of things that it appears *not* to be:
1) binutils, valac, gcc versions. A umockdev build with the versions that 
hirsute's 0.15.4-1 built with.
2) The "debugedit: debian/umockdev/usr/bin/umockdev-record: Unknown DWARF 
DW_FORM_0x1f20" messages; building an unstripped umockdev doesn't emit this 
message (as it's no longer invoked by dh_strip), but the built package still 
results in the Mir tests failing as above.

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

Title:
  Broken on ppc64el (toolchain bug?)

Status in umockdev package in Ubuntu:
  New

Bug description:
  umockdev appears to be broken on ppc64el in impish. Running it on one
  of Mir's umockdev-using tests results in:

  (impish-ppc64el)root@juju-deb017-porterbox-1:/build/mir-Xn1VqE/umockdev# 
umockdev-run ../mir-2.4.1/build-ppc64el/bin/mir_umock_unit_tests
  MIR_CLIENT_PLATFORM_PATH=../mir-2.4.1/build-ppc64el/bin/../lib/client-modules/
  MIR_SERVER_PLATFORM_PATH=../mir-2.4.1/build-ppc64el/bin/../lib/server-modules/
  LD_LIBRARY_PATH=../mir-2.4.1/build-ppc64el/bin/../lib
  exec=../mir-2.4.1/build-ppc64el/bin/mir_umock_unit_tests.bin
  *** stack smashing detected ***: terminated
  umockdev-run: unable to propagate signal 6 to child 15833: No such process

  (You can also see this in the Mir 2.4.1-0ubuntu1 build log:
  https://launchpadlibrarian.net/546972958/buildlog_ubuntu-impish-
  ppc64el.mir_2.4.1-0ubuntu1_BUILDING.txt.gz )

  Installing umockdev 0.15.4-1 and libumockdev0 0.15.4-1 from hirsute
  results in those tests passing.

  Strangely, rebuilding umockdev 0.15.4-1 in a hirsute sbuild
  environment results in packages that do *not* pass those tests,
  suggesting a toolchain change might be responsible.

  Unfortunately, I've tried rebuilding umockdev with gcc-9, gcc-11, and
  vala 0.48.12-1 in Impish and none of these appear to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: umockdev 0.16.1-1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  8 16:04:15 2021
  InstallationDate: Installed on 2021-06-26 (11 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
  SourcePackage: umockdev
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/umockdev/+bug/1934995/+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 1934995] Re: Broken on ppc64el (toolchain bug?)

2021-07-09 Thread Chris Halse Rogers
Next possible culprit: binutils

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

Title:
  Broken on ppc64el (toolchain bug?)

Status in umockdev package in Ubuntu:
  New

Bug description:
  umockdev appears to be broken on ppc64el in impish. Running it on one
  of Mir's umockdev-using tests results in:

  (impish-ppc64el)root@juju-deb017-porterbox-1:/build/mir-Xn1VqE/umockdev# 
umockdev-run ../mir-2.4.1/build-ppc64el/bin/mir_umock_unit_tests
  MIR_CLIENT_PLATFORM_PATH=../mir-2.4.1/build-ppc64el/bin/../lib/client-modules/
  MIR_SERVER_PLATFORM_PATH=../mir-2.4.1/build-ppc64el/bin/../lib/server-modules/
  LD_LIBRARY_PATH=../mir-2.4.1/build-ppc64el/bin/../lib
  exec=../mir-2.4.1/build-ppc64el/bin/mir_umock_unit_tests.bin
  *** stack smashing detected ***: terminated
  umockdev-run: unable to propagate signal 6 to child 15833: No such process

  (You can also see this in the Mir 2.4.1-0ubuntu1 build log:
  https://launchpadlibrarian.net/546972958/buildlog_ubuntu-impish-
  ppc64el.mir_2.4.1-0ubuntu1_BUILDING.txt.gz )

  Installing umockdev 0.15.4-1 and libumockdev0 0.15.4-1 from hirsute
  results in those tests passing.

  Strangely, rebuilding umockdev 0.15.4-1 in a hirsute sbuild
  environment results in packages that do *not* pass those tests,
  suggesting a toolchain change might be responsible.

  Unfortunately, I've tried rebuilding umockdev with gcc-9, gcc-11, and
  vala 0.48.12-1 in Impish and none of these appear to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: umockdev 0.16.1-1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  8 16:04:15 2021
  InstallationDate: Installed on 2021-06-26 (11 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
  SourcePackage: umockdev
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/umockdev/+bug/1934995/+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 1934995] Re: Broken on ppc64el (toolchain bug?)

2021-07-08 Thread Chris Halse Rogers
Yeah, whatever change in dependencies causes this it goes back to
hirsute release.

Running mir 2.3.3's tests against 0.15.4-1 from the hirsute archive
works; running those tests against 0.15.4-1 rebuilt in a hirsute chroot
fails.

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

Title:
  Broken on ppc64el (toolchain bug?)

Status in umockdev package in Ubuntu:
  New

Bug description:
  umockdev appears to be broken on ppc64el in impish. Running it on one
  of Mir's umockdev-using tests results in:

  (impish-ppc64el)root@juju-deb017-porterbox-1:/build/mir-Xn1VqE/umockdev# 
umockdev-run ../mir-2.4.1/build-ppc64el/bin/mir_umock_unit_tests
  MIR_CLIENT_PLATFORM_PATH=../mir-2.4.1/build-ppc64el/bin/../lib/client-modules/
  MIR_SERVER_PLATFORM_PATH=../mir-2.4.1/build-ppc64el/bin/../lib/server-modules/
  LD_LIBRARY_PATH=../mir-2.4.1/build-ppc64el/bin/../lib
  exec=../mir-2.4.1/build-ppc64el/bin/mir_umock_unit_tests.bin
  *** stack smashing detected ***: terminated
  umockdev-run: unable to propagate signal 6 to child 15833: No such process

  (You can also see this in the Mir 2.4.1-0ubuntu1 build log:
  https://launchpadlibrarian.net/546972958/buildlog_ubuntu-impish-
  ppc64el.mir_2.4.1-0ubuntu1_BUILDING.txt.gz )

  Installing umockdev 0.15.4-1 and libumockdev0 0.15.4-1 from hirsute
  results in those tests passing.

  Strangely, rebuilding umockdev 0.15.4-1 in a hirsute sbuild
  environment results in packages that do *not* pass those tests,
  suggesting a toolchain change might be responsible.

  Unfortunately, I've tried rebuilding umockdev with gcc-9, gcc-11, and
  vala 0.48.12-1 in Impish and none of these appear to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: umockdev 0.16.1-1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  8 16:04:15 2021
  InstallationDate: Installed on 2021-06-26 (11 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
  SourcePackage: umockdev
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/umockdev/+bug/1934995/+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 1934995] Re: Broken on ppc64el (toolchain bug?)

2021-07-08 Thread Chris Halse Rogers
Seb has rebuilt bolt in impish, which uses umockdev for some of its
tests, and that apparently works (
https://matrix.to/#/!cVrEyzKyyNYOVfcQsb:libera.chat/$az_4Y_uIkZ02vMS6WjfQlkTvOH_ikJQTCkqRsAcOBfY?via=libera.chat=matrix.org=cooperteam.net
)

The stack-smashing backtrace implicates LTTNG, so maybe there's some
strange interaction there?

I'm not sure this is an upstream bug, as rebuilding 0.15.4 makes the
crash appear.

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

Title:
  Broken on ppc64el (toolchain bug?)

Status in umockdev package in Ubuntu:
  New

Bug description:
  umockdev appears to be broken on ppc64el in impish. Running it on one
  of Mir's umockdev-using tests results in:

  (impish-ppc64el)root@juju-deb017-porterbox-1:/build/mir-Xn1VqE/umockdev# 
umockdev-run ../mir-2.4.1/build-ppc64el/bin/mir_umock_unit_tests
  MIR_CLIENT_PLATFORM_PATH=../mir-2.4.1/build-ppc64el/bin/../lib/client-modules/
  MIR_SERVER_PLATFORM_PATH=../mir-2.4.1/build-ppc64el/bin/../lib/server-modules/
  LD_LIBRARY_PATH=../mir-2.4.1/build-ppc64el/bin/../lib
  exec=../mir-2.4.1/build-ppc64el/bin/mir_umock_unit_tests.bin
  *** stack smashing detected ***: terminated
  umockdev-run: unable to propagate signal 6 to child 15833: No such process

  (You can also see this in the Mir 2.4.1-0ubuntu1 build log:
  https://launchpadlibrarian.net/546972958/buildlog_ubuntu-impish-
  ppc64el.mir_2.4.1-0ubuntu1_BUILDING.txt.gz )

  Installing umockdev 0.15.4-1 and libumockdev0 0.15.4-1 from hirsute
  results in those tests passing.

  Strangely, rebuilding umockdev 0.15.4-1 in a hirsute sbuild
  environment results in packages that do *not* pass those tests,
  suggesting a toolchain change might be responsible.

  Unfortunately, I've tried rebuilding umockdev with gcc-9, gcc-11, and
  vala 0.48.12-1 in Impish and none of these appear to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: umockdev 0.16.1-1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  8 16:04:15 2021
  InstallationDate: Installed on 2021-06-26 (11 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
  SourcePackage: umockdev
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/umockdev/+bug/1934995/+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 1934995] [NEW] Broken on ppc64el (toolchain bug?)

2021-07-08 Thread Chris Halse Rogers
Public bug reported:

umockdev appears to be broken on ppc64el in impish. Running it on one of
Mir's umockdev-using tests results in:

(impish-ppc64el)root@juju-deb017-porterbox-1:/build/mir-Xn1VqE/umockdev# 
umockdev-run ../mir-2.4.1/build-ppc64el/bin/mir_umock_unit_tests
MIR_CLIENT_PLATFORM_PATH=../mir-2.4.1/build-ppc64el/bin/../lib/client-modules/
MIR_SERVER_PLATFORM_PATH=../mir-2.4.1/build-ppc64el/bin/../lib/server-modules/
LD_LIBRARY_PATH=../mir-2.4.1/build-ppc64el/bin/../lib
exec=../mir-2.4.1/build-ppc64el/bin/mir_umock_unit_tests.bin
*** stack smashing detected ***: terminated
umockdev-run: unable to propagate signal 6 to child 15833: No such process

(You can also see this in the Mir 2.4.1-0ubuntu1 build log:
https://launchpadlibrarian.net/546972958/buildlog_ubuntu-impish-
ppc64el.mir_2.4.1-0ubuntu1_BUILDING.txt.gz )

Installing umockdev 0.15.4-1 and libumockdev0 0.15.4-1 from hirsute
results in those tests passing.

Strangely, rebuilding umockdev 0.15.4-1 in a hirsute sbuild environment
results in packages that do *not* pass those tests, suggesting a
toolchain change might be responsible.

Unfortunately, I've tried rebuilding umockdev with gcc-9, gcc-11, and
vala 0.48.12-1 in Impish and none of these appear to work.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: umockdev 0.16.1-1
ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
Uname: Linux 5.11.0-20-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu67
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul  8 16:04:15 2021
InstallationDate: Installed on 2021-06-26 (11 days ago)
InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
SourcePackage: umockdev
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Broken on ppc64el (toolchain bug?)

Status in umockdev package in Ubuntu:
  New

Bug description:
  umockdev appears to be broken on ppc64el in impish. Running it on one
  of Mir's umockdev-using tests results in:

  (impish-ppc64el)root@juju-deb017-porterbox-1:/build/mir-Xn1VqE/umockdev# 
umockdev-run ../mir-2.4.1/build-ppc64el/bin/mir_umock_unit_tests
  MIR_CLIENT_PLATFORM_PATH=../mir-2.4.1/build-ppc64el/bin/../lib/client-modules/
  MIR_SERVER_PLATFORM_PATH=../mir-2.4.1/build-ppc64el/bin/../lib/server-modules/
  LD_LIBRARY_PATH=../mir-2.4.1/build-ppc64el/bin/../lib
  exec=../mir-2.4.1/build-ppc64el/bin/mir_umock_unit_tests.bin
  *** stack smashing detected ***: terminated
  umockdev-run: unable to propagate signal 6 to child 15833: No such process

  (You can also see this in the Mir 2.4.1-0ubuntu1 build log:
  https://launchpadlibrarian.net/546972958/buildlog_ubuntu-impish-
  ppc64el.mir_2.4.1-0ubuntu1_BUILDING.txt.gz )

  Installing umockdev 0.15.4-1 and libumockdev0 0.15.4-1 from hirsute
  results in those tests passing.

  Strangely, rebuilding umockdev 0.15.4-1 in a hirsute sbuild
  environment results in packages that do *not* pass those tests,
  suggesting a toolchain change might be responsible.

  Unfortunately, I've tried rebuilding umockdev with gcc-9, gcc-11, and
  vala 0.48.12-1 in Impish and none of these appear to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: umockdev 0.16.1-1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  8 16:04:15 2021
  InstallationDate: Installed on 2021-06-26 (11 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
  SourcePackage: umockdev
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/umockdev/+bug/1934995/+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 1932542] Re: Add support for zstd

2021-07-06 Thread Chris Halse Rogers
Hello Dimitri, or anyone else affected,

Accepted initramfs-tools into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.130ubuntu3.13 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: initramfs-tools (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

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

Title:
  Add support for zstd

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Fix Committed
Status in initramfs-tools source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * initramfs-tools in impish has changed default initrd compression to
  zstd. To allow compressing and uncompressing such initrds on Focal LTS
  release we should backport zstd support in the mkinitramfs &
  unmkinitramffs tooling. For example ubuntu-cdimage uses unmkinitramfs
  tool to unpack and inspect impish initrds on a focal host.

   * Cherrypicking the feature from 0.138 release, which is also present
  in Hirsute and Impish.

  [Test Plan]

   * Create initrd with zstd $ mkinitramfs -c zstd -o zstd-initrd.img

   * Uncompress it with $ unmkinitramfs ./zstd-initrd.img zstd-initrd-
  unpacked

   * For bionic also repeat the same with lz4.

  [Where problems could occur]

   * This adds support for zstd compressed initrd in both mkinitramfs
  and unmkinitramfs. However our GA kernels do not support zstd
  compressed initrds. And depends on zstd package is not added either.
  Meaning one still has to install zstd to gain the unpack support.
  Changing initramfs.conf to zstd may result in unbootable instance when
  used with GA kernel.

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

2021-07-06 Thread Chris Halse Rogers
The verification of the Stable Release Update for reprepro 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 file in Ubuntu.
https://bugs.launchpad.net/bugs/1923845

Title:
  Please compress packages with zstd by default

Status in appstream-glib package in Ubuntu:
  New
Status in apt package in Ubuntu:
  Fix Released
Status in aptly package in Ubuntu:
  New
Status in boinc package in Ubuntu:
  New
Status in busybox package in Ubuntu:
  New
Status in cdebootstrap package in Ubuntu:
  New
Status in cdist package in Ubuntu:
  New
Status in debdelta package in Ubuntu:
  New
Status in debian-el package in Ubuntu:
  New
Status in debootstrap package in Ubuntu:
  Fix Released
Status in debsig-verify package in Ubuntu:
  New
Status in debsigs package in Ubuntu:
  New
Status in diffoscope package in Ubuntu:
  Fix Committed
Status in dpkg package in Ubuntu:
  Fix Released
Status in dpkg-sig package in Ubuntu:
  New
Status in file package in Ubuntu:
  New
Status in hello package in Ubuntu:
  Fix Released
Status in libsolv package in Ubuntu:
  New
Status in lintian package in Ubuntu:
  Fix Released
Status in lutris package in Ubuntu:
  New
Status in obs-build package in Ubuntu:
  New
Status in osc package in Ubuntu:
  New
Status in radare2 package in Ubuntu:
  New
Status in reprepro package in Ubuntu:
  Fix Released
Status in vim-scripts package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  New
Status in reprepro source package in Focal:
  Fix Released
Status in reprepro source package in Groovy:
  Fix Released
Status in reprepro source package in Hirsute:
  Fix Released
Status in debian-el package in Debian:
  New

Bug description:
  https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
  on Hirsute having both data and control members of the .deb being
  compressed with zstd. It can be handy for testing various tools.

  [dpkg]
  Decompression support in dpkg landed first in Bionic and is being SRUd to 
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the 
zstd-compressed binary packages.
  From dpkg's perspective the upgrade path is cleared.

  The original plan was compressing only the internal data.tar .deb
  member, but dpkg uses uniform compression by default since dpkg 1.19.0
  thus I'm collecting all the changes to support control.tar.zst, too,
  in this bug.

  Reviewed packages from:
  https://codesearch.debian.net/search?q=data.tar.xz=1=1
  https://codesearch.debian.net/search?q=control.tar.xz=1=1

  appstream-glib  - needs fix: libappstream-builder/asb-package-deb.c
  aptly   - needs fix: deb/deb.go
  boinc   - needs fix: debian/fetch_example_applications.sh
  busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
  cdebootstrap- needs fix: src/package.c
  cdist   - may need fix, can use dpkg-deb: 
cdist/preos/debootstrap/files/devuan-debootstrap/functions
  debdelta- needs fix: debdelta debpatch.sh
  debian-el   - needs fix: deb-view.el
  debian-handbook - needs fix, maybe later, for Debian
  debootstrap - needs fix, 
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
  debsigs - needs fix, debsigs
  debsig-verify   - needs fix, src/debsig-verify.c
  diffoscope  - needs fix, diffoscope/comparators/deb.py
  dpkg- needs fix, change default
  dpkg-sig- needs fix, dpkg-sig
  dpmb- needs fix, maybe later, for Debian
  elfutils- may need fix, uses dpkg-deb if it is available, does not 
handle .gz either
  file- needs fix, magic/Magdir/archive
  libsolv - needs fix, ext/repo_deb.c
  lintian - needs fix malformed-deb-archive
  lutris  - needs fix, lutris/util/extract.py
  obs-build   - needs fix Build/Deb.pm
  osc - needs fix osc/util/debquery.py control.tar.zst only
  python-apt  - needs fix 
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
  radare2 - needs fix
  reprepro- needs fix, debfile.c
  vim-scripts - needs fix debPlugin/autoload/deb.vim
  winetricks  - needs fix when Debian switches src/winetricks
  zeroinstall-injector - needs fix src/zeroinstall/archive.ml

  acr - skip, does not _have to_ be fixed, just creates packages, 
see dist/deb_hand.mak
  alien   - skip, uses dpkg-deb to extract .deb
  ansible - not affected, just test data in dbdata.tar.xz
  anthy   - not affected, just changelog entry
 

[Touch-packages] [Bug 1925795] Re: SRU the current 0.20.4 stable update

2021-06-09 Thread Chris Halse Rogers
Hey Seb! This is a candidate for release into -updates, but I don't
think we can do that while it supersedes any package in Groovy.

I understand that the Desktop team has constrained resources. The SRU
team intends to propose a policy change to help, but for now could you
please do a Groovy upload too?

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

Title:
  SRU the current 0.20.4 stable update

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

Bug description:
  * Impact

  That's the current GNOME stable update, including some bugfixes and 
translation updates
  https://gitlab.gnome.org/GNOME/libsecret/-/blob/master/NEWS

  There are non trivial changes to the meson build system included in
  the update but we still build using autotools so that's not impacting
  us

  
  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Libsecret is providing an API to access gnome-keyring secrets, try a few 
applications using it and make sure credentials are correctly available. To 
list a few possible candidate softwares
  - evince (try to open a a password protected pdf, it should store and 
remember the password)
  - evolution
  - epiphany-browser 
  - vinagre
  - balsa
  - deja-dup

  * Regression potential

  Nothing specific to try in those changes, just ensure the library
  still access the passwords as expected

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

2021-06-02 Thread Chris Halse Rogers
The verification of the Stable Release Update for evolution-data-server
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 evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1925742

Title:
  Recent iCloud versions trigger an issue in IMAP x

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Focal:
  Fix Released

Bug description:
  * Impact

  The Icloud service introduced changes that are confusing evolution-
  data-server which means evolution is now failing to connect to the
  email server

  * Test case

  Set up an iCloud account and try to use it for emails in evolution

  * Regression potential

  The change is in the imapx connection code, it could create problems
  with other type of servers so we should try to test on different
  providers.

  
  -


  The bug has been fixed yesterday by Evolution's developer:
  https://gitlab.gnome.org/GNOME/evolution/-/issues/1468

  However, the package in Ubuntu (at least in Focal Fosa) still needs to
  be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+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 1922951] Update Released

2021-06-02 Thread Chris Halse Rogers
The verification of the Stable Release Update for evolution-data-server
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 evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1922951

Title:
  SRU the current 3.36.5 stable update

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Focal:
  Fix Released

Bug description:
  * Impact

  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that the calendar integration in GNOME and gnome-calendar is
  working, also test evolution with an email account.

  * Regression potential

  There is no specific change or feature to test in the upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1922951/+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 1925775] Re: SRU the current 3.36.1 stable update

2021-05-26 Thread Chris Halse Rogers
Hello Sebastien, or anyone else affected,

Accepted gnome-online-accounts into focal-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/gnome-online-accounts/3.36.1-0ubuntu1 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: gnome-online-accounts (Ubuntu Focal)
   Status: New => 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 gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/1925775

Title:
  SRU the current 3.36.1 stable update

Status in gnome-online-accounts package in Ubuntu:
  Fix Released
Status in gnome-online-accounts source package in Focal:
  Fix Committed

Bug description:
  * Impact
  That's the current GNOME stable update, including some API documentation 
fixes and translation updates
  https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/blob/gnome-3-36/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Try adding online account in a GNOME session, ensure the service is
  correctly enabled in application, for example that a google accounts
  are picked up in gnome-calendar and evolution.

  * Regression potential

  The changes are in API documentation so nothing specific to check, if
  there is an issue it would be from a toolchain regression

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1925775/+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 1926843] Re: online accounts integration with fb isn't working

2021-05-26 Thread Chris Halse Rogers
Hello Lars, or anyone else affected,

Accepted gnome-online-accounts into focal-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/gnome-online-accounts/3.36.1-0ubuntu1 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: gnome-online-accounts (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 gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/1926843

Title:
  online accounts integration with fb isn't working

Status in gnome-online-accounts package in Ubuntu:
  Fix Released
Status in gnome-online-accounts source package in Focal:
  Fix Committed
Status in gnome-online-accounts source package in Hirsute:
  Fix Committed

Bug description:
  * Impact

  The online accounts setting are proposing a facebook item which isn't
  working

  * Test case

  Go to settings -> online account, browse the accounts option proposed,
  facebook shouldn't be in the list since it doesn't work.

  * Regression potential

  The change is to disable the facebook provider using the upstream
  provided build option. Check that facebook isn't listed anymore but
  that the other providers still are. Since it's a build option change
  it could fail to build so check for that as well on launchpad.

  Since the facebook service currently doesn't consider gnome-online-
  accounts as a valid client there should be no user with that provider
  configured. Even if there were since the service isn't working they
  would see a functional regression.

  ---

  Hi i tryed to use gnome-control-center online-accounts to make easy
  like windows 10 to login to email or add other login so its more easy
  with ID to use pincode or other ID fingerprint and other.

  But its look its much issue compared with windows 10 with thunderbird,
  firefox, and other program.

  Worst is facebook only little windows with issue with login?

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-online-accounts 3.38.1-1ubuntu1
  Uname: Linux 5.12.0-051200-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  1 19:38:03 2021
  InstallationDate: Installed on 2019-05-07 (725 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+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 1926254] Update Released

2021-05-18 Thread Chris Halse Rogers
The verification of the Stable Release Update for openssl 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 openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1926254

Title:
  x509 Certificate verification fails when
  basicConstraints=CA:FALSE,pathlen:0 on self-signed leaf certs

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Focal:
  Fix Committed
Status in openssl source package in Groovy:
  Fix Committed
Status in openssl source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  In openssl 1.1.1f, the below commit was merged:

  commit ba4356ae4002a04e28642da60c551877eea804f7
  Author: Bernd Edlinger 
  Date:   Sat Jan 4 15:54:53 2020 +0100
  Subject: Fix error handling in x509v3_cache_extensions and related functions
  Link: 
https://github.com/openssl/openssl/commit/ba4356ae4002a04e28642da60c551877eea804f7

  This introduced a regression which caused certificate validation to
  fail when certificates violate RFC 5280 [1], namely, when a
  certificate has "basicConstraints=CA:FALSE,pathlen:0". This
  combination is commonly seen by self-signed leaf certificates with an
  intermediate CA before the root CA.

  Because of this, openssl 1.1.1f rejects these certificates and they
  cannot be used in the system certificate store, and ssl connections
  fail when you try to use them to connect to a ssl endpoint.

  The error you see when you try verify is:

  $ openssl verify -CAfile CA/rootCA_cert.pem -untrusted CA/subCA_cert.pem 
user1_cert.pem
  error 20 at 0 depth lookup: unable to get local issuer certificate
  error user1_cert.pem: verification failed

  The exact same certificates work fine on Xenial, Bionic and Hirsute.

  [1] https://tools.ietf.org/html/rfc5280.html

  [Testcase]

  We will create our own root CA, intermediate CA and leaf server
  certificate.

  Create necessary directories:

  $ mkdir reproducer
  $ cd reproducer
  $ mkdir CA

  Write openssl configuration files to disk for each CA and cert:

  $ cat << EOF >> rootCA.cnf
  [ req ]
  prompt  = no
  distinguished_name  = req_distinguished_name
  x509_extensions = usr_cert

  [ req_distinguished_name ]
  C  = DE
  O  = Test Org
  CN = Test RSA PSS Root-CA

  [ usr_cert ]
  basicConstraints= critical,CA:TRUE
  keyUsage= critical,keyCertSign,cRLSign
  subjectKeyIdentifier= hash
  authorityKeyIdentifier  = keyid:always
  EOF

  $ cat << EOF >> subCA.cnf
  [ req ]
  prompt  = no
  distinguished_name  = req_distinguished_name
  x509_extensions = usr_cert

  [ req_distinguished_name ]
  C  = DE
  O  = Test Org
  CN = Test RSA PSS Sub-CA

  [ usr_cert ]
  basicConstraints= critical,CA:TRUE,pathlen:0
  keyUsage= critical,keyCertSign,cRLSign
  subjectKeyIdentifier= hash
  authorityKeyIdentifier  = keyid:always
  EOF

  $ cat << EOF >> user.cnf
  [ req ]
  prompt  = no
  distinguished_name  = req_distinguished_name
  x509_extensions = usr_cert

  [ req_distinguished_name ]
  C  = DE
  O  = Test Org
  CN = Test User

  [ usr_cert ]
  basicConstraints= critical,CA:FALSE,pathlen:0
  keyUsage= critical,digitalSignature,keyAgreement
  extendedKeyUsage= clientAuth,serverAuth
  subjectKeyIdentifier= hash
  authorityKeyIdentifier  = keyid:always
  EOF

  Then generate the necessary RSA keys and form certificates:

  $ openssl genpkey -algorithm RSA-PSS -out rootCA_key.pem -pkeyopt 
rsa_keygen_bits:2048
  $ openssl req -config rootCA.cnf -set_serial 01 -new -batch -sha256 -nodes 
-x509 -days 9125 -out CA/rootCA_cert.pem -key rootCA_key.pem -sigopt 
rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1

  $ openssl genpkey -algorithm RSA-PSS -out subCA_key.pem -pkeyopt 
rsa_keygen_bits:2048
  $ openssl req -config subCA.cnf -new -out subCA_req.pem -key subCA_key.pem 
-sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1
  $ openssl x509 -req -sha256 -in subCA_req.pem -CA CA/rootCA_cert.pem -CAkey 
rootCA_key.pem -out CA/subCA_cert.pem -CAserial rootCA_serial.txt 
-CAcreateserial -extfile subCA.cnf -extensions usr_cert -days 4380 -sigopt 
rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1
  $ c_rehash CA

  $ openssl genpkey -algorithm RSA-PSS -out user1_key.pem -pkeyopt 
rsa_keygen_bits:2048
  $ openssl req -config user.cnf -new -out user1_req.pem -key user1_key.pem 
-sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1
  $ openssl x509 -req -sha256 -in user1_req.pem -CA CA/subCA_cert.pem -CAkey 

[Touch-packages] [Bug 1927161] Update Released

2021-05-18 Thread Chris Halse Rogers
The verification of the Stable Release Update for openssl 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 openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1927161

Title:
  dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch'
  patches files multiple times; split the diff in multiple files or
  merge the hunks into a single one

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Groovy:
  Fix Committed
Status in openssl source package in Hirsute:
  Fix Committed
Status in openssl source package in Impish:
  Fix Released

Bug description:
  [impact]

  openssl doesn't build source properly because of a badly-constructed
  patch

  [test case]

  $ pull-lp-source openssl groovy
  ...
  $ cd openssl-1.1.1f/
  $ quilt pop -a
  ...
  $ dpkg-buildpackage -d -S
  dpkg-buildpackage: info: source package openssl
  dpkg-buildpackage: info: source version 1.1.1f-1ubuntu4.3
  dpkg-buildpackage: info: source distribution groovy-security
  dpkg-buildpackage: info: source changed by Marc Deslauriers 

   dpkg-source --before-build .
  dpkg-source: warning: can't parse dependency perl:native
  dpkg-source: error: diff 'openssl-1.1.1f/debian/patches/pr12272.patch' 
patches files multiple times; split the diff in multiple files or merge the 
hunks into a single one
  dpkg-buildpackage: error: dpkg-source --before-build . subprocess returned 
exit status 25

  Test builds are available in the following ppa:

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

  [regression potential]

  any regression would likely cause a failed build or would affect the
  functionality that patch pr12272 was added for, which is adding
  support for Intel CET

  [scope]

  this is needed only for g and later

  this is caused by the bad patch 'pr12272.patch' which is only included
  in g/h/i, so this does not apply to f or earlier

  [other info]

  note that if the patches are applied, this bug is bypassed; i.e. if
  'quilt pop -a' is removed from the test case above, the bug doesn't
  reproduce. this is only a problem when the patches aren't already
  applied and dpkg-buildpackage needs to call dpkg-source to apply the
  patches.

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

2021-05-18 Thread Chris Halse Rogers
The verification of the Stable Release Update for rtl8812au 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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1914279

Title:
  linux from security may force reboots without complete dkms modules

Status in acpi-call package in Ubuntu:
  Fix Released
Status in apt package in Ubuntu:
  Invalid
Status in backport-iwlwifi-dkms package in Ubuntu:
  Fix Released
Status in bcmwl package in Ubuntu:
  Fix Released
Status in dahdi-linux package in Ubuntu:
  Fix Released
Status in dkms package in Ubuntu:
  Fix Released
Status in dm-writeboost package in Ubuntu:
  Fix Released
Status in evdi package in Ubuntu:
  Fix Released
Status in gost-crypto package in Ubuntu:
  Fix Released
Status in iptables-netflow package in Ubuntu:
  Fix Released
Status in liblzf package in Ubuntu:
  Fix Released
Status in lime-forensics package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-meta package in Ubuntu:
  Triaged
Status in lttng-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in openafs package in Ubuntu:
  New
Status in oss4 package in Ubuntu:
  Fix Released
Status in r8168 package in Ubuntu:
  Fix Released
Status in rtl8812au package in Ubuntu:
  Fix Released
Status in sysdig package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  Invalid
Status in v4l2loopback package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Fix Released
Status in virtualbox-hwe package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in acpi-call source package in Focal:
  Fix Released
Status in backport-iwlwifi-dkms source package in Focal:
  Fix Released
Status in bcmwl source package in Focal:
  Fix Released
Status in dahdi-linux source package in Focal:
  Fix Released
Status in dm-writeboost source package in Focal:
  Fix Released
Status in evdi source package in Focal:
  Fix Released
Status in gost-crypto source package in Focal:
  Fix Released
Status in iptables-netflow source package in Focal:
  Fix Released
Status in liblzf source package in Focal:
  Fix Released
Status in lime-forensics source package in Focal:
  Fix Released
Status in lttng-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Focal:
  Fix Released
Status in oss4 source package in Focal:
  Fix Released
Status in r8168 source package in Focal:
  Fix Released
Status in rtl8812au source package in Focal:
  Fix Released
Status in sysdig source package in Focal:
  Fix Released
Status in v4l2loopback source package in Focal:
  Fix Released
Status in virtualbox source package in Focal:
  Fix Released
Status in virtualbox-hwe source package in Focal:
  Fix Released
Status in zfs-linux source package in Focal:
  Fix Released

Bug description:
  Whilst discussing

  https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
  ubuntu-desktop-installation-media/20606

  We have noticed a reference to somebody not having working backport-
  iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8
  switch.

  However, kernel meta switch was pushed to security pocket, but the
  dkms modules are all in -updates only.

  This may result in people automatically installing the new kernel with
  unatanded upgrades; dkms modules failing to build; and a reboot
  required flag left on disk.

  At this point launching update manager will not offer to install dkms
  modules from updates, and will guide the users to reboot. which
  will then cause them to boot the new kernel without the dkms modules
  that might be providing networking for them.

  Should dkms modules SRUs always getting published into -security
  pocket, as well as the -updates pocket?

  Should linux maintainer scripts prevent touching reboot required flag
  if any dkms modules fail to build?

  Should apt / unattanded-upgrades / update-manager always update dkms
  modules with kernels?

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

2021-05-18 Thread Chris Halse Rogers
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/1917780

Title:
  initramfs-tools does not include fsck binaries in the initrd if all
  mount pass are 0

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Fix Released
Status in initramfs-tools source package in Focal:
  Fix Released
Status in initramfs-tools source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * initramfs-tools does not include fsck in initrd if MNT_PASS equals
  zero in the fstab entries.

  This has lead to the following situation :
  when dropping to initramfs shell during boot due to fs errors, we are not 
able to run fsck manually
  because it is not included in initrd.

  fsck should be included regardless of the MNT_PASS value.

  [Test Plan]

   * change /etc/fstab with PASSNO set to 0 for all entries
   * update-initramfs -u
   * lsinitramfs that is just generated
   * observe that it includes fsck utilities for the filesystems in /etc/fstab. 
I.e. fsck.ext4 e2fsck must exist

  [Where problems could occur]

   * The initramfs size will increase slightly upon upgrade, for the
  same initramfs-tools default options & kernel. However, one can
  control and remove fsck binaries (or include more of them) by setting
  FSTYPE variable in the initramfs settings.

  [scope]

  this is required for b/f/g

  this is fixed already in h and i

  [other info]

  debian MR is open:
  https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/49

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

2021-05-18 Thread Chris Halse Rogers
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/1927779

Title:
  MODULES=list results in error

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Invalid
Status in initramfs-tools source package in Focal:
  Fix Released
Status in initramfs-tools source package in Groovy:
  Fix Released

Bug description:
  [impact]

  setting MODULES=list in /etc/initramfs-tools/initramfs.conf results in
  an error/warning when running update-initramfs

  [test case]

  edit initramfs.conf to change MODULES=list and run update-initramfs:

  $ grep MODULES /etc/initramfs-tools/initramfs.conf
  # MODULES: [ most | netboot | dep | list ]
  MODULES=list
  $ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-5.8.0-48-generic
  find: ‘/var/tmp/mkinitramfs_Yr04uh/lib/modules/5.8.0-48-generic/kernel’: No 
such file or directory

  [regression potential]

  any regression would likely result in an initramfs that did not
  include the correct/required modules, and/or failure to build a new
  initramfs

  [scope]

  this is needed for f and g.

  this is not fixed in debian, but is fixed in h and i.

  the code in b is different and doesn't include this bug, so this
  doesn't apply to b.

  for debian, MR open:
  https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/48

  [other info]

  this caused some of the 'amd64-*' autopkgtests to fail in h until it
  was fixed. those autopkgtests don't exist in g and earlier so this was
  not noticed until now.

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

2021-05-18 Thread Chris Halse Rogers
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/1876570

Title:
  Could not resume from hibernation when swap is specified as device

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Fix Committed
Status in initramfs-tools source package in Focal:
  Fix Committed
Status in initramfs-tools source package in Groovy:
  Fix Committed
Status in initramfs-tools source package in Hirsute:
  Fix Released

Bug description:
  [impact]

  unable to resume from hibernation when resume= boot param is specified
  as device path

  [test case]

  set up device/partition for swap, e.g. /dev/vda2

  add 'resume=/dev/vda2' kernel boot parameter

  hibernate

  power system back on; it should resume from /dev/vda2 instead of
  coldboot

  [regression potential]

  any regression would likely result in failure to correctly resume from
  hibernation, incorrectly attempting to resume from hibernation, or
  failing to resume from hibernation.

  [scope]

  this is needed in b/f/g/h

  this bug was introduced, ironically, by bug 1644975, which was added
  in bionic, so this bug doesn't exist in xenial.

  this code that introduced this bug isn't included in Debian, so no
  change is needed there.

  [original description]

  I originally experienced this on Pop!_OS but I have reproduced it on a
  freshly installed Ubuntu.

  1. Ubuntu 20.04 LTS
  2. initramfs-tools-core 0.136ubuntu6
  3. I expect the system to resume from hibernation when running pm_hibernate
  4. The system starts up anew when I try to resume

  I have setup a swap partition on /dev/vda2 in /etc/fstab. To enable
  hibernate I added the kernel parameter "resume=/dev/vda2" to
  GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and run update-grub.

  From debugging initramfs it tries to follow a symbolic link

  DEV=$(readlink "$resume")
  (see /usr/share/initramfs-tools/scripts/local-premount/resume, line 35)

  which works well when swap is specified with uuid. When swap is
  specified as a device directly the readlink returns an empty string
  and the system does not resume from hibernation.

  To verify this I added the parameter -f to readlink and run "update-
  initramfs -u". The system now hibernates successfully.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 13:26:02 2020
  InstallationDate: Installed on 2020-05-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1876570/+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 1926437] Re: [SRU] Backport zstd support, fix bug in python-apt

2021-05-18 Thread Chris Halse Rogers
The focal and groovy autopkgtest failures in apt-clone look suspiciously
like real regressions. Do we have an analysis of those?

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

Title:
  [SRU] Backport zstd support, fix bug in python-apt

Status in apt package in Ubuntu:
  Fix Released
Status in python-apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in python-apt source package in Xenial:
  Fix Committed
Status in python-apt source package in Bionic:
  Fix Committed
Status in python-apt source package in Focal:
  Fix Committed
Status in python-apt source package in Groovy:
  Fix Committed
Status in python-apt source package in Hirsute:
  Fix Released
Status in python-apt source package in Impish:
  Fix Released

Bug description:
  [Impact]
  APT in xenial needs to learn about zstd support to enable Launchpad to work 
with zstd packages.

  python-apt in all releases needs to be adjusted to pass the compressor
  names instead of programs to ExtractTar, as otherwise, if
  /usr/bin/zstd does not exist, it will pass "false" as the compressor,
  and then ExtractTar fails (same for other compressors).

  On hirsute, the python-apt upload also includes some new  
annotations for build-dependencies, as it's a straight upload of the 2.2
  stable series.

  [Test plan]
  The apt regression tests cover the compression methods extensively, including 
even stored compressed lists in /var/lib/apt and fetching Packages files 
compressed with such methods, for all compression methods.

  The final test is to make apt_inst.DebFile("glibc-doc-
  reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall() from
  1923845 work in python3-apt.

  For hirsute, the build dependency changes will verify themselves
  during the build ;)

  [Where problems could occur]

  APT:

  The changes to APT are adding the zstd compression backend to FileFd
  and then linking it into the configuration. The former is adding new
  code, triggered only on zstd files, and should not be able to cause
  regressions.

  The latter is a bunch of small lines here and there, and it caused
  issues during backporting in the test suite because it expected
  compressors in a specific order. However, chances are that nothing
  else has as stringent requirements as the test suite, so I don't
  believe that is a problem for existing users.

  Bugs can of course be in the code dealing with zstd, and that might
  open you up to security vulnerabilities in the zstd code if you pass
  APT zstd compressed files.

  A regression can be if clients used apt-helper cat-file to cat a zstd-
  compressed file ending in .zst - they'll now get uncompressed content,
  rather than compressed.

  python-apt:

  The change just replaces Binary with Name, aligning the code with APT
  itself, so it's so trivial, we don't expect regressions.

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

2021-04-06 Thread Chris Halse Rogers
The verification of the Stable Release Update for apt 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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1806076

Title:
  unattended-upgrade --help raises UnicodeEncodeError when stdout
  encoding is ascii

Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Won't Fix
Status in apt source package in Xenial:
  New
Status in unattended-upgrades source package in Xenial:
  Won't Fix
Status in apt source package in Bionic:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Won't Fix

Bug description:
  [Impact]

   * unattended-upgrades --help crashes in apt.systemd.daily script when
  locale is not in UTF-8.

  [Test Case]

  In the fixed case no crash is observed.

  rbalint@yogi:~$ lxc launch ubuntu:18.04 bb-lp-1806076
  Creating bb-lp-1806076
  Starting bb-lp-1806076
  rbalint@yogi:~$ lxc shell bb-lp-1806076
  mesg: ttyname failed: No such device
  root@bb-lp-1806076:~# apt install -yqq language-pack-ru-base
  The following package was automatically installed and is no longer required:
    libfreetype6
  Use 'apt autoremove' to remove it.
  The following additional packages will be installed:
    language-pack-ru
  The following NEW packages will be installed:
    language-pack-ru language-pack-ru-base
  0 upgraded, 2 newly installed, 0 to remove and 7 not upgraded.
  Need to get 2310 kB of archives.
  After this operation, 11.8 MB of additional disk space will be used.
  Selecting previously unselected package language-pack-ru-base.
  (Reading database ... 28536 files and directories currently installed.)
  Preparing to unpack .../language-pack-ru-base_1%3a18.04+20180712_all.deb ...
  Unpacking language-pack-ru-base (1:18.04+20180712) ...
  Selecting previously unselected package language-pack-ru.
  Preparing to unpack .../language-pack-ru_1%3a18.04+20180712_all.deb ...
  Unpacking language-pack-ru (1:18.04+20180712) ...
  Setting up language-pack-ru (1:18.04+20180712) ...
  Setting up language-pack-ru-base (1:18.04+20180712) ...
  Generating locales (this might take a while)...
    ru_RU.UTF-8... done
    ru_UA.UTF-8... done
  Generation complete.

  root@bb-lp-1806076:~# echo LANG=ru_RU | tee /etc/default/locale
  LANG=ru_RU
  root@bb-lp-1806076:~#
  /usr/lib/apt/apt.systemd.daily update
  Traceback (most recent call last):
    File "/usr/bin/unattended-upgrade", line 2171, in 
  (options, args) = parser.parse_args()  # type: ignore
    File "/usr/lib/python3.6/optparse.py", line 1387, in parse_args
  stop = self._process_args(largs, rargs, values)
    File "/usr/lib/python3.6/optparse.py", line 1427, in _process_args
  self._process_long_opt(rargs, values)
    File "/usr/lib/python3.6/optparse.py", line 1501, in _process_long_opt
  option.process(opt, value, values, self)
    File "/usr/lib/python3.6/optparse.py", line 785, in process
  self.action, self.dest, opt, value, values, parser)
    File "/usr/lib/python3.6/optparse.py", line 807, in take_action
  parser.print_help()
    File "/usr/lib/python3.6/optparse.py", line 1647, in print_help
  file.write(self.format_help())
  UnicodeEncodeError: 'ascii' codec can't encode characters in position 
126-133: ordinal not in range(128)

  root@bb-lp-1806076:~# echo LANG=ru_RU.UTF-8 | tee /etc/default/locale
  LANG=ru_RU.UTF-8
  root@bb-lp-1806076:~# /usr/lib/apt/apt.systemd.daily update
  root@bb-lp-1806076:~#

  [Where problems could occur]

  * Nowhere, really. The fix is setting LC_ALL=C.UTF-8 for u-u --help
  and it is processed by grep then.

  [Original Bug Text]

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.1ubuntu1.18.04.6, the problem page at 
https://errors.ubuntu.com/problem/b3e3265e302351558260f54ae37c7b4c193dfc95 
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/.

  Also seen in:
   * https://errors.ubuntu.com/problem/936bb1c75c4efe018f968a5773b820bcf52c298a

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

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

[Touch-packages] [Bug 1877987] Update Released

2021-04-06 Thread Chris Halse Rogers
The verification of the Stable Release Update for apt 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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1877987

Title:
  apt search coredumping

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

Bug description:
  [Impact]
  Search sometimes crashes if no translated description is available, as the 
translated description object was used without a check as to whether it exists.

  [Test case]
  No reproducer available at the moment.

  
  [Where problems could occur]
  In search command only, and only when looking at descriptions

  [Original bug report]
  root@citoyx:/var/crash# apt search jdk
  Sorting... Done
  Segmentation fault (core dumped)

  May 11 12:34:25 citoyx kernel: [ 1354.337907] apt[10418]: segfault at 
7f67292dcfc0 ip 7f6309ce4997 sp 7ffdab880930 error 4 in 
libapt-pkg.so.6.0.0[7f6309bb5000+147000]
  May 11 12:34:25 citoyx kernel: [ 1354.337916] Code: 48 8b 45 18 48 8b 04 d0 
48 83 c4 08 5b 5d c3 0f 1f 40 00 f3 0f 1e fa 55 48 89 fd 53 48 89 f3 48 83 ec 
08 48 8b 06 48 8b 4e 08 <8b> 10 48 8d 04 d5 00 00 00 00 48 29 d0 48 8b 51 60 48 
8d 04 c2 0f

  root@citoyx:/var/crash# cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"

  apt search is coredumping
  While apt install/upgrade/update is running fine

  crash file in attachment.

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

2021-04-06 Thread Chris Halse Rogers
The verification of the Stable Release Update for apt 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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1918907

Title:
  Default Acquire::AllowReleaseInfoChange::Suite to "true"

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Fix Released

Bug description:
  [Impact]
  APT 1.6-2.0 deny third-party repositories from changing their Suite value. 
This change was reverted in later apt releases, and will be reverted in 1.8 in 
Debian as well, so for consistency, we want to push that change to stable

  [Test plan]
  We added test cases to our extensive integration test suite run by 
autopkgtest.

  [Where problems could occur]
  It's hard to imagine anything here, we simply turn the flag for allowed from 
false to true. We even add tests for Suite changes :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1918907/+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 1877987] Re: apt search coredumping

2021-04-06 Thread Chris Halse Rogers
apt 2.0.5 hasn't appeared in the errors.ubuntu.com crash bin, so that
seems a reasonable assertion.

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

Title:
  apt search coredumping

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

Bug description:
  [Impact]
  Search sometimes crashes if no translated description is available, as the 
translated description object was used without a check as to whether it exists.

  [Test case]
  No reproducer available at the moment.

  
  [Where problems could occur]
  In search command only, and only when looking at descriptions

  [Original bug report]
  root@citoyx:/var/crash# apt search jdk
  Sorting... Done
  Segmentation fault (core dumped)

  May 11 12:34:25 citoyx kernel: [ 1354.337907] apt[10418]: segfault at 
7f67292dcfc0 ip 7f6309ce4997 sp 7ffdab880930 error 4 in 
libapt-pkg.so.6.0.0[7f6309bb5000+147000]
  May 11 12:34:25 citoyx kernel: [ 1354.337916] Code: 48 8b 45 18 48 8b 04 d0 
48 83 c4 08 5b 5d c3 0f 1f 40 00 f3 0f 1e fa 55 48 89 fd 53 48 89 f3 48 83 ec 
08 48 8b 06 48 8b 4e 08 <8b> 10 48 8d 04 d5 00 00 00 00 48 29 d0 48 8b 51 60 48 
8d 04 c2 0f

  root@citoyx:/var/crash# cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"

  apt search is coredumping
  While apt install/upgrade/update is running fine

  crash file in attachment.

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

2021-02-16 Thread Chris Halse Rogers
The verification of the Stable Release Update for whoopsie 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 whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1914481

Title:
  use the size of the data when determining the server response

Status in whoopsie package in Ubuntu:
  Fix Released
Status in whoopsie source package in Focal:
  Fix Committed
Status in whoopsie source package in Groovy:
  Fix Released
Status in whoopsie source package in Hirsute:
  Fix Released

Bug description:
  [Note]
  This SRU has been built in a security-only PPA and should be released to both 
-updates and -security.

  [Impact]
  whoopsie's server_response code is using "g_string_append" instead of 
"g_string_append_len" which has the knock on effect of sending too much data to 
its "handle_response". This ends up being a problem if the daisy servers are 
running on Ubuntu 18.04 instead of Ubuntu 16.04.

  Here's an example when using whoopsie on groovy to send a crash to a
  bionic daisy server:

  [15:35:30] Sent; server replied with: No error
  [15:35:30] Response code: 200
  [15:35:30] Initial response data is: 2bbb776e-64e6-11eb-a8d6-00163eddedf4 
OOPSID
  0

  [15:35:30] Got command: OOPSID

  We can see a fair number of extra characters (\n0\n\n) after the OOSID
  command. This becomes more problematic when daisy requests a core dump
  from the client as the CORE command won't match and the client will
  never send the core dump.

  [Test Case]
  Setup a Bionic version of the Error Tracker:
  0) modify /etc/hosts so daisy.staging.ubuntu.com points to the IP of the 
apache server for daisy
  1) sudo service stop whoopsie
  2) sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f
  3) Run test/submit-crash test-crashes/hirsute/amd64/_bin_cat.2001.crash
  4) check the whoopsie log file for "Got command: OOPSID" and extra data.

  With the version of whoopsie from -proposed this will not happen.
  Additionally, a regression test should be run against the staging
  version of the error tracker by removing the entry from /etc/hosts for
  the daisy.staging server. After confirming that one test crash works
  one should also send a python crash, and an end of life release crash
  as those all generate different response codes from the server.

  [Regression Potential]
  The code being changed is clearly wrong and doesn't confirm to the curl API 
https://curl.se/libcurl/c/CURLOPT_WRITEFUNCTION.html. Additionallly, this is 
similar to the code before r707 of daisy which introduced this change so there 
is little chance of regression. That being said we are running a regression 
test to ensure whoopsie works with servers running Ubuntu 16.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1914481/+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 1883694] Proposed package upload rejected

2021-01-12 Thread Chris Halse Rogers
An upload of glib2.0 to focal-proposed has been rejected from the upload
queue for the following reason: "The bug reference in the changelog is
for https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1883694 which
is the already-fixed SRU bug for 2.64.3. Please file a new bug to track
this new SRU.".

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

Title:
  [SRU] New upstream release 2.64.3

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

Bug description:
  [ Description ]

  Take this new upstrem stable release.

  +glib2.0 (2.64.3-1~ubuntu20.04.1) UNRELEASED; urgency=medium
  +
  +  * No-change backport from unstable / groovy to focal.
  +
  + -- Iain Lane   Tue, 16 Jun 2020 11:53:34 +0100
  +
  +glib2.0 (2.64.3-1) unstable; urgency=medium
  +
  +  * Team upload
  +
  +  [ Laurent Bigonville ]
  +  * Drop the libgio-fam package, and install the fam GIO plugin in
  +libglib2.0-0 on Hurd ports. See: #885011 (Closes: #875915)
  +  * Stop building the libgio-fam package on kFreeBSD ports.
  +It is no longer necessary now that gkqueuefilemonitor is available.
  +
  +  [ Simon McVittie ]
  +  * Clarify changelog entry regarding Hurd and kFreeBSD
  +  * New upstream stable release
  +
  + -- Simon McVittie   Fri, 29 May 2020 20:24:33 +0100

  The gio-fam related changes do not affect Ubuntu, as they are for
  hurd/kfreebsd only.

  Upstream NEWS diff:

  * Stability improvements for various unit tests

  * Bugs fixed:
   - #1954 gdbus-server-auth intermittent failure
   - #2094 Deprecation warnings when compiling with 
-DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_28 
-DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_28
   - !1470 Backport !1440 -Wformat-nonliteral fixes to glib-2-64
   - !1471 Backport !1448 memory monitor test dependency fixes to glib-2-64
   - !1473 CI: Switch to new Windows runners (2.64)
   - !1478 Backport !1477 D-Bus keyring handling fixes to glib-2-64
   - !1483 Backport !1481 “array: fix corrupt state of GPtrArray after 
g_ptr_array_extend_and_steal()” to glib-2-64
   - !1484 Backport !1480 “CI: Make sure we use meson 0.49.2 in MSYS2” to 
glib-2-64
   - !1486 Backport !1472 “gthread: ignore deprecated declarations in static 
inline functions” to glib-2-64
   - !1495 Backport !1493 “meson: Remove stray ], in O_DIRECTORY check” to 
glib-2-64
   - !1501 Backport !1439 “Fix stpcpy() detection“ to glib-2-64

  * Translation updates:
   - Chinese (Taiwan)
   - German

  [ QA ]

  Upstream release, so QA already performed by maintainers

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  This upload will trigger many autopkgtests that we expect to not be
  regressed by this upload.

  [ Regression potential ]

  Various fixes in multiple places so multiple apps could be affected.
  Pretty much all parts of GNOME use GLib, so test anything in the
  desktop that you can.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1883694/+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 1881947] Re: Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52, function main(). Aborting.

2021-01-11 Thread Chris Halse Rogers
Hello dann, or anyone else affected,

Accepted systemd into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/246.6-1ubuntu1.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-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. 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 Groovy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-groovy

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

Title:
  Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52,
  function main(). Aborting.

Status in systemd:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in systemd source package in Hirsute:
  In Progress

Bug description:
  [Impact]

   * Autopkgtest fails due to corrupted journal file

  [Test Case]

   * Observe autopkgtest root-unittests not failing with:

  Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52,
  function main(). Aborting.

  [Where problems could occur]

   * The change has no impact on the systemd binary packages. The
  relaxed test could hide a journal corruption problem, but it seems the
  corrupted journal files occur only on arm64 probably due to arm64
  reboots being resets: LP: #1748280.

  [Original Bug Text]

  Observed in an focal/arm64 autopkgtest failure of systemd 245.4-4ubuntu3.1:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20200603_071743_738b2@/log.gz

  [...]
  PASS: test-journal-enum
  == test-journal-flush ===
  Root directory /var/log/journal removed.
  Directory /var/log/journal/3286b2469d224077b1026d239d625b0d removed.
  mmap cache statistics: 739 hit, 5 miss
  journal_file_copy_entry failed: Bad message
  Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52, function 
main(). Aborting.
  FAIL: test-journal-flush (code: 134)
  Aborted (core dumped)
  == test-journal-importer ===
  [...]
  autopkgtest [07:17:29]:  summary
  timedatedPASS
  hostnamedPASS
  localed-locale   PASS
  localed-x11-keymap   PASS
  logind   PASS
  unit-config  PASS
  storage  PASS
  networkd-test.py PASS
  build-login  PASS
  boot-and-servicesPASS
  udev PASS
  root-unittests   FAIL non-zero exit status 134
  upstream PASS
  boot-smoke   PASS
  systemd-fsckdPASS
  Exit request sent.
  [...]

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1881947/+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 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration

2021-01-11 Thread Chris Halse Rogers
Hello Christian, or anyone else affected,

Accepted systemd into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/246.6-1ubuntu1.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-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. 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 Groovy)
   Status: New => Fix Committed

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

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

Title:
  autopkgtest success rate dropped inhibiting proposed migration

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

Bug description:
  [impact]

  autopkgtests are failing/flaky and prevent other packages from
  migrating to -updates

  [test case]

  check autopkgtest history

  [regression potential]

  in regard to the changed test cases, any regression would likely
  result in either an incorrectly passed test, or an incorrectly failed
  test.

  [scope]

  for systemd, this is needed for x, b, and f.

  tests in g appear to be mostly stable, but I've opened MR (linked from
  this bug) to update the tests there as well.

  i don't plan to update x, as it's reaching ESM in ~6 months, and
  backporting the test fixes is more work than just a simple code copy,
  since there are additional differences/changes needed in the older
  version of systemd (and python3). the failing/flaky tests in x have
  been like that forever, and people have just retried them; we can keep
  retrying them until x moves into ESM next year.

  [original description]

  Hi,
  we had such cases in the past like bug 1817721 for bionic and maybe bug 
1892130 is about the same as well. There were more but I didn't want to search 
for all of them - what I checked is that there are no open ones clearly 
pointing out the recent further drop in already flaky subtests.

  In particular the tests "tests-in-lxd" and "systemd-fsckd" were known
  to be flaky before, but got even worse.

  Here stats of the last 40 runs, it might be a coincidences that this
  is after 246-2ubuntu1 landed. Could as well be any other change

  groovy
    amd64
  tests-in-lxd   (F 42% S  0% B 10% => P 45%/) 
BFFFBFF.B.F.F...FBF
  build-login(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  unit-config(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  networkd-testpy(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-and-services  (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-smoke (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  logind (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  storage(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  upstream   (F 35% S  0% B 10% => P 52%/) 
..FFB.FFF.FFBFF.B.F.F..FFBF
  udev   (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  systemd-fsckd  (F 37% S  0% B 10% => P 50%/) 
BFFFB.FF...FB.F..B.
  root-unittests (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
    ppc64el
  tests-in-lxd   (F 25% S  0% B  0% => P 75%/) 
FFFFF.F.
  systemd-fsckd  (F 35% S  0% B  0% => P 65%/) 
FFF...FFFFF.F..F
  root-unittests (F  2% S  0% B  0% => P 97%/) 

[Touch-packages] [Bug 1902960] Re: Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS resolution in some cases

2021-01-11 Thread Chris Halse Rogers
Hello David, or anyone else affected,

Accepted systemd into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/246.6-1ubuntu1.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-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. 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 Groovy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-groovy

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

Title:
  Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS
  resolution in some cases

Status in cloud-images:
  New
Status in systemd:
  New
Status in cloud-init package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Focal:
  Incomplete
Status in systemd source package in Focal:
  Fix Committed
Status in cloud-init source package in Groovy:
  Incomplete
Status in systemd source package in Groovy:
  Fix Committed

Bug description:
  [impact]

  on boot of a specific azure instance, the ID_NET_DRIVER parameter of
  the instance's eth0 interface is not set. That leads to a failure of
  systemd-networkd to take control of the interface after a restart of
  systemd-networkd, which results in DNS failures (at first) and
  eventually complete loss of networking (once the DHCP lease expires).

  [test case]

  this occurs on first boot of an instance using the specific image; it
  is not reproducable using the latest ubuntu image nor any reboot of
  the affected image, and it has not been reproducable (for me) when
  using debug-enabled images based on the affected image.

  So, while the problem is reproducable using the specific image in
  question, it's not possible to verify the fix since any change to the
  image removes reproducability.

  however, while the problem itself can't be reproduced and then
  verified, if the assumption is correct (that the 'add' uevent is being
  missed on boot), that is possible to test and verify:

  $ udevadm info /sys/class/net/eth0 | grep ID_NET_DRIVER
  E: ID_NET_DRIVER=hv_netvsc
  $ sudo rm /run/udev/data/n2 

  (note, change 'n2' to whichever network interface index is correct)

  $ udevadm info /sys/class/net/eth0 | grep ID_NET_DRIVER
  $ sudo udevadm trigger -c change /sys/class/net/eth0
  $ udevadm info /sys/class/net/eth0 | grep ID_NET_DRIVER

  (note the 'change' uevent did not populate ID_NET_DRIVER property)

  $ sudo udevadm trigger -c add /sys/class/net/eth0
  $ udevadm info /sys/class/net/eth0 | grep ID_NET_DRIVER
  E: ID_NET_DRIVER=hv_netvsc

  (note the 'add' uevent did populate ID_NET_DRIVER)

  the test verification should result in ID_NET_DRIVER being populated
  for a 'change' uevent.

  [regression potential]

  any regression would likely involve problems with systemd-udevd
  processing 'change' events from network devices, and/or incorrect
  udevd device properties.

  [scope]

  this is needed only for focal and groovy.

  this is fixed by upstream commit e0e789c1e97 which is first included
  in v247, so this is fixed already in hirsute.

  while this commit is not included in bionic, due to the difficult
  nature of reproducing (and verifying) this, and the fact it has only
  been seen once on a focal image, I don't think it's appropriate to SRU
  to bionic at this point; possibly it may be appropriate if this is
  ever reproduced with a bionic image.

  [other info]

  note that this bug's subject and description, as well as the upstream
  systemd bug subject and description, talk about the problem being DNS
  resolution. However that is strictly a side-effect of the real problem
  and is not the actual issue.

  [original description]

  The systemd upgrade 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to
  have broken DNS resolution across much of our Azure fleet earlier
  today.  We ended up mitigating this by forcing 

[Touch-packages] [Bug 1905044] Re: systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8

2021-01-11 Thread Chris Halse Rogers
Hello Kleber, or anyone else affected,

Accepted systemd into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/246.6-1ubuntu1.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-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. 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 Groovy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-groovy

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

Title:
  systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in systemd source package in Hirsute:
  Fix Released

Bug description:
  [impact]

  autopkgtest failure when running with 5.8 kernel, if systemd is built
  with earlier kernel (e.g. 5.4)

  [test case]

  see autopkgtest results, e.g. links in original description below

  [regression potential]

  as this only fixes a test case, any regression would likely result in
  an incorrectly passing, or incorrectly failing, test.

  [scope]

  this is needed for b/f/g/h.

  this bug was introduced by upstream commit 23cc81e7c22 which first
  added testing for 'invalid' cap numbers, but incorrectly using
  capability_list_length() instead of cap_last_cap(). That commit was
  first included in v236, so this bug does not exist before Bionic.

  this is fixed upstream by commit
  ebc815cd1c647faa934a446ceea91ff4bc9dffa4, which was first included in
  v247, so this is needed for h and earlier.

  Also note that even though the 5.8 kernel is not planned to be
  released for Bionic, this test also runs at build time, and since the
  LP build farm builds inside chroots, if the build farm ever moved up
  to Focal with a 5.8 kernel, the build of systemd for Bionic would
  start failing (since it would still be building using the older kernel
  headers, inside the chroot), so this does need to be fixed in Bionic
  systemd as well.

  [other info]

  there is a non-test bug related to this in bug 1905245

  [original description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20201117_174614_4ece6@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20201117_221555_48b91@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/s/systemd/20201117_175806_e779f@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20201117_153051_90e7e@/log.gz

  The failing testcases are:

  - root-unittests

  Assertion 'capability_set_to_string_alloc(c, ) == 0' failed at 
src/test/test-cap-list.c:60, funct
  ion test_capability_set_one(). Aborting.
  FAIL: test-cap-list (code: 134)

  - upstream

  TEST-24-UNIT-TESTS:

  --- test-cap-list begin ---
  Assertion 'capability_set_to_string_alloc(c, ) == 0' failed at 
src/test/test-cap-list.c:60, funct
  ion test_capability_set_one(). Aborting.
  --- test-cap-list end ---

  Both seem to be failing with the same assertion.

  These tests are successful on Focal with linux 5.4, therefore they
  would regress when upgrading the kernel from 5.4 to 5.8.

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

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

[Touch-packages] [Bug 1907306] Re: networkd dhcpv4 client never attempts more than 2 renew and 2 rebind

2021-01-11 Thread Chris Halse Rogers
Hello Dan, or anyone else affected,

Accepted systemd into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/246.6-1ubuntu1.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-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. 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 Groovy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-groovy

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

Title:
  networkd dhcpv4 client never attempts more than 2 renew and 2 rebind

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in systemd source package in Hirsute:
  In Progress

Bug description:
  [impact]

  networkd dhcpv4 client never attempts more than 2 renew and 2 rebind

  [test case]

  configure an interface to use dhcpv4; acquire a dhcpv4 address, then
  stop the dhcpv4 server, and wait for the networkd client to perform
  its renewals and rebinds before expiring the lease

  using a 20 minute lease time as an example (all times are approximate
  due to RFC-mandated random 'fuzz' time of -1 to +1 sec):

  the current behavior would be to sent renew requests at:

  10:00
  13:45

  and then rebind requests at:

  17:30
  18:45

  then the lease would expire at 20:00

  the correct/new behavior should be renew requests at:

  10:00
  13:45
  15:37
  16:37

  and then rebind requests at:

  17:30
  18:45
  19:45

  and then lease expiration at 20:00.

  longer lease times would increase the number of retransmissions.

  [regression potential]

  any regression would likely result in problems receiving and/or
  maintaining a dhcpv4 address

  [scope]

  this is needed in b/f/g/h.

  this was fixed upstream in:
  https://github.com/systemd/systemd/pull/17908

  that was just added, so this is not fixed in any ubuntu release yet.

  technically, this is needed in x as well, however I don't plan to
  backport to x since 1) it reaches ESM soon and 2) the default network
  management tool in x is ifupdown, not systemd-networkd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1907306/+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 1908067] Re: systemd-fsckd test fails on groovy checking plymouth-start isactive

2021-01-11 Thread Chris Halse Rogers
Hello Dan, or anyone else affected,

Accepted systemd into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/246.6-1ubuntu1.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-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. 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 Groovy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-groovy

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

Title:
  systemd-fsckd test fails on groovy checking plymouth-start isactive

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

Bug description:
  [impact]

  systemd-fsckd test fails on groovy because plymouth-start service is
  active

  [test case]

  check autopkgtest logs of systemd-fsckd test case on groovy

  [regression potential]

  incorrectly passed, or failed, systemd-fsckd test

  [scope]

  this is needed only for groovy.

  the plymouth-start.service did not include RemainAfterExit=true before 
groovy, so the service is expected to be inactive when checked by the test 
before groovy. this is already fixed in hirsute:
  
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c46eda821e97df5595a4cdc5f5c41a9b49a51745

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1908067/+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 1905245] Re: "Failed to parse bus message: Invalid argument" with Linux 5.8

2021-01-11 Thread Chris Halse Rogers
Hello Gary, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.44 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed-bionic

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

Title:
  "Failed to parse bus message: Invalid argument" with Linux 5.8

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

Bug description:
  [impact]

  newer kernels introduced a new capability, and existing systemd
  doesn't have the name mapping for the new cap (since the mapping table
  is generated at systemd compile time), so it fails when trying to map
  the capability to a user-facing name, which causes failure when
  running commands like 'systemctl show'

  [test case]

  install a focal system, and install the 5.8 (or newer) kernel, e.g.
  from linux-generic-hwe-20.04-edge, and reboot into the new kernel.

  Find any service that does not specify its CapabilityBoundingSet; e.g.
  'apparmor', and run systemctl show on it:

  ubuntu@lp1905245-f:~$ systemctl show -p CapabilityBoundingSet apparmor
  Failed to parse bus message: Invalid argument

  the command should correctly show the value, e.g.:
  $ systemctl show -p CapabilityBoundingSet apparmor
  CapabilityBoundingSet=cap_chown cap_dac_override ...etc...

  [regression potential]

  a regression would likely occur while systemd is parsing or printing
  or otherwise handling kernel capabilities. A regression could happen
  when running systemd commands, such as systemctl, or when pid1 is
  managing services.

  [scope]

  this is needed only in focal and bionic.

  This is fixed upstream by PR 16424:
  https://github.com/systemd/systemd/pull/16424
  which was first included in v246, so this is already fixed in groovy and 
later.

  This was introduced upstream in systemd by commit
  52610b020c077ee769c6923249f7e6c4e99d2980 which was first included in
  v235, so this bug does not exist in Xenial.

  This bug will reproduce on any system running under the 5.8 kernel,
  with the new capability, if the systemd binary was compiled with
  kernel headers that do not include the new capability. This means this
  is reproducable on bare-metal/vm instances running 5.8, as well as
  containers on hosts running 5.8. Therefore, while bionic may not ever
  receive a new kernel with added capability, it still needs to be
  patched to avoid the bug on a bionic container running on a host with
  the 5.8 kernel.

  [other info]

  there is a testcase-only related bug 1905044

  [original description]

  When I run `systemctl show myservice.service`, I get the following
  error message:

     Failed to parse bus message: Invalid argument

  systemd version: 245.4-4ubuntu3.3
  linux version: 5.8.0-29-generic #31~20.04.1-Ubuntu  (From 
linux-generic-hwe-20.04-edge)

  This is a bug that has been fixed in Debian. See
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964926

  Please can we port the fix to the ubuntu 20.04 version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905245/+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 1878955] Re: resolved dhclient-enter-hook complains about an empty file

2021-01-11 Thread Chris Halse Rogers
Hello Craig, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.44 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed-bionic

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

Title:
  resolved dhclient-enter-hook complains about an empty file

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

Bug description:
  [impact]

  When starting/using `dhclient`, it will often return an error such as:

  cmp: EOF on /tmp/tmp.yCyV6zBzhB which is empty

  [test case]

  run dhclient for the first time (for the current boot) on a
  bionic/focal system, or remove the file(s) in
  /run/systemd/resolved.conf.d/ starting with 'isc-dhcp-*', and then run
  dhclient.

  [regression potential]

  any regression would likely cause the DNS configuration that dhclient
  gets to not be properly reported to systemd-resolved, resulting in
  problematic/broken systemd DNS resolution.

  [scope]

  this is needed in b/f

  this hook was removed from systemd starting in g, and the hook was not
  yet added in x, so this change is needed only in b and f.

  [original description]

  When starting/using `dhclient`, it will often return an error such as:

  cmp: EOF on /tmp/tmp.yCyV6zBzhB which is empty

  This is due to the use of `cmp` in "/etc/dhcp/dhclient-enter-
  hooks.d/resolved"

  Because the $oldstate file can be empty, or different, it should use
  `cmp --quiet`

  This happens when "/run/systemd/resolved.conf.d/isc-
  dhcp-v*-$interface.conf" files do not exist, or when the content
  changes.

  This is very loosely related to
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1878955/+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 1881947] Re: Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52, function main(). Aborting.

2021-01-11 Thread Chris Halse Rogers
Hello dann, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.44 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed-bionic

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

Title:
  Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52,
  function main(). Aborting.

Status in systemd:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  In Progress
Status in systemd source package in Hirsute:
  In Progress

Bug description:
  [Impact]

   * Autopkgtest fails due to corrupted journal file

  [Test Case]

   * Observe autopkgtest root-unittests not failing with:

  Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52,
  function main(). Aborting.

  [Where problems could occur]

   * The change has no impact on the systemd binary packages. The
  relaxed test could hide a journal corruption problem, but it seems the
  corrupted journal files occur only on arm64 probably due to arm64
  reboots being resets: LP: #1748280.

  [Original Bug Text]

  Observed in an focal/arm64 autopkgtest failure of systemd 245.4-4ubuntu3.1:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20200603_071743_738b2@/log.gz

  [...]
  PASS: test-journal-enum
  == test-journal-flush ===
  Root directory /var/log/journal removed.
  Directory /var/log/journal/3286b2469d224077b1026d239d625b0d removed.
  mmap cache statistics: 739 hit, 5 miss
  journal_file_copy_entry failed: Bad message
  Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52, function 
main(). Aborting.
  FAIL: test-journal-flush (code: 134)
  Aborted (core dumped)
  == test-journal-importer ===
  [...]
  autopkgtest [07:17:29]:  summary
  timedatedPASS
  hostnamedPASS
  localed-locale   PASS
  localed-x11-keymap   PASS
  logind   PASS
  unit-config  PASS
  storage  PASS
  networkd-test.py PASS
  build-login  PASS
  boot-and-servicesPASS
  udev PASS
  root-unittests   FAIL non-zero exit status 134
  upstream PASS
  boot-smoke   PASS
  systemd-fsckdPASS
  Exit request sent.
  [...]

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1881947/+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 1905044] Re: systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8

2021-01-11 Thread Chris Halse Rogers
Hello Kleber, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.44 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed-bionic

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

Title:
  systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  In Progress
Status in systemd source package in Hirsute:
  Fix Released

Bug description:
  [impact]

  autopkgtest failure when running with 5.8 kernel, if systemd is built
  with earlier kernel (e.g. 5.4)

  [test case]

  see autopkgtest results, e.g. links in original description below

  [regression potential]

  as this only fixes a test case, any regression would likely result in
  an incorrectly passing, or incorrectly failing, test.

  [scope]

  this is needed for b/f/g/h.

  this bug was introduced by upstream commit 23cc81e7c22 which first
  added testing for 'invalid' cap numbers, but incorrectly using
  capability_list_length() instead of cap_last_cap(). That commit was
  first included in v236, so this bug does not exist before Bionic.

  this is fixed upstream by commit
  ebc815cd1c647faa934a446ceea91ff4bc9dffa4, which was first included in
  v247, so this is needed for h and earlier.

  Also note that even though the 5.8 kernel is not planned to be
  released for Bionic, this test also runs at build time, and since the
  LP build farm builds inside chroots, if the build farm ever moved up
  to Focal with a 5.8 kernel, the build of systemd for Bionic would
  start failing (since it would still be building using the older kernel
  headers, inside the chroot), so this does need to be fixed in Bionic
  systemd as well.

  [other info]

  there is a non-test bug related to this in bug 1905245

  [original description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20201117_174614_4ece6@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20201117_221555_48b91@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/s/systemd/20201117_175806_e779f@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20201117_153051_90e7e@/log.gz

  The failing testcases are:

  - root-unittests

  Assertion 'capability_set_to_string_alloc(c, ) == 0' failed at 
src/test/test-cap-list.c:60, funct
  ion test_capability_set_one(). Aborting.
  FAIL: test-cap-list (code: 134)

  - upstream

  TEST-24-UNIT-TESTS:

  --- test-cap-list begin ---
  Assertion 'capability_set_to_string_alloc(c, ) == 0' failed at 
src/test/test-cap-list.c:60, funct
  ion test_capability_set_one(). Aborting.
  --- test-cap-list end ---

  Both seem to be failing with the same assertion.

  These tests are successful on Focal with linux 5.4, therefore they
  would regress when upgrading the kernel from 5.4 to 5.8.

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

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

[Touch-packages] [Bug 1907306] Re: networkd dhcpv4 client never attempts more than 2 renew and 2 rebind

2021-01-11 Thread Chris Halse Rogers
Hello Dan, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.44 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed-bionic

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

Title:
  networkd dhcpv4 client never attempts more than 2 renew and 2 rebind

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  In Progress
Status in systemd source package in Hirsute:
  In Progress

Bug description:
  [impact]

  networkd dhcpv4 client never attempts more than 2 renew and 2 rebind

  [test case]

  configure an interface to use dhcpv4; acquire a dhcpv4 address, then
  stop the dhcpv4 server, and wait for the networkd client to perform
  its renewals and rebinds before expiring the lease

  using a 20 minute lease time as an example (all times are approximate
  due to RFC-mandated random 'fuzz' time of -1 to +1 sec):

  the current behavior would be to sent renew requests at:

  10:00
  13:45

  and then rebind requests at:

  17:30
  18:45

  then the lease would expire at 20:00

  the correct/new behavior should be renew requests at:

  10:00
  13:45
  15:37
  16:37

  and then rebind requests at:

  17:30
  18:45
  19:45

  and then lease expiration at 20:00.

  longer lease times would increase the number of retransmissions.

  [regression potential]

  any regression would likely result in problems receiving and/or
  maintaining a dhcpv4 address

  [scope]

  this is needed in b/f/g/h.

  this was fixed upstream in:
  https://github.com/systemd/systemd/pull/17908

  that was just added, so this is not fixed in any ubuntu release yet.

  technically, this is needed in x as well, however I don't plan to
  backport to x since 1) it reaches ESM soon and 2) the default network
  management tool in x is ifupdown, not systemd-networkd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1907306/+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 1878955] Re: resolved dhclient-enter-hook complains about an empty file

2021-01-11 Thread Chris Halse Rogers
Hello Craig, 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.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.

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

Title:
  resolved dhclient-enter-hook complains about an empty file

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [impact]

  When starting/using `dhclient`, it will often return an error such as:

  cmp: EOF on /tmp/tmp.yCyV6zBzhB which is empty

  [test case]

  run dhclient for the first time (for the current boot) on a
  bionic/focal system, or remove the file(s) in
  /run/systemd/resolved.conf.d/ starting with 'isc-dhcp-*', and then run
  dhclient.

  [regression potential]

  any regression would likely cause the DNS configuration that dhclient
  gets to not be properly reported to systemd-resolved, resulting in
  problematic/broken systemd DNS resolution.

  [scope]

  this is needed in b/f

  this hook was removed from systemd starting in g, and the hook was not
  yet added in x, so this change is needed only in b and f.

  [original description]

  When starting/using `dhclient`, it will often return an error such as:

  cmp: EOF on /tmp/tmp.yCyV6zBzhB which is empty

  This is due to the use of `cmp` in "/etc/dhcp/dhclient-enter-
  hooks.d/resolved"

  Because the $oldstate file can be empty, or different, it should use
  `cmp --quiet`

  This happens when "/run/systemd/resolved.conf.d/isc-
  dhcp-v*-$interface.conf" files do not exist, or when the content
  changes.

  This is very loosely related to
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1878955/+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 1881947] Re: Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52, function main(). Aborting.

2021-01-11 Thread Chris Halse Rogers
Hello dann, 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.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.

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

Title:
  Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52,
  function main(). Aborting.

Status in systemd:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  In Progress
Status in systemd source package in Hirsute:
  In Progress

Bug description:
  [Impact]

   * Autopkgtest fails due to corrupted journal file

  [Test Case]

   * Observe autopkgtest root-unittests not failing with:

  Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52,
  function main(). Aborting.

  [Where problems could occur]

   * The change has no impact on the systemd binary packages. The
  relaxed test could hide a journal corruption problem, but it seems the
  corrupted journal files occur only on arm64 probably due to arm64
  reboots being resets: LP: #1748280.

  [Original Bug Text]

  Observed in an focal/arm64 autopkgtest failure of systemd 245.4-4ubuntu3.1:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20200603_071743_738b2@/log.gz

  [...]
  PASS: test-journal-enum
  == test-journal-flush ===
  Root directory /var/log/journal removed.
  Directory /var/log/journal/3286b2469d224077b1026d239d625b0d removed.
  mmap cache statistics: 739 hit, 5 miss
  journal_file_copy_entry failed: Bad message
  Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52, function 
main(). Aborting.
  FAIL: test-journal-flush (code: 134)
  Aborted (core dumped)
  == test-journal-importer ===
  [...]
  autopkgtest [07:17:29]:  summary
  timedatedPASS
  hostnamedPASS
  localed-locale   PASS
  localed-x11-keymap   PASS
  logind   PASS
  unit-config  PASS
  storage  PASS
  networkd-test.py PASS
  build-login  PASS
  boot-and-servicesPASS
  udev PASS
  root-unittests   FAIL non-zero exit status 134
  upstream PASS
  boot-smoke   PASS
  systemd-fsckdPASS
  Exit request sent.
  [...]

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1881947/+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 1890448] Re: hwdb: Add EliteBook to use micmute hotkey

2021-01-11 Thread Chris Halse Rogers
Hello Kai-Heng, 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.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.

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

Title:
  hwdb: Add EliteBook to use micmute hotkey

Status in HWE Next:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  Micmute hotkey on many HP EliteBooks don't work.

  [Fix]
  Commit b6eb208b29ae ("hwdb: Add EliteBook to use micmute hotkey"), to map AT 
keyboard's scancode to micmute hotkey.

  [Test]
  With the one-liner fix, micmute hotkey works on all the EliteBooks I tested.

  [Regression Potential]
  The hwdb originally only matches a few EliteBook, and fix changes that to 
match all EliteBook models. So if there's an EliteBook that uses the scancode 
for other purpose, there will be a regression.
  However, the risk is rather slim because HP is confident that all EliteBooks 
use the same scancode for mic mute hotkey.

  [scope]

  this is needed for f and earlier.

  this is fixed upstream by commit b6eb208b29ae which is included
  starting in v246, so g and later are already fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1890448/+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 1903300] Re: systemd-networkd silently fails to set vxlan multicast group

2021-01-11 Thread Chris Halse Rogers
Hello Martin, 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.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.

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

Title:
  systemd-networkd silently fails to set vxlan multicast group

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

Bug description:
  [impact]

  setting VXLAN.Group does not correctly configure multicast group

  [test case]

  taken from upstream bug, example networkd config:

  [NetDev]
  Kind=vxlan
  Name=myvx

  [VXLAN]
  VNI=1
  Group=ff02::42:1
  DestinationPort=8472

  After restarting systemd-networkd the VXLAN device is created, but the
  group address is not assigned. Use ip -d link show myvx and networkctl
  show myvx to verify.

  [regression potential]

  any regression would likely cause problems only with VXLAN netdevs
  created by networkd.

  [scope]

  this is needed only for f.

  this was introduced by upstream commit 83cb24ac20b which was first in
  v243, so this bug does not exist in b and earlier.

  this was fixed by upstream commit
  7c9b26900cc33daf080627daf5904de74c1ef267 (and two following commits)
  which were first included in v246, so this is already fixed in g and
  later.

  [original description]

  
  Fixed upstream, please include [1].

  Thank you.

  [1] https://github.com/systemd/systemd/pull/15397

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.3
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Nov  6 14:16:19 2020
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=97786d27-c04a-4592-a087-f19a689468a9 ro console=tty1 console=ttyS0
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2020-08-27 (70 days ago)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.13.0-48-gd9c812dda519-prebuilt.qemu.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-5.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.13.0-48-gd9c812dda519-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-5.1:cvnQEMU:ct1:cvrpc-q35-5.1:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-5.1
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1903300/+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 1907306] Re: networkd dhcpv4 client never attempts more than 2 renew and 2 rebind

2021-01-11 Thread Chris Halse Rogers
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.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.

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

Title:
  networkd dhcpv4 client never attempts more than 2 renew and 2 rebind

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  In Progress
Status in systemd source package in Hirsute:
  In Progress

Bug description:
  [impact]

  networkd dhcpv4 client never attempts more than 2 renew and 2 rebind

  [test case]

  configure an interface to use dhcpv4; acquire a dhcpv4 address, then
  stop the dhcpv4 server, and wait for the networkd client to perform
  its renewals and rebinds before expiring the lease

  using a 20 minute lease time as an example (all times are approximate
  due to RFC-mandated random 'fuzz' time of -1 to +1 sec):

  the current behavior would be to sent renew requests at:

  10:00
  13:45

  and then rebind requests at:

  17:30
  18:45

  then the lease would expire at 20:00

  the correct/new behavior should be renew requests at:

  10:00
  13:45
  15:37
  16:37

  and then rebind requests at:

  17:30
  18:45
  19:45

  and then lease expiration at 20:00.

  longer lease times would increase the number of retransmissions.

  [regression potential]

  any regression would likely result in problems receiving and/or
  maintaining a dhcpv4 address

  [scope]

  this is needed in b/f/g/h.

  this was fixed upstream in:
  https://github.com/systemd/systemd/pull/17908

  that was just added, so this is not fixed in any ubuntu release yet.

  technically, this is needed in x as well, however I don't plan to
  backport to x since 1) it reaches ESM soon and 2) the default network
  management tool in x is ifupdown, not systemd-networkd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1907306/+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 1905044] Re: systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8

2021-01-11 Thread Chris Halse Rogers
Hello Kleber, 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.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.

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

Title:
  systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  In Progress
Status in systemd source package in Hirsute:
  Fix Released

Bug description:
  [impact]

  autopkgtest failure when running with 5.8 kernel, if systemd is built
  with earlier kernel (e.g. 5.4)

  [test case]

  see autopkgtest results, e.g. links in original description below

  [regression potential]

  as this only fixes a test case, any regression would likely result in
  an incorrectly passing, or incorrectly failing, test.

  [scope]

  this is needed for b/f/g/h.

  this bug was introduced by upstream commit 23cc81e7c22 which first
  added testing for 'invalid' cap numbers, but incorrectly using
  capability_list_length() instead of cap_last_cap(). That commit was
  first included in v236, so this bug does not exist before Bionic.

  this is fixed upstream by commit
  ebc815cd1c647faa934a446ceea91ff4bc9dffa4, which was first included in
  v247, so this is needed for h and earlier.

  Also note that even though the 5.8 kernel is not planned to be
  released for Bionic, this test also runs at build time, and since the
  LP build farm builds inside chroots, if the build farm ever moved up
  to Focal with a 5.8 kernel, the build of systemd for Bionic would
  start failing (since it would still be building using the older kernel
  headers, inside the chroot), so this does need to be fixed in Bionic
  systemd as well.

  [other info]

  there is a non-test bug related to this in bug 1905245

  [original description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20201117_174614_4ece6@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20201117_221555_48b91@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/s/systemd/20201117_175806_e779f@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20201117_153051_90e7e@/log.gz

  The failing testcases are:

  - root-unittests

  Assertion 'capability_set_to_string_alloc(c, ) == 0' failed at 
src/test/test-cap-list.c:60, funct
  ion test_capability_set_one(). Aborting.
  FAIL: test-cap-list (code: 134)

  - upstream

  TEST-24-UNIT-TESTS:

  --- test-cap-list begin ---
  Assertion 'capability_set_to_string_alloc(c, ) == 0' failed at 
src/test/test-cap-list.c:60, funct
  ion test_capability_set_one(). Aborting.
  --- test-cap-list end ---

  Both seem to be failing with the same assertion.

  These tests are successful on Focal with linux 5.4, therefore they
  would regress when upgrading the kernel from 5.4 to 5.8.

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

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

[Touch-packages] [Bug 1902960] Re: Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS resolution in some cases

2021-01-11 Thread Chris Halse Rogers
Hello David, 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.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.

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

Title:
  Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS
  resolution in some cases

Status in cloud-images:
  New
Status in systemd:
  New
Status in cloud-init package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Focal:
  Incomplete
Status in systemd source package in Focal:
  Fix Committed
Status in cloud-init source package in Groovy:
  Incomplete
Status in systemd source package in Groovy:
  In Progress

Bug description:
  [impact]

  on boot of a specific azure instance, the ID_NET_DRIVER parameter of
  the instance's eth0 interface is not set. That leads to a failure of
  systemd-networkd to take control of the interface after a restart of
  systemd-networkd, which results in DNS failures (at first) and
  eventually complete loss of networking (once the DHCP lease expires).

  [test case]

  this occurs on first boot of an instance using the specific image; it
  is not reproducable using the latest ubuntu image nor any reboot of
  the affected image, and it has not been reproducable (for me) when
  using debug-enabled images based on the affected image.

  So, while the problem is reproducable using the specific image in
  question, it's not possible to verify the fix since any change to the
  image removes reproducability.

  however, while the problem itself can't be reproduced and then
  verified, if the assumption is correct (that the 'add' uevent is being
  missed on boot), that is possible to test and verify:

  $ udevadm info /sys/class/net/eth0 | grep ID_NET_DRIVER
  E: ID_NET_DRIVER=hv_netvsc
  $ sudo rm /run/udev/data/n2 

  (note, change 'n2' to whichever network interface index is correct)

  $ udevadm info /sys/class/net/eth0 | grep ID_NET_DRIVER
  $ sudo udevadm trigger -c change /sys/class/net/eth0
  $ udevadm info /sys/class/net/eth0 | grep ID_NET_DRIVER

  (note the 'change' uevent did not populate ID_NET_DRIVER property)

  $ sudo udevadm trigger -c add /sys/class/net/eth0
  $ udevadm info /sys/class/net/eth0 | grep ID_NET_DRIVER
  E: ID_NET_DRIVER=hv_netvsc

  (note the 'add' uevent did populate ID_NET_DRIVER)

  the test verification should result in ID_NET_DRIVER being populated
  for a 'change' uevent.

  [regression potential]

  any regression would likely involve problems with systemd-udevd
  processing 'change' events from network devices, and/or incorrect
  udevd device properties.

  [scope]

  this is needed only for focal and groovy.

  this is fixed by upstream commit e0e789c1e97 which is first included
  in v247, so this is fixed already in hirsute.

  while this commit is not included in bionic, due to the difficult
  nature of reproducing (and verifying) this, and the fact it has only
  been seen once on a focal image, I don't think it's appropriate to SRU
  to bionic at this point; possibly it may be appropriate if this is
  ever reproduced with a bionic image.

  [other info]

  note that this bug's subject and description, as well as the upstream
  systemd bug subject and description, talk about the problem being DNS
  resolution. However that is strictly a side-effect of the real problem
  and is not the actual issue.

  [original description]

  The systemd upgrade 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to
  have broken DNS resolution across much of our Azure fleet earlier
  today.  We ended up mitigating this 

[Touch-packages] [Bug 1905245] Re: "Failed to parse bus message: Invalid argument" with Linux 5.8

2021-01-11 Thread Chris Halse Rogers
Hello Gary, 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.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.

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

Title:
  "Failed to parse bus message: Invalid argument" with Linux 5.8

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [impact]

  newer kernels introduced a new capability, and existing systemd
  doesn't have the name mapping for the new cap (since the mapping table
  is generated at systemd compile time), so it fails when trying to map
  the capability to a user-facing name, which causes failure when
  running commands like 'systemctl show'

  [test case]

  install a focal system, and install the 5.8 (or newer) kernel, e.g.
  from linux-generic-hwe-20.04-edge, and reboot into the new kernel.

  Find any service that does not specify its CapabilityBoundingSet; e.g.
  'apparmor', and run systemctl show on it:

  ubuntu@lp1905245-f:~$ systemctl show -p CapabilityBoundingSet apparmor
  Failed to parse bus message: Invalid argument

  the command should correctly show the value, e.g.:
  $ systemctl show -p CapabilityBoundingSet apparmor
  CapabilityBoundingSet=cap_chown cap_dac_override ...etc...

  [regression potential]

  a regression would likely occur while systemd is parsing or printing
  or otherwise handling kernel capabilities. A regression could happen
  when running systemd commands, such as systemctl, or when pid1 is
  managing services.

  [scope]

  this is needed only in focal and bionic.

  This is fixed upstream by PR 16424:
  https://github.com/systemd/systemd/pull/16424
  which was first included in v246, so this is already fixed in groovy and 
later.

  This was introduced upstream in systemd by commit
  52610b020c077ee769c6923249f7e6c4e99d2980 which was first included in
  v235, so this bug does not exist in Xenial.

  This bug will reproduce on any system running under the 5.8 kernel,
  with the new capability, if the systemd binary was compiled with
  kernel headers that do not include the new capability. This means this
  is reproducable on bare-metal/vm instances running 5.8, as well as
  containers on hosts running 5.8. Therefore, while bionic may not ever
  receive a new kernel with added capability, it still needs to be
  patched to avoid the bug on a bionic container running on a host with
  the 5.8 kernel.

  [other info]

  there is a testcase-only related bug 1905044

  [original description]

  When I run `systemctl show myservice.service`, I get the following
  error message:

     Failed to parse bus message: Invalid argument

  systemd version: 245.4-4ubuntu3.3
  linux version: 5.8.0-29-generic #31~20.04.1-Ubuntu  (From 
linux-generic-hwe-20.04-edge)

  This is a bug that has been fixed in Debian. See
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964926

  Please can we port the fix to the ubuntu 20.04 version.

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


  1   2   3   4   >