[Touch-packages] [Bug 2062927] Re: Ambiguity in mdns configuration
This report raises an important question about the defaults and setup for systemd-resolved. This was first raised in the following post a year ago: https://lists.ubuntu.com/archives/ubuntu- devel/2023-March/042499.html but as far as I can see remains unresolved. This is an important issue for many and some clarity is required, perhaps Lukas Märdian could update us? slyon @ ubuntu.com ** Package changed: ubuntu => systemd (Ubuntu) ** Also affects: avahi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2062927 Title: Ambiguity in mdns configuration Status in avahi package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Hi, I recently failed to get a 22.04 and 23.04 running reliably in a network with a cheap Huawei fiber router which provides routing and DHCP, but does not offer a DNS service with a zone with DHCP hosts. Therefore, machines cannot find each other by DNS. Since mdns is designed to solve this problem (and I could remember that Ubuntu was dealing with such networks properly about 10 years ago), I tried to configure the machines to use mdns. I was not able to get things running, since there are collisions between systemd/resolved on one hand, and avahi daemon on the other, colliding both on the UDP port and the functionality. systemd/resolved are not really able to provide all services, but it is not possible to use avahi only either, since systemd/resolved is built so deeply into ubuntu, that it can't be removed or turned off without breaking lots of functionalities. Furthermore, I found systemd to be unreliable as an mdns resolver. Sometimes it works, sometimes it doesn't, sometimes it takes minutes. I would have expected that Ubuntu would drop avahi daemon after moving to systemd, but now I found that 24.04 still comes with avahi daemon and competing functionalities. E.g. avahi suggests to install libnss-mdns, while resolved wants mdns to be enabled in /etc/systemd/resolved.conf and to handle it itself. So what is the suggested way to use Ubuntu in a network without proper DNS for DHCP-clients? systemd+resolved? avahi? both? I did not find any documentation about this, no simple configuration settings, no answer to the question how mdns should be used on Ubuntu since Ubuntu moved to systemd. Nobody seems to care. regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/2062927/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2047975] Re: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status
** Tags removed: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2047975 Title: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Noble: Triaged Bug description: upgraded from 22.04 -> 24.04 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: systemd-resolved 253.5-1ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Wed Jan 3 21:06:55 2024 ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-02-27 (311 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.1ubuntu5 apt 2.7.6 SourcePackage: systemd Title: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-01-03 (0 days ago) mtime.conffile..etc.systemd.resolved.conf: 2023-02-27T21:16:55.869158 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2047975/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2047975] Re: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status
I got some information from a user on a more recent duplicate (bug
2063533). The problem seems to be that some users, when disabling the
stub-resolver, also create a symlink /etc/resolv.conf ->
/run/systemd/resolve/resolv.conf. This is not actually necessary because
systemd-resolved will make stub-resolv.conf a symlink to resolv.conf
when DNSStubListener=no.
Hence, the command
cp "${DPKG_ROOT}/etc/resolv.conf"
"${DPKG_ROOT}/run/systemd/resolve/stub-resolv.conf"
in systemd-resolved.postinst fails because the source and destination
are *both* symlinks to /run/systemd/resolve/resolv.conf.
** Also affects: systemd (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Noble)
Status: New => Triaged
** Changed in: systemd (Ubuntu Noble)
Importance: Undecided => High
** Changed in: systemd (Ubuntu Noble)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Tags added: foundations-todo systemd-sru-next
--
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/2047975
Title:
package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade:
installed systemd-resolved package post-installation script subprocess
returned error exit status 1 [cp: '/etc/resolv.conf' and
'/run/systemd/resolve/stub-resolv.conf' are the same file]
Status in systemd package in Ubuntu:
Confirmed
Status in systemd source package in Noble:
Triaged
Bug description:
upgraded from 22.04 -> 24.04
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: systemd-resolved 253.5-1ubuntu7
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Wed Jan 3 21:06:55 2024
ErrorMessage: installed systemd-resolved package post-installation script
subprocess returned error exit status 1
InstallationDate: Installed on 2023-02-27 (311 days ago)
InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release
amd64 (20220809)
Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
dpkg 1.22.1ubuntu5
apt 2.7.6
SourcePackage: systemd
Title: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade:
installed systemd-resolved package post-installation script subprocess returned
error exit status 1
UpgradeStatus: Upgraded to noble on 2024-01-03 (0 days ago)
mtime.conffile..etc.systemd.resolved.conf: 2023-02-27T21:16:55.869158
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2047975/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063533] Re: package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status
*** This bug is a duplicate of bug 2047975 *** https://bugs.launchpad.net/bugs/2047975 Ah, I see. Thanks for that link. The issue is that it is not actually necessary to make the /etc/resolv.conf -> /run/systemd/resolve/resolv.conf symlink. systemd-resolved will handle DNSStubListener=no by making /run/systemd/resolve/stub-resolv.conf a symlink to /run/systemd/resolve/resolv.conf. Anyways, this gives me the info I need to write a patch. Thanks again. -- 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/2063533 Title: package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] Status in systemd package in Ubuntu: New Bug description: Trying to update 22.04.4 to 24.04 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Thu Apr 25 23:05:36 2024 ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2024-04-09 (16 days ago) InstallationMedia: Ubuntu-Server 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SourcePackage: systemd Title: package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-04-26 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-04-18T19:50:32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063533/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063533] Re: package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status
*** This bug is a duplicate of bug 2047975 *** https://bugs.launchpad.net/bugs/2047975 How exactly did you disable the stub resolver? -- 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/2063533 Title: package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] Status in systemd package in Ubuntu: New Bug description: Trying to update 22.04.4 to 24.04 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Thu Apr 25 23:05:36 2024 ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2024-04-09 (16 days ago) InstallationMedia: Ubuntu-Server 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SourcePackage: systemd Title: package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-04-26 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-04-18T19:50:32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063533/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063533] Re: package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status
*** This bug is a duplicate of bug 2047975 *** https://bugs.launchpad.net/bugs/2047975 And, if you still have an affected system in this state, what does readlink /etc/resolv.conf show? -- 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/2063533 Title: package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] Status in systemd package in Ubuntu: New Bug description: Trying to update 22.04.4 to 24.04 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Thu Apr 25 23:05:36 2024 ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2024-04-09 (16 days ago) InstallationMedia: Ubuntu-Server 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SourcePackage: systemd Title: package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-04-26 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-04-18T19:50:32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063533/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063464] Re: Package wasn't installed on upgrade from Jammy to Noble
** Changed in: systemd (Ubuntu) Status: Incomplete => New ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2063464 Title: Package wasn't installed on upgrade from Jammy to Noble Status in systemd package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: I just do-release-upgraded from Jammy to Noble on a pretty minimal server. After upgrade, network was fine but DNS names could not be resolved. I discovered systemd-resolved wasn't installed. I copied and installed that package manually, which immediately resolved the problem. So I assume this is a mistake in the upgrade process. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Apr 25 15:27:23 2024 SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:0:0:25766:2024-04-25 15:32:14.748564723 +:2024-04-25 15:32:14.747564766 +:/var/crash/_usr_bin_docker-compose.0.crash DistroRelease: Ubuntu 24.04 Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Tags: noble dist-upgrade Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) UserGroups: N/A VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063464/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063464] Re: Package wasn't installed on upgrade from Jammy to Noble
Sorry for the previous noise, I was on the wrong page. Can you please run apport-collect -p ubuntu-release-upgrader 2063464 so that upgrade logs are attached? ** Also affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Incomplete ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2063464 Title: Package wasn't installed on upgrade from Jammy to Noble Status in systemd package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Incomplete Bug description: I just do-release-upgraded from Jammy to Noble on a pretty minimal server. After upgrade, network was fine but DNS names could not be resolved. I discovered systemd-resolved wasn't installed. I copied and installed that package manually, which immediately resolved the problem. So I assume this is a mistake in the upgrade process. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Apr 25 15:27:23 2024 SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063464/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063464] Re: Package wasn't installed on upgrade from Jammy to Noble
-- 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/2063464 Title: Package wasn't installed on upgrade from Jammy to Noble Status in systemd package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Incomplete Bug description: I just do-release-upgraded from Jammy to Noble on a pretty minimal server. After upgrade, network was fine but DNS names could not be resolved. I discovered systemd-resolved wasn't installed. I copied and installed that package manually, which immediately resolved the problem. So I assume this is a mistake in the upgrade process. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Apr 25 15:27:23 2024 SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063464/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063349] Re: systemd-coredump handler does not forward the crash to the container
Okay. The title should be changed then -- systemd-coredump on the host attempts to forward the crash to the container, but finds that systemd- coredump is not present in the container, so it falls back to keeping it on the host. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2063349 Title: systemd-coredump handler does not forward the crash to the container Status in apport package in Ubuntu: Triaged Bug description: Steps to reproduce: 1. install systemd-coredump on the host 2. open a shell on a noble container 2.1 machinectl pull-raw "http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img; noble 2.2 machinectl start noble 2.3 machinectl shell noble 3. install chaos-marmosets inside the container (# apt install chaos-marmosets) 4. generate a crash inside the container (# divide-by-zero) Observed behaviour: The .crash file is present on the host /var/crash Expected behaviour: The .crash file should be present inside the container /var/crash Note: Here is how you can enable Host Network on the container https://wiki.archlinux.org/title/systemd-nspawn#Use_host_networking ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: apport 2.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportLog: INFO: apport (pid 126611) 2024-04-24 16:34:39,226: executable: /usr/bin/divide-by-zero (command line "divide-by-zero") INFO: apport (pid 126611) 2024-04-24 16:34:39,664: wrote report /var/crash/_usr_bin_divide-by-zero.1000.crash INFO: apport (pid 127435) 2024-04-24 16:41:16,322: executable: /usr/bin/divide-by-zero (command line "divide-by-zero") INFO: apport (pid 127435) 2024-04-24 16:41:16,758: wrote report /var/crash/_usr_bin_divide-by-zero.297664512.crash ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 17:03:02 2024 InstallationDate: Installed on 2024-04-18 (6 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240418) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2063349/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063349] Re: systemd-coredump handler does not forward the crash to the container
root@selected-slug:~# machinectl pull-raw "http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img; noble Enqueued transfer job 1. Press C-c to continue download in background. Pulling 'http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img', saving as 'noble'. Downloading 453.0M for http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. HTTP request to http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.roothash.p7s failed with code 404. Root hash signature file could not be retrieved, proceeding without. HTTP request to http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.verity failed with code 404. Verity integrity file could not be retrieved, proceeding without. HTTP request to http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.nspawn failed with code 404. Settings file could not be retrieved, proceeding without. Downloading 833B for http://cloud-images.ubuntu.com/noble/current/SHA256SUMS.gpg. Acquired 833B. Download of http://cloud-images.ubuntu.com/noble/current/SHA256SUMS.gpg complete. HTTP request to http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.roothash failed with code 404. Root hash file could not be retrieved, proceeding without. Downloading 6.9K for http://cloud-images.ubuntu.com/noble/current/SHA256SUMS. Got 37% of http://cloud-images.ubuntu.com/noble/current/SHA256SUMS. Acquired 6.9K. Download of http://cloud-images.ubuntu.com/noble/current/SHA256SUMS complete. Got 1% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 2min 13s left at 3.3M/s. Got 5% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 41s left at 10.4M/s. Got 11% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 26s left at 14.9M/s. Got 16% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 21s left at 17.5M/s. Got 22% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 18s left at 19.0M/s. Got 28% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 16s left at 20.1M/s. Got 33% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 14s left at 20.6M/s. Got 39% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 13s left at 21.1M/s. Got 44% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 11s left at 21.3M/s. Got 50% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 10s left at 21.8M/s. Got 53% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 9s left at 21.3M/s. Got 58% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 8s left at 21.4M/s. Got 64% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 7s left at 21.7M/s. Got 69% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 6s left at 21.9M/s. Got 75% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 4s left at 22.2M/s. Got 81% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 3s left at 22.4M/s. Got 87% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 2s left at 22.6M/s. Got 93% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 1s left at 22.7M/s. Got 98% of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 306ms left at 22.8M/s. Acquired 453.0M. Download of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img complete. SHA256 checksum of http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img is valid. gpg: Signature made Wed Apr 24 00:22:50 2024 UTC gpg:using RSA key D2EB44626FDDC30B513D5BB71A5D6C4C7DB87C81 gpg: Good signature from "UEC Image Automatic Signing Key " [unknown] gpg: WARNING: Using untrusted key! Signature verification succeeded. Unpacking QCOW2 file. Created new local image 'noble'. Operation completed successfully. Exiting. root@selected-slug:~# machinectl start noble root@selected-slug:~# machinectl shell noble Connected to machine noble. Press ^] three times within 1s to exit session. ### In the container now ### root@ubuntu:~# apt update && apt install systemd-coredump chaos-marmosets -y Get:1 http://archive.ubuntu.com/ubuntu noble InRelease [256 kB] Get:2 http://archive.ubuntu.com/ubuntu noble-updates InRelease [89.7 kB] Get:3 http://archive.ubuntu.com/ubuntu noble-backports InRelease [90.8 kB] Hit:4 http://security.ubuntu.com/ubuntu noble-security InRelease Get:5 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages [1403 kB] Get:6 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages [15.5
[Touch-packages] [Bug 2063349] Re: systemd-coredump handler does not forward the crash to the container
Did you verify that systemd-coredump is installed in the container? ** Changed in: apport (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2063349 Title: systemd-coredump handler does not forward the crash to the container Status in apport package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1. install systemd-coredump on the host 2. open a shell on a noble container 2.1 machinectl pull-raw "http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img; noble 2.2 machinectl start noble 2.3 machinectl shell noble 3. install chaos-marmosets inside the container (# apt install chaos-marmosets) 4. generate a crash inside the container (# divide-by-zero) Observed behaviour: The .crash file is present on the host /var/crash Expected behaviour: The .crash file should be present inside the container /var/crash Note: Here is how you can enable Host Network on the container https://wiki.archlinux.org/title/systemd-nspawn#Use_host_networking ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: apport 2.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportLog: INFO: apport (pid 126611) 2024-04-24 16:34:39,226: executable: /usr/bin/divide-by-zero (command line "divide-by-zero") INFO: apport (pid 126611) 2024-04-24 16:34:39,664: wrote report /var/crash/_usr_bin_divide-by-zero.1000.crash INFO: apport (pid 127435) 2024-04-24 16:41:16,322: executable: /usr/bin/divide-by-zero (command line "divide-by-zero") INFO: apport (pid 127435) 2024-04-24 16:41:16,758: wrote report /var/crash/_usr_bin_divide-by-zero.297664512.crash ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 17:03:02 2024 InstallationDate: Installed on 2024-04-18 (6 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240418) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2063349/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 The problem is that gnome-shell crashes during the upgrade, so packages including systemd-resolved never finish getting installed. Marking as a duplicate of bug 2054761. ** This bug has been marked a duplicate of bug 2054761 gnome-shell crashed with signal 5: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients' -- 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/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to the end of the upgrade, I got an „Oh, no! Something has gone wrong and the system cannot recover. Call the system administrator” message after a red FAILED in the terminal. The system administrator is myself, because my computer is a personal one. Hard reset, same error, Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish the update with dpkg. While dpkg was upgrading, it printed an error message for every WiFi connection: „[Failed] Failed to migrate [I do not remember, something with /etc/netplan]” It took at least one and a half hour to find the solution on Ask Ubuntu. The problem was: /etc/resolv.conf became a broken link, along with systemd-resolve.service. I needed to remove both of them and write a new resolv.conf to fix the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.45.90-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 08:21:02 2024 InstallationDate: Installed on 2023-07-05 (236 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) IpRoute: default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.45.90 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 Adding my journal from the crash. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2055012/+attachment/5769751/+files/journal.txt -- 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/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to the end of the upgrade, I got an „Oh, no! Something has gone wrong and the system cannot recover. Call the system administrator” message after a red FAILED in the terminal. The system administrator is myself, because my computer is a personal one. Hard reset, same error, Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish the update with dpkg. While dpkg was upgrading, it printed an error message for every WiFi connection: „[Failed] Failed to migrate [I do not remember, something with /etc/netplan]” It took at least one and a half hour to find the solution on Ask Ubuntu. The problem was: /etc/resolv.conf became a broken link, along with systemd-resolve.service. I needed to remove both of them and write a new resolv.conf to fix the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.45.90-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 08:21:02 2024 InstallationDate: Installed on 2023-07-05 (236 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) IpRoute: default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.45.90 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
** Changed in: ubuntu-release-upgrader (Ubuntu) Importance: Undecided => Critical -- 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/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to the end of the upgrade, I got an „Oh, no! Something has gone wrong and the system cannot recover. Call the system administrator” message after a red FAILED in the terminal. The system administrator is myself, because my computer is a personal one. Hard reset, same error, Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish the update with dpkg. While dpkg was upgrading, it printed an error message for every WiFi connection: „[Failed] Failed to migrate [I do not remember, something with /etc/netplan]” It took at least one and a half hour to find the solution on Ask Ubuntu. The problem was: /etc/resolv.conf became a broken link, along with systemd-resolve.service. I needed to remove both of them and write a new resolv.conf to fix the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.45.90-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 08:21:02 2024 InstallationDate: Installed on 2023-07-05 (236 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) IpRoute: default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.45.90 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
I attempted an upgrade from a clean Jammy install to Noble so that I could gather upgrade logs. I have attached them here. ** Attachment added: "dist-upgrade.tar.gz" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+attachment/5769726/+files/dist-upgrade.tar.gz ** Also affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to the end of the upgrade, I got an „Oh, no! Something has gone wrong and the system cannot recover. Call the system administrator” message after a red FAILED in the terminal. The system administrator is myself, because my computer is a personal one. Hard reset, same error, Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish the update with dpkg. While dpkg was upgrading, it printed an error message for every WiFi connection: „[Failed] Failed to migrate [I do not remember, something with /etc/netplan]” It took at least one and a half hour to find the solution on Ask Ubuntu. The problem was: /etc/resolv.conf became a broken link, along with systemd-resolve.service. I needed to remove both of them and write a new resolv.conf to fix the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.45.90-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 08:21:02 2024 InstallationDate: Installed on 2023-07-05 (236 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) IpRoute: default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.45.90 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2062542] Re: systemd-resolved stub gives SERVFAIL for DNSSEC negative response
What version of Ubuntu is this? ** Changed in: systemd (Ubuntu) Status: New => Incomplete ** Changed in: systemd (Ubuntu) Importance: Undecided => Low -- 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/2062542 Title: systemd-resolved stub gives SERVFAIL for DNSSEC negative response Status in systemd package in Ubuntu: Incomplete Bug description: This issue surface when researching the issue that Postfix on my system (with DANE enabled) deferred mail deliveries with 100s of this warning in the log: Warning: DANE TLSA lookup problem: Host or domain name not found. Name service error for name=_25._tcp.cluster5.us.messagelabs.com type=TLSA: Host not found, try again The DNS resolver on my machine was pointing at the systemd-resolved stub: $ cat /etc/resolv.conf | grep nameserver nameserver 127.0.0.53 $ resolvectl status Global Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=allow-downgrade/supported resolv.conf mode: stub Note DNSSEC is enabled (else Postfix couldn't be doing DANE). Now if I query the TLSA record for the messagelab server, I get a SERVFAIL from the stub resolver: $ delv +dnssec _25._tcp.cluster5.us.messagelabs.com TLSA ;; resolution failed: SERVFAIL Whereas if I query my upstream DNS or Google DNS, I get a DNSSEC validated (negative) response: $ delv @8.8.8.8 +dnssec _25._tcp.cluster5.us.messagelabs.com TLSA ;; resolution failed: ncache nxrrset ; negative response, fully validated ; _25._tcp.cluster5.us.messagelabs.com. 299 IN \-TLSA ;-$NXRRSET ; _25._tcp.cluster5.us.messagelabs.com. RRSIG NSEC ... ; _25._tcp.cluster5.us.messagelabs.com. NSEC \000._25._tcp.cluster5.us.messagelabs.com. A PTR HINFO MX TXT RP SRV NAPTR SSHFP RRSIG NSEC SVCB HTTPS SPF IXFR AXFR CAA ; messagelabs.com. SOA ns-1714.awsdns-22.co.uk. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400 ; messagelabs.com. RRSIG SOA ... I assume Postfix (with smtp_tls_security_level = dane i.e. "Opportunistic DANE") deals with the negative response by downgrading to "encrypt", whereas the SERVFAIL response makes it refuse to connect altogether. My workaround was to switch from the systemd-resolved stub resolver to the upstream servers. In /etc/systemd/resolved.conf set: DNS=... your upstream servers if not already given through DHCP ... DNSStubListener=no Then restart the service and restart Postfix if it is chrooted (so the new /etc/resolv.conf gets copied into the chroot): systemctl restart systemd-resolved systemctl restart postfix I am not sure if this could be considered a Postfix bug as well (it could consider a SERVFAIL on a TLSA record the same as a negative), but surely it seems to me the systemd-resolved stub resolver should not return the SERVFAIL here. For more background on this bug report, please see https://serverfault.com/a/1158198/299950 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2062542/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
** Changed in: systemd (Ubuntu Noble)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2058179
Title:
Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Status in Native ZFS for Linux:
Fix Released
Status in systemd package in Ubuntu:
Fix Committed
Status in zfs-linux package in Ubuntu:
In Progress
Status in systemd source package in Noble:
Fix Committed
Status in zfs-linux source package in Noble:
In Progress
Bug description:
As per https://github.com/openzfs/zfs/issues/15930
ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
copy_file_range, breaking a multitude of applications.
Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
2.2.2.
One notable issue is when running Root on ZFS: systemd-sysusers will
always fail to create users/groups with the error "Failed to backup
/etc/{group,passwd}: Operation not supported" due to the call to
copy_file_range.
To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2062424] Re: When accelerometer detects rotation, it goes into airplane mode
This is probably a hwdb issue. Can you share the output of dmidecode -s system-product-name? And can you try and figure out what keycode is issued by the rotation? The evtest command should help with that. ** Also affects: systemd-hwe (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2062424 Title: When accelerometer detects rotation, it goes into airplane mode Status in systemd-hwe package in Ubuntu: New Status in util-linux package in Ubuntu: New Bug description: On a HP ENVY X360 15-EW1073CL laptop, when the accelerometer detects rotation, it will go into airplane mode. I tried installing KDE plasma to see whether it would fix the problem, but the problem persists. However, I suspect that it's really not rfkill the module containing the bug, but rather some other system that associates orientation change to airplane mode. Waiting for iio-sensor-proxy to appear +++ iio-sensor-proxy appeared === Has accelerometer (orientation: normal) === Has ambient light sensor (value: 68,134003, unit: lux) === No proximity sensor Light changed: 69,920003 (lux) Light changed: 70,124003 (lux) Light changed: 2,13 (lux) Light changed: 7,599000 (lux) Light changed: 7,388000 (lux) Accelerometer orientation changed: left-up << goes into airplane mode Light changed: 6,643000 (lux) Light changed: 7,177000 (lux) Accelerometer orientation changed: normal<< sometimes comes back, sometimes it doesn't Light changed: 7,283000 (lux) Light changed: 8,97 (lux) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: rfkill 2.37.2-4ubuntu3.4 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 18 17:50:45 2024 InstallationDate: Installed on 2024-04-17 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-hwe/+bug/2062424/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Since kernel rebuilds are required for the ZFS fix to be readily
available, I am uploading the systemd workaround to help mitigate the
problem.
** Changed in: systemd (Ubuntu Noble)
Status: Triaged => In Progress
** Changed in: systemd (Ubuntu Noble)
Importance: Medium => Critical
** Changed in: systemd (Ubuntu Noble)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Tags removed: systemd-sru-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2058179
Title:
Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Status in Native ZFS for Linux:
Fix Released
Status in systemd package in Ubuntu:
In Progress
Status in zfs-linux package in Ubuntu:
In Progress
Status in systemd source package in Noble:
In Progress
Status in zfs-linux source package in Noble:
In Progress
Bug description:
As per https://github.com/openzfs/zfs/issues/15930
ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
copy_file_range, breaking a multitude of applications.
Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
2.2.2.
One notable issue is when running Root on ZFS: systemd-sysusers will
always fail to create users/groups with the error "Failed to backup
/etc/{group,passwd}: Operation not supported" due to the call to
copy_file_range.
To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
** Tags added: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2058179
Title:
Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Status in Native ZFS for Linux:
Fix Released
Status in systemd package in Ubuntu:
Triaged
Status in zfs-linux package in Ubuntu:
Confirmed
Bug description:
As per https://github.com/openzfs/zfs/issues/15930
ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
copy_file_range, breaking a multitude of applications.
Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
2.2.2.
One notable issue is when running Root on ZFS: systemd-sysusers will
always fail to create users/groups with the error "Failed to backup
/etc/{group,passwd}: Operation not supported" due to the call to
copy_file_range.
To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Fix for systemd to work around this:
https://github.com/systemd/systemd/pull/32341.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Triaged
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** Tags added: systemd-sru-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2058179
Title:
Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Status in Native ZFS for Linux:
Fix Released
Status in systemd package in Ubuntu:
Triaged
Status in zfs-linux package in Ubuntu:
Confirmed
Bug description:
As per https://github.com/openzfs/zfs/issues/15930
ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
copy_file_range, breaking a multitude of applications.
Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
2.2.2.
One notable issue is when running Root on ZFS: systemd-sysusers will
always fail to create users/groups with the error "Failed to backup
/etc/{group,passwd}: Operation not supported" due to the call to
copy_file_range.
To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2061214] Re: Software sources not correctly updated after upgrade
** Changed in: software-properties (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2061214 Title: Software sources not correctly updated after upgrade Status in software-properties package in Ubuntu: New Bug description: Upgrading Lubuntu Jammy to Lubuntu Noble using TUI results in "Software sources" not correctly updated after upgrade. Prompt= shows normal and not LTS Used command sudo do-release-upgrade -d Otherwise the upgrade is good see attached screenshot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: software-properties-common 0.99.46 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Apr 13 11:44:28 2024 InstallationDate: Installed on 2024-04-13 (0 days ago) InstallationMedia: Lubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240331) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-02-22T14:20:00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2061214/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2059412] Re: SyntaxWarning: invalid escape sequence '\.'
** Changed in: software-properties (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2059412
Title:
SyntaxWarning: invalid escape sequence '\.'
Status in software-properties package in Ubuntu:
Fix Committed
Bug description:
Installing software-properties gives
--->
/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogMirror.py:197:
SyntaxWarning: invalid escape sequence '\.'
elif
re.match("^((ftp)|(http)|(file)|(rsync)|(https))://([a-z]|[A-Z]|[0-9]|:|/|\.|~)+$",
uri) == None:
<---
Marked as "wishlist" importance because Python still passes that to
re.match as '\.' instead of '.', so the behavior is correct, as can be
confirmed with
--->
% python3 -c 'print("\.")'
:1: SyntaxWarning: invalid escape sequence '\.'
\.
<---
In a future Python version they will be eventually a SyntaxError[1].
[1] https://docs.python.org/3/reference/lexical_analysis.html#escape-
sequences
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2059412/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2060331] Re: add-apt-repository --list not returning any deb822 repositories
** Changed in: software-properties (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2060331 Title: add-apt-repository --list not returning any deb822 repositories Status in software-properties package in Ubuntu: Fix Committed Bug description: Recreating the following bug report (#2052851) with a new title per Jeremy Bícha's (jbicha) request: https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2052851 --- On Ubuntu 23.10: * When adding a PPA, 'add-apt-repository' will add the repository in the new deb822 format as a '.sources' file in '/etc/apt/sources.list.d' * However, 'add-apt-repository --list' cannot see/understand the new '.sources' file For example, with the flacon ppa (https://launchpad.net/~flacon/+archive/ubuntu/ppa): 1. 'sudo add-apt-repository ppa:flacon/ppa' adds the flacon repo as '/etc/apt/sources.list.d/flacon-ubuntu-ppa-mantic.sources' 2. apt can install and update from the new repo, as expected. you can also remove the repo, as expected, by running 'sudo add-apt-repository --remove ppa:flacon/ppa' 3. However, 'add-apt-repository --list' does not list the repo as it should. GUI package managers such as Muon and Synaptic also do not see the new repo. It makes working with packages frustrating, and unfortunately, per Julian Andres Klode (juliank), there seems to be no plan to fix the broken 'software-properties-common' any time soon. See here: https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2033949 Also see related issues: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2036761 https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2037210 https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2036288 https://lists.ubuntu.com/archives/ubuntu-devel/2023-September/042791.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2060331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2060915] Re: Comments in source files flood "other software"
** Changed in: software-properties (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2060915 Title: Comments in source files flood "other software" Status in software-properties package in Ubuntu: Fix Committed Bug description: Reproduction case: Add the attached source file to /etc/apt/sources.list.d/. You don't need to 'apt update' for this test. Open software-properties-gtk. Issue: All the comments at the top of the file are displayed, flooding the interface. Limiting the number of comment lines displayed and only displaying the full comments in a tool tip (GTK.Tree has a couple of set_tooltip functions) may result in a better user interface. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2060915/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2061978] Re: Pressing enter on close button of out-of-date cache dialog still triggers the reload button
** Changed in: software-properties (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2061978 Title: Pressing enter on close button of out-of-date cache dialog still triggers the reload button Status in software-properties package in Ubuntu: Fix Committed Bug description: Start software-properties-gtk, make any change in the sources configuration, e.g. by just toggling universe check button, enter your password and click close. A dialog appears saying that > To install software and updates from newly added or changed sources, you have to reload the information about available software. with a reload and a close button. Press the right arrow key and close will be selected in the interface, evidenced by a faint border around that button. Press the enter key. - Expected: The close button becomes dark for a brief moment, indicating that it has been pressed, and the program exits immediately. - Observed: The reload button becomes dark for a brief moment, indicating that it has been pressed, and the program starts updating the cache. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2061978/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2047447] Re: No valid source.list found while upgrading from mantic to noble
Paul, please open a separate bug report. We need to see your sources.list, sources.list.d/* etc. to see what is going on. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in python-apt source package in Mantic: Confirmed Status in ubuntu-release-upgrader source package in Mantic: Invalid Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information No valid sources.list entry found While scanning your repository information no entry about mantic could be found. An upgrade might not succeed. Do you want to continue anyway? Continue [yN] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2061383] Re: [noble] Add ManageForeignNextHops feature to fix NextHop deletions
It's too late in the cycle to include this in the release of 24.04. This would need to happen as an SRU, but I am not sure it will be appropriate for this change given it is adding a new feature. ** Changed in: systemd (Ubuntu) Status: New => Confirmed ** Changed in: systemd (Ubuntu) Importance: Undecided => Wishlist ** Also affects: systemd (Ubuntu Noble) Importance: Wishlist Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2061383 Title: [noble] Add ManageForeignNextHops feature to fix NextHop deletions Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Noble: Confirmed Bug description: Hi, I was wondering if it was possible to integrate the new ManageForeignNextHops feature via a backport into Ubuntu 24.04. Without this feature/bugfix we have problems with systemd-networkd deleting the Nexthops of FRR on a restart of Switch failure. This is especially problematic with our EVPN setup. For more information please have a look into the following issue: https://github.com/systemd/systemd/issues/29034 https://github.com/systemd/systemd/commit/0977039bdc9e857cdb0dfe1d96d0de0d94d02155 Best regards, Justin Lamp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2061383/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2059872] Re: Unable to listen on port 22 if multiple Port= present in sshd configuration
The fix is already in noble-proposed, so you could enable that and install from there. Or, you can wait probably another day until it lands in the release pocket. ** Changed in: openssh (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2059872 Title: Unable to listen on port 22 if multiple Port= present in sshd configuration Status in openssh package in Ubuntu: Fix Committed Bug description: Recently introduced sshd-socket-generator for socket activation in openssh 1:9.6p1-3ubuntu3 has a bug when dealing with multiple Port or ListenAddress entries in the sshd configuration. If you have multiple Port or ListenAddress and one of them is for port 22, it just skips it. To show it clearly, here is an example: Port 22 Port 1024 It generates: ListenStream= ListenStream=1024 Now nothing is listening to port 22, hence breaking existing configurations. This was tested on 1:9.6p1-3ubuntu11. The intention seems to be to not generate the drop-in if only port 22 is in use, but it does not account for the case of multiple Port or ListenAddress where one of them is for port 22. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2059872/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2061128] Re: `add-apt-repository --pocket` doesn't work on Noble (Deb822?)
Hm, yeah this was overlooked too. The initial deb822 support in software-properties was mostly about adding PPAs. It looks like we need to go through and add more general deb822 support. ** Tags added: foundations-todo ** Changed in: software-properties (Ubuntu) Importance: Undecided => Medium ** Changed in: software-properties (Ubuntu) Assignee: (unassigned) => Nick Rosbrook (enr0n) ** Changed in: software-properties (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2061128 Title: `add-apt-repository --pocket` doesn't work on Noble (Deb822?) Status in software-properties package in Ubuntu: Confirmed Bug description: It seems like `add-apt-repository` doesn't know how to enable a new pocket when Ubuntu's sources are defined in Deb822 (.sources) source file. Step to reproduce: 1. Create a Noble chroot with e.g. Docker. Verify that in such chroot, Deb822 is used for Ubuntu's source (`ls /etc/apt/sources.list.d/ubuntu.sources`). 2. Run `add-apt-repository --pocket proposed`. Accept the prompt. 3. Run `apt policy`. - Expected result: `noble-proposed` is listed. - Actual result: `noble-proposed` is not listed. This might be related to LP: #2060331, but since I'm not sure how it works, I'm filing a new bug here. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: software-properties-common 0.99.46 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CloudSerial: 20240225 Date: Fri Apr 12 18:38:12 2024 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) TERM=xterm SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2061128/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2060331] Re: add-apt-repository --list not returning any deb822 repositories
** Changed in: software-properties (Ubuntu) Assignee: (unassigned) => Nick Rosbrook (enr0n) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2060331 Title: add-apt-repository --list not returning any deb822 repositories Status in software-properties package in Ubuntu: Confirmed Bug description: Recreating the following bug report (#2052851) with a new title per Jeremy Bícha's (jbicha) request: https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2052851 --- On Ubuntu 23.10: * When adding a PPA, 'add-apt-repository' will add the repository in the new deb822 format as a '.sources' file in '/etc/apt/sources.list.d' * However, 'add-apt-repository --list' cannot see/understand the new '.sources' file For example, with the flacon ppa (https://launchpad.net/~flacon/+archive/ubuntu/ppa): 1. 'sudo add-apt-repository ppa:flacon/ppa' adds the flacon repo as '/etc/apt/sources.list.d/flacon-ubuntu-ppa-mantic.sources' 2. apt can install and update from the new repo, as expected. you can also remove the repo, as expected, by running 'sudo add-apt-repository --remove ppa:flacon/ppa' 3. However, 'add-apt-repository --list' does not list the repo as it should. GUI package managers such as Muon and Synaptic also do not see the new repo. It makes working with packages frustrating, and unfortunately, per Julian Andres Klode (juliank), there seems to be no plan to fix the broken 'software-properties-common' any time soon. See here: https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2033949 Also see related issues: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2036761 https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2037210 https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2036288 https://lists.ubuntu.com/archives/ubuntu-devel/2023-September/042791.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2060331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2059874] Re: on upgrade sshd-socket-generator conversion does not respect administrator intent
** Changed in: openssh (Ubuntu) Status: Confirmed => Fix Committed -- 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/2059874 Title: on upgrade sshd-socket-generator conversion does not respect administrator intent Status in openssh package in Ubuntu: Fix Committed Bug description: the openssh-server 1:9.6p1-3ubuntu11 postinst contains this code snippet: if [ "$action" == configure ]; then ..snip.. if dpkg --compare-versions "$2" lt-nl 1:9.6p1-3ubuntu3~; then ..snip.. if [ -d /run/systemd/system ]; then # Make sure ssh.service is disabled. systemctl unmask ssh.service systemctl disable --now ssh.service > /dev/null 2>&1 # sshd-socket-generator is invoked on daemon-reload. systemctl daemon-reload systemctl enable ssh.socket fi fi fi This does not respect existing service and socket unit configuration, it effectively re-enables a disabled ssh.service (and even a masked one), and a manually disabled socket unit. I strongly suspect it does not respect systemd presets either. This is unexpected behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2059874/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055806] Re: sshd.service ssh.socket systemd-tmpfiles-setup:Before= - Missing privilege separation directory: /run/sshd
** Tags removed: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2055806 Title: sshd.service ssh.socket systemd-tmpfiles-setup:Before= - Missing privilege separation directory: /run/sshd Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Mantic: New Bug description: Symptom: ssh.service is not running and not accepting new SSH connections and returns socket closed error upon attempted connection. ssh.service shows a failed with error message "Missing privilege separation directory: /run/sshd". The following line is needed in the SystemD Unit configuration of the ssh.service file for the openssh-server package to fix what appears to be a race condition when ssh.service is sometimes started before systemd-tmpfiles-setup.service is finished processing the file in /usr/lib/tmpfiles.d/openssh.server.conf that is required to create the /run/sshd directory that is required by ssh.service to start property. There might be more depth or an alternative reason to why /run/sshd/ still didn't exist after using ```systemctl reset-failed ssh.service```. So more investigation is needed by someone with more background in systemd-tmpfiles-setup.service and openssh-server package after it when to socket activation. = Error Messages = ``` $journalctl -u ssh.service -b-1 Mar 02 21:30:56 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server... Mar 02 21:30:56 server sshd[1271]: Missing privilege separation directory: /run/sshd Mar 02 21:30:56 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION Mar 02 21:30:56 server systemd[1]: ssh.service: Failed with result 'exit-code'. Mar 02 21:30:56 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:56 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 1. Mar 02 21:30:56 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:56 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server... Mar 02 21:30:56 server sshd[1369]: Missing privilege separation directory: /run/sshd Mar 02 21:30:56 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION Mar 02 21:30:56 server systemd[1]: ssh.service: Failed with result 'exit-code'. Mar 02 21:30:56 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:56 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 2. Mar 02 21:30:56 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:56 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server... Mar 02 21:30:56 server sshd[1454]: Missing privilege separation directory: /run/sshd Mar 02 21:30:56 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION Mar 02 21:30:56 server systemd[1]: ssh.service: Failed with result 'exit-code'. Mar 02 21:30:56 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:57 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 3. Mar 02 21:30:57 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:57 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server... Mar 02 21:30:57 server sshd[1465]: Missing privilege separation directory: /run/sshd Mar 02 21:30:57 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION Mar 02 21:30:57 server systemd[1]: ssh.service: Failed with result 'exit-code'. Mar 02 21:30:57 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:57 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 4. Mar 02 21:30:57 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:57 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server... Mar 02 21:30:57 server sshd[1475]: Missing privilege separation directory: /run/sshd Mar 02 21:30:57 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION Mar 02 21:30:57 server systemd[1]: ssh.service: Failed with result 'exit-code'. Mar 02 21:30:57 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:57 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 5. Mar 02 21:30:57 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:57 server systemd[1]: ssh.service: Start request repeated too quickly. Mar 02 21:30:57 server systemd[1]: ssh.service: Failed with result 'exit-code'. Mar 02 21:30:57 server systemd[1]: Failed
[Touch-packages] [Bug 2059550] Re: autopkgtest failures on 1:5.0.3-2ubuntu3 (Noble)
** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/2059550 Title: autopkgtest failures on 1:5.0.3-2ubuntu3 (Noble) Status in lxc package in Ubuntu: Fix Committed Bug description: We can see autopkgtest failures on Noble: https://autopkgtest.ubuntu.com/packages/lxc 1:5.0.3-2ubuntu2 from noble-proposed/universe Details from log (https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/l/lxc/20240327_203000_ce7d4@/log.gz): = 3266s Removing autopkgtest-satdep (0) ... 3269s autopkgtest [20:29:48]: test no-devel: [--- 3269s + grep LXC_DEVEL /usr/include/lxc/version.h 3269s + grep 0 3269s #define LXC_DEVEL 0 3269s autopkgtest [20:29:48]: test no-devel: ---] 3269s autopkgtest [20:29:48]: test no-devel: - - - - - - - - - - results - - - - - - - - - - 3269s no-devel PASS 3269s autopkgtest [20:29:48]: summary 3269s exercise FAIL non-zero exit status 1 3269s unprivileged-containers FAIL non-zero exit status 1 3269s basics-create-destroy PASS (superficial) 3269s no-devel PASS = unprivileged-containers = 1896s Unpacking the rootfs 1900s 1900s --- 1900s You just created an Ubuntu mantic amd64 (20240326_07:42) container. 1900s 1900s To enable SSH, run: apt install openssh-server 1900s No default root or user password are set by LXC. 1900s + systemd-run --scope --quiet --user --property=Delegate=yes lxc-start -n mycontainer 1900s Failed to connect to bus: No medium found = exercise = 1113s FAIL: lxc-tests: /usr/bin/lxc-test-unpriv 1113s --- 1113s Name: c1 1113s State: RUNNING 1113s PID:52927 1113s Link: veth1001_HZ75 1113s TX bytes: 0 bytes 1113s RX bytes: 0 bytes 1113s Total bytes: 0 bytes 1113s Name: c1 1113s State: RUNNING 1113s PID:52994 1113s Link: veth1001_ujGT 1113s TX bytes: 0 bytes 1113s RX bytes: 0 bytes 1113s Total bytes: 0 bytes 1113s lxc-copy: c1: ../src/lxc/utils.c: lxc_drop_groups: 1365 Operation not permitted - Failed to drop supplimentary groups <...> 1113s info: Removing crontab ... 1113s info: Removing user `lxcunpriv' ... 1113s FAIL 1113s --- 1114s PASS: lxc-tests: /usr/bin/lxc-test-usernic 1114s PASS: lxc-tests: /usr/bin/lxc-test-usernsexec 1114s PASS: lxc-tests: /usr/bin/lxc-test-utils 1114s 1114s SUMMARY: pass=55, fail=1, ignored=0 1115s autopkgtest [19:53:54]: test exercise: ---] 1115s autopkgtest [19:53:54]: test exercise: - - - - - - - - - - results - - - - - - - - - - 1115s exercise FAIL non-zero exit status 1 = In the previous version we had no unprivileged-containers testsuite because it was inherited from Debian. lxc-test-unpriv was a skipped test too because we had this piece of code: https://git.launchpad.net/ubuntu/+source/lxc/tree/debian/tests/exercise?h=applied/ubuntu/noble#n129 = # Skip some tests due to cgroup v2 incompatibility if [ -e /sys/fs/cgroup/system.slice/memory.current ]; then [ "$testbin" = "lxc-test-apparmor-mount" ] && \ ignore "$STRING" && continue [ "$testbin" = "lxc-test-autostart" ] && \ ignore "$STRING" && continue [ "$testbin" = "lxc-test-no-new-privs" ] && \ ignore "$STRING" && continue [ "$testbin" = "lxc-test-unpriv" ] && \ ignore "$STRING" && continue fi = Just compare: https://git.launchpad.net/ubuntu/+source/lxc/tree/debian/tests/control?h=applied/ubuntu/noble and https://git.launchpad.net/ubuntu/+source/lxc/tree/debian/tests/control?h=applied/ubuntu/noble-devel We want to fix all of this for sure, but it would be awesome to get an updated and actual version of LXC in the upcoming Ubuntu Noble release too. So, may be it makes sense to skip this tests for the sake of having LXC updated. What I found in Debian, is that autopkgtests are skipped too: https://ci.debian.net/packages/l/lxc/unstable/amd64/ Taking this into account it (probably) reasonable to skip this tests too for now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2059550/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2060681] Re: systemd-networkd-wait-online.service halts booting for 2 1/2 minutes
*** This bug is a duplicate of bug 2060311 *** https://bugs.launchpad.net/bugs/2060311 Thanks. I am going to mark this as a duplicate. It does appear to be the same problem. ** This bug has been marked a duplicate of bug 2060311 Setting "optional: true" to overcome he timeout "Job systemd-networkd-wait-online" does no longer work with latest noble image -- 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/2060681 Title: systemd-networkd-wait-online.service halts booting for 2 1/2 minutes Status in systemd package in Ubuntu: Incomplete Bug description: When booting http://cdimage.ubuntu.com/ubuntu-server/daily- preinstalled/20240409/noble-preinstalled-server-riscv64.img.xz the system waits for 2 1/2 minutes for systemd-networkd-wait- online.service to time out. See attached boot chart. --- ProblemType: Bug ApportVersion: 2.28.0-0ubuntu1 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20240409 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) DistroRelease: Ubuntu 24.04 Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge +-01.0 Red Hat, Inc. Virtio RNG \-02.0 Red Hat, Inc. Virtio block device Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: systemd 255.4-1ubuntu7 PackageArchitecture: riscv64 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-20-generic root=LABEL=cloudimg-rootfs ro efi=debug earlycon init=/lib/systemd/systemd-bootchart ProcVersionSignature: Ubuntu 6.8.0-20.20.1-generic 6.8.1 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. Tags: cloud-image noble Uname: Linux 6.8.0-20-generic riscv64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2060681/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2060311] Re: Setting "optional: true" to overcome he timeout "Job systemd-networkd-wait-online" does no longer work with latest noble image
** Changed in: netplan
Importance: Undecided => Critical
** Changed in: netplan
Importance: Critical => High
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2060311
Title:
Setting "optional: true" to overcome he timeout "Job systemd-networkd-
wait-online" does no longer work with latest noble image
Status in Netplan:
New
Status in Ubuntu on IBM z Systems:
New
Status in systemd package in Ubuntu:
New
Bug description:
Especially on s390x (but not limited to s390x) it's often the case that a
system has network devices that are not necessarily connected during boot-up
and one gets such a 2 min timeout:
"Job systemd-networkd-wait-online. Start running (1min 59s / no limit)"
In the past I could avoid that by setting "optional: true" post-install (no
perfect, but worked),
but this does no longer seem to work using the latest noble ISO image (Apr
5th).
Setting 'optional: true' in /etc/netplan/50-cloud-init.yaml looks like
this for me:
# This file is generated from information provided by the datasource. Changes
# to it will not persist across an instance reboot. To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
ethernets:
enP1p0s0:
optional: true
dhcp4: true
enP1p0s0d1:
optional: true
dhcp4: true
enP2p0s0:
optional: true
dhcp4: true
enP2p0s0d1:
optional: true
dhcp4: true
encc000: {}
version: 2
vlans:
encc000.2653:
addresses:
- 10.11.12.15/24
gateway4: 10.11.12.1
id: 2653
link: encc000
nameservers:
addresses:
- 10.11.12.1
... can be set fine (also --dry-run does not moan, except about
dhcp4).
This worked in the past on noble, but also on older Ubuntu releases
like jammy.
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2060311/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2060681] Re: systemd-networkd-wait-online.service halts booting for 2 1/2 minutes
This is probably a duplicate of bug 2060311. Can you attach your netplan config? ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2060681 Title: systemd-networkd-wait-online.service halts booting for 2 1/2 minutes Status in systemd package in Ubuntu: Incomplete Bug description: When booting http://cdimage.ubuntu.com/ubuntu-server/daily- preinstalled/20240409/noble-preinstalled-server-riscv64.img.xz the system waits for 2 1/2 minutes for systemd-networkd-wait- online.service to time out. See attached boot chart. --- ProblemType: Bug ApportVersion: 2.28.0-0ubuntu1 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20240409 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) DistroRelease: Ubuntu 24.04 Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge +-01.0 Red Hat, Inc. Virtio RNG \-02.0 Red Hat, Inc. Virtio block device Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: systemd 255.4-1ubuntu7 PackageArchitecture: riscv64 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-20-generic root=LABEL=cloudimg-rootfs ro efi=debug earlycon init=/lib/systemd/systemd-bootchart ProcVersionSignature: Ubuntu 6.8.0-20.20.1-generic 6.8.1 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. Tags: cloud-image noble Uname: Linux 6.8.0-20-generic riscv64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2060681/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2060331] Re: add-apt-repository --list not returning any deb822 repositories
Thanks for the bug report. This was overlooked when adding deb822 support. ** Changed in: software-properties (Ubuntu) Status: New => Confirmed ** Changed in: software-properties (Ubuntu) Importance: Undecided => Low ** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2060331 Title: add-apt-repository --list not returning any deb822 repositories Status in software-properties package in Ubuntu: Confirmed Bug description: Recreating the following bug report (#2052851) with a new title per Jeremy Bícha's (jbicha) request: https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2052851 --- On Ubuntu 23.10: * When adding a PPA, 'add-apt-repository' will add the repository in the new deb822 format as a '.sources' file in '/etc/apt/sources.list.d' * However, 'add-apt-repository --list' cannot see/understand the new '.sources' file For example, with the flacon ppa (https://launchpad.net/~flacon/+archive/ubuntu/ppa): 1. 'sudo add-apt-repository ppa:flacon/ppa' adds the flacon repo as '/etc/apt/sources.list.d/flacon-ubuntu-ppa-mantic.sources' 2. apt can install and update from the new repo, as expected. you can also remove the repo, as expected, by running 'sudo add-apt-repository --remove ppa:flacon/ppa' 3. However, 'add-apt-repository --list' does not list the repo as it should. GUI package managers such as Muon and Synaptic also do not see the new repo. It makes working with packages frustrating, and unfortunately, per Julian Andres Klode (juliank), there seems to be no plan to fix the broken 'software-properties-common' any time soon. See here: https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2033949 Also see related issues: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2036761 https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2037210 https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2036288 https://lists.ubuntu.com/archives/ubuntu-devel/2023-September/042791.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2060331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055200] Re: tests-in-lxd is broken with latest autopkgtest version
** Changed in: systemd (Ubuntu Mantic) Status: Won't Fix => Triaged ** Changed in: systemd (Ubuntu Mantic) Importance: Undecided => Low -- 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/2055200 Title: tests-in-lxd is broken with latest autopkgtest version Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Triaged Status in systemd source package in Mantic: Triaged Bug description: With autopkgtest 5.32 being SRU'd to Jammy[1], `tests-in-lxd` breaks because it can't patch `autopkgtest-build-lxd` anymore. Please find a debdiff attached to fix that issue. [1]: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2051939 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2055200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2060150] Re: openssh sets PAM_RHOST to UNKNOWN causing slow logins
I was preparing a bug fix upload, so I have picked this up as well. ** Changed in: openssh (Ubuntu) Assignee: (unassigned) => Nick Rosbrook (enr0n) ** Changed in: openssh (Ubuntu) Status: Confirmed => In Progress -- 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/2060150 Title: openssh sets PAM_RHOST to UNKNOWN causing slow logins Status in openssh package in Ubuntu: In Progress Bug description: When using sshd's -i option with stdio that is not a AF_INET/AF_INET6 socket, auth_get_canonical_hostname() returns "UNKNOWN" which is then set as the value of PAM_RHOST, causing pam to try to do a reverse DNS query of "UNKNOWN", which times out multiple times, causing a substantial slowdown when logging in. upstream PR: https://github.com/openssh/openssh-portable/pull/388 upstream email: https://lists.mindrot.org/pipermail/openssh-unix-dev/2024-April/041289.html Fedora backport: https://src.fedoraproject.org/rpms/openssh/pull-request/71 Debian backport: https://salsa.debian.org/ssh-team/openssh/-/merge_requests/25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2060150/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2060311] Re: Setting "optional: true" to overcome he timeout "Job systemd-networkd-wait-online" does no longer work with latest noble image
There has been confusion in this area in the past. But the stance of
upstream is that RequiredForOnline=no => "interface is _ignored_ by
systemd-networkd-wait-online". Hence, if every interface is optional:
true, it is expected that systemd-networkd-wait-online will timeout.
I have recently suggested that netplan moves to a strategy where if
interface ethX is optional:false, then enable systemd-networkd-wait-
online@ethX.service. And, if ethX has optional: true, then do nothing
(namely do _not_ set RequiredForOnline=no). We probably need to then
either disable systemd-networkd-wait-online.service by default, or
change the default flags.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags added: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2060311
Title:
Setting "optional: true" to overcome he timeout "Job systemd-networkd-
wait-online" does no longer work with latest noble image
Status in Netplan:
New
Status in Ubuntu on IBM z Systems:
New
Status in systemd package in Ubuntu:
New
Bug description:
Especially on s390x (but not limited to s390x) it's often the case that a
system has network devices that are not necessarily connected during boot-up
and one gets such a 2 min timeout:
"Job systemd-networkd-wait-online. Start running (1min 59s / no limit)"
In the past I could avoid that by setting "optional: true" post-install (no
perfect, but worked),
but this does no longer seem to work using the latest noble ISO image (Apr
5th).
Setting 'optional: true' in /etc/netplan/50-cloud-init.yaml looks like
this for me:
# This file is generated from information provided by the datasource. Changes
# to it will not persist across an instance reboot. To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
ethernets:
enP1p0s0:
optional: true
dhcp4: true
enP1p0s0d1:
optional: true
dhcp4: true
enP2p0s0:
optional: true
dhcp4: true
enP2p0s0d1:
optional: true
dhcp4: true
encc000: {}
version: 2
vlans:
encc000.2653:
addresses:
- 10.11.12.15/24
gateway4: 10.11.12.1
id: 2653
link: encc000
nameservers:
addresses:
- 10.11.12.1
... can be set fine (also --dry-run does not moan, except about
dhcp4).
This worked in the past on noble, but also on older Ubuntu releases
like jammy.
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2060311/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2060311] Re: Setting "optional: true" to overcome he timeout "Job systemd-networkd-wait-online" does no longer work with latest noble image
Okay. Looking at the logs though, it doesn't seem that encc00 ever gets
configured. If it's optional: false, then it has RequiredForOnline=yes.
If it's not getting configured, then it's also expected that systemd-
networkd-wait-online times out. Or am I missing something else?
If we don't want network-online.target to block boot, then we need to
change cloud-init's systemd units. The dependency ordering in their
units is what leads to the possibility of boot blocking on network-
online.target.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2060311
Title:
Setting "optional: true" to overcome he timeout "Job systemd-networkd-
wait-online" does no longer work with latest noble image
Status in Netplan:
New
Status in Ubuntu on IBM z Systems:
New
Status in systemd package in Ubuntu:
New
Bug description:
Especially on s390x (but not limited to s390x) it's often the case that a
system has network devices that are not necessarily connected during boot-up
and one gets such a 2 min timeout:
"Job systemd-networkd-wait-online. Start running (1min 59s / no limit)"
In the past I could avoid that by setting "optional: true" post-install (no
perfect, but worked),
but this does no longer seem to work using the latest noble ISO image (Apr
5th).
Setting 'optional: true' in /etc/netplan/50-cloud-init.yaml looks like
this for me:
# This file is generated from information provided by the datasource. Changes
# to it will not persist across an instance reboot. To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
ethernets:
enP1p0s0:
optional: true
dhcp4: true
enP1p0s0d1:
optional: true
dhcp4: true
enP2p0s0:
optional: true
dhcp4: true
enP2p0s0d1:
optional: true
dhcp4: true
encc000: {}
version: 2
vlans:
encc000.2653:
addresses:
- 10.11.12.15/24
gateway4: 10.11.12.1
id: 2653
link: encc000
nameservers:
addresses:
- 10.11.12.1
... can be set fine (also --dry-run does not moan, except about
dhcp4).
This worked in the past on noble, but also on older Ubuntu releases
like jammy.
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2060311/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2060221] [NEW] nm_netplan.py autopkgtest fails with ModuleNotFoundError: No module named 'gi'
Public bug reported: Example log: https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/amd64/n/network-manager/20240404_183130_7a1cc@/log.gz The relevant part is: 3988s autopkgtest [18:31:02]: test nm_netplan.py: [--- 3988s Traceback (most recent call last): 3988s File "/tmp/autopkgtest.Q1jKoU/build.9D4/src/debian/tests/nm_netplan.py", line 18, in 3988s import gi 3988s ModuleNotFoundError: No module named 'gi' 3988s autopkgtest [18:31:02]: test nm_netplan.py: ---] 3989s autopkgtest [18:31:03]: test nm_netplan.py: - - - - - - - - - - results - - - - - - - - - - 3989s nm_netplan.pyFAIL non-zero exit status 1 It seems that nm_netplan.py needs to depend on python3-gi ** Affects: network-manager (Ubuntu) Importance: Undecided Assignee: Nick Rosbrook (enr0n) Status: New ** Tags: update-excuse ** Tags added: update-excuse ** Changed in: network-manager (Ubuntu) Assignee: (unassigned) => Nick Rosbrook (enr0n) -- 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/2060221 Title: nm_netplan.py autopkgtest fails with ModuleNotFoundError: No module named 'gi' Status in network-manager package in Ubuntu: New Bug description: Example log: https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/amd64/n/network-manager/20240404_183130_7a1cc@/log.gz The relevant part is: 3988s autopkgtest [18:31:02]: test nm_netplan.py: [--- 3988s Traceback (most recent call last): 3988s File "/tmp/autopkgtest.Q1jKoU/build.9D4/src/debian/tests/nm_netplan.py", line 18, in 3988s import gi 3988s ModuleNotFoundError: No module named 'gi' 3988s autopkgtest [18:31:02]: test nm_netplan.py: ---] 3989s autopkgtest [18:31:03]: test nm_netplan.py: - - - - - - - - - - results - - - - - - - - - - 3989s nm_netplan.pyFAIL non-zero exit status 1 It seems that nm_netplan.py needs to depend on python3-gi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2060221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2060150] Re: openssh sets PAM_RHOST to UNKNOWN causing slow logins
** Changed in: openssh (Ubuntu) Importance: Undecided => Medium ** Changed in: openssh (Ubuntu) Status: New => Confirmed -- 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/2060150 Title: openssh sets PAM_RHOST to UNKNOWN causing slow logins Status in openssh package in Ubuntu: Confirmed Bug description: When using sshd's -i option with stdio that is not a AF_INET/AF_INET6 socket, auth_get_canonical_hostname() returns "UNKNOWN" which is then set as the value of PAM_RHOST, causing pam to try to do a reverse DNS query of "UNKNOWN", which times out multiple times, causing a substantial slowdown when logging in. upstream PR: https://github.com/openssh/openssh-portable/pull/388 upstream email: https://lists.mindrot.org/pipermail/openssh-unix-dev/2024-April/041289.html Fedora backport: https://src.fedoraproject.org/rpms/openssh/pull-request/71 Debian backport: https://salsa.debian.org/ssh-team/openssh/-/merge_requests/25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2060150/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2059874] Re: on upgrade sshd-socket-generator conversion does not respect administrator intent
> For me the biggest problem was the socket unit beeing re-enabled when I had it disabled it but still running sshd.service (ie without socket activation) - now you're unexpectidly switched back to using socket activation - something I explicitly opted out of. Okay. We could probably adjust the check to ignore migration if the user is upgrading from kinetic or newer and has ssh.socket disabled. > I could also see this causing problems if you have the socket unit masked (dont see why you would want that however) but the the service is enabled, now you are without sshd. Actually I think the postinst would also fail in that case, as systemctl enable fails enabling masked units. This is a good point as well. ** Changed in: openssh (Ubuntu) Status: Incomplete => Confirmed ** Changed in: openssh (Ubuntu) Importance: Low => Medium ** Changed in: openssh (Ubuntu) Assignee: (unassigned) => Nick Rosbrook (enr0n) ** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2059874 Title: on upgrade sshd-socket-generator conversion does not respect administrator intent Status in openssh package in Ubuntu: Confirmed Bug description: the openssh-server 1:9.6p1-3ubuntu11 postinst contains this code snippet: if [ "$action" == configure ]; then ..snip.. if dpkg --compare-versions "$2" lt-nl 1:9.6p1-3ubuntu3~; then ..snip.. if [ -d /run/systemd/system ]; then # Make sure ssh.service is disabled. systemctl unmask ssh.service systemctl disable --now ssh.service > /dev/null 2>&1 # sshd-socket-generator is invoked on daemon-reload. systemctl daemon-reload systemctl enable ssh.socket fi fi fi This does not respect existing service and socket unit configuration, it effectively re-enables a disabled ssh.service (and even a masked one), and a manually disabled socket unit. I strongly suspect it does not respect systemd presets either. This is unexpected behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2059874/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2059874] Re: on upgrade sshd-socket-generator conversion does not respect administrator intent
Is there a strong use case for installing openssh-server, but then not wanting it to run as a daemon (i.e. disabling the necessary systemd units)? The purpose of this snippet is to migrate to socket activated sshd by default, which is the case for new installs of openssh-server. ** Changed in: openssh (Ubuntu) Status: New => Incomplete ** Changed in: openssh (Ubuntu) Importance: Undecided => Low -- 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/2059874 Title: on upgrade sshd-socket-generator conversion does not respect administrator intent Status in openssh package in Ubuntu: Incomplete Bug description: the openssh-server 1:9.6p1-3ubuntu11 postinst contains this code snippet: if [ "$action" == configure ]; then ..snip.. if dpkg --compare-versions "$2" lt-nl 1:9.6p1-3ubuntu3~; then ..snip.. if [ -d /run/systemd/system ]; then # Make sure ssh.service is disabled. systemctl unmask ssh.service systemctl disable --now ssh.service > /dev/null 2>&1 # sshd-socket-generator is invoked on daemon-reload. systemctl daemon-reload systemctl enable ssh.socket fi fi fi This does not respect existing service and socket unit configuration, it effectively re-enables a disabled ssh.service (and even a masked one), and a manually disabled socket unit. I strongly suspect it does not respect systemd presets either. This is unexpected behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2059874/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2059872] Re: Unable to listen on port 22 if multiple Port= present in sshd configuration
** Changed in: openssh (Ubuntu) Status: Triaged => In Progress -- 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/2059872 Title: Unable to listen on port 22 if multiple Port= present in sshd configuration Status in openssh package in Ubuntu: In Progress Bug description: Recently introduced sshd-socket-generator for socket activation in openssh 1:9.6p1-3ubuntu3 has a bug when dealing with multiple Port or ListenAddress entries in the sshd configuration. If you have multiple Port or ListenAddress and one of them is for port 22, it just skips it. To show it clearly, here is an example: Port 22 Port 1024 It generates: ListenStream= ListenStream=1024 Now nothing is listening to port 22, hence breaking existing configurations. This was tested on 1:9.6p1-3ubuntu11. The intention seems to be to not generate the drop-in if only port 22 is in use, but it does not account for the case of multiple Port or ListenAddress where one of them is for port 22. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2059872/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2059872] Re: Unable to listen on port 22 if multiple Port= present in sshd configuration
Thanks for reporting this. I confirmed it with: root@n:~# cat > /etc/ssh/sshd_config.d/ports.conf << EOF > Port 22 > Port 1024 > EOF root@n:~# /lib/systemd/system-generators/sshd-socket-generator . root@n:~# cat ssh.socket.d/addresses.conf # Automatically generated by sshd-socket-generator [Socket] ListenStream= ListenStream=1024 Looking at the code the bug is very clear. ** Changed in: openssh (Ubuntu) Status: New => Triaged ** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2059872 Title: Unable to listen on port 22 if multiple Port= present in sshd configuration Status in openssh package in Ubuntu: Triaged Bug description: Recently introduced sshd-socket-generator for socket activation in openssh 1:9.6p1-3ubuntu3 has a bug when dealing with multiple Port or ListenAddress entries in the sshd configuration. If you have multiple Port or ListenAddress and one of them is for port 22, it just skips it. To show it clearly, here is an example: Port 22 Port 1024 It generates: ListenStream= ListenStream=1024 Now nothing is listening to port 22, hence breaking existing configurations. This was tested on 1:9.6p1-3ubuntu11. The intention seems to be to not generate the drop-in if only port 22 is in use, but it does not account for the case of multiple Port or ListenAddress where one of them is for port 22. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2059872/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2059872] Re: Unable to listen on port 22 if multiple Port= present in sshd configuration
** Changed in: openssh (Ubuntu) Importance: Undecided => High ** Changed in: openssh (Ubuntu) Assignee: (unassigned) => Nick Rosbrook (enr0n) -- 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/2059872 Title: Unable to listen on port 22 if multiple Port= present in sshd configuration Status in openssh package in Ubuntu: New Bug description: Recently introduced sshd-socket-generator for socket activation in openssh 1:9.6p1-3ubuntu3 has a bug when dealing with multiple Port or ListenAddress entries in the sshd configuration. If you have multiple Port or ListenAddress and one of them is for port 22, it just skips it. To show it clearly, here is an example: Port 22 Port 1024 It generates: ListenStream= ListenStream=1024 Now nothing is listening to port 22, hence breaking existing configurations. This was tested on 1:9.6p1-3ubuntu11. The intention seems to be to not generate the drop-in if only port 22 is in use, but it does not account for the case of multiple Port or ListenAddress where one of them is for port 22. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2059872/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037210] Re: unable to add PPA by its sources.list line
** Changed in: software-properties (Ubuntu) Status: Confirmed => In Progress ** Tags removed: rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2037210 Title: unable to add PPA by its sources.list line Status in Software Properties: Confirmed Status in software-properties package in Ubuntu: In Progress Bug description: Steps to reproduce: 1. Have Ubuntu 23.10 installed 2. Run ``` sudo apt-key adv --keyserver keyserver.ubuntu.com --recv E756285F30DB2B2BB35012E219BFCAF5168D33A9 sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/vte/ubuntu jammy main" sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/wnck/ubuntu jammy main" ``` Expected results: * key added, two repositories are added to the relevant *.list files at /etc/apt/sources.list.d/ Actual results: * relevant *.list files at /etc/apt/sources.list.d/ are not created, having errors instead ``` $ sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/vte/ubuntu jammy main" Repository: 'deb http: //ppa.launchpad.net/nrbrtx/vte/ubuntu jammy main Components: ' Description: This PPA contains VTE library from Ubuntu 20.04 LTS which is not affected by stupid bug https://pad.lv/1922276 . So user will be able to select all terminal output with full scroll-back in MATE Terminal and other VTE-based terminals as it is expected. This PPA is useful for Ubuntu 22.04 LTS, Debian 11 (bullseye) and Debian 12 (bookworm). As usual one can always remove this PPA and downgrade VTE packages by using `sudo apt-get install ppa-purge` and `sudo ppa-purge ppa:nrbrtx/vte`. More info: https://launchpad.net/~nrbrtx/+archive/ubuntu/vte Adding repository. E: Malformed entry 1 in sources file /etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI) E: The list of sources could not be read. $ sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/wnck/ubuntu jammy main" Repository: 'deb http: //ppa.launchpad.net/nrbrtx/wnck/ubuntu jammy main Components: ' Description: This PPA provides patched libwnck3 package to fix https://github.com/mate-desktop/mate-panel/issues/1230 and https://pad.lv/1947420 . See details at https://github.com/mate-desktop/mate-panel/issues/1230#issuecomment-997422612 . This PPA is useful for Ubuntu 22.04 LTS and Debian 12 (bookworm). As usual one can always remove this PPA and downgrade WNCK packages by using `sudo apt-get install ppa-purge` and `sudo ppa-purge ppa:nrbrtx/wnck`. More info: https://launchpad.net/~nrbrtx/+archive/ubuntu/wnck Adding repository. Found existing deb entry in /etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources E: Malformed entry 1 in sources file /etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI) E: The list of sources could not be read. $ sudo apt-get update E: Malformed entry 1 in sources file /etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI) E: The list of sources could not be read. ``` ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: software-properties-common 0.99.39 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME-Flashback Date: Sun Sep 24 14:02:10 2023 PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to mantic on 2023-04-13 (164 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-09-24T13:25:34.901411 To manage notifications about this bug go to: https://bugs.launchpad.net/software-properties/+bug/2037210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2049247] Re: Broken IPv4 support on IPv6-preferring networks (v255)
The referenced patch was included in v255.4, which has now landed in
noble.
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2049247
Title:
Broken IPv4 support on IPv6-preferring networks (v255)
Status in systemd:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Bug description:
I noticed a bug in systemd version 255 which is currently available in
noble-proposed (255.2-3ubuntu1).
I have already reported to upstream at
https://github.com/systemd/systemd/issues/30891 but there's no fix
available yet as of today.
I'm still reporting the bug here anyways because this bug can, under
some conditions, result in the loss of IPv4 network connectivity in a
completely standard Ubuntu 24.04 installation just by updating to
systemd 255. I'm hoping that that's okay even though it's a bug caused
by upstream not by Ubuntu; just because it could have a bad impact if
this version ends up in 24.04 as it is.
---
In systemd version 255, a feature has been added to "support" the
IPv6-only DHCP option 108 defined in RFC8925. I'm putting "support" in
quotation marks because one functionality that this RFC marks as a
requirement is not implemented in systemd yet.
To summarize: Option 108 can be sent by a DHCPv4 client to signal to
the DHCPv4 server: "Hey, if (and only if) your network has proper IPv6
support and a working NAT64 gateway, I don't really need my own IPv4
address, I can handle it using 464XLAT and NAT64". The point of that
option is to be able to run a Dual Stack network, where only clients
that really need IPv4 (older Linux, Windows, etc.) will receive an
IPv4 from DHCP, and clients that don't need IPv4 (Android, MacOS,
Linux with systemd >=255, etc.) won't receive one from DHCP and
instead set up a 464XLAT for outgoing IPv4 connectivity.
This new code in systemd is enabled by default (the option
"IPv6OnlyMode" defaults to "yes"). However, systemd does not actually
have code to set up a 464XLAT yet (which violates the RFC).
This means that systemd signals to the DHCPv4 server "Hey, I don't
need IPv4, I'll just use 464XLAT and NAT64" but then it doesn't
actually do that. Updating systemd on an Ubuntu 24.04 installation
(where systemd-networkd is used) will result in the loss of the DHCP-
assigned IPv4 address, breaking network connectivity for all IPv4-only
applications.
---
Information on how to reproduce this issue can be found in detail in
the github bug report linked above, but to summarize:
1. Have a Dual Stack network that announces a NAT64 through RAs or through
DNS (or, ideally, both)
2. Configure your DHCPv4 server to hand out option 108 ("v6-only-preferred")
3. Connect an Ubuntu machine with systemd < 255.
4. Notice that IPv4 connectivity is working fine.
5. Update to systemd = 255.
6. Notice that there's no IPv4 connectivity anymore and IPv4-only apps break.
---
The proper fix for this issue to make systemd conform to the RFC would
be to implement a 464XLAT. However that's not an easy task and most
certainly not something that would end up as a hotfix / patch release.
A good workaround for this bug would be, in my opinion, to change the
default value for the "IPv6OnlyMode" to "no" when compiling systemd.
That way, the RFC-violating code doesn't run by default, and if a user
does set up a 464XLAT on their machine in some other way (outside of
systemd) they can just change their config to include
"IPv6OnlyMode=yes" and it'll be working as intended.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: systemd 255.2-3ubuntu1
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
Date: Sat Jan 13 07:05:42 2024
InstallationDate: Installed on 2024-01-12 (0 days ago)
InstallationMedia: Ubuntu-Server 23.10 "Mantic Minotaur" - Release amd64
(20231011)
Lsusb:
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Lsusb-t:
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=ohci-pci/12p, 12M
|__ Port 001: Dev 002, If 0, Class=Human Interface Device,
Driver=usbhid, 12M
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=linux
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.6.0-14-generic
root=UUID=b5e6aabf-881a-4589-85ae-688f41df0be7 ro
SourcePackage: systemd
UpgradeStatus: Upgraded to noble on 2024-01-12 (0 days ago)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor:
[Touch-packages] [Bug 2037210] Re: unable to add PPA by its sources.list line
** Tags added: rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2037210 Title: unable to add PPA by its sources.list line Status in Software Properties: Confirmed Status in software-properties package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 23.10 installed 2. Run ``` sudo apt-key adv --keyserver keyserver.ubuntu.com --recv E756285F30DB2B2BB35012E219BFCAF5168D33A9 sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/vte/ubuntu jammy main" sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/wnck/ubuntu jammy main" ``` Expected results: * key added, two repositories are added to the relevant *.list files at /etc/apt/sources.list.d/ Actual results: * relevant *.list files at /etc/apt/sources.list.d/ are not created, having errors instead ``` $ sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/vte/ubuntu jammy main" Repository: 'deb http: //ppa.launchpad.net/nrbrtx/vte/ubuntu jammy main Components: ' Description: This PPA contains VTE library from Ubuntu 20.04 LTS which is not affected by stupid bug https://pad.lv/1922276 . So user will be able to select all terminal output with full scroll-back in MATE Terminal and other VTE-based terminals as it is expected. This PPA is useful for Ubuntu 22.04 LTS, Debian 11 (bullseye) and Debian 12 (bookworm). As usual one can always remove this PPA and downgrade VTE packages by using `sudo apt-get install ppa-purge` and `sudo ppa-purge ppa:nrbrtx/vte`. More info: https://launchpad.net/~nrbrtx/+archive/ubuntu/vte Adding repository. E: Malformed entry 1 in sources file /etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI) E: The list of sources could not be read. $ sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/wnck/ubuntu jammy main" Repository: 'deb http: //ppa.launchpad.net/nrbrtx/wnck/ubuntu jammy main Components: ' Description: This PPA provides patched libwnck3 package to fix https://github.com/mate-desktop/mate-panel/issues/1230 and https://pad.lv/1947420 . See details at https://github.com/mate-desktop/mate-panel/issues/1230#issuecomment-997422612 . This PPA is useful for Ubuntu 22.04 LTS and Debian 12 (bookworm). As usual one can always remove this PPA and downgrade WNCK packages by using `sudo apt-get install ppa-purge` and `sudo ppa-purge ppa:nrbrtx/wnck`. More info: https://launchpad.net/~nrbrtx/+archive/ubuntu/wnck Adding repository. Found existing deb entry in /etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources E: Malformed entry 1 in sources file /etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI) E: The list of sources could not be read. $ sudo apt-get update E: Malformed entry 1 in sources file /etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI) E: The list of sources could not be read. ``` ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: software-properties-common 0.99.39 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME-Flashback Date: Sun Sep 24 14:02:10 2023 PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to mantic on 2023-04-13 (164 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-09-24T13:25:34.901411 To manage notifications about this bug go to: https://bugs.launchpad.net/software-properties/+bug/2037210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2059258] [NEW] conntrack-tools: FTBFS: configure: error: Package requirements (libtirpc) were not met
Public bug reported: Imported from Debian bug http://bugs.debian.org/1066476: Source: conntrack-tools Version: 1:1.4.8-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for byacc... no > checking for pkg-config... /usr/bin/pkg-config > checking pkg-config is at least version 0.9.0... yes > checking for rpc/rpc_msg.h... no > checking for libtirpc... no > configure: error: Package requirements (libtirpc) were not met > > Package 'libtirpc', required by 'virtual:world', not found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables LIBTIRPC_CFLAGS > and LIBTIRPC_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2024/03/13/conntrack-tools_1.4.8-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. ** Affects: conntrack-tools (Ubuntu) Importance: Undecided Assignee: Nick Rosbrook (enr0n) Status: Triaged ** Affects: kmod (Ubuntu) Importance: Undecided Status: New ** Affects: conntrack-tools (Debian) Importance: Undecided Status: New ** Tags: update-excuse ** Bug watch added: Debian Bug tracker #1066476 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066476 ** Changed in: conntrack-tools (Debian) Remote watch: None => Debian Bug tracker #1066476 ** Changed in: conntrack-tools (Ubuntu) Status: New => Incomplete ** Changed in: conntrack-tools (Ubuntu) Status: Incomplete => Triaged ** Changed in: conntrack-tools (Ubuntu) Assignee: (unassigned) => Nick Rosbrook (enr0n) ** Also affects: kmod (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/2059258 Title: conntrack-tools: FTBFS: configure: error: Package requirements (libtirpc) were not met Status in conntrack-tools package in Ubuntu: Triaged Status in kmod package in Ubuntu: New Status in conntrack-tools package in Debian: New Bug description: Imported from Debian bug http://bugs.debian.org/1066476: Source: conntrack-tools Version: 1:1.4.8-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for byacc... no > checking for pkg-config... /usr/bin/pkg-config > checking pkg-config is at least version 0.9.0... yes > checking for rpc/rpc_msg.h... no > checking for libtirpc... no > configure: error: Package requirements (libtirpc) were not met > > Package 'libtirpc', required by 'virtual:world', not found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables LIBTIRPC_CFLAGS > and LIBTIRPC_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2024/03/13/conntrack-tools_1.4.8-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce thi
[Touch-packages] [Bug 2059258] Re: conntrack-tools: FTBFS: configure: error: Package requirements (libtirpc) were not met
This is currently blocking kmod from migrating. The issue is already fixed in Debian, so we could just sync 1:1.4.8-2 when appropriate. ** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/2059258 Title: conntrack-tools: FTBFS: configure: error: Package requirements (libtirpc) were not met Status in conntrack-tools package in Ubuntu: Triaged Status in kmod package in Ubuntu: New Status in conntrack-tools package in Debian: New Bug description: Imported from Debian bug http://bugs.debian.org/1066476: Source: conntrack-tools Version: 1:1.4.8-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for byacc... no > checking for pkg-config... /usr/bin/pkg-config > checking pkg-config is at least version 0.9.0... yes > checking for rpc/rpc_msg.h... no > checking for libtirpc... no > configure: error: Package requirements (libtirpc) were not met > > Package 'libtirpc', required by 'virtual:world', not found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables LIBTIRPC_CFLAGS > and LIBTIRPC_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2024/03/13/conntrack-tools_1.4.8-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/conntrack-tools/+bug/2059258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058800] Re: [needs-packaging] Add systemd-bsod
This is already done in noble. ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2058800 Title: [needs-packaging] Add systemd-bsod Status in systemd package in Ubuntu: Fix Released Bug description: One of the components of systemd 255 and later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2058800/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056153] Re: Removing the systemd-resolved package breaks DNSSEC validation
Or, actually, not exactly. We don't want the stub-resolv.conf since systemd-resolved is leaving, but we probably do want the options. -- 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/2056153 Title: Removing the systemd-resolved package breaks DNSSEC validation Status in systemd package in Ubuntu: Confirmed Bug description: Removing the systemd-resolved package breaks glibc DNSSEC validation, because it removes an existing line from the new /etc/resolv.conf file. This line should be retained so that packages like Exim can continue to use the AD bit after systemd-resolved is removed. ubuntu@instance:~$ grep -v '^#' /etc/resolv.conf nameserver 127.0.0.53 options edns0 trust-ad search vcn.oraclevcn.com ubuntu@instance:~$ sudo apt remove systemd-resolved ubuntu@instance:~$ grep -v '^#' /etc/resolv.conf nameserver 169.254.169.254 search vcn.oraclevcn.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2056153/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056153] Re: Removing the systemd-resolved package breaks DNSSEC validation
Yeah, this looks like a bug. The systemd-resolved.postrm is copying /run/systemd/resolve/resolv.conf to /etc/resolv.conf, rather then copying /run/systemd/resolve/stub-resolv.conf (which is where /etc/resolv.conf is symlinked to prior to removal). ** Changed in: systemd (Ubuntu) Status: New => Confirmed ** Changed in: systemd (Ubuntu) Importance: Undecided => Low -- 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/2056153 Title: Removing the systemd-resolved package breaks DNSSEC validation Status in systemd package in Ubuntu: Confirmed Bug description: Removing the systemd-resolved package breaks glibc DNSSEC validation, because it removes an existing line from the new /etc/resolv.conf file. This line should be retained so that packages like Exim can continue to use the AD bit after systemd-resolved is removed. ubuntu@instance:~$ grep -v '^#' /etc/resolv.conf nameserver 127.0.0.53 options edns0 trust-ad search vcn.oraclevcn.com ubuntu@instance:~$ sudo apt remove systemd-resolved ubuntu@instance:~$ grep -v '^#' /etc/resolv.conf nameserver 169.254.169.254 search vcn.oraclevcn.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2056153/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054977] Re: systemd-networkd fails to renew DHCP v4 lease when renew attempt times out
I think this would be better suited as an upstream issue, because AFAICT this case is still not handled in the latest version. If you do open an upstream bug (https://github.com/systemd/systemd/issues), they will want to see this reproduced on at least systemd v254. Please comment back here if you open a bug upstream. ** Changed in: systemd (Ubuntu) Status: Confirmed => Incomplete ** Changed in: systemd (Ubuntu) Importance: Undecided => Low -- 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/2054977 Title: systemd-networkd fails to renew DHCP v4 lease when renew attempt times out Status in systemd package in Ubuntu: Incomplete Bug description: I'm seeing exactly what this gist describes: https://gist.github.com/raggi/1f8d0b9f45c5b62e7131b03e6e2ffe68 Summary: 1. Configure a machine with a DHCPv4 lease on a network with a DHCPv4 server. 2. Place machine under unusual load sufficient to cause a timeout on netlink requests. 3. Observe the interface failing with the following logs: systemd-networkd[139370]: eth0: Could not set DHCPv4 address: Connection timed out systemd-networkd[139370]: eth0: Failed The error seems to come from here: https://github.com/systemd/systemd/blob/v245.4/src/network/networkd-dhcp4.c#L781 Expected behavior The DHCPv4 client should retry the lease refresh when the issue is a timeout, eventually succeeding in these scenarios. Actual behavior Permanent loss of connectivity on the affected interface. Additional info: $ lsb_release -rd Description:Ubuntu 20.04.6 LTS Release:20.04 $ apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3.23 Candidate: 245.4-4ubuntu3.23 Version table: *** 245.4-4ubuntu3.23 500 500 http://ap-southeast-2.ec2.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 mirror+file:/etc/apt/source-mirrors.txt focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 245.4-4ubuntu3.20 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 500 mirror+file:/etc/apt/source-mirrors.txt focal-security/main amd64 Packages 245.4-4ubuntu3 500 500 http://ap-southeast-2.ec2.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 mirror+file:/etc/apt/source-mirrors.txt focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2054977/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056802] Re: crypttab does not honor `x-initrd.attach` option
AFAIK, we don't use systemd-cryptsetup in Ubuntu's initrd, and you are trying to use an option specific to systemd's crypttab implementation. So I am not surprised by: cryptsetup: WARNING: dm_crypt-0: ignoring unknown option x-initrd.attach What are you trying to do here exactly? ** Changed in: systemd (Ubuntu Focal) Status: Confirmed => Incomplete ** Changed in: systemd (Ubuntu Jammy) Status: Confirmed => Incomplete ** Changed in: systemd (Ubuntu Mantic) Status: Confirmed => Incomplete ** Changed in: systemd (Ubuntu Noble) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2056802 Title: crypttab does not honor `x-initrd.attach` option Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Bionic: Won't Fix Status in systemd source package in Focal: Incomplete Status in systemd source package in Jammy: Incomplete Status in systemd source package in Mantic: Incomplete Status in systemd source package in Noble: Incomplete Bug description: From systemd version 245+ an option was added x-initrd.attach - Setup this encrypted block device in the initrd, similarly to systemd.mount(5) units marked with x-initrd.mount. Although it's not necessary to mark the mount entry for the root file system with x-initrd.mount, x-initrd.attach is still recommended with the encrypted block device containing the root file system as otherwise systemd will attempt to detach the device during the regular system shutdown while it's still in use. With this option the device will still be detached but later after the root file system is unmounted. All other encrypted block devices that contain file systems mounted in the initrd should use this option. Added in version 245. [0] - release: noble systemd version: 253.5-1ubuntu6 Install noble to a vm with virt-manager and encrypt the lvm during subiquity install. After successful install, Modify /etc/crypttab to include the parameter in the 4th column example: sda6_crypt UUID=099aae4a-b11b-49a6-a6c4-62939eddf7a0 none luks,x-initrd.attach update-initramfs -u -k all During boot or shutdown the logs show cryptsetup: WARNING: dm_crypt-0: ignoring unknown option x-initrd.attach There are two separate problems 1. crypttab doesn't recognize x-initrd.attach option in /etc/crypttab file. cryptsetup: WARNING: dm_crypt-0: ignoring unknown option x-initrd.attach 2. this error happens on shutdown/restart [systemd-cryptsetup]: Device dm-crypt-0 is still in use. [systemd-cryptsetup]: Failed to deactivate: Device or resource busy. The vm does eventually shutdown after throwing the above warnings. [0] https://www.freedesktop.org/software/systemd/man/latest/crypttab.html#x-initrd.attach These patches look like they could fix the issue, The last one might not be needed. git format-patch -1 8ce02b87cece09797c1030c778db4180e1e2ce2e https://github.com/systemd/systemd/commit/8ce02b87cece09797c1030c778db4180e1e2ce2e git format-patch -1 1dc85eff1d0dff18aaeaae530c91bf53f34b726e https://github.com/systemd/systemd/commit/1dc85eff1d0dff18aaeaae530c91bf53f34b726e git format-patch -1 bf1484c70a24cf04c145a9509c8124ffd7fb0879 https://github.com/systemd/systemd/commit/bf1484c70a24cf04c145a9509c8124ffd7fb0879 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2056802/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2057768] Re: Unit and its Alias appear to be separate entities when enabling the unit by filepath
** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Mantic) Status: New => Won't Fix ** Changed in: systemd (Ubuntu Focal) Status: New => Confirmed ** Changed in: systemd (Ubuntu Jammy) Status: New => Confirmed ** Changed in: systemd (Ubuntu Focal) Importance: Undecided => Wishlist ** Changed in: systemd (Ubuntu Jammy) Importance: Undecided => Wishlist ** Changed in: systemd (Ubuntu) Importance: Wishlist => Medium -- 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/2057768 Title: Unit and its Alias appear to be separate entities when enabling the unit by filepath Status in systemd package in Ubuntu: Triaged Status in systemd source package in Focal: Confirmed Status in systemd source package in Jammy: Confirmed Status in systemd source package in Mantic: Won't Fix Bug description: ### systemd version the issue has been seen with 245 ### Used distribution Linux Mint 20.1 and Ubuntu 20.04 ### Linux kernel version used 5.4.0-135-generic ### CPU architectures issue was seen on None ### Component systemctl ### Expected behaviour you didn't see When including an alias in a unit file that is enabled by referring to its filepath, its alias should refer to the unit - the two should refer to the exact same service. This is the case when the unit file is enabled inside one of the systemd directories. I expect alias and unit to refer to one identical service also when enabling via filepath. In particular, the output of `systemctl status ...` should be identical for a Unit and its Alias. ### Unexpected behaviour you saw After passing a systemd unit including an alias to `systemctl enable PATH...` by path, systemctl treated the unit and its alias as separate units. Specifically, `systemctl status` reports different results (running/inactive, PID if applicable) for the unit name and its alias. When I start the unit by its original name, only the status of the unit is reported as running while the status of the alias remains inactive, and vice versa. After starting the Alias too, two services with different PIDs are running. (When copying the unit into /etc/systemd/system/ and running `systemctl enable UNIT...` this issue does not occur and alias and unit behave the same.) ### Steps to reproduce the problem ``` ~$ cat dummy.service [Service] ExecStart=tail -f /dev/null [Install] Alias=dumb.service ~$ sudo systemctl enable ~/dummy.service Created symlink /etc/systemd/system/dumb.service → /home/lukas/dummy.service. Created symlink /etc/systemd/system/dummy.service → /home/lukas/dummy.service. ~$ sudo systemctl start dummy ~$ systemctl status dummy ● dummy.service Loaded: loaded (/etc/systemd/system/dummy.service; enabled; vendor preset:> Active: active (running) since Tue 2024-03-12 15:36:58 CET; 8s ago Main PID: 159809 (tail) Tasks: 1 (limit: 76978) Memory: 160.0K CGroup: /system.slice/dummy.service └─159809 /usr/bin/tail -f /dev/null Mär 12 15:36:58 MyMachine systemd[1]: Started dummy.service. ~$ systemctl status dumb ● dumb.service Loaded: loaded (/etc/systemd/system/dumb.service; enabled; vendor preset: > Active: inactive (dead) Mär 12 15:30:53 MyMachine systemd[1]: Started dumb.service. Mär 12 15:31:16 MyMachine systemd[1]: Stopping dumb.service... Mär 12 15:31:16 MyMachine systemd[1]: dumb.service: Succeeded. Mär 12 15:31:16 MyMachine systemd[1]: Stopped dumb.service. ~$ ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2057768/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2057768] Re: Unit and its Alias appear to be separate entities when enabling the unit by filepath
Fixed in upstream: https://github.com/systemd/systemd/pull/31816. I will plan on getting this patch in noble, but I am not sure about focal or jammy. ** Changed in: systemd (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2057768 Title: Unit and its Alias appear to be separate entities when enabling the unit by filepath Status in systemd package in Ubuntu: Triaged Bug description: ### systemd version the issue has been seen with 245 ### Used distribution Linux Mint 20.1 and Ubuntu 20.04 ### Linux kernel version used 5.4.0-135-generic ### CPU architectures issue was seen on None ### Component systemctl ### Expected behaviour you didn't see When including an alias in a unit file that is enabled by referring to its filepath, its alias should refer to the unit - the two should refer to the exact same service. This is the case when the unit file is enabled inside one of the systemd directories. I expect alias and unit to refer to one identical service also when enabling via filepath. In particular, the output of `systemctl status ...` should be identical for a Unit and its Alias. ### Unexpected behaviour you saw After passing a systemd unit including an alias to `systemctl enable PATH...` by path, systemctl treated the unit and its alias as separate units. Specifically, `systemctl status` reports different results (running/inactive, PID if applicable) for the unit name and its alias. When I start the unit by its original name, only the status of the unit is reported as running while the status of the alias remains inactive, and vice versa. After starting the Alias too, two services with different PIDs are running. (When copying the unit into /etc/systemd/system/ and running `systemctl enable UNIT...` this issue does not occur and alias and unit behave the same.) ### Steps to reproduce the problem ``` ~$ cat dummy.service [Service] ExecStart=tail -f /dev/null [Install] Alias=dumb.service ~$ sudo systemctl enable ~/dummy.service Created symlink /etc/systemd/system/dumb.service → /home/lukas/dummy.service. Created symlink /etc/systemd/system/dummy.service → /home/lukas/dummy.service. ~$ sudo systemctl start dummy ~$ systemctl status dummy ● dummy.service Loaded: loaded (/etc/systemd/system/dummy.service; enabled; vendor preset:> Active: active (running) since Tue 2024-03-12 15:36:58 CET; 8s ago Main PID: 159809 (tail) Tasks: 1 (limit: 76978) Memory: 160.0K CGroup: /system.slice/dummy.service └─159809 /usr/bin/tail -f /dev/null Mär 12 15:36:58 MyMachine systemd[1]: Started dummy.service. ~$ systemctl status dumb ● dumb.service Loaded: loaded (/etc/systemd/system/dumb.service; enabled; vendor preset: > Active: inactive (dead) Mär 12 15:30:53 MyMachine systemd[1]: Started dumb.service. Mär 12 15:31:16 MyMachine systemd[1]: Stopping dumb.service... Mär 12 15:31:16 MyMachine systemd[1]: dumb.service: Succeeded. Mär 12 15:31:16 MyMachine systemd[1]: Stopped dumb.service. ~$ ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2057768/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2057768] Re: Unit and its Alias appear to be separate entities when enabling the unit by filepath
This affects all current releases AFAICT. ** Changed in: systemd (Ubuntu) Status: New => Confirmed ** Changed in: systemd (Ubuntu) Importance: Undecided => Wishlist ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Nick Rosbrook (enr0n) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2057768 Title: Unit and its Alias appear to be separate entities when enabling the unit by filepath Status in systemd package in Ubuntu: Confirmed Bug description: ### systemd version the issue has been seen with 245 ### Used distribution Linux Mint 20.1 and Ubuntu 20.04 ### Linux kernel version used 5.4.0-135-generic ### CPU architectures issue was seen on None ### Component systemctl ### Expected behaviour you didn't see When including an alias in a unit file that is enabled by referring to its filepath, its alias should refer to the unit - the two should refer to the exact same service. This is the case when the unit file is enabled inside one of the systemd directories. I expect alias and unit to refer to one identical service also when enabling via filepath. In particular, the output of `systemctl status ...` should be identical for a Unit and its Alias. ### Unexpected behaviour you saw After passing a systemd unit including an alias to `systemctl enable PATH...` by path, systemctl treated the unit and its alias as separate units. Specifically, `systemctl status` reports different results (running/inactive, PID if applicable) for the unit name and its alias. When I start the unit by its original name, only the status of the unit is reported as running while the status of the alias remains inactive, and vice versa. After starting the Alias too, two services with different PIDs are running. (When copying the unit into /etc/systemd/system/ and running `systemctl enable UNIT...` this issue does not occur and alias and unit behave the same.) ### Steps to reproduce the problem ``` ~$ cat dummy.service [Service] ExecStart=tail -f /dev/null [Install] Alias=dumb.service ~$ sudo systemctl enable ~/dummy.service Created symlink /etc/systemd/system/dumb.service → /home/lukas/dummy.service. Created symlink /etc/systemd/system/dummy.service → /home/lukas/dummy.service. ~$ sudo systemctl start dummy ~$ systemctl status dummy ● dummy.service Loaded: loaded (/etc/systemd/system/dummy.service; enabled; vendor preset:> Active: active (running) since Tue 2024-03-12 15:36:58 CET; 8s ago Main PID: 159809 (tail) Tasks: 1 (limit: 76978) Memory: 160.0K CGroup: /system.slice/dummy.service └─159809 /usr/bin/tail -f /dev/null Mär 12 15:36:58 MyMachine systemd[1]: Started dummy.service. ~$ systemctl status dumb ● dumb.service Loaded: loaded (/etc/systemd/system/dumb.service; enabled; vendor preset: > Active: inactive (dead) Mär 12 15:30:53 MyMachine systemd[1]: Started dumb.service. Mär 12 15:31:16 MyMachine systemd[1]: Stopping dumb.service... Mär 12 15:31:16 MyMachine systemd[1]: dumb.service: Succeeded. Mär 12 15:31:16 MyMachine systemd[1]: Stopped dumb.service. ~$ ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2057768/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2047447] Re: No valid source.list found while upgrading from mantic to noble
We decided it would be best to just SRU python-apt to mantic to fix this, rather than write a workaround in ubuntu-release-upgrader. Updating the tasks to reflect that. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Confirmed => Invalid ** Changed in: ubuntu-release-upgrader (Ubuntu Mantic) Status: New => Invalid ** Changed in: python-apt (Ubuntu Mantic) Status: New => Confirmed ** Changed in: python-apt (Ubuntu Mantic) Assignee: (unassigned) => Julian Andres Klode (juliank) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in python-apt source package in Mantic: Confirmed Status in ubuntu-release-upgrader source package in Mantic: Invalid Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information No valid sources.list entry found While scanning your repository information no entry about mantic could be found. An upgrade might not succeed. Do you want to continue anyway? Continue [yN] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2047447] Re: No valid source.list found while upgrading from mantic to noble
Very odd. I am able to upgrade just fine using your sources, Xavier. For now, I will work on fixing the issue I described[1] since it is at least *one* way to reproduce this error. [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/+bug/2047447/comments/7 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in python-apt source package in Mantic: New Status in ubuntu-release-upgrader source package in Mantic: New Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information No valid sources.list entry found While scanning your repository information no entry about mantic could be found. An upgrade might not succeed. Do you want to continue anyway? Continue [yN] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2047447] Re: No valid source.list found while upgrading from mantic to noble
> The problem not in "sources" file but "empty" /etc/apt/sources.list That is not the case. You can easily verify this by testing with an empty /etc/apt/sources.list, and /etc/apt/sources.list.d/ubuntu.sources which contains: Types: deb URIs: http://archive.ubuntu.com/ubuntu Suites: mantic mantic-updates Components: main universe Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg Types: deb URIs: http://security.ubuntu.com/ubuntu Suites: mantic-security Components: main universe Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in python-apt source package in Mantic: New Status in ubuntu-release-upgrader source package in Mantic: New Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information No valid sources.list entry found While scanning your repository information no entry about mantic could be found. An upgrade might not succeed. Do you want to continue anyway? Continue [yN] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2047447] Re: No valid source.list found while upgrading from mantic to noble
Thanks, Xavier. Can you please attach a tarball with all of those .sources? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in python-apt source package in Mantic: New Status in ubuntu-release-upgrader source package in Mantic: New Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information No valid sources.list entry found While scanning your repository information no entry about mantic could be found. An upgrade might not succeed. Do you want to continue anyway? Continue [yN] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054716] Re: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Confirmed ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Nick Rosbrook (enr0n) ** Changed in: systemd (Ubuntu) Importance: Undecided => High -- 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/2054716 Title: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1 Status in policykit-1 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I was working on recreating bug 2054319 and did so by modifying my /etc/apt/sources.list file from jammy to noble and installing polkit and all its dependencies. bdmurray@clean-jammy-amd64:~$ sudo apt-get install gir1.2-polkit-1.0 libpolkit-agent-1-0:amd64 libpolkit-gobject-1-0:amd64 pkexec policykit-1 polkitd Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-6.2.0-26-generic linux-headers-6.2.0-36-generic linux-headers-6.5.0-14-generic linux-hwe-6.2-headers-6.2.0-26 linux-hwe-6.2-headers-6.2.0-36 linux-hwe-6.5-headers-6.5.0-14 linux-image-6.2.0-26-generic linux-image-6.2.0-36-generic linux-image-6.5.0-14-generic linux-modules-6.2.0-26-generic linux-modules-6.2.0-36-generic linux-modules-6.5.0-14-generic linux-modules-extra-6.2.0-26-generic linux-modules-extra-6.2.0-36-generic linux-modules-extra-6.5.0-14-generic Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libduktape207 libgcrypt20 libglib2.0-0 libglib2.0-bin libnss-systemd libpam-systemd libsystemd-shared libsystemd0 libudev1 libzstd1 locales systemd systemd-dev systemd-oomd systemd-resolved systemd-sysv systemd-timesyncd udev Suggested packages: glibc-doc rng-tools low-memory-monitor polkitd-pkla systemd-container systemd-homed systemd-userdbd systemd-boot libqrencode4 libtss2-rc0 Recommended packages: libnss-nis libnss-nisplus The following NEW packages will be installed: libduktape207 libsystemd-shared systemd-dev systemd-resolved The following packages will be upgraded: gir1.2-polkit-1.0 libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libgcrypt20 libglib2.0-0 libglib2.0-bin libnss-systemd libpam-systemd libpolkit-agent-1-0 libpolkit-gobject-1-0 libsystemd0 libudev1 libzstd1 locales pkexec policykit-1 polkitd systemd systemd-oomd systemd-sysv systemd-timesyncd udev 26 upgraded, 4 newly installed, 0 to remove and 1407 not upgraded. Need to get 34.9 MB of archives. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: polkitd 124-1 ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail Date: Thu Feb 22 08:46:48 2024 ErrorMessage: installed polkitd package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-11-02 (112 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: policykit-1 Title: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2054716/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054716] Re: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1
After the upgrade, I manually run the systemd-sysusers command and see this. root@j:~# SYSTEMD_LOG_LEVEL=debug systemd-sysusers polkit.conf Failed to connect to /run/systemd/userdb/io.systemd.DynamicUser: Connection refused Unable to connect to /run/systemd/userdb/io.systemd.DynamicUser: Connection refused Failed to connect to /run/systemd/userdb/io.systemd.DynamicUser: Connection refused Unable to connect to /run/systemd/userdb/io.systemd.DynamicUser: Connection refused Failed to check if group polkitd already exists: Connection refused So, the getgrnam() call in systemd-sysusers results in libnss-systemd attempting to make a varlink call to pid1 to check if the group exists as a dynamic group, but the varlink connection setup fails. This appears to go away after a reboot, but not a `systemctl daemon re-exec`. I have yet to figure out the root cause on the systemd side. However, as a workaround, we could set SYSTEMD_NSS_BYPASS_DYNAMIC=1 when calling systemd-sysusers in polkitd.postinst. This should be safe because the polkitd package is creating a real user/group for polkitd, so a successful check from io.systemd.DynamicUser is irrelevant. I have prepared a patch with this proposed workaround, but will continue to look into this from the systemd side. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/2054716 Title: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1 Status in policykit-1 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I was working on recreating bug 2054319 and did so by modifying my /etc/apt/sources.list file from jammy to noble and installing polkit and all its dependencies. bdmurray@clean-jammy-amd64:~$ sudo apt-get install gir1.2-polkit-1.0 libpolkit-agent-1-0:amd64 libpolkit-gobject-1-0:amd64 pkexec policykit-1 polkitd Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-6.2.0-26-generic linux-headers-6.2.0-36-generic linux-headers-6.5.0-14-generic linux-hwe-6.2-headers-6.2.0-26 linux-hwe-6.2-headers-6.2.0-36 linux-hwe-6.5-headers-6.5.0-14 linux-image-6.2.0-26-generic linux-image-6.2.0-36-generic linux-image-6.5.0-14-generic linux-modules-6.2.0-26-generic linux-modules-6.2.0-36-generic linux-modules-6.5.0-14-generic linux-modules-extra-6.2.0-26-generic linux-modules-extra-6.2.0-36-generic linux-modules-extra-6.5.0-14-generic Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libduktape207 libgcrypt20 libglib2.0-0 libglib2.0-bin libnss-systemd libpam-systemd libsystemd-shared libsystemd0 libudev1 libzstd1 locales systemd systemd-dev systemd-oomd systemd-resolved systemd-sysv systemd-timesyncd udev Suggested packages: glibc-doc rng-tools low-memory-monitor polkitd-pkla systemd-container systemd-homed systemd-userdbd systemd-boot libqrencode4 libtss2-rc0 Recommended packages: libnss-nis libnss-nisplus The following NEW packages will be installed: libduktape207 libsystemd-shared systemd-dev systemd-resolved The following packages will be upgraded: gir1.2-polkit-1.0 libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libgcrypt20 libglib2.0-0 libglib2.0-bin libnss-systemd libpam-systemd libpolkit-agent-1-0 libpolkit-gobject-1-0 libsystemd0 libudev1 libzstd1 locales pkexec policykit-1 polkitd systemd systemd-oomd systemd-sysv systemd-timesyncd udev 26 upgraded, 4 newly installed, 0 to remove and 1407 not upgraded. Need to get 34.9 MB of archives. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: polkitd 124-1 ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail Date: Thu Feb 22 08:46:48 2024 ErrorMessage: installed polkitd package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-11-02 (112 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: policykit-1 Title: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1 UpgradeStatus: No
[Touch-packages] [Bug 2054716] Re: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1
Actually, while the delta in systemd.postinst is still likely unnecessary, this should not affect polkitd.postinst. The real error looks like: Setting up polkitd (124-1) ... [0;1;31mFailed to check if group polkitd already exists: Connection refused[0m So I am looking into that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/2054716 Title: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1 Status in policykit-1 package in Ubuntu: Confirmed Bug description: I was working on recreating bug 2054319 and did so by modifying my /etc/apt/sources.list file from jammy to noble and installing polkit and all its dependencies. bdmurray@clean-jammy-amd64:~$ sudo apt-get install gir1.2-polkit-1.0 libpolkit-agent-1-0:amd64 libpolkit-gobject-1-0:amd64 pkexec policykit-1 polkitd Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-6.2.0-26-generic linux-headers-6.2.0-36-generic linux-headers-6.5.0-14-generic linux-hwe-6.2-headers-6.2.0-26 linux-hwe-6.2-headers-6.2.0-36 linux-hwe-6.5-headers-6.5.0-14 linux-image-6.2.0-26-generic linux-image-6.2.0-36-generic linux-image-6.5.0-14-generic linux-modules-6.2.0-26-generic linux-modules-6.2.0-36-generic linux-modules-6.5.0-14-generic linux-modules-extra-6.2.0-26-generic linux-modules-extra-6.2.0-36-generic linux-modules-extra-6.5.0-14-generic Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libduktape207 libgcrypt20 libglib2.0-0 libglib2.0-bin libnss-systemd libpam-systemd libsystemd-shared libsystemd0 libudev1 libzstd1 locales systemd systemd-dev systemd-oomd systemd-resolved systemd-sysv systemd-timesyncd udev Suggested packages: glibc-doc rng-tools low-memory-monitor polkitd-pkla systemd-container systemd-homed systemd-userdbd systemd-boot libqrencode4 libtss2-rc0 Recommended packages: libnss-nis libnss-nisplus The following NEW packages will be installed: libduktape207 libsystemd-shared systemd-dev systemd-resolved The following packages will be upgraded: gir1.2-polkit-1.0 libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libgcrypt20 libglib2.0-0 libglib2.0-bin libnss-systemd libpam-systemd libpolkit-agent-1-0 libpolkit-gobject-1-0 libsystemd0 libudev1 libzstd1 locales pkexec policykit-1 polkitd systemd systemd-oomd systemd-sysv systemd-timesyncd udev 26 upgraded, 4 newly installed, 0 to remove and 1407 not upgraded. Need to get 34.9 MB of archives. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: polkitd 124-1 ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail Date: Thu Feb 22 08:46:48 2024 ErrorMessage: installed polkitd package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-11-02 (112 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: policykit-1 Title: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2054716/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054716] Re: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1
So the call of: systemd-tmpfiles --create || : in systemd.postinst is an Ubuntu delta from Debian, which was originally introduced in to fix bug 1748147. If a package just lets debhelper generate its systemd-tmpfiles and systemd-sysusers calls (dh_installtmpfiles and dh_installsysusers), then each package's postinst will call systemd-tmpfiles and systemd-sysusers such that *only* configurations shipped by the package are processed. >From a quick investigation, it seems that we might not need the fix for bug 1748147 any longer (calling systemd-tmpfiles --create var.conf after systemd-tmpfiles --create 00rsyslog.conf does not undo the syslog changes). Hence, dropping this call from systemd.postinst might be the right fix. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/2054716 Title: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1 Status in policykit-1 package in Ubuntu: Confirmed Bug description: I was working on recreating bug 2054319 and did so by modifying my /etc/apt/sources.list file from jammy to noble and installing polkit and all its dependencies. bdmurray@clean-jammy-amd64:~$ sudo apt-get install gir1.2-polkit-1.0 libpolkit-agent-1-0:amd64 libpolkit-gobject-1-0:amd64 pkexec policykit-1 polkitd Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-6.2.0-26-generic linux-headers-6.2.0-36-generic linux-headers-6.5.0-14-generic linux-hwe-6.2-headers-6.2.0-26 linux-hwe-6.2-headers-6.2.0-36 linux-hwe-6.5-headers-6.5.0-14 linux-image-6.2.0-26-generic linux-image-6.2.0-36-generic linux-image-6.5.0-14-generic linux-modules-6.2.0-26-generic linux-modules-6.2.0-36-generic linux-modules-6.5.0-14-generic linux-modules-extra-6.2.0-26-generic linux-modules-extra-6.2.0-36-generic linux-modules-extra-6.5.0-14-generic Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libduktape207 libgcrypt20 libglib2.0-0 libglib2.0-bin libnss-systemd libpam-systemd libsystemd-shared libsystemd0 libudev1 libzstd1 locales systemd systemd-dev systemd-oomd systemd-resolved systemd-sysv systemd-timesyncd udev Suggested packages: glibc-doc rng-tools low-memory-monitor polkitd-pkla systemd-container systemd-homed systemd-userdbd systemd-boot libqrencode4 libtss2-rc0 Recommended packages: libnss-nis libnss-nisplus The following NEW packages will be installed: libduktape207 libsystemd-shared systemd-dev systemd-resolved The following packages will be upgraded: gir1.2-polkit-1.0 libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libgcrypt20 libglib2.0-0 libglib2.0-bin libnss-systemd libpam-systemd libpolkit-agent-1-0 libpolkit-gobject-1-0 libsystemd0 libudev1 libzstd1 locales pkexec policykit-1 polkitd systemd systemd-oomd systemd-sysv systemd-timesyncd udev 26 upgraded, 4 newly installed, 0 to remove and 1407 not upgraded. Need to get 34.9 MB of archives. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: polkitd 124-1 ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail Date: Thu Feb 22 08:46:48 2024 ErrorMessage: installed polkitd package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-11-02 (112 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: policykit-1 Title: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2054716/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2047447] Re: No valid source.list found while upgrading from mantic to noble
Xavier - Copying those sources as-is into /etc/apt/sources.list.d/ubuntu.sources works fine for me. Did you have any other sources? Any other /etc/apt/sources.list.d/*.sources? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in python-apt source package in Mantic: New Status in ubuntu-release-upgrader source package in Mantic: New Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information No valid sources.list entry found While scanning your repository information no entry about mantic could be found. An upgrade might not succeed. Do you want to continue anyway? Continue [yN] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2047447] Re: No valid source.list found while upgrading from mantic to noble
Xavier - do you happen to have the /etc/apt/sources.list.d/ubuntu.sources that was on your machine for the failed upgrade attempt? ** Also affects: python-apt (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: ubuntu-release-upgrader (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: python-apt (Ubuntu Mantic) Importance: Undecided => High ** Changed in: ubuntu-release-upgrader (Ubuntu Mantic) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in python-apt source package in Mantic: New Status in ubuntu-release-upgrader source package in Mantic: New Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information No valid sources.list entry found While scanning your repository information no entry about mantic could be found. An upgrade might not succeed. Do you want to continue anyway? Continue [yN] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2047447] Re: No valid source.list found while upgrading from mantic to noble
This appears to be a bug in python-apt. It fails to parse .sources files which contain a comment paragraph which is not connect to a source stanza (I think). I.e., this first scenario is fine: root@mantic:~# cat /etc/apt/sources.list.d/ubuntu.sources # This comment is OK. Types: deb URIs: http://archive.ubuntu.com/ubuntu Suites: mantic mantic-updates Components: main universe Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg Types: deb URIs: http://security.ubuntu.com/ubuntu Suites: mantic-security Components: main universe Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg root@mantic:~# python3 Python 3.11.6 (main, Oct 8 2023, 05:06:43) [GCC 13.2.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> from aptsources.sourceslist import SourcesList >>> for e in SourcesList(deb822=True): ... print(str(e)) ... # This comment is OK. Types: deb URIs: http://archive.ubuntu.com/ubuntu Suites: mantic mantic-updates Components: main universe Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg Types: deb URIs: http://security.ubuntu.com/ubuntu Suites: mantic-security Components: main universe Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg >>> As opposed to this, which fails: root@mantic:~# cat /etc/apt/sources.list.d/ubuntu.sources # This comment is NOT OK. # This comment is OK. Types: deb URIs: http://archive.ubuntu.com/ubuntu Suites: mantic mantic-updates Components: main universe Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg Types: deb URIs: http://security.ubuntu.com/ubuntu Suites: mantic-security Components: main universe Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg root@mantic:~# python3 Python 3.11.6 (main, Oct 8 2023, 05:06:43) [GCC 13.2.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> from aptsources.sourceslist import SourcesList >>> for e in SourcesList(deb822=True): ... print(str(e)) ... WARNING:root:could not open file '/etc/apt/sources.list.d/ubuntu.sources': Unable to parse section data >>> -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in python-apt source package in Mantic: New Status in ubuntu-release-upgrader source package in Mantic: New Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information No valid sources.list entry found While scanning your repository information no entry about mantic could be found. An
[Touch-packages] [Bug 2047447] Re: No valid source.list found while upgrading from mantic to noble
** Also affects: python-apt (Ubuntu) Importance: Undecided Status: New ** Changed in: python-apt (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information No valid sources.list entry found While scanning your repository information no entry about mantic could be found. An upgrade might not succeed. Do you want to continue anyway? Continue [yN] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055806] Re: sshd.service ssh.socket systemd-tmpfiles-setup:Before= - Missing privilege separation directory: /run/sshd
** Changed in: openssh (Ubuntu) Status: Triaged => Fix Committed -- 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/2055806 Title: sshd.service ssh.socket systemd-tmpfiles-setup:Before= - Missing privilege separation directory: /run/sshd Status in openssh package in Ubuntu: Fix Committed Status in openssh source package in Mantic: New Bug description: Symptom: ssh.service is not running and not accepting new SSH connections and returns socket closed error upon attempted connection. ssh.service shows a failed with error message "Missing privilege separation directory: /run/sshd". The following line is needed in the SystemD Unit configuration of the ssh.service file for the openssh-server package to fix what appears to be a race condition when ssh.service is sometimes started before systemd-tmpfiles-setup.service is finished processing the file in /usr/lib/tmpfiles.d/openssh.server.conf that is required to create the /run/sshd directory that is required by ssh.service to start property. There might be more depth or an alternative reason to why /run/sshd/ still didn't exist after using ```systemctl reset-failed ssh.service```. So more investigation is needed by someone with more background in systemd-tmpfiles-setup.service and openssh-server package after it when to socket activation. = Error Messages = ``` $journalctl -u ssh.service -b-1 Mar 02 21:30:56 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server... Mar 02 21:30:56 server sshd[1271]: Missing privilege separation directory: /run/sshd Mar 02 21:30:56 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION Mar 02 21:30:56 server systemd[1]: ssh.service: Failed with result 'exit-code'. Mar 02 21:30:56 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:56 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 1. Mar 02 21:30:56 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:56 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server... Mar 02 21:30:56 server sshd[1369]: Missing privilege separation directory: /run/sshd Mar 02 21:30:56 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION Mar 02 21:30:56 server systemd[1]: ssh.service: Failed with result 'exit-code'. Mar 02 21:30:56 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:56 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 2. Mar 02 21:30:56 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:56 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server... Mar 02 21:30:56 server sshd[1454]: Missing privilege separation directory: /run/sshd Mar 02 21:30:56 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION Mar 02 21:30:56 server systemd[1]: ssh.service: Failed with result 'exit-code'. Mar 02 21:30:56 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:57 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 3. Mar 02 21:30:57 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:57 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server... Mar 02 21:30:57 server sshd[1465]: Missing privilege separation directory: /run/sshd Mar 02 21:30:57 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION Mar 02 21:30:57 server systemd[1]: ssh.service: Failed with result 'exit-code'. Mar 02 21:30:57 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:57 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 4. Mar 02 21:30:57 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:57 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server... Mar 02 21:30:57 server sshd[1475]: Missing privilege separation directory: /run/sshd Mar 02 21:30:57 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION Mar 02 21:30:57 server systemd[1]: ssh.service: Failed with result 'exit-code'. Mar 02 21:30:57 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:57 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 5. Mar 02 21:30:57 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:57 server systemd[1]: ssh.service: Start request repeated too quickly. Mar 02 21:30:57 server systemd[1]: ssh.service: Failed with result 'exit-code'.
[Touch-packages] [Bug 2055720] Re: Edubuntu upgrade removed universe repo mantic -> noble
** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2055720 Title: Edubuntu upgrade removed universe repo mantic -> noble Status in software-properties package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Fix Committed Bug description: Upon upgrade from mantic to noble, my bare metal Edubuntu install removed the Universe repo from the installation and, therefore, did not upgrade any Edubuntu-specific packages. I suspect this was caused by the apt DEB-822 upgrade to the repo and not detecting the universe repo as required by the Edubuntu installation. As Edubuntu looks identical to Ubuntu Desktop in terms of installation on the surface due to it also being a GNOME desktop, I suspect an assumption may have been derived from this. Additionally, simply trying `add-apt-repository universe` was ineffective, so that might need some work as well. Will attach logs if I can find them, but please do advise what logs you need. --- ProblemType: Bug ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2023-03-04 (366 days ago) InstallationMedia: Edubuntu 23.04 "Lunar Lobster" - Alpha amd64 Binary-1 (20230304) NonfreeKernelModules: nvidia_modeset nvidia Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8 Tags: noble wayland-session dist-upgrade Uname: Linux 6.5.0-21-generic x86_64 UpgradeStatus: Upgraded to noble on 2024-03-01 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2055720/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055720] Re: Edubuntu upgrade removed universe repo mantic -> noble
As a quick fix, we will just make sure that universe and multiverse are included in the default sources generated when this case is encountered. That should be the case either way. I am still not sure why you hit this case, but according to the log it didn't look like you had other sources enabled somehow. I marked software-properties invalid since this is pertaining to u-r-u. ** Tags removed: rls-nn-incoming ** Tags added: foundations-todo ** Changed in: ubuntu-release-upgrader (Ubuntu) Assignee: (unassigned) => Nick Rosbrook (enr0n) ** Changed in: software-properties (Ubuntu) Status: New => Invalid ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2055720 Title: Edubuntu upgrade removed universe repo mantic -> noble Status in software-properties package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: Upon upgrade from mantic to noble, my bare metal Edubuntu install removed the Universe repo from the installation and, therefore, did not upgrade any Edubuntu-specific packages. I suspect this was caused by the apt DEB-822 upgrade to the repo and not detecting the universe repo as required by the Edubuntu installation. As Edubuntu looks identical to Ubuntu Desktop in terms of installation on the surface due to it also being a GNOME desktop, I suspect an assumption may have been derived from this. Additionally, simply trying `add-apt-repository universe` was ineffective, so that might need some work as well. Will attach logs if I can find them, but please do advise what logs you need. --- ProblemType: Bug ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2023-03-04 (366 days ago) InstallationMedia: Edubuntu 23.04 "Lunar Lobster" - Alpha amd64 Binary-1 (20230304) NonfreeKernelModules: nvidia_modeset nvidia Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8 Tags: noble wayland-session dist-upgrade Uname: Linux 6.5.0-21-generic x86_64 UpgradeStatus: Upgraded to noble on 2024-03-01 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2055720/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055806] Re: sshd.service ssh.socket systemd-tmpfiles-setup:Before= - Missing privilege separation directory: /run/sshd
** Also affects: openssh (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: openssh (Ubuntu Mantic) Importance: Undecided => Low ** Changed in: openssh (Ubuntu) Status: New => Triaged ** Changed in: openssh (Ubuntu) Importance: Undecided => High ** Tags removed: rls-nn-incoming ** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2055806 Title: sshd.service ssh.socket systemd-tmpfiles-setup:Before= - Missing privilege separation directory: /run/sshd Status in openssh package in Ubuntu: Triaged Status in openssh source package in Mantic: New Bug description: Symptom: ssh.service is not running and not accepting new SSH connections and returns socket closed error upon attempted connection. ssh.service shows a failed with error message "Missing privilege separation directory: /run/sshd". The following line is needed in the SystemD Unit configuration of the ssh.service file for the openssh-server package to fix what appears to be a race condition when ssh.service is sometimes started before systemd-tmpfiles-setup.service is finished processing the file in /usr/lib/tmpfiles.d/openssh.server.conf that is required to create the /run/sshd directory that is required by ssh.service to start property. There might be more depth or an alternative reason to why /run/sshd/ still didn't exist after using ```systemctl reset-failed ssh.service```. So more investigation is needed by someone with more background in systemd-tmpfiles-setup.service and openssh-server package after it when to socket activation. = Error Messages = ``` $journalctl -u ssh.service -b-1 Mar 02 21:30:56 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server... Mar 02 21:30:56 server sshd[1271]: Missing privilege separation directory: /run/sshd Mar 02 21:30:56 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION Mar 02 21:30:56 server systemd[1]: ssh.service: Failed with result 'exit-code'. Mar 02 21:30:56 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:56 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 1. Mar 02 21:30:56 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:56 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server... Mar 02 21:30:56 server sshd[1369]: Missing privilege separation directory: /run/sshd Mar 02 21:30:56 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION Mar 02 21:30:56 server systemd[1]: ssh.service: Failed with result 'exit-code'. Mar 02 21:30:56 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:56 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 2. Mar 02 21:30:56 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:56 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server... Mar 02 21:30:56 server sshd[1454]: Missing privilege separation directory: /run/sshd Mar 02 21:30:56 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION Mar 02 21:30:56 server systemd[1]: ssh.service: Failed with result 'exit-code'. Mar 02 21:30:56 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:57 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 3. Mar 02 21:30:57 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:57 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server... Mar 02 21:30:57 server sshd[1465]: Missing privilege separation directory: /run/sshd Mar 02 21:30:57 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION Mar 02 21:30:57 server systemd[1]: ssh.service: Failed with result 'exit-code'. Mar 02 21:30:57 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:57 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 4. Mar 02 21:30:57 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:57 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server... Mar 02 21:30:57 server sshd[1475]: Missing privilege separation directory: /run/sshd Mar 02 21:30:57 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION Mar 02 21:30:57 server systemd[1]: ssh.service: Failed with result 'exit-code'. Mar 02 21:30:57 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:57 server systemd[1]: ssh.service: Scheduled restart job, restart
[Touch-packages] [Bug 2056151] Re: systemd should create empty /etc/$program.conf.d directories
** Changed in: systemd (Ubuntu) Importance: Undecided => Wishlist ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2056151 Title: systemd should create empty /etc/$program.conf.d directories Status in systemd package in Ubuntu: Confirmed Bug description: As a header to all .conf files in systemd there's a comment saying # Entries in this file show the compile time defaults. Local configuration # should be created by either modifying this file (or a copy of it placed in # /etc/ if the original file is shipped in /usr/), or by creating "drop-ins" in # the /etc/systemd/user.conf.d/ directory. The latter is generally recommended. (with variations on the actual directory name, of course) Since the .d method is the recommended way, the systemd package should create the empty directory as a way to reduce friction and make it more even more discoverable to the user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2056151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055895] Re: cp -n prints warning on stderr
The usage of cp -n that causes this is actually in /usr/share/initramfs- tools/hooks/klibc-utils, which is already fixed in -proposed: https://launchpad.net/ubuntu/+source/klibc/2.0.13-4. ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid ** Changed in: coreutils (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2055895 Title: cp -n prints warning on stderr Status in coreutils package in Ubuntu: Triaged Status in initramfs-tools package in Ubuntu: Invalid Bug description: With coreutils, cp -n will start printing a warning on stderr: cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead See the debian bug for some more context: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1058752 This change may cause issues in other packages autopkgtest (given the stderr output) or elsewhere, so this bug is used to track such cases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2055895/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055720] Re: Edubuntu upgrade removed universe repo mantic -> noble
Thanks. A few more things: 1. Were you still using /etc/apt/sources.list before the upgrade? Or were you an early deb822 adopter (i.e. already using /etc/apt/sources.list.d/ubuntu.sources)? 2. Do you have /etc/apt/sources.list.distUpgrade? If so, can you share that please? 3. Can you please attach the resulting /etc/apt/sources.list.d/ubuntu.sources? According to the log, you have no valid mirrors configured, so u-r-u goes ahead and generates some default sources (which does not include universe -- that is a bug in itself IMO): 2024-03-01 09:25:39,054 DEBUG updateSourcesList() 2024-03-01 09:25:49,077 DEBUG rewriteSourcesList() with mirror_check 2024-03-01 09:25:49,077 WARNING mirror check skipped, *overriden* via config 2024-03-01 09:25:49,078 DEBUG examining: 'deb [arch=amd64,arm64,armhf] http://packages.microsoft.com/repos/code stable main' 2024-03-01 09:25:49,078 ERROR No valid mirror found 2024-03-01 09:26:04,429 DEBUG rewriteSourcesList() 2024-03-01 09:26:04,430 WARNING mirror check skipped, *overriden* via config 2024-03-01 09:26:04,430 DEBUG examining: 'deb [arch=amd64,arm64,armhf] http://packages.microsoft.com/repos/code stable main' 2024-03-01 09:26:12,205 INFO Generated new default sources.list What's odd is that it appears that u-r-u only looked at /etc/apt/sources.list.d/vscode.list. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2055720 Title: Edubuntu upgrade removed universe repo mantic -> noble Status in software-properties package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: Upon upgrade from mantic to noble, my bare metal Edubuntu install removed the Universe repo from the installation and, therefore, did not upgrade any Edubuntu-specific packages. I suspect this was caused by the apt DEB-822 upgrade to the repo and not detecting the universe repo as required by the Edubuntu installation. As Edubuntu looks identical to Ubuntu Desktop in terms of installation on the surface due to it also being a GNOME desktop, I suspect an assumption may have been derived from this. Additionally, simply trying `add-apt-repository universe` was ineffective, so that might need some work as well. Will attach logs if I can find them, but please do advise what logs you need. --- ProblemType: Bug ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2023-03-04 (366 days ago) InstallationMedia: Edubuntu 23.04 "Lunar Lobster" - Alpha amd64 Binary-1 (20230304) NonfreeKernelModules: nvidia_modeset nvidia Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8 Tags: noble wayland-session dist-upgrade Uname: Linux 6.5.0-21-generic x86_64 UpgradeStatus: Upgraded to noble on 2024-03-01 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2055720/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055895] Re: cp -n prints warning on stderr
This affects initramfs-tools autopkgtest[1]: 4856s autopkgtest [23:01:25]: test qemu-net: ---] 4857s autopkgtest [23:01:26]: test qemu-net: - - - - - - - - - - results - - - - - - - - - - 4857s qemu-net FAIL stderr: cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s autopkgtest [23:01:26]: test qemu-net: - - - - - - - - - - stderr - - - - - - - - - - 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead 4857s cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead [1] https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- noble/noble/arm64/i/initramfs-tools/20240301_230142_4f7c6@/log.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2055895 Title: cp -n prints warning on stderr Status in coreutils package in Ubuntu: New Status in initramfs-tools package in Ubuntu: New Bug description: With coreutils, cp -n will start printing a warning on stderr: cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead See the debian bug for some more context: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1058752 This change may cause issues in other packages autopkgtest (given the stderr output) or elsewhere, so this bug is used to track such cases. To manage
[Touch-packages] [Bug 2055895] [NEW] cp -n prints warning on stderr
Public bug reported: With coreutils, cp -n will start printing a warning on stderr: cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead See the debian bug for some more context: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1058752 This change may cause issues in other packages autopkgtest (given the stderr output) or elsewhere, so this bug is used to track such cases. ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2055895 Title: cp -n prints warning on stderr Status in coreutils package in Ubuntu: New Status in initramfs-tools package in Ubuntu: New Bug description: With coreutils, cp -n will start printing a warning on stderr: cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead See the debian bug for some more context: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1058752 This change may cause issues in other packages autopkgtest (given the stderr output) or elsewhere, so this bug is used to track such cases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2055895/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055806] Re: sshd.service ssh.socket systemd-tmpfiles-setup:Before= - Missing privilege separation directory: /run/sshd
I think we originally broke this out into a tmpfile since the openssh- server.postinst was calling sshd -G to parse config. However, with the sshd-socket-generator approach, we don't call sshd directly anymore, so we could probably just go back to setting RuntimeDirectory=/run/sshd in ssh.service. -- 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/2055806 Title: sshd.service ssh.socket systemd-tmpfiles-setup:Before= - Missing privilege separation directory: /run/sshd Status in openssh package in Ubuntu: New Bug description: Symptom: ssh.service is not running and not accepting new SSH connections and returns socket closed error upon attempted connection. ssh.service shows a failed with error message "Missing privilege separation directory: /run/sshd". The following line is needed in the SystemD Unit configuration of the ssh.service file for the openssh-server package to fix what appears to be a race condition when ssh.service is sometimes started before systemd-tmpfiles-setup.service is finished processing the file in /usr/lib/tmpfiles.d/openssh.server.conf that is required to create the /run/sshd directory that is required by ssh.service to start property. There might be more depth or an alternative reason to why /run/sshd/ still didn't exist after using ```systemctl reset-failed ssh.service```. So more investigation is needed by someone with more background in systemd-tmpfiles-setup.service and openssh-server package after it when to socket activation. = Error Messages = ``` $journalctl -u ssh.service -b-1 Mar 02 21:30:56 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server... Mar 02 21:30:56 server sshd[1271]: Missing privilege separation directory: /run/sshd Mar 02 21:30:56 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION Mar 02 21:30:56 server systemd[1]: ssh.service: Failed with result 'exit-code'. Mar 02 21:30:56 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:56 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 1. Mar 02 21:30:56 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:56 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server... Mar 02 21:30:56 server sshd[1369]: Missing privilege separation directory: /run/sshd Mar 02 21:30:56 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION Mar 02 21:30:56 server systemd[1]: ssh.service: Failed with result 'exit-code'. Mar 02 21:30:56 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:56 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 2. Mar 02 21:30:56 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:56 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server... Mar 02 21:30:56 server sshd[1454]: Missing privilege separation directory: /run/sshd Mar 02 21:30:56 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION Mar 02 21:30:56 server systemd[1]: ssh.service: Failed with result 'exit-code'. Mar 02 21:30:56 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:57 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 3. Mar 02 21:30:57 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:57 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server... Mar 02 21:30:57 server sshd[1465]: Missing privilege separation directory: /run/sshd Mar 02 21:30:57 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION Mar 02 21:30:57 server systemd[1]: ssh.service: Failed with result 'exit-code'. Mar 02 21:30:57 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:57 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 4. Mar 02 21:30:57 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:57 server systemd[1]: Starting ssh.service - OpenBSD Secure Shell server... Mar 02 21:30:57 server sshd[1475]: Missing privilege separation directory: /run/sshd Mar 02 21:30:57 server systemd[1]: ssh.service: Control process exited, code=exited, status=255/EXCEPTION Mar 02 21:30:57 server systemd[1]: ssh.service: Failed with result 'exit-code'. Mar 02 21:30:57 server systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server. Mar 02 21:30:57 server systemd[1]: ssh.service: Scheduled restart job, restart counter is at 5. Mar 02 21:30:57 server systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server. Mar
[Touch-packages] [Bug 2055720] Re: Edubuntu upgrade removed universe repo mantic -> noble
Can you please run apport-collect 2055720? There are some ubuntu- release-upgrader logs that would be helpful to have. This will also attach your apt sources etc. which make things easier to understand. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2055720 Title: Edubuntu upgrade removed universe repo mantic -> noble Status in software-properties package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: Incomplete Bug description: Upon upgrade from mantic to noble, my bare metal Edubuntu install removed the Universe repo from the installation and, therefore, did not upgrade any Edubuntu-specific packages. I suspect this was caused by the apt DEB-822 upgrade to the repo and not detecting the universe repo as required by the Edubuntu installation. As Edubuntu looks identical to Ubuntu Desktop in terms of installation on the surface due to it also being a GNOME desktop, I suspect an assumption may have been derived from this. Additionally, simply trying `add-apt-repository universe` was ineffective, so that might need some work as well. Will attach logs if I can find them, but please do advise what logs you need. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2055720/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2019026] Re: systemd /tmp cleaning is suboptimal
I have uploaded a change to add the 30d cleanup age. ** Changed in: systemd (Ubuntu Noble) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2019026 Title: systemd /tmp cleaning is suboptimal Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Noble: Fix Committed Bug description: Historically on Debian and Ubuntu, before systemd, the default handling of /tmp was to periodically, and at boot, remove all files/directories older than 30 days; and leave other contents alone. With the move to systemd, the "default" (really, hard-coded in /usr/lib/tmpfiles.d/tmp.conf) is to not clean /tmp periodically, but at boot to remove all contents. This is suboptimal for two reasons. By cleaning /tmp *only* at boot, if a system makes heavy use of /tmp and has lots of inodes under it, possibly due to failures of some process to clean up after itself, at boot the system will be unavailable for an unnecessarily long time while these files are removed. By cleaning *all* files under /tmp, this makes a reboot an Event where in-progress files may be unnecessarily lost. While the FHS does not *guarantee* that files under /tmp will persist across boot (because /tmp may be a tmpfs), it also does not *require* that /tmp be cleared on boot. Although data stored in /tmp may be deleted in a site-specific manner, it is recommended that files and directories located in /tmp be deleted whenever the system is booted. FHS added this recommendation on the basis of historical precedent and common practice, but did not make it a requirement because system administration is not within the scope of this standard. I therefore believe the correct value for /usr/lib/tmpfiles.d/tmp.conf to restore past behavior is 'd /tmp 1777 root root 30d'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2019026/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2019026] Re: systemd /tmp cleaning is suboptimal
** Changed in: systemd (Ubuntu Noble) Status: Confirmed => Triaged ** Changed in: systemd (Ubuntu Noble) Assignee: (unassigned) => Nick Rosbrook (enr0n) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2019026 Title: systemd /tmp cleaning is suboptimal Status in systemd package in Ubuntu: Triaged Status in systemd source package in Noble: Triaged Bug description: Historically on Debian and Ubuntu, before systemd, the default handling of /tmp was to periodically, and at boot, remove all files/directories older than 30 days; and leave other contents alone. With the move to systemd, the "default" (really, hard-coded in /usr/lib/tmpfiles.d/tmp.conf) is to not clean /tmp periodically, but at boot to remove all contents. This is suboptimal for two reasons. By cleaning /tmp *only* at boot, if a system makes heavy use of /tmp and has lots of inodes under it, possibly due to failures of some process to clean up after itself, at boot the system will be unavailable for an unnecessarily long time while these files are removed. By cleaning *all* files under /tmp, this makes a reboot an Event where in-progress files may be unnecessarily lost. While the FHS does not *guarantee* that files under /tmp will persist across boot (because /tmp may be a tmpfs), it also does not *require* that /tmp be cleared on boot. Although data stored in /tmp may be deleted in a site-specific manner, it is recommended that files and directories located in /tmp be deleted whenever the system is booted. FHS added this recommendation on the basis of historical precedent and common practice, but did not make it a requirement because system administration is not within the scope of this standard. I therefore believe the correct value for /usr/lib/tmpfiles.d/tmp.conf to restore past behavior is 'd /tmp 1777 root root 30d'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2019026/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055065] Re: Please merge kbd 2.6.4-2 (main) from Debian unstable
** Changed in: kbd (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/2055065 Title: Please merge kbd 2.6.4-2 (main) from Debian unstable Status in kbd package in Ubuntu: Fix Committed Bug description: debian: kbd| 2.0.4-4 | oldoldstable | source, amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x kbd| 2.3.0-3 | oldstable | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x kbd| 2.5.1-1 | stable | source kbd| 2.5.1-1+b1| stable | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x kbd| 2.6.4-2 | testing| source, amd64, arm64, armel, armhf, i386, mips64el, ppc64el, s390x kbd| 2.6.4-2 | unstable | source, amd64, arm64, armel, armhf, i386, mips64el, ppc64el, riscv64, s390x kbd| 2.6.4-2 | unstable-debug | source ubuntu: kbd | 1.15.5-1ubuntu1 | trusty | source, amd64, arm64, armhf, i386, powerpc, ppc64el kbd | 1.15.5-1ubuntu4 | xenial | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x kbd | 1.15.5-1ubuntu5 | xenial-updates | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x kbd | 2.0.4-2ubuntu1 | bionic | source, amd64, arm64, armhf, i386, ppc64el, s390x kbd | 2.0.4-4ubuntu2 | focal | source, amd64, arm64, armhf, ppc64el, riscv64, s390x kbd | 2.3.0-3ubuntu4 | jammy | source, amd64, arm64, armhf, ppc64el, riscv64, s390x kbd | 2.3.0-3ubuntu4.22.04 | jammy-updates | source, amd64, arm64, armhf, ppc64el, riscv64, s390x kbd | 2.5.1-1ubuntu1 | mantic | source, amd64, arm64, armhf, ppc64el, riscv64, s390x kbd | 2.5.1-1ubuntu1 | noble | source, amd64, arm64, armhf, ppc64el, riscv64, s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/2055065/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2036127] Re: Restarting `systemd-networkd` looses unmanaged bridged parents
Ah I'm sorry - KeepMaster= was not added until v250. I must have tested that on Noble. For jammy, I think the best solution is to add the snippet I suggested to your netplan config. Your opposition to it sounds mostly ideological. I'm sorry it's not ideal, but it seems like a valid workaround to me. -- 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/2036127 Title: Restarting `systemd-networkd` looses unmanaged bridged parents Status in systemd package in Ubuntu: Invalid Bug description: My home network comprises many VLANs managed by `systemd- networkd`/`netplan`. Those VLANs are then used as parent interfaces for LXD networks. Whenever `systemd-networkd` is restarted (i.e: post- update), my whole network breaks because all the unmanaged bridges lose their parent devices. Another way to see it is that `systemd- networkd` undoes the `master` setting of those VLAN devices. Here is a simplified reproducer: 1. Create a `vlan1` device $ lxc launch ubuntu:22.04 networkd-bug Creating networkd-bug Starting networkd-bug $ lxc file push - networkd-bug/etc/netplan/99-vlan1.yaml << EOF network: version: 2 vlans: vlan1: id: 1 link: eth0 EOF $ lxc exec networkd-bug -- netplan apply 2. Manually create a bridge and join `vlan1` to it $ lxc exec networkd-bug -- ip link add br0 type bridge $ lxc exec networkd-bug -- ip link set vlan1 master br0 $ lxc exec networkd-bug -- ip link 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: vlan1@eth0: mtu 1500 qdisc noqueue master br0 state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff 3: br0: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 42:b6:31:01:47:9a brd ff:ff:ff:ff:ff:ff 164: eth0@if165: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff link-netnsid 0 3. Restart `systemd-networkd` $ lxc exec networkd-bug -- systemctl restart systemd-networkd 4. Notice `vlan1` lost it's master config $ lxc exec networkd-bug -- ip link 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: vlan1@eth0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff 3: br0: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 42:b6:31:01:47:9a brd ff:ff:ff:ff:ff:ff 164: eth0@if165: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff link-netnsid 0 Ideally, `vlan1` should retain it's `master` setting and I wouldn't loose connectivity :) Additional information: # apt-cache policy systemd netplan.io iproute2 systemd: Installed: 249.11-0ubuntu3.9 Candidate: 249.11-0ubuntu3.9 Version table: *** 249.11-0ubuntu3.9 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3.7 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 249.11-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages netplan.io: Installed: 0.105-0ubuntu2~22.04.3 Candidate: 0.105-0ubuntu2~22.04.3 Version table: *** 0.105-0ubuntu2~22.04.3 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.104-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages iproute2: Installed: 5.15.0-1ubuntu2 Candidate: 5.15.0-1ubuntu2 Version table: *** 5.15.0-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status # lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 # uname -a Linux networkd-bug 6.2.0-32-generic #32~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 18 10:40:13 UTC 2 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036127/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055200] Re: tests-in-lxd is broken with latest autopkgtest version
Uploaded the fix to noble. ** Changed in: systemd (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2055200 Title: tests-in-lxd is broken with latest autopkgtest version Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Jammy: Triaged Status in systemd source package in Mantic: Won't Fix Bug description: With autopkgtest 5.32 being SRU'd to Jammy[1], `tests-in-lxd` breaks because it can't patch `autopkgtest-build-lxd` anymore. Please find a debdiff attached to fix that issue. [1]: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2051939 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2055200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055200] Re: tests-in-lxd is broken with latest autopkgtest version
** Tags added: systemd-sru-next -- 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/2055200 Title: tests-in-lxd is broken with latest autopkgtest version Status in systemd package in Ubuntu: Triaged Status in systemd source package in Jammy: Triaged Status in systemd source package in Mantic: Won't Fix Bug description: With autopkgtest 5.32 being SRU'd to Jammy[1], `tests-in-lxd` breaks because it can't patch `autopkgtest-build-lxd` anymore. Please find a debdiff attached to fix that issue. [1]: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2051939 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2055200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055200] Re: tests-in-lxd is broken with latest autopkgtest version
** Summary changed: - tests-in-lxd is broken on Jammy with latest autopkgtest version + tests-in-lxd is broken with latest autopkgtest version ** Also affects: systemd (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Mantic) Status: New => Won't Fix ** Changed in: systemd (Ubuntu Jammy) Status: New => Triaged ** Changed in: systemd (Ubuntu Jammy) Importance: Undecided => Low ** Changed in: systemd (Ubuntu) Status: New => Triaged ** Changed in: systemd (Ubuntu) Importance: Undecided => Medium -- 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/2055200 Title: tests-in-lxd is broken with latest autopkgtest version Status in systemd package in Ubuntu: Triaged Status in systemd source package in Jammy: Triaged Status in systemd source package in Mantic: Won't Fix Bug description: With autopkgtest 5.32 being SRU'd to Jammy[1], `tests-in-lxd` breaks because it can't patch `autopkgtest-build-lxd` anymore. Please find a debdiff attached to fix that issue. [1]: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2051939 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2055200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055180] Re: coreutils 9.4-3ubuntu1 FTBFS
** Changed in: coreutils (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2055180 Title: coreutils 9.4-3ubuntu1 FTBFS Status in coreutils package in Ubuntu: Fix Committed Bug description: The recent upload FTBFS due to a build-time test failure[1]: FAIL: tests/cp/cp-i === --- err4 2024-02-26 18:03:34.566066156 + +++ err_skip 2024-02-26 18:03:34.554065852 + @@ -1 +1 @@ -cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead +cp: not replacing 'd' FAIL tests/cp/cp-i.sh (exit status: 1) This appears related to a new Debian patch that we pulled in with the merge. [1] https://launchpadlibrarian.net/716215295/buildlog_ubuntu-noble- amd64.coreutils_9.4-3ubuntu1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2055180/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055180] Re: coreutils 9.4-3ubuntu1 FTBFS
** Changed in: coreutils (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2055180 Title: coreutils 9.4-3ubuntu1 FTBFS Status in coreutils package in Ubuntu: In Progress Bug description: The recent upload FTBFS due to a build-time test failure[1]: FAIL: tests/cp/cp-i === --- err4 2024-02-26 18:03:34.566066156 + +++ err_skip 2024-02-26 18:03:34.554065852 + @@ -1 +1 @@ -cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead +cp: not replacing 'd' FAIL tests/cp/cp-i.sh (exit status: 1) This appears related to a new Debian patch that we pulled in with the merge. [1] https://launchpadlibrarian.net/716215295/buildlog_ubuntu-noble- amd64.coreutils_9.4-3ubuntu1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2055180/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055180] [NEW] coreutils 9.4-3ubuntu1 FTBFS
Public bug reported: The recent upload FTBFS due to a build-time test failure[1]: FAIL: tests/cp/cp-i === --- err42024-02-26 18:03:34.566066156 + +++ err_skip2024-02-26 18:03:34.554065852 + @@ -1 +1 @@ -cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead +cp: not replacing 'd' FAIL tests/cp/cp-i.sh (exit status: 1) This appears related to a new Debian patch that we pulled in with the merge. [1] https://launchpadlibrarian.net/716215295/buildlog_ubuntu-noble- amd64.coreutils_9.4-3ubuntu1_BUILDING.txt.gz ** Affects: coreutils (Ubuntu) Importance: High Assignee: Nick Rosbrook (enr0n) Status: Confirmed ** Tags: update-excuse ** Changed in: coreutils (Ubuntu) Importance: Undecided => High ** Changed in: coreutils (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2055180 Title: coreutils 9.4-3ubuntu1 FTBFS Status in coreutils package in Ubuntu: Confirmed Bug description: The recent upload FTBFS due to a build-time test failure[1]: FAIL: tests/cp/cp-i === --- err4 2024-02-26 18:03:34.566066156 + +++ err_skip 2024-02-26 18:03:34.554065852 + @@ -1 +1 @@ -cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead +cp: not replacing 'd' FAIL tests/cp/cp-i.sh (exit status: 1) This appears related to a new Debian patch that we pulled in with the merge. [1] https://launchpadlibrarian.net/716215295/buildlog_ubuntu-noble- amd64.coreutils_9.4-3ubuntu1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2055180/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823171] Re: systemd-resolve hides DS records in explicit queries
** Changed in: systemd (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1823171 Title: systemd-resolve hides DS records in explicit queries Status in systemd package in Ubuntu: New Bug description: When querying for DS resource records on a DNSSEC signed domain using dig, the DS records are not shown when the system is using systemd- resolve. Run: dig +short DS ripe.net Expected: something like 40991 8 2 D8D3C88263D58930A8B5FE16427130AB84CA73A4988385B2F4B121A7 2E5299A6 Actual result: no output. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.15 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE Date: Thu Apr 4 14:14:06 2019 MachineType: MSI MS-7A70 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=/dev/mapper/system-slash ro SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.80 dmi.board.asset.tag: Default string dmi.board.name: B250M PRO-VDH (MS-7A70) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.80:bd07/03/2018:svnMSI:pnMS-7A70:pvr2.0:rvnMSI:rnB250MPRO-VDH(MS-7A70):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7A70 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823171/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2036127] Re: Restarting `systemd-networkd` looses unmanaged bridged parents
This path is wrong: /etc/systemd/network/99-netplan- vlan1.network.d/keep_master.conf. It should in fact be etc/systemd/network/10-netplan-vlan1.network.d/keep_master.conf. Did you restart systemd-networkd afterward? -- 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/2036127 Title: Restarting `systemd-networkd` looses unmanaged bridged parents Status in systemd package in Ubuntu: Invalid Bug description: My home network comprises many VLANs managed by `systemd- networkd`/`netplan`. Those VLANs are then used as parent interfaces for LXD networks. Whenever `systemd-networkd` is restarted (i.e: post- update), my whole network breaks because all the unmanaged bridges lose their parent devices. Another way to see it is that `systemd- networkd` undoes the `master` setting of those VLAN devices. Here is a simplified reproducer: 1. Create a `vlan1` device $ lxc launch ubuntu:22.04 networkd-bug Creating networkd-bug Starting networkd-bug $ lxc file push - networkd-bug/etc/netplan/99-vlan1.yaml << EOF network: version: 2 vlans: vlan1: id: 1 link: eth0 EOF $ lxc exec networkd-bug -- netplan apply 2. Manually create a bridge and join `vlan1` to it $ lxc exec networkd-bug -- ip link add br0 type bridge $ lxc exec networkd-bug -- ip link set vlan1 master br0 $ lxc exec networkd-bug -- ip link 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: vlan1@eth0: mtu 1500 qdisc noqueue master br0 state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff 3: br0: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 42:b6:31:01:47:9a brd ff:ff:ff:ff:ff:ff 164: eth0@if165: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff link-netnsid 0 3. Restart `systemd-networkd` $ lxc exec networkd-bug -- systemctl restart systemd-networkd 4. Notice `vlan1` lost it's master config $ lxc exec networkd-bug -- ip link 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: vlan1@eth0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff 3: br0: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 42:b6:31:01:47:9a brd ff:ff:ff:ff:ff:ff 164: eth0@if165: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff link-netnsid 0 Ideally, `vlan1` should retain it's `master` setting and I wouldn't loose connectivity :) Additional information: # apt-cache policy systemd netplan.io iproute2 systemd: Installed: 249.11-0ubuntu3.9 Candidate: 249.11-0ubuntu3.9 Version table: *** 249.11-0ubuntu3.9 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3.7 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 249.11-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages netplan.io: Installed: 0.105-0ubuntu2~22.04.3 Candidate: 0.105-0ubuntu2~22.04.3 Version table: *** 0.105-0ubuntu2~22.04.3 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.104-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages iproute2: Installed: 5.15.0-1ubuntu2 Candidate: 5.15.0-1ubuntu2 Version table: *** 5.15.0-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status # lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 # uname -a Linux networkd-bug 6.2.0-32-generic #32~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 18 10:40:13 UTC 2 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036127/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1949723] Re: systemd-resolved segfault in hashmap_iterate_entry
The mentioned fix in the upstream report has been in systemd since 2021. ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Changed in: systemd (Ubuntu Focal) Importance: Undecided => Low -- 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/1949723 Title: systemd-resolved segfault in hashmap_iterate_entry Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: New Bug description: installed libnss-resolve that put "resolve" in nsswitch.conf. $ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 $ dpkg -l systemd | grep systemd ii systemd245.4-4ubuntu3.13 amd64system and service manager $ grep ^hosts /etc/nsswitch.conf hosts: files libvirt mdns4_minimal resolve [NOTFOUND=return] dns mymachines systemd-resolved crashed once with segmentation fault. (gdb) bt #0 0x7f119c67693a in hashmap_iterate_entry (h=h@entry=0x706f746b73656465, i=i@entry=0x7ffc4ef515d0) at ../src/basic/hashmap.c:705 #1 0x7f119c6789d6 in internal_hashmap_iterate (h=0x706f746b73656465, i=i@entry=0x7ffc4ef515d0, value=value@entry=0x7ffc4ef515c8, key=key@entry=0x0) at ../src/basic/hashmap.c:714 #2 0x7f119c678a8b in set_iterate (s=, i=i@entry=0x7ffc4ef515d0, value=value@entry=0x7ffc4ef515c8) at ../src/basic/hashmap.c:735 #3 0x55ba5e0ea917 in dns_query_candidate_go (c=c@entry=0x55ba5f353180) at ../src/resolve/resolved-dns-query.c:152 #4 0x55ba5e0e9f0c in dns_query_candidate_notify (c=c@entry=0x55ba5f353180) at ../src/resolve/resolved-dns-query.c:312 #5 0x55ba5e0ea178 in dns_transaction_complete (t=0x55ba5f37a9d0, state=) at ../src/resolve/resolved-dns-transaction.c:351 #6 0x55ba5e0e27cd in dns_transaction_process_dnssec (t=t@entry=0x55ba5f37a9d0) at ../src/resolve/resolved-dns-transaction.c:838 #7 0x55ba5e0e3649 in dns_transaction_process_reply (t=t@entry=0x55ba5f37a9d0, p=p@entry=0x55ba5f39dce0) at ../src/resolve/resolved-dns-transaction.c:1210 #8 0x55ba5e0e40ab in on_dns_packet (s=, fd=, revents=, userdata=0x55ba5f37a9d0) at ../src/resolve/resolved-dns-transaction.c:1264 #9 0x7f119c5e6c77 in source_dispatch (s=s@entry=0x55ba5f346780) at ../src/libsystemd/sd-event/sd-event.c:3193 #10 0x7f119c5e6f11 in sd_event_dispatch (e=e@entry=0x55ba5f320430) at ../src/libsystemd/sd-event/sd-event.c:3634 #11 0x7f119c5e8948 in sd_event_run (e=e@entry=0x55ba5f320430, timeout=timeout@entry=18446744073709551615) at ../src/libsystemd/sd-event/sd-event.c:3692 #12 0x7f119c5e8b6f in sd_event_loop (e=0x55ba5f320430) at ../src/libsystemd/sd-event/sd-event.c:3714 #13 0x55ba5e0c326a in run (argv=, argc=) at ../src/resolve/resolved.c:84 #14 main (argc=, argv=) at ../src/resolve/resolved.c:91 This seems to have been reported upstream https://github.com/systemd/systemd/issues/16168 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1880839] Re: Clock skew on testbeds
** Changed in: systemd (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1880839 Title: Clock skew on testbeds Status in Auto Package Testing: New Status in systemd package in Ubuntu: Won't Fix Bug description: Clock stepped backward on a testbed: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest- groovy/groovy/amd64/b/boost1.71/20200501_151103_1e387@/log.gz ... context FAIL stderr: make[2]: Warning: File '/tmp/tmp.qPfGPM84a1/src/demo2.cpp' has modification time 0.52 s in the future autopkgtest [13:55:37]: test context: - - - - - - - - - - stderr - - - - - - - - - - make[2]: Warning: File '/tmp/tmp.qPfGPM84a1/src/demo2.cpp' has modification time 0.52 s in the future make[2]: warning: Clock skew detected. Your build may be incomplete. .. To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1880839/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
