[Touch-packages] [Bug 2081192] Re: Cannot change MemoryKSM in systemd units
Thanks for reporting this. I can reproduce as well. It appears this was fixed upstream in https://github.com/systemd/systemd/pull/31683. It should already be fixed in Oraculr, but we will backport this to Noble. ** Also affects: systemd (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Changed in: systemd (Ubuntu Noble) Status: New => Triaged ** Changed in: systemd (Ubuntu Noble) Assignee: (unassigned) => Nick Rosbrook (enr0n) ** Changed in: systemd (Ubuntu Noble) Importance: Undecided => Medium ** 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/2081192 Title: Cannot change MemoryKSM in systemd units Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Noble: Triaged Bug description: In one of my working unit (service), I try to toggle the MemoryKSM boolean setting. Using any of: MemoryKSM=yes MemoryKSM=on MemoryKSM=true MemoryKSM=1 Results in: Sep 19 16:16:56 systemd[1]: Started XXX.service - XXX service. Sep 19 16:16:56 (e_server)[4487]: XXX.service: Failed to set KSM: Invalid argument Sep 19 16:16:56 systemd[1]: XXX.service: Main process exited, code=exited, status=245/KSM Sep 19 16:16:56 systemd[1]: XXX.service: Failed with result 'exit-code'. The following lines allow the service to start: MemoryKSM="yes" MemoryKSM="on" MemoryKSM="true" MemoryKSM="1" but still, MemoryKSM stays off: # systemctl show XXX.service | grep MemoryKSM MemoryKSM=no KSM is activated in my running kernel: # cat /boot/config-$(uname -r) | grep KSM CONFIG_KSM=y Using prctl (libc6 2.39-0ubuntu8.3) to toggle KSM inside a running process also works. I can read and set the memory_merge switch. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd 255.4-1ubuntu8.4 ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12 Uname: Linux 6.8.0-45-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: server CloudID: openstack CloudName: openstack CloudPlatform: openstack CloudSerial: 20240612 CloudSubPlatform: metadata (http://169.254.169.254) Date: Thu Sep 19 16:06:51 2024 Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet Lsusb-t: /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 002: Dev 003, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: OpenStack Foundation OpenStack Nova ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-45-generic root=UUID=1c5e2fdc-a746-403d-9fc0-71af31bc9c19 ro console=tty1 console=ttyS0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnOpenStackFoundation:pnOpenStackNova:pvr26.2.3:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.family: Virtual Machine dmi.product.name: OpenStack Nova dmi.product.version: 26.2.3 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2081192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054761] Re: Dist upgrades from Jammy to Noble crash [Oh no! Something has gone wrong.]
I'm sorry to hear about your upgrade troubles. If you have logs from the the boot where the upgrade occurred, please open a different bug with those logs so that the root cause for the hang can be investigated. But, if you unplugged your machine during the upgrade because it was unresponsive, I am not surprised things were broken when you rebooted. That is different than being affected by this bug. -- 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/2054761 Title: Dist upgrades from Jammy to Noble crash [Oh no! Something has gone wrong.] Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in mutter source package in Noble: Invalid Status in systemd source package in Noble: Fix Released Bug description: [Impact] During upgrades from Jammy to Noble, systemd.postinst trys to reexec all running user managers. It does so using a feature that was not added until v250, and attempting this against a v249 daemon results in it being killed instead, which brings down all user sessions. Hence, during the upgrades, the user session is killed, and the system is left in a bad state. [Test Plan] Run an upgrade from Jammy to Noble on Ubuntu desktop. The upgrade should proceed normally (or at least not have the entire session killed by systemd.postinst). [Where problems could occur] The fix is to add a version guard against this logic in systemd.postinst. If the version string was wrong or typo'd, the fix would not work as expected. [Original Description] Feb 21 21:39:12 autopkgtest gnome-shell[17945]: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients' Feb 21 21:39:12 autopkgtest gnome-session-binary[17908]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5 Feb 21 21:39:12 autopkgtest gnome-shell[17959]: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients' Feb 21 21:39:12 autopkgtest gnome-session-binary[17908]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5 https://errors.ubuntu.com/problem/bf714caff944bed915a3c4321664107c65547d1f https://errors.ubuntu.com/problem/db8f7e3dfc79e658b9b2aa8c596b014ce4b9f217 https://errors.ubuntu.com/oops/af2e99fc-d101-11ee-8a58-fa163ec8ca8c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2054761/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2080257] Re: [WSL] systemd fails to upgrade on WSL1
It appears to be a known issue that WSL1 does not support F_OFD_SETLKW, which is what systemd is using here. I could add a fallback to use F_SETLKW instead, but according to [1], it sounds like the locking is just broken on WSL1? So the "fallback" would probably lead to even more issues. Do you get the same error in the "WSL2 and systemd disabled" case? I don't understand why disabling systemd would change anything related to the kernel. [1] https://github.com/Microsoft/WSL/issues/1927 ** Bug watch added: github.com/Microsoft/WSL/issues #1927 https://github.com/Microsoft/WSL/issues/1927 -- 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/2080257 Title: [WSL] systemd fails to upgrade on WSL1 Status in systemd package in Ubuntu: Confirmed Bug description: Original report: https://github.com/ubuntu/WSL/issues/493 On WSL with systemd disabled (wsl1 or wsl2 without systemd enabled), systemd fails to upgrade. # Test Case WSL1 1. Install Ubuntu 24.04 with WSL from a Windows shell wsl --install --enable-wsl1 ubuntu-24.04 or wsl --install ubuntu-24.04 wsl --set-version ubuntu-24.04 1 => Verify that 24.04 is using version 1 NAMESTATE VERSION Ubuntu-22.04Stopped 2 Ubuntu-24.04Running 1 2. Start the distro if it is not already running ubuntu2404.exe 3. In the distro run the following command: sudo apt install --reinstall systemd # Expected result systemd is reinstalled without any issue # Actual result systemd postinst script fails and the following error is displayed to the user: ``` root@drenec:~# apt install --reinstall systemd Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 2 not upgraded. Need to get 3470 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 systemd amd64 255.4-1ubuntu8.4 [3470 kB] Fetched 3470 kB in 1s (2816 kB/s) (Reading database ... 40771 files and directories currently installed.) Preparing to unpack .../systemd_255.4-1ubuntu8.4_amd64.deb ... Unpacking systemd (255.4-1ubuntu8.4) over (255.4-1ubuntu8.4) ... Setting up systemd (255.4-1ubuntu8.4) ... Failed to take /etc/passwd lock: Invalid argument dpkg: error processing package systemd (--configure): installed systemd package post-installation script subprocess returned error exit status 1 Processing triggers for dbus (1.14.10-4ubuntu4.1) ... Processing triggers for man-db (2.12.0-4build2) ... Errors were encountered while processing: systemd E: Sub-process /usr/bin/dpkg returned an error code (1) ``` There is no easy way to recover from the error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2080257/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2077159] Re: i40e interfaces renamed after upgrade from hwe-6.5
Re-adding a Linux task to see if anyone can confirm whether kernel
interface naming was changed between these two kernel versions.
--
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/2077159
Title:
i40e interfaces renamed after upgrade from hwe-6.5
Status in linux package in Ubuntu:
New
Status in netplan.io package in Ubuntu:
New
Status in systemd package in Ubuntu:
Incomplete
Bug description:
Server running Ubuntu 22.04.4 LTS
Interface names with linux-image-6.5.0-21-generic 6.5.0-21.21~22.04.1:
3: eno1: mtu 9100 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp102s0f0
4: eno5: mtu 1500 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp183s0f0
6: eno2: mtu 1500 qdisc mq master mgmt
state UP mode DEFAULT group default qlen 1000
altname enp102s0f1
7: eno6: mtu 1500 qdisc mq master mgmt
state DOWN mode DEFAULT group default qlen 1000
altname enp183s0f1
8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f2
9: eno7: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f2
10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f3
11: eno8: mtu 1500 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp183s0f3
Interface names with linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3:
3: eno5np0: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f0np0
4: eno1: mtu 9100 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altname enp102s0f0
5: enp101s0f1np1: mtu 9100 qdisc mq state
DOWN mode DEFAULT group default qlen 1000
6: eno2: mtu 1500 qdisc mq master mgmt
state UP mode DEFAULT group default qlen 1000
altname enp102s0f1
7: eno6np1: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f1np1
8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f2
9: eno7np2: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp183s0f2np2
10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
altname enp102s0f3
11: eno8np3: mtu 1500 qdisc noop state DOWN mode
DEFAULT group default qlen 1000
altname enp183s0f3np3
Expected result: Static network configuration via netplan keeps
working after the upgrade.
Actual result: Static network configuration is no longer applied for the
interface that changed their name.
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Aug 16 09:40 seq
crw-rw 1 root audio 116, 33 Aug 16 09:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5json:
{
"result": "skip"
}
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-12-04 (260 days ago)
InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release
amd64 (20230217.1)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Supermicro SYS-5019D-FN8TP
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-21-generic
root=/dev/mapper/system-root ro
ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-g
[Touch-packages] [Bug 2077159] Re: i40e interfaces renamed after upgrade from hwe-6.5
By default, the NamePolicy=[1] (as configured in /usr/lib/systemd/network/99-default.link) is: [Link] NamePolicy=keep kernel database onboard slot path This means that if the kernel claims to assign a predictable name, then that will take precedence over other policies, including the "onboard" policy, which appears to be the one you are expecting. So, maybe the previous kernel was just issuing ethX, which is not predictable, and "onboard" was the winning rename policy. It's also possible that something else is renaming the interface first, which means that the "keep" policy would take effect. Now, I think if you want to continue relying on the "onboard" policy, you should use a drop-in to give that policy higher priority. E.g.: $ mkdir -p /etc/systemd/network/99-default.link.d $ cat > /etc/systemd/network/99-default.link.d/name-policy.conf [Link] NamePolicy=onboard keep kernel database slot path I think that should fix your problem. [1] https://www.freedesktop.org/software/systemd/man/latest/systemd.link.html#NamePolicy= ** Changed in: systemd (Ubuntu) Status: New => Incomplete ** Also affects: linux (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/2077159 Title: i40e interfaces renamed after upgrade from hwe-6.5 Status in linux package in Ubuntu: New Status in netplan.io package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: Server running Ubuntu 22.04.4 LTS Interface names with linux-image-6.5.0-21-generic 6.5.0-21.21~22.04.1: 3: eno1: mtu 9100 qdisc mq state DOWN mode DEFAULT group default qlen 1000 altname enp102s0f0 4: eno5: mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f0 6: eno2: mtu 1500 qdisc mq master mgmt state UP mode DEFAULT group default qlen 1000 altname enp102s0f1 7: eno6: mtu 1500 qdisc mq master mgmt state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f1 8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp102s0f2 9: eno7: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f2 10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp102s0f3 11: eno8: mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f3 Interface names with linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3: 3: eno5np0: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f0np0 4: eno1: mtu 9100 qdisc mq state DOWN mode DEFAULT group default qlen 1000 altname enp102s0f0 5: enp101s0f1np1: mtu 9100 qdisc mq state DOWN mode DEFAULT group default qlen 1000 6: eno2: mtu 1500 qdisc mq master mgmt state UP mode DEFAULT group default qlen 1000 altname enp102s0f1 7: eno6np1: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f1np1 8: eno3: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp102s0f2 9: eno7np2: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f2np2 10: eno4: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp102s0f3 11: eno8np3: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 altname enp183s0f3np3 Expected result: Static network configuration via netplan keeps working after the upgrade. Actual result: Static network configuration is no longer applied for the interface that changed their name. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 16 09:40 seq crw-rw 1 root audio 116, 33 Aug 16 09:40 timer AplayDevices: Error: [Errno 2]
[Touch-packages] [Bug 2080257] Re: [WSL] systemd fails to upgrade on WSL1
This error is coming from systemd-sysusers in systemd.postinst. To isolate the failing call, can you share the output of: $ SYSTEMD_LOG_LEVEL=debug systemd-sysusers basic.conf systemd- journal.conf systemd-network.conf Looking at the code, this is either failing on an open() or flock(), so likely we are trying to use a flag that's not supported in WSL? ** 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/2080257 Title: [WSL] systemd fails to upgrade on WSL1 Status in systemd package in Ubuntu: Confirmed Bug description: Original report: https://github.com/ubuntu/WSL/issues/493 On WSL with systemd disabled (wsl1 or wsl2 without systemd enabled), systemd fails to upgrade. # Test Case WSL1 1. Install Ubuntu 24.04 with WSL from a Windows shell wsl --install --enable-wsl1 ubuntu-24.04 or wsl --install ubuntu-24.04 wsl --set-version ubuntu-24.04 1 => Verify that 24.04 is using version 1 NAMESTATE VERSION Ubuntu-22.04Stopped 2 Ubuntu-24.04Running 1 2. Start the distro if it is not already running ubuntu2404.exe 3. In the distro run the following command: sudo apt install --reinstall systemd # Expected result systemd is reinstalled without any issue # Actual result systemd postinst script fails and the following error is displayed to the user: ``` root@drenec:~# apt install --reinstall systemd Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 2 not upgraded. Need to get 3470 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 systemd amd64 255.4-1ubuntu8.4 [3470 kB] Fetched 3470 kB in 1s (2816 kB/s) (Reading database ... 40771 files and directories currently installed.) Preparing to unpack .../systemd_255.4-1ubuntu8.4_amd64.deb ... Unpacking systemd (255.4-1ubuntu8.4) over (255.4-1ubuntu8.4) ... Setting up systemd (255.4-1ubuntu8.4) ... Failed to take /etc/passwd lock: Invalid argument dpkg: error processing package systemd (--configure): installed systemd package post-installation script subprocess returned error exit status 1 Processing triggers for dbus (1.14.10-4ubuntu4.1) ... Processing triggers for man-db (2.12.0-4build2) ... Errors were encountered while processing: systemd E: Sub-process /usr/bin/dpkg returned an error code (1) ``` There is no easy way to recover from the error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2080257/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2077779] Re: PTP device symlink missing after running udevadm trigger command
I am tracking this for future SRUs, so unsubscribing sponsors. -- 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/209 Title: PTP device symlink missing after running udevadm trigger command Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Focal: Triaged Status in systemd source package in Jammy: Triaged Status in systemd source package in Noble: Triaged Status in systemd source package in Oracular: Fix Committed Bug description: [Impact] PTP device symlink creation rules are executed only when the udev action is 'add'. If the rules are reloaded and the udevadm trigger command is run to reapply changes, the symlink may be deleted. This can prevent the chronyd service from restarting properly. [Fix] Upstream has a patch to fix this issue. commit 6bd12be3fa7761f190e17efdbdbff4440da7528b Author: Chengen Du CommitDate: Thu Aug 15 15:38:46 2024 +0900 udev: Handle PTP device symlink properly on udev action 'change' PTP device symlink creation rules are currently executed only when the udev action is 'add'. If a user reloads the rules and runs the udevadm trigger command to reapply changes, the symlink may be deleted, which can prevent the chronyd service from restarting properly. Signed-off-by: Chengen Du [Test Plan] 1. Create a VM on Azure. 2. Run the `udevadm trigger` command. 3. Restart the chronyd service by running `systemctl restart chronyd`. 4. Verify that the service starts normally by running `systemctl status chronyd`. [Where problems could occur] The patch allows PTP device symlink creation rules to be executed when the udev action is 'change'. This update primarily affects services that rely on the PTP device symlink, such as chronyd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/209/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2080972] Re: /tmp as non-tmpfs doesn't get cleaned upon reboot
To be specific, the override I would suggest is: $ mkdir -p /etc/tmpfiles.d $ cat > /etc/tmpfiles.d/tmp.conf << EOF D /tmp 1777 root root 10d q /var/tmp 1777 root root 30d EOF In particular, this is flipping the 'q' to a 'D' for the /tmp line. -- 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/2080972 Title: /tmp as non-tmpfs doesn't get cleaned upon reboot Status in systemd package in Ubuntu: Invalid Bug description: On Oracular, it seems `/tmp` doesn't get cleaned on reboot, when the `/etc/systemd/system/tmp.mount` file is present. Reproducer: $ wget https://cloud-images.ubuntu.com/minimal/daily/oracular/20240913/oracular-minimal-cloudimg-amd64.img $ qemu-img resize oracular-minimal-cloudimg-amd64.img +20G $ cat >user-data
[Touch-packages] [Bug 2080972] Re: /tmp as non-tmpfs doesn't get cleaned upon reboot
This is expected behavior. Since /tmp is a tmpfs by default, the default /usr/lib/tmpfiles.d/tmp.conf is configured with a 10d cleanup age for /tmp, but it is *not* configured to clean /tmp at boot, because that is unnecessary for a tmpfs. If you want to clean /tmp at boot *and* have your tmp.mount override, you need to also override tmpfiles.d/tmp.conf with appropriate settings for /tmp and /var/tmp (because both of these are listed in the default tmp.conf). ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2080972 Title: /tmp as non-tmpfs doesn't get cleaned upon reboot Status in systemd package in Ubuntu: Invalid Bug description: On Oracular, it seems `/tmp` doesn't get cleaned on reboot, when the `/etc/systemd/system/tmp.mount` file is present. Reproducer: $ wget https://cloud-images.ubuntu.com/minimal/daily/oracular/20240913/oracular-minimal-cloudimg-amd64.img $ qemu-img resize oracular-minimal-cloudimg-amd64.img +20G $ cat >user-data
[Touch-packages] [Bug 2080257] Re: [WSL] systemd fails to upgrade on WSL1
** Tags added: foundations-todo ** 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/2080257 Title: [WSL] systemd fails to upgrade on WSL1 Status in systemd package in Ubuntu: New Bug description: Original report: https://github.com/ubuntu/WSL/issues/493 On WSL with systemd disabled (wsl1 or wsl2 without systemd enabled), systemd fails to upgrade. # Test Case WSL1 1. Install Ubuntu 24.04 with WSL from a Windows shell wsl --install --enable-wsl1 ubuntu-24.04 or wsl --install ubuntu-24.04 wsl --set-version ubuntu-24.04 1 => Verify that 24.04 is using version 1 NAMESTATE VERSION Ubuntu-22.04Stopped 2 Ubuntu-24.04Running 1 2. Start the distro if it is not already running ubuntu2404.exe 3. In the distro run the following command: sudo apt install --reinstall systemd # Expected result systemd is reinstalled without any issue # Actual result systemd postinst script fails and the following error is displayed to the user: ``` root@drenec:~# apt install --reinstall systemd Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 2 not upgraded. Need to get 3470 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 systemd amd64 255.4-1ubuntu8.4 [3470 kB] Fetched 3470 kB in 1s (2816 kB/s) (Reading database ... 40771 files and directories currently installed.) Preparing to unpack .../systemd_255.4-1ubuntu8.4_amd64.deb ... Unpacking systemd (255.4-1ubuntu8.4) over (255.4-1ubuntu8.4) ... Setting up systemd (255.4-1ubuntu8.4) ... Failed to take /etc/passwd lock: Invalid argument dpkg: error processing package systemd (--configure): installed systemd package post-installation script subprocess returned error exit status 1 Processing triggers for dbus (1.14.10-4ubuntu4.1) ... Processing triggers for man-db (2.12.0-4build2) ... Errors were encountered while processing: systemd E: Sub-process /usr/bin/dpkg returned an error code (1) ``` There is no easy way to recover from the error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2080257/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2078597] Re: Failed to flush binfmt_misc rules, ignoring: Permission denied
Are you able to run unprivileged containers instead? That would be the suggested configuration from upstream LXD. There are many things that do not work with systemd in privileged LXD containers due to AppArmor etc. Upstream systemd does not like adding workarounds for issues caused by AppArmor rules, and upstream LXD (from what I understand) does not want to spend a lot of effort supporting privileged containers, when unprivileged containers are the more secure alternative. For those reasons, I am going to mark this "won't fix." If running unprivileged containers does not work for you, I would suggest either masking the systemd-binfmt.service unit in your containers, or follow up with upstream(s) about the issue. ** Changed in: systemd (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2078597 Title: Failed to flush binfmt_misc rules, ignoring: Permission denied Status in systemd package in Ubuntu: Won't Fix Bug description: After upgrading an LXD guest machine from 22.04 to 24.04.1, system isn't healthy, systemctl complains that systemd-binfmt.service fails: Aug 31 19:23:51 install systemd-binfmt[1147]: Failed to flush binfmt_misc rules, ignoring: Permission denied Aug 31 19:23:51 install systemd-binfmt[1147]: /usr/lib/binfmt.d/python3.12.conf:1: Failed to delete rule 'python3.12', ignoring: Permission denied Aug 31 19:23:51 install systemd-binfmt[1147]: /usr/lib/binfmt.d/python3.12.conf:1: Failed to add binary format 'python3.12': Permission denied Aug 31 19:23:51 install systemd[1]: systemd-binfmt.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:23:51 install systemd[1]: systemd-binfmt.service: Failed with result 'exit-code'. Aug 31 19:23:51 install systemd[1]: Failed to start systemd-binfmt.service - Set Up Additional Binary Formats. Reason: # strace -s 80 /usr/lib/systemd/systemd-binfmt |& fgrep EACCES openat(AT_FDCWD, "/proc/sys/fs/binfmt_misc/status", O_WRONLY|O_NOCTTY|O_CLOEXEC) = -1 EACCES (Permission denied) openat(AT_FDCWD, "/proc/sys/fs/binfmt_misc/python3.12", O_WRONLY|O_NOCTTY|O_CLOEXEC) = -1 EACCES (Permission denied) openat(AT_FDCWD, "/proc/sys/fs/binfmt_misc/register", O_WRONLY|O_NOCTTY|O_CLOEXEC) = -1 EACCES (Permission denied) There is (like with other programs) a problem with latest LXD/24.04/apparmor settings. podman/docker also don't run without workarounds in apparmor. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd 255.4-1ubuntu8.4 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown CloudBuildName: server CloudSerial: 20221101.1 Date: Sun Sep 1 02:10:13 2024 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 1c4f:0063 SiGma Micro Touchpad (integrated in detachable keyboard of Chuwi SurBook) Bus 001 Device 003: ID 13d3:3458 IMC Networks Bluetooth Radio Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-41-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro SourcePackage: systemd 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. -- Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: Upgraded to noble on 2024-08-31 (0 days ago) dmi.bios.date: 04/10/2017 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: J3160-NUC dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd04/10/2017:br5.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnJ3160-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-07-22T17:59:07 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2078597/+subscri
[Touch-packages] [Bug 2078571] Re: Removable Storage - Removable Drives not executed after upgrade 22.04 to 24.04
Thank you for taking the time to report this bug and helping to make Ubuntu better. I suspect a support site would be more appropriate, e.g. https://askubuntu.com, or for more options please look at https://discourse.ubuntu.com/t/community-support/709. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2078571 Title: Removable Storage - Removable Drives not executed after upgrade 22.04 to 24.04 Status in systemd package in Ubuntu: Invalid Bug description: After the release upgrade 22.04 to 24.04, the earlier 'auto'-mounted external drives are still set in System Settings, but none is actually mounted at start. That can easily be done later, but, reproducible, is never done at startup. This could be linked to the udev problem described in #2078564? systemsettings 4:5.27.11-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2078571/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2077779] Re: PTP device symlink missing after running udevadm trigger command
** Changed in: systemd (Ubuntu Focal) Status: In Progress => Triaged ** Changed in: systemd (Ubuntu Jammy) Status: In Progress => Triaged ** Changed in: systemd (Ubuntu Noble) Status: In Progress => Triaged ** Changed in: systemd (Ubuntu Focal) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Jammy) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Noble) 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/209 Title: PTP device symlink missing after running udevadm trigger command Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Focal: Triaged Status in systemd source package in Jammy: Triaged Status in systemd source package in Noble: Triaged Status in systemd source package in Oracular: Fix Committed Bug description: [Impact] PTP device symlink creation rules are executed only when the udev action is 'add'. If the rules are reloaded and the udevadm trigger command is run to reapply changes, the symlink may be deleted. This can prevent the chronyd service from restarting properly. [Fix] Upstream has a patch to fix this issue. commit 6bd12be3fa7761f190e17efdbdbff4440da7528b Author: Chengen Du CommitDate: Thu Aug 15 15:38:46 2024 +0900 udev: Handle PTP device symlink properly on udev action 'change' PTP device symlink creation rules are currently executed only when the udev action is 'add'. If a user reloads the rules and runs the udevadm trigger command to reapply changes, the symlink may be deleted, which can prevent the chronyd service from restarting properly. Signed-off-by: Chengen Du [Test Plan] 1. Create a VM on Azure. 2. Run the `udevadm trigger` command. 3. Restart the chronyd service by running `systemctl restart chronyd`. 4. Verify that the service starts normally by running `systemctl status chronyd`. [Where problems could occur] The patch allows PTP device symlink creation rules to be executed when the udev action is 'change'. This update primarily affects services that rely on the PTP device symlink, such as chronyd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/209/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2078597] Re: Failed to flush binfmt_misc rules, ignoring: Permission denied
systemd-binfmt should just exit when /proc/sys/fs/binfmt_misc is not mounted rw, which I thought was usually the case in LXD containers. Are you running a privileged or unprivileged container? ** 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/2078597 Title: Failed to flush binfmt_misc rules, ignoring: Permission denied Status in systemd package in Ubuntu: Incomplete Bug description: After upgrading an LXD guest machine from 22.04 to 24.04.1, system isn't healthy, systemctl complains that systemd-binfmt.service fails: Aug 31 19:23:51 install systemd-binfmt[1147]: Failed to flush binfmt_misc rules, ignoring: Permission denied Aug 31 19:23:51 install systemd-binfmt[1147]: /usr/lib/binfmt.d/python3.12.conf:1: Failed to delete rule 'python3.12', ignoring: Permission denied Aug 31 19:23:51 install systemd-binfmt[1147]: /usr/lib/binfmt.d/python3.12.conf:1: Failed to add binary format 'python3.12': Permission denied Aug 31 19:23:51 install systemd[1]: systemd-binfmt.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:23:51 install systemd[1]: systemd-binfmt.service: Failed with result 'exit-code'. Aug 31 19:23:51 install systemd[1]: Failed to start systemd-binfmt.service - Set Up Additional Binary Formats. Reason: # strace -s 80 /usr/lib/systemd/systemd-binfmt |& fgrep EACCES openat(AT_FDCWD, "/proc/sys/fs/binfmt_misc/status", O_WRONLY|O_NOCTTY|O_CLOEXEC) = -1 EACCES (Permission denied) openat(AT_FDCWD, "/proc/sys/fs/binfmt_misc/python3.12", O_WRONLY|O_NOCTTY|O_CLOEXEC) = -1 EACCES (Permission denied) openat(AT_FDCWD, "/proc/sys/fs/binfmt_misc/register", O_WRONLY|O_NOCTTY|O_CLOEXEC) = -1 EACCES (Permission denied) There is (like with other programs) a problem with latest LXD/24.04/apparmor settings. podman/docker also don't run without workarounds in apparmor. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd 255.4-1ubuntu8.4 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown CloudBuildName: server CloudSerial: 20221101.1 Date: Sun Sep 1 02:10:13 2024 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 1c4f:0063 SiGma Micro Touchpad (integrated in detachable keyboard of Chuwi SurBook) Bus 001 Device 003: ID 13d3:3458 IMC Networks Bluetooth Radio Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-41-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro SourcePackage: systemd 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. -- Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: Upgraded to noble on 2024-08-31 (0 days ago) dmi.bios.date: 04/10/2017 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: J3160-NUC dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd04/10/2017:br5.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnJ3160-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-07-22T17:59:07 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2078597/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2078564] Re: After upgrade 22.04 to 24.04, start delays by 2 minutes on udev
Thank you for taking the time to report this bug and helping to make Ubuntu better. I suspect a support site would be more appropriate, e.g. https://askubuntu.com, or for more options please look at https://discourse.ubuntu.com/t/community-support/709. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2078564 Title: After upgrade 22.04 to 24.04, start delays by 2 minutes on udev Status in systemd package in Ubuntu: Invalid Bug description: journalctl shows: Aug 31 14:27:28 My-ThinkPad-Helix-2nd systemd[1]: systemd-rfkill.service: Deactivated successfully. Aug 31 14:27:49 My-ThinkPad-Helix-2nd systemd[1]: systemd-fsckd.service: Deactivated successfully. Aug 31 14:28:23 My-ThinkPad-Helix-2nd systemd-udevd[570]: bdw_rt286: Worker [618] processing SEQNUM=4265 is taking a long time Aug 31 14:28:23 My-ThinkPad-Helix-2nd systemd-udevd[570]: 2-002c: Worker [617] processing SEQNUM=4534 is taking a long time Aug 31 14:29:19 My-ThinkPad-Helix-2nd udevadm[593]: Timed out for waiting the udev queue being empty. Aug 31 14:29:19 My-ThinkPad-Helix-2nd systemd[1]: systemd-udev-settle.service: Main process exited, code=exited, status=1/FAILURE Aug 31 14:29:19 My-ThinkPad-Helix-2nd systemd[1]: systemd-udev-settle.service: Failed with result 'exit-code'. Aug 31 14:29:19 My-ThinkPad-Helix-2nd systemd[1]: Failed to start systemd-udev-settle.service - Wait for udev To Complete Device Initialization. Aug 31 14:29:19 My-ThinkPad-Helix-2nd systemd[1]: Reached target sysinit.target - System Initialization. Aug 31 14:29:19 My-ThinkPad-Helix-2nd systemd[1]: Started acpid.path - ACPI Events Check. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: udev 255.4-1ubuntu8.4 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE CustomUdevRuleFiles: 99-megasync-udev.rules 70-snap.youtube-dl.rules 70-snap.thunderbird.rules 70-snap.firefox.rules 80-remote-sundtek.rules 70-snap.chromium.rules 80-remote-eeti.rules 70-snap.snapd.rules 70-snap.cups.rules 70-snap.vokoscreen-ng.rules Date: Sat Aug 31 14:55:21 2024 InstallationDate: Installed on 2019-02-16 (2023 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20CHS10P02 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-41-generic root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-08-30 (1 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 2.16 dmi.bios.vendor: LENOVO dmi.bios.version: N17ETB6W (2.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CHS10P02 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 11 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.66 dmi.modalias: dmi:bvnLENOVO:bvrN17ETB6W(2.16):bd09/02/2021:br2.16:efr1.66:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:skuLENOVO_MT_20CH_BU_Think_FM_ThinkPadHelix2nd: dmi.product.family: ThinkPad Helix 2nd dmi.product.name: 20CHS10P02 dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd dmi.product.version: ThinkPad Helix 2nd dmi.sys.vendor: LENOVO mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2078564/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051407] Re: qemu-net autopkgtest fails: Failed to send exit request: Resource temporarily unavailable
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2051407
Title:
qemu-net autopkgtest fails: Failed to send exit request: Resource
temporarily unavailable
Status in initramfs-tools package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Invalid
Bug description:
This log shows initramfs-tools' qemu-net test failing on arm64. Here's
the relevant portion:
https://autopkgtest.ubuntu.com/results/autopkgtest-
mantic/mantic/arm64/i/initramfs-tools/20240119_214255_431f3@/log.gz
[...]
5482s no valid interfaces found
5482s exiting due to oneshot
5482s no interfaces have a carrier
5482s exiting due to oneshot
5482s dhcpcd exited
5482s dhcpcd_fork_cb: truncated read 0 (expected 4)
5492s [ 839.627776] virtio_net virtio1 lan0: renamed from eth0 (while UP)
5492s [ 839.806177] virtio_net virtio2 lan1: renamed from eth1 (while UP)
5544s no such user dhcpcd
5544s dhcpcd-10.0.2 starting
5544s dev: loaded udev
5557s DUID 00:03:00:01:52:54:00:65:43:21
5557s lan0: IAID 00:65:43:21
5557s lan1: IAID 00:12:34:56
5557s lan1: soliciting a DHCP lease
5558s lan1: offered 10.0.2.15 from 10.0.2.2
5558s lan1: probing address 10.0.2.15/24
5558s lan0: soliciting a DHCP lease
5558s lan0: offered 10.0.3.15 from 10.0.3.2
5558s lan0: probing address 10.0.3.15/24
5567s lan1: leased 10.0.2.15 for 86400 seconds
5567s lan1: adding route to 10.0.2.0/24
5567s lan1: adding default route via 10.0.2.2
5569s lan1: Setting hostname: goulash
5571s exiting due to oneshot
5579s dhcpcd exited
5579s dhcpcd_fork_cb: truncated read 0 (expected 4)
5590s Begin: Running /scripts/init-bottom ... Failed to send exit request:
Resource temporarily unavailable
5658s done.
5661s /init: line 386: can't open /root/dev/console: no such file
5661s [ 1009.213600] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x0100
I compared this to this successful test log:
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/arm64/i/initramfs-tools/20240116_053535_e8fd8@/log.gz
They test output looks about the same, up until:
5590s Begin: Running /scripts/init-bottom ... Failed to send exit
request: Resource temporarily unavailable.
I believe that error message is coming from /usr/share/initramfs-
tools/scripts/init-bottom/udev. That file does this:
-START-
#!/bin/sh -e
... usual boilerplate ...
# Stop udevd, we'll miss a few events while we run init, but we catch up
udevadm control --exit
# move the /dev tmpfs to the rootfs; fall back to util-linux mount that does
# not understand -o move
mount -n -o move /dev "${rootmnt:?}/dev" || mount -n --move /dev
"${rootmnt}/dev"
-END-
`udevadm control --exit` tries to send an exit request to udev over a
control socket. "Resource temporarily unavailable" means that it
received an -EAGAIN when it tried to do so. udev_ctrl_send() doesn't
check for an -EAGAIN, so this is fatal. Since the script is `set -e`,
it fails to continue and therefore /dev never gets moved over.
Observations:
- The QEMU instance in the failed test ran much slower than the
successful one. The successful one made it to userspace in about 6
seconds, where the failed one took 63.
- Not all QEMU instance boots in this run took that long - the
others took 30-45s. So it's not like the QEMU version or guest kernel
are always slow.
- The failed instance emits "Failed to wait for daemon to reply:
Connection timed out" early on. I'm guessing that this is from the
`udevadm` calls in init-top/udev - likely the `udevadm settle`, since
it is the only one with a `|| true` to ignore errors. Perhaps this is
an early sign that something is wrong with systemd-udevd. Here's that
snippet:
---START---
[ 63.075129] Run /init as init process
Loading, please wait...
Starting systemd-udevd version 253.5-1ubuntu6.1
[ 233.675459] hrtimer: interrupt took 10193008 ns
Failed to wait for daemon to reply: Connection timed out
Begin: Loading essential drivers ... [ 576.182017] raid6: neonx8 gen()
210 MB/s
[ 576.261515] raid6: neonx4 gen() 244 MB/s
---END---
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2051407/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2080216] Re: sshd cannot bind to IPv4 interfaces
Is sshd not accessible at all over ipv4? How did you notice that sshd was not listening on ipv4? In the default case, we should end up with ssh.socket listening on [::]:22, but with IPV6_V6ONLY=0 so that sshd is still accessible over ipv4. > Setting net.ipv6.bindv6only=0 also helps, but that's not a solution. I think this is the default on Ubuntu, no? If your system does have net.ipv6.bindv6only=1, and you don't want to change it, a workaround for now should be to do: $ mkdir -p /etc/systemd/systemd/ssh.socket.d/ $ cat > /etc/systemd/system/ssh.socket.d/bindipv6only-both.conf << EOF [Socket] BindIPv6Only=both EOF which has the effect of setting IPV6_V6ONLY to 0 for this particular socket. We should probably fix sshd-socket-generator to automatically do this in certain cases. ** Changed in: openssh (Ubuntu) Importance: Undecided => Medium ** Changed in: openssh (Ubuntu) Status: New => Incomplete ** Changed in: openssh (Ubuntu) Status: Incomplete => Confirmed ** Tags added: rls-nn-incoming -- 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/2080216 Title: sshd cannot bind to IPv4 interfaces Status in openssh package in Ubuntu: Confirmed Bug description: After upgrading from 22.04 to 24.04 I noticed that my sshd only listening on IPv6 interface (::), while previously it was listening both IPv4 (0.0.0.0) and IPv6 (::). I tried to explicitly specify ListenAddress 0.0.0.0 (assuming it would bind to IPv4 only) but after restart sshd was still listening on IPv6 only. This problem affects other packages as well, for example, openvpn. Rebuilding applications from sources seems to fix the issue. Setting net.ipv6.bindv6only=0 also helps, but that's not a solution. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: openssh-server 1:9.6p1-3ubuntu13.5 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Sep 10 16:45:54 2024 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=screen.xterm-256color SourcePackage: openssh UpgradeStatus: Upgraded to noble on 2024-09-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2080216/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2079993] [NEW] systemd initramfs-tools hook fails on s390x if /etc/udev/rules.d/*.rules empty
Public bug reported: E.g. https://autopkgtest.ubuntu.com/results/autopkgtest- oracular/oracular/s390x/i/initramfs-tools/20240909_091354_592dd@/log.gz 1489s autopkgtest [09:13:45]: summary 1489s qemu-ata-onlySKIP Test lists explicitly supported architectures, but the current architecture s390x isn't listed. 1489s qemu-ata-onlySKIP Test lists explicitly supported architectures, but the current architecture s390x isn't listed. 1489s unit-tests PASS 1489s qemu-klibc FAIL stderr: /usr/sbin/chzdev: Could not open file /etc/udev/rules.d/*.rules: No such file or directory 1489s qemu-busybox FAIL stderr: /usr/sbin/chzdev: Could not open file /etc/udev/rules.d/*.rules: No such file or directory 1489s qemu-virtio-only FAIL stderr: /usr/sbin/chzdev: Could not open file /etc/udev/rules.d/*.rules: No such file or directory 1489s qemu-separate-usrFAIL stderr: /usr/sbin/chzdev: Could not open file /etc/udev/rules.d/*.rules: No such file or directory 1489s qemu-panic-shell FAIL stderr: /usr/sbin/chzdev: Could not open file /etc/udev/rules.d/*.rules: No such file or directory 1489s qemu-net FAIL stderr: /usr/sbin/chzdev: Could not open file /etc/udev/rules.d/*.rules: No such file or directory 1489s qemu-net-dnsmasq FAIL stderr: /usr/sbin/chzdev: Could not open file /etc/udev/rules.d/*.rules: No such file or directory 1493s nova [W] Using flock in prodstack6-s390x This is because of the glob usage `for rules in /etc/udev/rules.d/*.rules`. When no matching files are found, we just iterate over the string literal "/etc/udev/rules.d/*.rules". ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Tags added: update-e ** Tags removed: update-e ** Tags added: update-excuse -- 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/2079993 Title: systemd initramfs-tools hook fails on s390x if /etc/udev/rules.d/*.rules empty Status in systemd package in Ubuntu: New Bug description: E.g. https://autopkgtest.ubuntu.com/results/autopkgtest- oracular/oracular/s390x/i/initramfs- tools/20240909_091354_592dd@/log.gz 1489s autopkgtest [09:13:45]: summary 1489s qemu-ata-onlySKIP Test lists explicitly supported architectures, but the current architecture s390x isn't listed. 1489s qemu-ata-onlySKIP Test lists explicitly supported architectures, but the current architecture s390x isn't listed. 1489s unit-tests PASS 1489s qemu-klibc FAIL stderr: /usr/sbin/chzdev: Could not open file /etc/udev/rules.d/*.rules: No such file or directory 1489s qemu-busybox FAIL stderr: /usr/sbin/chzdev: Could not open file /etc/udev/rules.d/*.rules: No such file or directory 1489s qemu-virtio-only FAIL stderr: /usr/sbin/chzdev: Could not open file /etc/udev/rules.d/*.rules: No such file or directory 1489s qemu-separate-usrFAIL stderr: /usr/sbin/chzdev: Could not open file /etc/udev/rules.d/*.rules: No such file or directory 1489s qemu-panic-shell FAIL stderr: /usr/sbin/chzdev: Could not open file /etc/udev/rules.d/*.rules: No such file or directory 1489s qemu-net FAIL stderr: /usr/sbin/chzdev: Could not open file /etc/udev/rules.d/*.rules: No such file or directory 1489s qemu-net-dnsmasq FAIL stderr: /usr/sbin/chzdev: Could not open file /etc/udev/rules.d/*.rules: No such file or directory 1493s nova [W] Using flock in prodstack6-s390x This is because of the glob usage `for rules in /etc/udev/rules.d/*.rules`. When no matching files are found, we just iterate over the string literal "/etc/udev/rules.d/*.rules". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2079993/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2077779] Re: PTP device symlink missing after running udevadm trigger command
This patch is in v256.5, which I prepared and uploaded today. ** Changed in: systemd (Ubuntu Oracular) 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/209 Title: PTP device symlink missing after running udevadm trigger command Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Focal: In Progress Status in systemd source package in Jammy: In Progress Status in systemd source package in Noble: In Progress Status in systemd source package in Oracular: Fix Committed Bug description: [Impact] PTP device symlink creation rules are executed only when the udev action is 'add'. If the rules are reloaded and the udevadm trigger command is run to reapply changes, the symlink may be deleted. This can prevent the chronyd service from restarting properly. [Fix] Upstream has a patch to fix this issue. commit 6bd12be3fa7761f190e17efdbdbff4440da7528b Author: Chengen Du CommitDate: Thu Aug 15 15:38:46 2024 +0900 udev: Handle PTP device symlink properly on udev action 'change' PTP device symlink creation rules are currently executed only when the udev action is 'add'. If a user reloads the rules and runs the udevadm trigger command to reapply changes, the symlink may be deleted, which can prevent the chronyd service from restarting properly. Signed-off-by: Chengen Du [Test Plan] 1. Create a VM on Azure. 2. Run the `udevadm trigger` command. 3. Restart the chronyd service by running `systemctl restart chronyd`. 4. Verify that the service starts normally by running `systemctl status chronyd`. [Where problems could occur] The patch allows PTP device symlink creation rules to be executed when the udev action is 'change'. This update primarily affects services that rely on the PTP device symlink, such as chronyd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/209/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2077779] Re: PTP device symlink missing after running udevadm trigger command
** 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/209 Title: PTP device symlink missing after running udevadm trigger command Status in systemd package in Ubuntu: In Progress Status in systemd source package in Focal: In Progress Status in systemd source package in Jammy: In Progress Status in systemd source package in Noble: In Progress Status in systemd source package in Oracular: In Progress Bug description: [Impact] PTP device symlink creation rules are executed only when the udev action is 'add'. If the rules are reloaded and the udevadm trigger command is run to reapply changes, the symlink may be deleted. This can prevent the chronyd service from restarting properly. [Fix] Upstream has a patch to fix this issue. commit 6bd12be3fa7761f190e17efdbdbff4440da7528b Author: Chengen Du CommitDate: Thu Aug 15 15:38:46 2024 +0900 udev: Handle PTP device symlink properly on udev action 'change' PTP device symlink creation rules are currently executed only when the udev action is 'add'. If a user reloads the rules and runs the udevadm trigger command to reapply changes, the symlink may be deleted, which can prevent the chronyd service from restarting properly. Signed-off-by: Chengen Du [Test Plan] 1. Create a VM on Azure. 2. Run the `udevadm trigger` command. 3. Restart the chronyd service by running `systemctl restart chronyd`. 4. Verify that the service starts normally by running `systemctl status chronyd`. [Where problems could occur] The patch allows PTP device symlink creation rules to be executed when the udev action is 'change'. This update primarily affects services that rely on the PTP device symlink, such as chronyd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/209/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2078852] Re: systemd-resolved was re-enabled during upgrade from 22.04 to 24.04
*** This bug is a duplicate of bug 2078555 *** https://bugs.launchpad.net/bugs/2078555 Thanks for your bug report. As you noted, this is the same issue as bug 2078555 so I am marking this as a duplicate to consolidate. ** This bug has been marked a duplicate of bug 2078555 Upgrading from 22.04 to 24.04.01 breaks dnsmasq -- 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/2078852 Title: systemd-resolved was re-enabled during upgrade from 22.04 to 24.04 Status in systemd package in Ubuntu: New Bug description: systemd-resolved was disabled on my servers because i use a different DNS setup. During upgrade from 22.04 to 24.04, systemd-resolved was re-enabled by the upgrade process. This would have lead to downtime of some services as well other problems, because local DNS lookups failed to use the correct server. Re-enabling systemd-resolved also overwrote /etc/resolv.conf, which had to be restored from backups. This has now been a so long standing problem (going back many LTS releases) that i have a script for that called the "systemd- castrator". It basically does: systemctl disable systemd-resolved systemctl stop systemd-resolved and then restores the correct resolv.conf from my source code management. It would be nice if this problem could be solved by the Ubuntu team. E.g. "if a systemd service is manually disabled before the upgrade, it *stays* disabled after the upgrade". ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8.4 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Sep 3 20:00:16 2024 SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-08-31 (3 days ago) mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2078852/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2076023] Re: Failed to apply 'Match' directive in sshd_config with sshd-socket-generator
I am planning an SRU for noble in the next couple weeks. ** 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/2076023 Title: Failed to apply 'Match' directive in sshd_config with sshd-socket- generator Status in openssh package in Ubuntu: Fix Committed Status in openssh source package in Noble: Triaged Status in openssh source package in Oracular: Fix Committed Bug description: When using the Match statement in sshd_config or sshd_config.d/*.conf with socket activation(not classic method), sshd does not start as expected. Environment: Ubuntu: Ubuntu 24.04 LTS OpenSSH Server: 1:9.6p1-3ubuntu13.4 Steps to Reproduce: /etc/ssh/sshd_config ``` Include /etc/ssh/sshd_config.d/*.conf Port 22 Port 2 KbdInteractiveAuthentication no UsePAM yes X11Forwarding yes PrintMotd no AcceptEnv LANG LC_* Subsystem sftp/usr/lib/openssh/sftp-server Match LocalPort 2 PasswordAuthentication no PubkeyAuthentication yes ``` command: sudo systemctl daemon-reload && sudo systemctl restart ssh.socket Expected Behavior: sshd should listen on both ports 22 and 2. When connecting via port 2, password login should not be allowed and only public key authentication should be permitted. Actual Behavior: sshd only listens on port 22 and not on port 2. The configuration is not correctly applied. After daemon-reload, the output from journalctl is as follows: $ sudo journalctl -t (sd-exec- Aug 04 12:47:36 ults (sd-exec-[479259]: /usr/lib/systemd/system-generators/sshd-socket-generator failed with exit status 255. Additional Information: 1.Using sshd -T -C to test the configuration produces the following result: $ sudo sshd -T -C lport=22 | grep passwordauthentication passwordauthentication yes $ sudo sshd -T -C lport=2 | grep passwordauthentication passwordauthentication no 2.The output when manually running /usr/lib/systemd/system-generators/sshd-socket-generator is: $ sudo /usr/lib/systemd/system-generators/sshd-socket-generator ./ 'Match LocalPort' in configuration but 'lport' not in connection test specification. 3.I have test some cases, if sshd-socket-generator can not handle config rightly, sshd seems to run with default config. And I also noticed that there is no test case about the Match directive in https://git.launchpad.net/ubuntu/+source/openssh/tree/debian/tests/sshd-socket-generator. I guess the root cause of the issue lies in the sshd-socket-generator not correctly handling the Match directive. And a detailed assessment of potential security issues which caused by this bug is needed. If socket activation is to be widely adopted, this issue will undoubtedly be a significant stumbling block. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2076023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2076023] Re: Failed to apply 'Match' directive in sshd_config with sshd-socket-generator
** Changed in: openssh (Ubuntu Oracular) 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/2076023 Title: Failed to apply 'Match' directive in sshd_config with sshd-socket- generator Status in openssh package in Ubuntu: Fix Committed Status in openssh source package in Noble: Triaged Status in openssh source package in Oracular: Fix Committed Bug description: When using the Match statement in sshd_config or sshd_config.d/*.conf with socket activation(not classic method), sshd does not start as expected. Environment: Ubuntu: Ubuntu 24.04 LTS OpenSSH Server: 1:9.6p1-3ubuntu13.4 Steps to Reproduce: /etc/ssh/sshd_config ``` Include /etc/ssh/sshd_config.d/*.conf Port 22 Port 2 KbdInteractiveAuthentication no UsePAM yes X11Forwarding yes PrintMotd no AcceptEnv LANG LC_* Subsystem sftp/usr/lib/openssh/sftp-server Match LocalPort 2 PasswordAuthentication no PubkeyAuthentication yes ``` command: sudo systemctl daemon-reload && sudo systemctl restart ssh.socket Expected Behavior: sshd should listen on both ports 22 and 2. When connecting via port 2, password login should not be allowed and only public key authentication should be permitted. Actual Behavior: sshd only listens on port 22 and not on port 2. The configuration is not correctly applied. After daemon-reload, the output from journalctl is as follows: $ sudo journalctl -t (sd-exec- Aug 04 12:47:36 ults (sd-exec-[479259]: /usr/lib/systemd/system-generators/sshd-socket-generator failed with exit status 255. Additional Information: 1.Using sshd -T -C to test the configuration produces the following result: $ sudo sshd -T -C lport=22 | grep passwordauthentication passwordauthentication yes $ sudo sshd -T -C lport=2 | grep passwordauthentication passwordauthentication no 2.The output when manually running /usr/lib/systemd/system-generators/sshd-socket-generator is: $ sudo /usr/lib/systemd/system-generators/sshd-socket-generator ./ 'Match LocalPort' in configuration but 'lport' not in connection test specification. 3.I have test some cases, if sshd-socket-generator can not handle config rightly, sshd seems to run with default config. And I also noticed that there is no test case about the Match directive in https://git.launchpad.net/ubuntu/+source/openssh/tree/debian/tests/sshd-socket-generator. I guess the root cause of the issue lies in the sshd-socket-generator not correctly handling the Match directive. And a detailed assessment of potential security issues which caused by this bug is needed. If socket activation is to be widely adopted, this issue will undoubtedly be a significant stumbling block. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2076023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2076023] Re: Failed to apply 'Match' directive in sshd_config with sshd-socket-generator
I took another look, and this turns out to be simpler than I thought. The problem is that we explicitly attempt to parse the server match config (an unnecessary copypasta from sshd -T code path). But, in the generator, we only care about options that affect the listening addresses, and the match section is for modifying settings on a per- connection basis. Hence, the fix for this is to just not attempt to parse the match config, as it requires a connection spec, which we cannot have at generator time. ** Changed in: openssh (Ubuntu Oracular) Status: Confirmed => Triaged ** Changed in: openssh (Ubuntu Noble) Status: New => Triaged ** Changed in: openssh (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: openssh (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 openssh in Ubuntu. https://bugs.launchpad.net/bugs/2076023 Title: Failed to apply 'Match' directive in sshd_config with sshd-socket- generator Status in openssh package in Ubuntu: Triaged Status in openssh source package in Noble: Triaged Status in openssh source package in Oracular: Triaged Bug description: When using the Match statement in sshd_config or sshd_config.d/*.conf with socket activation(not classic method), sshd does not start as expected. Environment: Ubuntu: Ubuntu 24.04 LTS OpenSSH Server: 1:9.6p1-3ubuntu13.4 Steps to Reproduce: /etc/ssh/sshd_config ``` Include /etc/ssh/sshd_config.d/*.conf Port 22 Port 2 KbdInteractiveAuthentication no UsePAM yes X11Forwarding yes PrintMotd no AcceptEnv LANG LC_* Subsystem sftp/usr/lib/openssh/sftp-server Match LocalPort 2 PasswordAuthentication no PubkeyAuthentication yes ``` command: sudo systemctl daemon-reload && sudo systemctl restart ssh.socket Expected Behavior: sshd should listen on both ports 22 and 2. When connecting via port 2, password login should not be allowed and only public key authentication should be permitted. Actual Behavior: sshd only listens on port 22 and not on port 2. The configuration is not correctly applied. After daemon-reload, the output from journalctl is as follows: $ sudo journalctl -t (sd-exec- Aug 04 12:47:36 ults (sd-exec-[479259]: /usr/lib/systemd/system-generators/sshd-socket-generator failed with exit status 255. Additional Information: 1.Using sshd -T -C to test the configuration produces the following result: $ sudo sshd -T -C lport=22 | grep passwordauthentication passwordauthentication yes $ sudo sshd -T -C lport=2 | grep passwordauthentication passwordauthentication no 2.The output when manually running /usr/lib/systemd/system-generators/sshd-socket-generator is: $ sudo /usr/lib/systemd/system-generators/sshd-socket-generator ./ 'Match LocalPort' in configuration but 'lport' not in connection test specification. 3.I have test some cases, if sshd-socket-generator can not handle config rightly, sshd seems to run with default config. And I also noticed that there is no test case about the Match directive in https://git.launchpad.net/ubuntu/+source/openssh/tree/debian/tests/sshd-socket-generator. I guess the root cause of the issue lies in the sshd-socket-generator not correctly handling the Match directive. And a detailed assessment of potential security issues which caused by this bug is needed. If socket activation is to be widely adopted, this issue will undoubtedly be a significant stumbling block. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2076023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055239] Re: Warning: The unit file, source configuration file or drop-ins of {apt-news, esm-cache}.service changed on disk. Run 'systemctl daemon-reload' to reload units.
@corradoventu - the output you shared demonstrates that you are *not*
seeing this issue on 24.10.
@sunneyxue- likewise, your output demonstrates that the issue is fixed
on this system.
Note that it is possible at the time when you run `apt update`, that a
daemon-reload actually is needed, and the warning will *correctly* be
displayed. If we want this to always be hidden when running apt update,
the apt hook needs to be updated to pass --no-warn to the systemctl
call.
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: Invalid => New
** Changed in: ubuntu-advantage-tools (Ubuntu Noble)
Status: Invalid => New
** Changed in: ubuntu-advantage-tools (Ubuntu)
Importance: Undecided => Low
** Changed in: ubuntu-advantage-tools (Ubuntu Noble)
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/2055239
Title:
Warning: The unit file, source configuration file or drop-ins of {apt-
news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
to reload units.
Status in snapd:
New
Status in systemd package in Ubuntu:
Fix Released
Status in ubuntu-advantage-tools package in Ubuntu:
New
Status in systemd source package in Noble:
Fix Released
Status in ubuntu-advantage-tools source package in Noble:
New
Bug description:
[Impact]
systemd may incorrectly mark units as needing a daemon reload,
therefore unnecessarily printing the warning that a daemon-reload is
needed for the changes to take effect. This is misleading to users,
and particularly visible in cases like running apt update, since there
is an apt hook (/etc/apt/apt.conf.d/20apt-esm-hook.conf) that starts
two systemd services.
[Test Plan]
This bug can be triggered by running systemctl enable/disable on a
non-existent unit. After that, calling systemctl start/status/etc. will show a
false warning
that the unit changed on disk. Hence, to test, simply:
$ systemctl enable somethingthatdefinitelydoesnotexist.service
$ systemctl status systemd-resolved.service
$ apt update
On an effected system, warnings will be shown when calling both
commands after the "enable non-existent unit" step.
[Where problems could occur]
This patch fixes a previous commit by ensuring that the
manager->unit_file_state_outdated flag is set *only* when some
modifications succeeded, but the overall operation failed. In cases
where everything fails, it is not necessary to set the flag.
Since the patch is restricted to this area, any regressions from this
patch would most likely also be related to the NeedDaemonReload
property of units.
[Other information]
The patch is from upstream:
https://github.com/systemd/systemd/pull/32610/commits/d69cba3bfffc7b1e3197e2a34b459db13b1e1cb7#diff-84bbf3361da4139a5620a035ebd24f50a0e4d4ece7952dc2d8b4325e6ebdf6e0L2320
[Original Description]
I recently started seeing the following warning messages when I run
`apt update`.
$ sudo apt update
Warning: The unit file, source configuration file or drop-ins of
apt-news.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Warning: The unit file, source configuration file or drop-ins of
esm-cache.service changed on disk. Run 'systemctl daemon-reload' to reload
units.
...
apt-news.service for example is in /lib/systemd/system/apt-
news.service and it's a static file managed by the package. Does the
package maintenance script call systemd related hooks to reload the
config whenever the package gets updated?
$ systemctl cat apt-news.service
# /usr/lib/systemd/system/apt-news.service
# APT News is hosted at https://motd.ubuntu.com/aptnews.json and can include
# timely information related to apt updates available to your system.
...
$ dpkg -S /lib/systemd/system/apt-news.service
ubuntu-pro-client: /lib/systemd/system/apt-news.service
ProblemType: BugDistroRelease: Ubuntu 24.04
Package: ubuntu-pro-client 31.1
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 28 13:06:35 2024
InstallationDate: Installed on 2024-01-08 (51 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240104)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=SourcePackage: ubuntu-advantage-tools
UpgradeStatus: No upgrade log present (probably fresh install)
apparmor_logs.txt:
cloud-id.txt-error:
Failed running command 'cloud-id' [exit(2)]. Message: REDACTED config part
/etc/cloud/cloud.cfg.d/99-installer.cfg, insufficient permissions
REDACTED config part /etc/cloud/cloud.cfg.d/90-installer-network.cfg,
insufficien
[Touch-packages] [Bug 2055397] Re: netplan/systemd-networkd: route metric not applied to routes to the local subnet
The non-linux autopkgtest regressions were resolved with test retries/baseline tests. As previously stated, the linux-* tests should be ignored as they are denylisted. With, I believe the update could be 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/2055397 Title: netplan/systemd-networkd: route metric not applied to routes to the local subnet Status in cloud-init package in Ubuntu: Invalid Status in netplan.io package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Bug description: [SRU TEMPLATE] [DESCRIPTION] Cloud-init introduced a feature to configure policy routing on AWS EC2 instances with multiple NICs in https://github.com/canonical/cloud-init/commit/0ca5f31043e2d98eab31a43d9dde9bdaef1435cb targeting v24.1. Cloud-init generates the following netplan config: ``` $ cat /etc/netplan/50-cloud-init.yaml network: ethernets: ens5: dhcp4: true dhcp4-overrides: &id001 route-metric: 100 dhcp6: true dhcp6-overrides: *id001 match: macaddress: 0a:c8:ab:90:c2:fb set-name: ens5 ens6: dhcp4: true dhcp4-overrides: route-metric: 200 use-routes: true dhcp6: false match: macaddress: 0a:c6:55:a1:dc:3b routes: - table: 101 to: 0.0.0.0/0 via: 192.168.0.1 - table: 101 to: 192.168.0.0/20 routing-policy: - from: 192.168.10.212 table: 101 set-name: ens6 version: 2 ``` Which renders the following systemd-networkd config files: ``` $ cat 10-netplan-ens5.link [Match] MACAddress=0a:c8:ab:90:c2:fb [Link] Name=ens5 WakeOnLan=off $ cat 10-netplan-ens5.network [Match] MACAddress=0a:c8:ab:90:c2:fb Name=ens5 [Network] DHCP=yes LinkLocalAddressing=ipv6 [DHCP] RouteMetric=100 UseMTU=true $ cat 10-netplan-ens6.link [Match] MACAddress=0a:c6:55:a1:dc:3b [Link] Name=ens6 WakeOnLan=off $ cat 10-netplan-ens6.network [Match] MACAddress=0a:c6:55:a1:dc:3b Name=ens6 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 [Route] Destination=0.0.0.0/0 Gateway=192.168.0.1 Table=101 [Route] Destination=192.168.0.0/20 Scope=link Table=101 [RoutingPolicyRule] From=192.168.10.212 Table=101 [DHCP] RouteMetric=200 UseMTU=true ``` Which configures the instance with the following state in Ubuntu Focal: ``` $ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens5: mtu 9001 qdisc mq state UP group default qlen 1000 link/ether 0a:c8:ab:90:c2:fb brd ff:ff:ff:ff:ff:ff inet 192.168.12.94/20 brd 192.168.15.255 scope global dynamic ens5 valid_lft 2087sec preferred_lft 2087sec inet6 2a05:d012:ea0:c500:6d12:2b20:5fef:a502/128 scope global dynamic noprefixroute valid_lft 440sec preferred_lft 130sec inet6 fe80::8c8:abff:fe90:c2fb/64 scope link valid_lft forever preferred_lft forever 3: ens6: mtu 9001 qdisc mq state UP group default qlen 1000 link/ether 0a:c6:55:a1:dc:3b brd ff:ff:ff:ff:ff:ff inet 192.168.10.212/20 brd 192.168.15.255 scope global dynamic ens6 valid_lft 2083sec preferred_lft 2083sec inet6 fe80::8c6:55ff:fea1:dc3b/64 scope link valid_lft forever preferred_lft forever $ ip route show default via 192.168.0.1 dev ens5 proto dhcp src 192.168.12.94 metric 100 default via 192.168.0.1 dev ens6 proto dhcp src 192.168.10.212 metric 200 192.168.0.0/20 dev ens5 proto kernel scope link src 192.168.12.94 192.168.0.0/20 dev ens6 proto kernel scope link src 192.168.10.212 192.168.0.1 dev ens5 proto dhcp scope link src 192.168.12.94 metric 100 192.168.0.1 dev ens6 proto dhcp scope link src 192.168.10.212 metric 200 $ ip rule show 0: from all lookup local 0: from 192.168.10.212 lookup 101 32766: from all lookup main 32767: from all lookup default $ ip route show table 101 default via 192.168.0.1 dev ens6 proto static onlink 192.168.0.0/20 dev ens6 proto static scope link ``` The issue here is that the instance is not reachable from the same subnet via the private ipv4 of the primary NIC, packets are routed to egress via ens6 and dropped. The cause is that interface metrics are not applied to local subn
[Touch-packages] [Bug 2055239] Re: Warning: The unit file, source configuration file or drop-ins of {apt-news, esm-cache}.service changed on disk. Run 'systemctl daemon-reload' to reload units.
@sunneyxue, can you share the output of the following?
$ apt policy systemd
$ sudo systemctl daemon-reload
$ sudo systemctl enable somethingthatdefinitelydoesnotexist.service
$ sudo apt update
--
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/2055239
Title:
Warning: The unit file, source configuration file or drop-ins of {apt-
news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
to reload units.
Status in snapd:
New
Status in systemd package in Ubuntu:
Fix Released
Status in ubuntu-advantage-tools package in Ubuntu:
Invalid
Status in systemd source package in Noble:
Fix Released
Status in ubuntu-advantage-tools source package in Noble:
Invalid
Bug description:
[Impact]
systemd may incorrectly mark units as needing a daemon reload,
therefore unnecessarily printing the warning that a daemon-reload is
needed for the changes to take effect. This is misleading to users,
and particularly visible in cases like running apt update, since there
is an apt hook (/etc/apt/apt.conf.d/20apt-esm-hook.conf) that starts
two systemd services.
[Test Plan]
This bug can be triggered by running systemctl enable/disable on a
non-existent unit. After that, calling systemctl start/status/etc. will show a
false warning
that the unit changed on disk. Hence, to test, simply:
$ systemctl enable somethingthatdefinitelydoesnotexist.service
$ systemctl status systemd-resolved.service
$ apt update
On an effected system, warnings will be shown when calling both
commands after the "enable non-existent unit" step.
[Where problems could occur]
This patch fixes a previous commit by ensuring that the
manager->unit_file_state_outdated flag is set *only* when some
modifications succeeded, but the overall operation failed. In cases
where everything fails, it is not necessary to set the flag.
Since the patch is restricted to this area, any regressions from this
patch would most likely also be related to the NeedDaemonReload
property of units.
[Other information]
The patch is from upstream:
https://github.com/systemd/systemd/pull/32610/commits/d69cba3bfffc7b1e3197e2a34b459db13b1e1cb7#diff-84bbf3361da4139a5620a035ebd24f50a0e4d4ece7952dc2d8b4325e6ebdf6e0L2320
[Original Description]
I recently started seeing the following warning messages when I run
`apt update`.
$ sudo apt update
Warning: The unit file, source configuration file or drop-ins of
apt-news.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Warning: The unit file, source configuration file or drop-ins of
esm-cache.service changed on disk. Run 'systemctl daemon-reload' to reload
units.
...
apt-news.service for example is in /lib/systemd/system/apt-
news.service and it's a static file managed by the package. Does the
package maintenance script call systemd related hooks to reload the
config whenever the package gets updated?
$ systemctl cat apt-news.service
# /usr/lib/systemd/system/apt-news.service
# APT News is hosted at https://motd.ubuntu.com/aptnews.json and can include
# timely information related to apt updates available to your system.
...
$ dpkg -S /lib/systemd/system/apt-news.service
ubuntu-pro-client: /lib/systemd/system/apt-news.service
ProblemType: BugDistroRelease: Ubuntu 24.04
Package: ubuntu-pro-client 31.1
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 28 13:06:35 2024
InstallationDate: Installed on 2024-01-08 (51 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240104)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=SourcePackage: ubuntu-advantage-tools
UpgradeStatus: No upgrade log present (probably fresh install)
apparmor_logs.txt:
cloud-id.txt-error:
Failed running command 'cloud-id' [exit(2)]. Message: REDACTED config part
/etc/cloud/cloud.cfg.d/99-installer.cfg, insufficient permissions
REDACTED config part /etc/cloud/cloud.cfg.d/90-installer-network.cfg,
insufficient permissions
REDACTED config part /etc/cloud/cloud.cfg.d/99-installer.cfg, insufficient
permissions
REDACTED config part /etc/cloud/cloud.cfg.d/90-installer-network.cfg,
insufficient permissions
livepatch-status.txt-error: Invalid command specified
'/snap/bin/canonical-livepatch status'.
uaclient.conf:
contract_url: https://contracts.canonical.com
log_level: debug
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/2055239/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.ne
[Touch-packages] [Bug 2076340] Re: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x
I checked that the build flags for systemd on s390x and ppc64el in noble-proposed look correct: https://launchpadlibrarian.net/743007715/buildlog_ubuntu-noble-ppc64el.systemd_255.4-1ubuntu8.4_BUILDING.txt.gz https://launchpadlibrarian.net/743006792/buildlog_ubuntu-noble-s390x.systemd_255.4-1ubuntu8.4_BUILDING.txt.gz I.e., the package is no longer built with -fno-omit-frame-pointer on those arches. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bzip2 in Ubuntu. https://bugs.launchpad.net/bugs/2076340 Title: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x Status in atlas package in Ubuntu: New Status in bzip2 package in Ubuntu: Fix Released Status in containerd-app package in Ubuntu: New Status in curl package in Ubuntu: New Status in cyrus-sasl2 package in Ubuntu: New Status in dbus package in Ubuntu: Fix Released Status in docker.io-app package in Ubuntu: New Status in dotnet8 package in Ubuntu: New Status in gnutls28 package in Ubuntu: New Status in golang-1.22 package in Ubuntu: New Status in icu package in Ubuntu: Fix Released Status in lapack package in Ubuntu: Fix Released Status in libdeflate package in Ubuntu: New Status in libseccomp package in Ubuntu: Fix Released Status in libzdnn package in Ubuntu: Fix Released Status in libzstd package in Ubuntu: New Status in lz4 package in Ubuntu: New Status in mysql-8.0 package in Ubuntu: New Status in nettle package in Ubuntu: New Status in openssh package in Ubuntu: New Status in openssl package in Ubuntu: New Status in p11-kit package in Ubuntu: New Status in postgresql-16 package in Ubuntu: New Status in postgresql-common package in Ubuntu: New Status in powerpc-utils package in Ubuntu: Fix Released Status in python-greenlet package in Ubuntu: Fix Released Status in qemu package in Ubuntu: New Status in runc-app package in Ubuntu: Fix Released Status in rustc package in Ubuntu: New Status in s390-tools package in Ubuntu: New Status in s390-tools-signed package in Ubuntu: New Status in systemd package in Ubuntu: New Status in util-linux package in Ubuntu: New Status in xz-utils package in Ubuntu: New Status in zlib package in Ubuntu: New Status in atlas source package in Noble: Fix Committed Status in bzip2 source package in Noble: Fix Committed Status in containerd-app source package in Noble: Fix Committed Status in curl source package in Noble: Fix Committed Status in cyrus-sasl2 source package in Noble: Fix Committed Status in dbus source package in Noble: Fix Committed Status in docker.io-app source package in Noble: Fix Committed Status in dotnet8 source package in Noble: Fix Committed Status in gnutls28 source package in Noble: Fix Committed Status in golang-1.22 source package in Noble: Fix Committed Status in icu source package in Noble: Fix Committed Status in lapack source package in Noble: Fix Committed Status in libdeflate source package in Noble: Fix Committed Status in libseccomp source package in Noble: Fix Committed Status in libzdnn source package in Noble: Fix Committed Status in libzstd source package in Noble: Fix Committed Status in lz4 source package in Noble: Fix Committed Status in mysql-8.0 source package in Noble: Fix Committed Status in nettle source package in Noble: Fix Committed Status in openssh source package in Noble: Fix Committed Status in openssl source package in Noble: Fix Committed Status in p11-kit source package in Noble: Fix Committed Status in postgresql-16 source package in Noble: Fix Committed Status in postgresql-common source package in Noble: Fix Committed Status in powerpc-utils source package in Noble: Fix Committed Status in python-greenlet source package in Noble: Fix Committed Status in qemu source package in Noble: Fix Committed Status in runc-app source package in Noble: Fix Committed Status in rustc source package in Noble: Fix Committed Status in s390-tools source package in Noble: Fix Committed Status in s390-tools-signed source package in Noble: New Status in systemd source package in Noble: Fix Committed Status in util-linux source package in Noble: Fix Committed Status in xz-utils source package in Noble: Fix Committed Status in zlib source package in Noble: Fix Committed Bug description: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x This is batch of packages that we want to rebuild to pick up the changed build flags on ppc64el (LP: #2064539) and s390x (LP: #2064538). Impact: These are no change uploads on architectures other than ppc64el and s390x. All of those packages already built successful in oracular with the changed build flags. We will validate picking up the changed build flags by inspecting the log files on ppc64el and s390x. Packages with all passing autopkg tests: lapack golang-1.
[Touch-packages] [Bug 2055239] Re: Warning: The unit file, source configuration file or drop-ins of {apt-news, esm-cache}.service changed on disk. Run 'systemctl daemon-reload' to reload units.
@corradoventu, can you provide some evidence of that? I cannot reproduce
this on 24.10.
--
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/2055239
Title:
Warning: The unit file, source configuration file or drop-ins of {apt-
news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
to reload units.
Status in snapd:
New
Status in systemd package in Ubuntu:
Fix Released
Status in ubuntu-advantage-tools package in Ubuntu:
Invalid
Status in systemd source package in Noble:
Fix Committed
Status in ubuntu-advantage-tools source package in Noble:
Invalid
Bug description:
[Impact]
systemd may incorrectly mark units as needing a daemon reload,
therefore unnecessarily printing the warning that a daemon-reload is
needed for the changes to take effect. This is misleading to users,
and particularly visible in cases like running apt update, since there
is an apt hook (/etc/apt/apt.conf.d/20apt-esm-hook.conf) that starts
two systemd services.
[Test Plan]
This bug can be triggered by running systemctl enable/disable on a
non-existent unit. After that, calling systemctl start/status/etc. will show a
false warning
that the unit changed on disk. Hence, to test, simply:
$ systemctl enable somethingthatdefinitelydoesnotexist.service
$ systemctl status systemd-resolved.service
$ apt update
On an effected system, warnings will be shown when calling both
commands after the "enable non-existent unit" step.
[Where problems could occur]
This patch fixes a previous commit by ensuring that the
manager->unit_file_state_outdated flag is set *only* when some
modifications succeeded, but the overall operation failed. In cases
where everything fails, it is not necessary to set the flag.
Since the patch is restricted to this area, any regressions from this
patch would most likely also be related to the NeedDaemonReload
property of units.
[Other information]
The patch is from upstream:
https://github.com/systemd/systemd/pull/32610/commits/d69cba3bfffc7b1e3197e2a34b459db13b1e1cb7#diff-84bbf3361da4139a5620a035ebd24f50a0e4d4ece7952dc2d8b4325e6ebdf6e0L2320
[Original Description]
I recently started seeing the following warning messages when I run
`apt update`.
$ sudo apt update
Warning: The unit file, source configuration file or drop-ins of
apt-news.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Warning: The unit file, source configuration file or drop-ins of
esm-cache.service changed on disk. Run 'systemctl daemon-reload' to reload
units.
...
apt-news.service for example is in /lib/systemd/system/apt-
news.service and it's a static file managed by the package. Does the
package maintenance script call systemd related hooks to reload the
config whenever the package gets updated?
$ systemctl cat apt-news.service
# /usr/lib/systemd/system/apt-news.service
# APT News is hosted at https://motd.ubuntu.com/aptnews.json and can include
# timely information related to apt updates available to your system.
...
$ dpkg -S /lib/systemd/system/apt-news.service
ubuntu-pro-client: /lib/systemd/system/apt-news.service
ProblemType: BugDistroRelease: Ubuntu 24.04
Package: ubuntu-pro-client 31.1
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 28 13:06:35 2024
InstallationDate: Installed on 2024-01-08 (51 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240104)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=SourcePackage: ubuntu-advantage-tools
UpgradeStatus: No upgrade log present (probably fresh install)
apparmor_logs.txt:
cloud-id.txt-error:
Failed running command 'cloud-id' [exit(2)]. Message: REDACTED config part
/etc/cloud/cloud.cfg.d/99-installer.cfg, insufficient permissions
REDACTED config part /etc/cloud/cloud.cfg.d/90-installer-network.cfg,
insufficient permissions
REDACTED config part /etc/cloud/cloud.cfg.d/99-installer.cfg, insufficient
permissions
REDACTED config part /etc/cloud/cloud.cfg.d/90-installer-network.cfg,
insufficient permissions
livepatch-status.txt-error: Invalid command specified
'/snap/bin/canonical-livepatch status'.
uaclient.conf:
contract_url: https://contracts.canonical.com
log_level: debug
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/2055239/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2076883] Re: package libpam-systemd 255.4-1ubuntu8.2 failed to install/upgrade: installed systemd package pre-removal script subprocess returned error exit status 1
*** This bug is a duplicate of bug 2076882 *** https://bugs.launchpad.net/bugs/2076882 ** This bug has been marked a duplicate of bug 2076882 package systemd-resolved 255.4-1ubuntu8.2 failed to install/upgrade: installed systemd package pre-removal script subprocess returned error exit status 1 -- 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/2076883 Title: package libpam-systemd 255.4-1ubuntu8.2 failed to install/upgrade: installed systemd package pre-removal script subprocess returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: while or after upgrade from ubuntu 23.10 to 24.04 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: libpam-systemd 255.4-1ubuntu8.2 ProcVersionSignature: Ubuntu 6.8.0-40.40.1-lowlatency 6.8.12 Uname: Linux 6.8.0-40-lowlatency x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Aug 12 23:54:33 2024 ErrorMessage: installed systemd package pre-removal script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: /usr/bin/python3.12, Python 3.12.3, unpackaged RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SourcePackage: systemd Title: package libpam-systemd 255.4-1ubuntu8.2 failed to install/upgrade: installed systemd package pre-removal script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-08-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2076883/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2076882] Re: package systemd-resolved 255.4-1ubuntu8.2 failed to install/upgrade: installed systemd package pre-removal script subprocess returned error exit status 1
According to the DpkgTerminalLog.txt, your system is not /usr-merged: ** * * The systemd package cannot be installed because this system does * not have a merged /usr. * * Please install the usrmerge package to convert this system to merged-/usr. * * For more information please read https://wiki.debian.org/UsrMerge. * ** Can you confirm that's accurate by showing the output of: $ for dir in /bin /sbin /lib; do readlink -f "$dir"; done ** 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/2076882 Title: package systemd-resolved 255.4-1ubuntu8.2 failed to install/upgrade: installed systemd package pre-removal script subprocess returned error exit status 1 Status in systemd package in Ubuntu: Incomplete Bug description: This happened while or after upgrading from ubuntu 23.10 to 24.04 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8.2 ProcVersionSignature: Ubuntu 6.8.0-40.40.1-lowlatency 6.8.12 Uname: Linux 6.8.0-40-lowlatency x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Aug 12 23:53:18 2024 ErrorMessage: installed systemd package pre-removal script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: /usr/bin/python3.12, Python 3.12.3, unpackaged RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SourcePackage: systemd Title: package systemd-resolved 255.4-1ubuntu8.2 failed to install/upgrade: installed systemd package pre-removal script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-08-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2076882/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2076666] Re: systemd-firstboot.service not running on first boot
As can be seen here, it's skipped because ConditionFirstBoot=yes fails (i.e. the boot does not meat the "first boot semantics[1][2]). Essentially, this is determined by /etc/machine-id. I *believe* on Ubuntu, our images are configured with an empty /etc/machine-id, so as defined by [2], a "first boot" of an Ubuntu image will not be considered a "first boot" by ConditionFirstBoot= standards. I can't speak to the intentions of "first boot" for Ubuntu images, but this is working as intended from a systemd perspective. [1] https://www.freedesktop.org/software/systemd/man/latest/systemd.unit.html#ConditionFirstBoot= [2] https://www.freedesktop.org/software/systemd/man/latest/machine-id.html#First%20Boot%20Semantics ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/207 Title: systemd-firstboot.service not running on first boot Status in systemd package in Ubuntu: Invalid Bug description: Verified for 24.04 and 24.10 where `systemd-firstboot.service` is present. Does not apply to earlier releases. ○ systemd-firstboot.service - First Boot Wizard Loaded: loaded (/usr/lib/systemd/system/systemd-firstboot.service; static) Active: inactive (dead) Condition: start condition unmet at Mon 2024-08-12 16:19:33 UTC; 9min ago Docs: man:systemd-firstboot(1) Aug 12 16:19:33 ubuntu systemd[1]: systemd-firstboot.service - First Boot Wizard was skipped because of an unmet condition check (ConditionFirstBoot=yes). Cloud partners have inquired as to whether the inactive behavior is intentional - and if not if this is something which will be fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/207/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055239] Re: Warning: The unit file, source configuration file or drop-ins of {apt-news, esm-cache}.service changed on disk. Run 'systemctl daemon-reload' to reload units.
The new upload is just a no-change rebuild for new build flags, so my
previous verification stands.
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done verification-done-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/2055239
Title:
Warning: The unit file, source configuration file or drop-ins of {apt-
news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
to reload units.
Status in snapd:
New
Status in systemd package in Ubuntu:
Fix Released
Status in ubuntu-advantage-tools package in Ubuntu:
Invalid
Status in systemd source package in Noble:
Fix Committed
Status in ubuntu-advantage-tools source package in Noble:
Invalid
Bug description:
[Impact]
systemd may incorrectly mark units as needing a daemon reload,
therefore unnecessarily printing the warning that a daemon-reload is
needed for the changes to take effect. This is misleading to users,
and particularly visible in cases like running apt update, since there
is an apt hook (/etc/apt/apt.conf.d/20apt-esm-hook.conf) that starts
two systemd services.
[Test Plan]
This bug can be triggered by running systemctl enable/disable on a
non-existent unit. After that, calling systemctl start/status/etc. will show a
false warning
that the unit changed on disk. Hence, to test, simply:
$ systemctl enable somethingthatdefinitelydoesnotexist.service
$ systemctl status systemd-resolved.service
$ apt update
On an effected system, warnings will be shown when calling both
commands after the "enable non-existent unit" step.
[Where problems could occur]
This patch fixes a previous commit by ensuring that the
manager->unit_file_state_outdated flag is set *only* when some
modifications succeeded, but the overall operation failed. In cases
where everything fails, it is not necessary to set the flag.
Since the patch is restricted to this area, any regressions from this
patch would most likely also be related to the NeedDaemonReload
property of units.
[Other information]
The patch is from upstream:
https://github.com/systemd/systemd/pull/32610/commits/d69cba3bfffc7b1e3197e2a34b459db13b1e1cb7#diff-84bbf3361da4139a5620a035ebd24f50a0e4d4ece7952dc2d8b4325e6ebdf6e0L2320
[Original Description]
I recently started seeing the following warning messages when I run
`apt update`.
$ sudo apt update
Warning: The unit file, source configuration file or drop-ins of
apt-news.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Warning: The unit file, source configuration file or drop-ins of
esm-cache.service changed on disk. Run 'systemctl daemon-reload' to reload
units.
...
apt-news.service for example is in /lib/systemd/system/apt-
news.service and it's a static file managed by the package. Does the
package maintenance script call systemd related hooks to reload the
config whenever the package gets updated?
$ systemctl cat apt-news.service
# /usr/lib/systemd/system/apt-news.service
# APT News is hosted at https://motd.ubuntu.com/aptnews.json and can include
# timely information related to apt updates available to your system.
...
$ dpkg -S /lib/systemd/system/apt-news.service
ubuntu-pro-client: /lib/systemd/system/apt-news.service
ProblemType: BugDistroRelease: Ubuntu 24.04
Package: ubuntu-pro-client 31.1
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 28 13:06:35 2024
InstallationDate: Installed on 2024-01-08 (51 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240104)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=SourcePackage: ubuntu-advantage-tools
UpgradeStatus: No upgrade log present (probably fresh install)
apparmor_logs.txt:
cloud-id.txt-error:
Failed running command 'cloud-id' [exit(2)]. Message: REDACTED config part
/etc/cloud/cloud.cfg.d/99-installer.cfg, insufficient permissions
REDACTED config part /etc/cloud/cloud.cfg.d/90-installer-network.cfg,
insufficient permissions
REDACTED config part /etc/cloud/cloud.cfg.d/99-installer.cfg, insufficient
permissions
REDACTED config part /etc/cloud/cloud.cfg.d/90-installer-network.cfg,
insufficient permissions
livepatch-status.txt-error: Invalid command specified
'/snap/bin/canonical-livepatch status'.
uaclient.conf:
contract_url: https://contracts.canonical.com
log_level: debug
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/2055239/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch
[Touch-packages] [Bug 2075968] Re: cannot login after upgrade from xubuntu 22.04 to 24.04
I dug into this a bit more, and it seems this issue occurs specifically for the user `ubuntu`. Before the upgrade, I copied the contents of /etc/shadow, and compared them to /etc/shadow after the first reboot after the upgrade. $ diff -u <(/etc/shadow) /home/ubuntu/before/shadow --- /dev/fd/63 2024-08-08 14:57:08.366981261 -0400 +++ /home/ubuntu/before/shadow 2024-08-08 14:20:17.158139781 -0400 @@ -1,4 +1,4 @@ -root:$y$j9T$NXJHsSu.l5iqspt5f8zzu/$CaDVSozRbChrGCSerFmv3Ck8lxPAQlj9D7MdG4Wrbm6:19943:0:9:7::: +root:!:19934:0:9:7::: daemon:*:19769:0:9:7::: bin:*:19769:0:9:7::: sys:*:19769:0:9:7::: @@ -25,6 +25,7 @@ tss:*:19769:0:9:7::: uuidd:*:19769:0:9:7::: tcpdump:*:19769:0:9:7::: +avahi-autoipd:*:19769:0:9:7::: usbmux:*:19769:0:9:7::: dnsmasq:*:19769:0:9:7::: kernoops:*:19769:0:9:7::: @@ -39,10 +40,5 @@ colord:*:19769:0:9:7::: pulse:*:19769:0:9:7::: hplip:*:19769:0:9:7::: -ubuntu:!$y$j9T$LreISCn8cWENVi4Mw1/cv.$Kkn9WO6CGCd/QUW8CUJoCHRZE8./VZmCfqDixXr8TU6:19934:0:9:7::: +ubuntu:$y$j9T$LreISCn8cWENVi4Mw1/cv.$Kkn9WO6CGCd/QUW8CUJoCHRZE8./VZmCfqDixXr8TU6:19934:0:9:7::: sshd:*:19943:0:9:7::: -snapd-range-524288-root:!:19943:: -snap_daemon:!:19943:: -dhcpcd:!:19943:: -cups-browsed:!:19943:: -polkitd:!*:19943:: We can see that the entry for `ubuntu` changed. Looking at the journal, from that boot, it seems that cloud-init changed the passwd: $ journalctl -b -1 --grep ubuntu Aug 08 14:50:33 xubuntu kernel: Linux version 6.8.0-40-generic (buildd@lcy02-amd64-075) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.2.0-23ubuntu4) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #40-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 5 10:34:03 UTC 2024 (Ubuntu 6.8.0-40.40-generic 6.8.12) Aug 08 14:50:33 xubuntu kernel: Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (Ubuntu Core 2019): c1d57b8f6b743f23ee41f4f7ee292f06eecadfb9' Aug 08 14:50:33 xubuntu systemd[1]: systemd 255.4-1ubuntu8.2 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified) Aug 08 14:50:33 xubuntu systemd[1]: Hostname set to . Aug 08 14:50:34 xubuntu cloud-init[564]: Cloud-init v. 24.1.3-0ubuntu3.3 running 'init-local' at Thu, 08 Aug 2024 18:50:34 +. Up 4.19 seconds. Aug 08 14:50:34 xubuntu systemd-resolved[632]: Using system hostname 'xubuntu'. Aug 08 14:50:35 xubuntu cloud-init[760]: Cloud-init v. 24.1.3-0ubuntu3.3 running 'init' at Thu, 08 Aug 2024 18:50:35 +. Up 5.51 seconds. Aug 08 14:50:36 xubuntu passwd[869]: password for 'ubuntu' changed by 'root' Aug 08 14:50:37 xubuntu cloud-init[760]: SHA256:GGMsp52cN8EAJYlqOdJArAxzOEhwfitNlPBgGQCVOTE root@xubuntu Aug 08 14:50:37 xubuntu cloud-init[760]: SHA256:TcJuGTUBYjDMo+GVodNfGgE5P5FeszDy/8QddKQanJE root@xubuntu Aug 08 14:50:37 xubuntu cloud-init[760]: SHA256:hjnsPHfUrAQbIkiRETrAszNsqZppRrI3dhTU4BGKy5s root@xubuntu Looking at /etc/cloud/cloud.cfg, I see the lock_passwd[1] option set for `ubuntu`: # System and/or distro specific settings # (not accessible to handlers/transforms) system_info: # This will affect which distro class gets used distro: ubuntu # Default user name + that default users groups (if added/used) default_user: name: ubuntu lock_passwd: True gecos: Ubuntu groups: [adm, cdrom, dip, lxd, sudo] sudo: ["ALL=(ALL) NOPASSWD:ALL"] shell: /bin/bash The docs even say that cloud-init will apply lock_passwd for existing users. This seems wrong. [1] https://cloudinit.readthedocs.io/en/latest/reference/modules.html#users- and-groups ** Package changed: pam (Ubuntu) => cloud-init (Ubuntu) ** Summary changed: - cannot login after upgrade from xubuntu 22.04 to 24.04 + cloud-init locks out user `ubuntu` after upgrade from 22.04 to 24.04 ** Changed in: cloud-init (Ubuntu) Importance: Critical => High ** Changed in: cloud-init (Ubuntu Noble) Importance: Critical => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2075968 Title: cloud-init locks out user `ubuntu` after upgrade from 22.04 to 24.04 Status in cloud-init package in Ubuntu: New Status in cloud-init source package in Noble: New Bug description: After performing an upgrade, and then rebooting, I am no longer able to login with my user "ubuntu". I get an authentication failure with both the graphical login screen, and when attempting to login on a non-graphical tty. Dropping to a rescue shell, I can see this in the logs: root@xubuntu:~# journalctl -b --grep pam Aug 02 11:52:45 xubuntu systemd[1]: systemd 255.4-1ubuntu8.2 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECC
[Touch-packages] [Bug 2055239] Re: Warning: The unit file, source configuration file or drop-ins of {apt-news, esm-cache}.service changed on disk. Run 'systemctl daemon-reload' to reload units.
I have verified the fix using systemd 255.4-1ubuntu3.3 from noble- proposed. In a new container, I can see the issue at first: nr@six:~$ lxc launch ubuntu:noble lp2055239 Launching lp2055239 nr@six:~$ lxc exec lp2055239 bash root@lp2055239:~# systemctl enable somethingthatdefinitelydoesnotexist.service Failed to enable unit: Unit file somethingthatdefinitelydoesnotexist.service does not exist. root@lp2055239:~# systemctl status systemd-resolved.service Warning: The unit file, source configuration file or drop-ins of systemd-resolved.service changed on disk. Run> ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; preset: enabled) Active: active (running) since Thu 2024-08-08 13:34:53 UTC; 43s ago Docs: man:systemd-resolved.service(8) man:org.freedesktop.resolve1(5) https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients Main PID: 176 (systemd-resolve) Status: "Processing requests..." Tasks: 1 (limit: 18947) Memory: 2.6M (peak: 3.3M) CPU: 168ms CGroup: /system.slice/systemd-resolved.service └─176 /usr/lib/systemd/systemd-resolved Aug 08 13:34:52 lp2055239 systemd[1]: Starting systemd-resolved.service - Network Name Resolution... Aug 08 13:34:52 lp2055239 systemd-resolved[176]: Positive Trust Anchors: Aug 08 13:34:52 lp2055239 systemd-resolved[176]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bb> Aug 08 13:34:52 lp2055239 systemd-resolved[176]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-a> Aug 08 13:34:53 lp2055239 systemd-resolved[176]: Using system hostname 'lp2055239'. Aug 08 13:34:53 lp2055239 systemd[1]: Started systemd-resolved.service - Network Name Resolution. root@lp2055239:~# apt update Warning: The unit file, source configuration file or drop-ins of apt-news.service changed on disk. Run 'systemctl daemon-reload' to reload units. Warning: The unit file, source configuration file or drop-ins of esm-cache.service changed on disk. Run 'systemctl daemon-reload' to reload units. Hit:1 http://archive.ubuntu.com/ubuntu noble InRelease Get:2 http://archive.ubuntu.com/ubuntu noble-updates InRelease [126 kB] Get:3 http://security.ubuntu.com/ubuntu noble-security InRelease [126 kB] Get:4 http://archive.ubuntu.com/ubuntu noble-backports InRelease [126 kB] Get:5 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages [15.0 MB] 0% [5 Packages 8229 kB/15.0 MB 55%]^C Then, I enabled noble-proposed, upgraded systemd, and the issue was gone: root@lp2055239:~# cat > /etc/apt/sources.list.d/noble-proposed.sources << EOF > Types: deb URIs: http://us.archive.ubuntu.com/ubuntu/ Suites: noble-proposed Components: main restricted universe multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg > EOF root@lp2055239:~# apt update ... SNIP ... root@lp2055239:~# apt policy systemd systemd: Installed: 255.4-1ubuntu8.2 Candidate: 255.4-1ubuntu8.2 Version table: 255.4-1ubuntu8.3 100 100 http://us.archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages *** 255.4-1ubuntu8.2 500 500 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages 100 /var/lib/dpkg/status 255.4-1ubuntu8 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages root@lp2055239:~# apt install systemd -t noble-proposed ... SNIP ... root@lp2055239:~# apt policy systemd systemd: Installed: 255.4-1ubuntu8.3 Candidate: 255.4-1ubuntu8.3 Version table: *** 255.4-1ubuntu8.3 100 100 http://us.archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages 100 /var/lib/dpkg/status 255.4-1ubuntu8.2 500 500 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages 255.4-1ubuntu8 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages root@lp2055239:~# systemctl enable somethingthatdefinitelydoesnotexist.service Failed to enable unit: Unit file somethingthatdefinitelydoesnotexist.service does not exist. root@lp2055239:~# systemctl status systemd-resolved.service ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; preset: enabled) Active: active (running) since Thu 2024-08-08 13:37:39 UTC; 12s ago Docs: man:systemd-resolved.service(8) man:org.freedesktop.resolve1(5) https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients Main PID: 1681 (systemd-resolve) Status: "Processing requests..." Tasks: 1 (limit: 18947) Memory: 2.6M (peak: 3.3M) CPU: 102ms CGroup: /system.slice/systemd-resolved.s
[Touch-packages] [Bug 2003027] Re: fq_codel qdisc compiled but not enabled on 22.10
** Changed in: procps (Ubuntu Oracular) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/2003027 Title: fq_codel qdisc compiled but not enabled on 22.10 Status in Ubuntu: In Progress Status in procps package in Ubuntu: Fix Committed Status in The Noble Numbat: Confirmed Status in procps source package in Noble: Confirmed Status in The Oracular Oriole: In Progress Status in procps source package in Oracular: Fix Committed Bug description: [ Impact ] Starting with Ubuntu 22.10, the default qdisc regressed to pfifo_fast. This is due to a change we merged from Debian, removing systemd's /usr/lib/50-default.conf file. pfifo_fast does not prevent bufferbloat issues, severely degrading networking performance on Ubuntu systems. [ Test Plan ] On an Ubuntu VM, check that net.core.default_qdisc is set to 'fq_codel'. `tc qdisc show` should also confirm fq_codel is being used. halves@noble-vm:~$ sysctl net.core.default_qdisc net.core.default_qdisc = fq_codel halves@noble-vm:~$ tc qdisc show qdisc noqueue 0: dev lo root refcnt 2 qdisc mq 0: dev enp5s0 root qdisc fq_codel 0: dev enp5s0 parent :1 limit 10240p flows 1024 quantum 1514 target 5ms interval 100ms memory_limit 32Mb ecn drop_batch 64 [ Where Problems Could Occur ] Users relying on the default pfifo_fast qdisc could see different networking behavior. [ Other Info ] Instead of adding a sysctl.conf file, Debian has decided to change their default kernel configs to use fq_codel. This has the disadvantage of being "hidden" from end users, instead of being a queryable setting in e.g. /etc/sysctl.d/, and all kernel documentation still refers to pfifo_fast as being the default. Systemd's /usr/lib/50-default.conf file includes a lot of other settings that are either overruled elsewhere (e.g. from procps) or are entirely missing from our stable releases. Introducing a diff from Debian to ship this file only for the net.core.default_qdisc changes seems excessive, so having a dedicated place under procps where other similar toggles are already present seems like the more appropriate solution. -- [ Original Description ] fq_codel has been the default in ubuntu since #1436945 It is also now the default in debian. Somewhere between 22.04 and 22.10 though, it stopped being enabled by systemd? (it used to be enabled there via a sysctl), and thus 22.10 (I tried both ubuntu server and ubuntu studio) doesn't have it on. I rather *immediately* noticed this huge regression (I run my ethernet at 100Mbit, and thus immediately saw 400+ms latency) - and I hope it can be fixed in the next release? it can also be made the default via compiling it into the kernel as a kernel default. Aggh! death to fifos! root@localhost:~# sysctl -a | grep qdisc net.core.default_qdisc = pfifo_fast disc pfifo_fast 0: dev eth0 parent :1 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1 Sent 5250 bytes 53 pkt (dropped 0, overlimits 0 requeues 0) backlog 0b 0p requeues 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2003027/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055239] Re: Warning: The unit file, source configuration file or drop-ins of {apt-news, esm-cache}.service changed on disk. Run 'systemctl daemon-reload' to reload units.
** Changed in: systemd (Ubuntu Noble)
Status: Triaged => In Progress
** Changed in: systemd (Ubuntu Noble)
Milestone: None => ubuntu-24.04.1
--
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/2055239
Title:
Warning: The unit file, source configuration file or drop-ins of {apt-
news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
to reload units.
Status in snapd:
New
Status in systemd package in Ubuntu:
Fix Released
Status in ubuntu-advantage-tools package in Ubuntu:
Invalid
Status in systemd source package in Noble:
In Progress
Status in ubuntu-advantage-tools source package in Noble:
Invalid
Bug description:
[Impact]
systemd may incorrectly mark units as needing a daemon reload,
therefore unnecessarily printing the warning that a daemon-reload is
needed for the changes to take effect. This is misleading to users,
and particularly visible in cases like running apt update, since there
is an apt hook (/etc/apt/apt.conf.d/20apt-esm-hook.conf) that starts
two systemd services.
[Test Plan]
This bug can be triggered by running systemctl enable/disable on a
non-existent unit. After that, calling systemctl start/status/etc. will show a
false warning
that the unit changed on disk. Hence, to test, simply:
$ systemctl enable somethingthatdefinitelydoesnotexist.service
$ systemctl status systemd-resolved.service
$ apt update
On an effected system, warnings will be shown when calling both
commands after the "enable non-existent unit" step.
[Where problems could occur]
This patch fixes a previous commit by ensuring that the
manager->unit_file_state_outdated flag is set *only* when some
modifications succeeded, but the overall operation failed. In cases
where everything fails, it is not necessary to set the flag.
Since the patch is restricted to this area, any regressions from this
patch would most likely also be related to the NeedDaemonReload
property of units.
[Other information]
The patch is from upstream:
https://github.com/systemd/systemd/pull/32610/commits/d69cba3bfffc7b1e3197e2a34b459db13b1e1cb7#diff-84bbf3361da4139a5620a035ebd24f50a0e4d4ece7952dc2d8b4325e6ebdf6e0L2320
[Original Description]
I recently started seeing the following warning messages when I run
`apt update`.
$ sudo apt update
Warning: The unit file, source configuration file or drop-ins of
apt-news.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Warning: The unit file, source configuration file or drop-ins of
esm-cache.service changed on disk. Run 'systemctl daemon-reload' to reload
units.
...
apt-news.service for example is in /lib/systemd/system/apt-
news.service and it's a static file managed by the package. Does the
package maintenance script call systemd related hooks to reload the
config whenever the package gets updated?
$ systemctl cat apt-news.service
# /usr/lib/systemd/system/apt-news.service
# APT News is hosted at https://motd.ubuntu.com/aptnews.json and can include
# timely information related to apt updates available to your system.
...
$ dpkg -S /lib/systemd/system/apt-news.service
ubuntu-pro-client: /lib/systemd/system/apt-news.service
ProblemType: BugDistroRelease: Ubuntu 24.04
Package: ubuntu-pro-client 31.1
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 28 13:06:35 2024
InstallationDate: Installed on 2024-01-08 (51 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240104)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=SourcePackage: ubuntu-advantage-tools
UpgradeStatus: No upgrade log present (probably fresh install)
apparmor_logs.txt:
cloud-id.txt-error:
Failed running command 'cloud-id' [exit(2)]. Message: REDACTED config part
/etc/cloud/cloud.cfg.d/99-installer.cfg, insufficient permissions
REDACTED config part /etc/cloud/cloud.cfg.d/90-installer-network.cfg,
insufficient permissions
REDACTED config part /etc/cloud/cloud.cfg.d/99-installer.cfg, insufficient
permissions
REDACTED config part /etc/cloud/cloud.cfg.d/90-installer-network.cfg,
insufficient permissions
livepatch-status.txt-error: Invalid command specified
'/snap/bin/canonical-livepatch status'.
uaclient.conf:
contract_url: https://contracts.canonical.com
log_level: debug
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/2055239/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~tou
[Touch-packages] [Bug 2055239] Re: Warning: The unit file, source configuration file or drop-ins of {apt-news, esm-cache}.service changed on disk. Run 'systemctl daemon-reload' to reload units.
** Description changed:
+ [Impact]
+
+ systemd may incorrectly mark units as needing a daemon reload, therefore
+ unnecessarily printing the warning that a daemon-reload is needed for
+ the changes to take effect. This is misleading to users, and
+ particularly visible in cases like running apt update, since there is an
+ apt hook (/etc/apt/apt.conf.d/20apt-esm-hook.conf) that starts two
+ systemd services.
+
+ [Test Plan]
+
+ This bug can be triggered by running systemctl enable/disable on a
non-existent unit. After that, calling systemctl start/status/etc. will show a
false warning
+ that the unit changed on disk. Hence, to test, simply:
+
+ $ systemctl enable somethingthatdefinitelydoesnotexist.service
+ $ systemctl status systemd-resolved.service
+ $ apt update
+
+ On an effected system, warnings will be shown when calling both commands
+ after the "enable non-existent unit" step.
+
+ [Where problems could occur]
+
+ This patch fixes a previous commit by ensuring that the
+ manager->unit_file_state_outdated flag is set *only* when some
+ modifications succeeded, but the overall operation failed. In cases
+ where everything fails, it is not necessary to set the flag.
+
+ Since the patch is restricted to this area, any regressions from this
+ patch would most likely also be related to the NeedDaemonReload property
+ of units.
+
+ [Other information]
+
+ The patch is from upstream:
+
https://github.com/systemd/systemd/pull/32610/commits/d69cba3bfffc7b1e3197e2a34b459db13b1e1cb7#diff-84bbf3361da4139a5620a035ebd24f50a0e4d4ece7952dc2d8b4325e6ebdf6e0L2320
+
+ [Original Description]
+
I recently started seeing the following warning messages when I run `apt
update`.
$ sudo apt update
Warning: The unit file, source configuration file or drop-ins of
apt-news.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Warning: The unit file, source configuration file or drop-ins of
esm-cache.service changed on disk. Run 'systemctl daemon-reload' to reload
units.
...
apt-news.service for example is in /lib/systemd/system/apt-news.service
and it's a static file managed by the package. Does the package
maintenance script call systemd related hooks to reload the config
whenever the package gets updated?
$ systemctl cat apt-news.service
# /usr/lib/systemd/system/apt-news.service
# APT News is hosted at https://motd.ubuntu.com/aptnews.json and can include
# timely information related to apt updates available to your system.
...
$ dpkg -S /lib/systemd/system/apt-news.service
ubuntu-pro-client: /lib/systemd/system/apt-news.service
ProblemType: BugDistroRelease: Ubuntu 24.04
Package: ubuntu-pro-client 31.1
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 28 13:06:35 2024
InstallationDate: Installed on 2024-01-08 (51 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240104)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=SourcePackage: ubuntu-advantage-tools
UpgradeStatus: No upgrade log present (probably fresh install)
apparmor_logs.txt:
cloud-id.txt-error:
Failed running command 'cloud-id' [exit(2)]. Message: REDACTED config part
/etc/cloud/cloud.cfg.d/99-installer.cfg, insufficient permissions
REDACTED config part /etc/cloud/cloud.cfg.d/90-installer-network.cfg,
insufficient permissions
REDACTED config part /etc/cloud/cloud.cfg.d/99-installer.cfg, insufficient
permissions
REDACTED config part /etc/cloud/cloud.cfg.d/90-installer-network.cfg,
insufficient permissions
livepatch-status.txt-error: Invalid command specified
'/snap/bin/canonical-livepatch status'.
uaclient.conf:
contract_url: https://contracts.canonical.com
log_level: debug
--
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/2055239
Title:
Warning: The unit file, source configuration file or drop-ins of {apt-
news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
to reload units.
Status in snapd:
New
Status in systemd package in Ubuntu:
Fix Released
Status in ubuntu-advantage-tools package in Ubuntu:
Invalid
Status in systemd source package in Noble:
Triaged
Status in ubuntu-advantage-tools source package in Noble:
Invalid
Bug description:
[Impact]
systemd may incorrectly mark units as needing a daemon reload,
therefore unnecessarily printing the warning that a daemon-reload is
needed for the changes to take effect. This is misleading to users,
and particularly visible in cases like running apt update, since there
is an apt hook (/etc/apt/apt.conf.d/20apt-esm-hook.conf) th
[Touch-packages] [Bug 2067907] Re: systemd tools fail to mount disk images with btrfs filesystems
** Changed in: systemd (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2067907 Title: systemd tools fail to mount disk images with btrfs filesystems Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Noble: Fix Released Bug description: SRU Justification [Impact] In Ubuntu Noble, systemd-repart fail to mount images with btrfs filesystems in them. This is because the kernel removed the "norecovery" mount option which systemd-repart adds in when mounting filesystems from disk images. Commit which removed "norecovery" in the kernel: https://github.com/torvalds/linux/commit/a1912f712188291f9d7d434fba155461f1ebef66. [Fix] The issue was worked around upstream in systemd in https://github.com/systemd/systemd/pull/32892 and https://github.com/systemd/systemd/pull/32948. [Test] To reproduce: git clone https://github.com/systemd/mkosi cd mkosi bin/mkosi -d fedora -t disk --tools-tree=default -f sudo systemd-repart --image mkosi.output/image.raw The last command will fail with "Failed to mount image: Invalid argument". After backporting the two systemd commits, the last command will succeed. [Regression Potential] Low, the systemd commits only change behavior for btrfs filesystems, which are currently not working at all. The commits have been backported to the systemd stable releases and we've had no reports of any issues caused by backporting these commits. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2067907/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2075988] Re: Add comments to default config to explain Ubuntu deltas
We currently have: ``` Include /etc/ssh/sshd_config.d/*.conf # When systemd socket activation is used (the default), the socket # configuration must be re-generated after changing Port, AddressFamily, or # ListenAddress. # # For changes to take effect, run: # # systemctl daemon-reload # systemctl restart ssh.socket # #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: ``` in the default sshd_config on oracular. I started an SRU for noble that was kicked out by a security update, but I will re-upload that soon. Is this what you are looking for? Or something different? ** 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/2075988 Title: Add comments to default config to explain Ubuntu deltas Status in openssh package in Ubuntu: Incomplete Bug description: Hello, reading https://discourse.ubuntu.com/t/sshd-now-uses-socket- based-activation-ubuntu-22-10-and-later/30189/44 a great point is made here. Can we put some comments in the default config explaining the deltas we make? This would be the most visible place for end-users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2075988/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2073356] Re: Choose password for new keyring the first time chromium-browser is started on each session
** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2073356 Title: Choose password for new keyring the first time chromium-browser is started on each session Status in chromium-browser package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: Invalid Bug description: I get this popup the first time I start chromium-browser: https://askubuntu.com/questions/1446379/why-am-i-always-asked-to- create-a-new-keyring either manually or via a startup script. Closing and restarting does not create the popup until I reboot. After the reboot, the password prompt is back again. What I do is just enter enter enter with empty password and life moves on. Under "Passwords and Keys" in settings, I just get a new "Default keyring" every time this happens. My disk is encrypted, I don't have a password to login, and I don't want to type any passwords after unlocking my disk during boot. Ubuntu 24.04, snap chromium version 126.0.6478.126. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2073356/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2074302] Re: Asus Laptop (R558U) does not suspend after upgrade to 24.04
This does not sound like a systemd bug, but more like kernel or the nouveau driver. From the attached CurrentDmesg.txt: [ 248.207134] nouveau :01:00.0: Enabling HDA controller [ 248.310486] [ cut here ] [ 248.310488] WARNING: CPU: 0 PID: 1530 at kernel/workqueue.c:1790 __queue_work.part.0+0x30c/0x3e0 [ 248.310496] Modules linked in: rfcomm snd_seq_dummy snd_hrtimer ccm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) qrtr snd_sof_pci_intel_skl snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils hid_generic soundwire_generic_allocation hidp soundwire_bus snd_soc_avs snd_soc_hda_codec snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi cmac algif_hash algif_skcipher snd_hda_codec_hdmi af_alg bnep snd_soc_core snd_ctl_led snd_compress ac97_bus snd_hda_codec_realtek snd_pcm_dmaengine snd_hda_codec_generic snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec snd_hda_core snd_hwdep uvcvideo snd_pcm videobuf2_vmalloc rtl8723be uvc videobuf2_memops videobuf2_v4l2 snd_seq_midi intel_rapl_msr mei_hdcp mei_pxp ee1004 joydev btcoexist intel_tcc_cooling rtsx_usb_ms snd_seq_midi_event rtl8723_common nouveau memstick rtl_pci x 86_pkg_temp_thermal rtlwifi [ 248.310558] processor_thermal_device_pci_legacy intel_powerclamp snd_rawmidi processor_thermal_device mac80211 coretemp videodev processor_thermal_wt_hint btusb kvm_intel btrtl processor_thermal_rfim btintel mfd_aaeon drm_gpuvm asus_nb_wmi btbcm processor_thermal_rapl kvm snd_seq intel_rapl_common btmtk irqbypass snd_seq_device asus_wmi processor_thermal_wt_req snd_timer videobuf2_common processor_thermal_power_floor drm_exec ledtrig_audio cfg80211 bluetooth mc mei_me i2c_i801 gpu_sched rapl processor_thermal_mbox sparse_keymap snd intel_cstate ecdh_generic ecc libarc4 platform_profile mxm_wmi i2c_smbus soundcore drm_ttm_helper i915 intel_xhci_usb_role_switch intel_pch_thermal mei int3403_thermal drm_buddy intel_soc_dts_iosf binfmt_misc int340x_thermal_zone ttm elan_i2c drm_display_helper cec rc_core intel_pmc_core i2c_algo_bit intel_vsec pmt_telemetry pmt_class int3400_thermal asus_wireless acpi_thermal_rel acpi_pad input_leds mac_hid serio_raw msr parport_pc ppdev lp parport ef i_pstore nfnetlink dmi_sysfs ip_tables [ 248.310628] x_tables autofs4 dm_crypt rtsx_usb_sdmmc rtsx_usb crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic ghash_clmulni_intel sha256_ssse3 sha1_ssse3 r8169 xhci_pci ahci realtek intel_lpss_pci i2c_hid_acpi intel_lpss i2c_hid xhci_pci_renesas libahci hid idma64 video wmi aesni_intel crypto_simd cryptd [ 248.310654] CPU: 0 PID: 1530 Comm: systemd-logind Tainted: G IOE 6.8.0-38-generic #38-Ubuntu [ 248.310657] Hardware name: ASUSTeK COMPUTER INC. X556UR/X556UR, BIOS X556UR.309 10/24/2016 [ 248.310659] RIP: 0010:__queue_work.part.0+0x30c/0x3e0 [ 248.310663] Code: 4c 8b 30 49 89 c7 49 39 fe 0f 84 5a fe ff ff 0f 0b e9 53 fe ff ff 65 8b 3d cd 72 b0 44 e8 3c c0 ff ff 89 45 d0 e9 23 fd ff ff <0f> 0b e9 e2 fe ff ff 48 8b 0b 44 89 e0 49 8d 57 68 83 c8 07 83 e1 [ 248.310665] RSP: 0018:a6c1011e77a8 EFLAGS: 00010082 [ 248.310668] RAX: RBX: 965c8ec1f4c0 RCX: [ 248.310670] RDX: RSI: RDI: [ 248.310672] RBP: a6c1011e77e0 R08: R09: [ 248.310673] R10: R11: R12: 2000 [ 248.310675] R13: 965c8ec1f4c8 R14: 9660eb434500 R15: 965c801d8a00 [ 248.310677] FS: 752bdd8264c0() GS:9660eb40() knlGS: [ 248.310679] CS: 0010 DS: ES: CR0: 80050033 [ 248.310681] CR2: 7acac820 CR3: 00011168c005 CR4: 003706f0 [ 248.310683] Call Trace: [ 248.310685] [ 248.310688] ? show_regs+0x6d/0x80 [ 248.310692] ? __warn+0x89/0x160 [ 248.310696] ? __queue_work.part.0+0x30c/0x3e0 [ 248.310700] ? report_bug+0x17e/0x1b0 [ 248.310705] ? handle_bug+0x51/0xa0 [ 248.310709] ? exc_invalid_op+0x18/0x80 [ 248.310712] ? asm_exc_invalid_op+0x1b/0x20 [ 248.310718] ? __queue_work.part.0+0x30c/0x3e0 [ 248.310722] ? __queue_work.part.0+0x14b/0x3e0 [ 248.310725] ? nvkm_ioctl+0x132/0x2b0 [nouveau] [ 248.310829] ? __pfx_pci_pm_runtime_resume+0x10/0x10 [ 248.310833] __queue_work+0x36/0xa0 [ 248.310838] queue_work_on+0x67/0x70 [ 248.310841] nouveau_display_hpd_resume+0x49/0x60 [nouveau] [ 248.310977] nouveau_pmops_runtime_resume+0xef/0x1a0 [nouveau] [ 248.32] pci_pm_runtime_resume+0xa0/0x100 [ 248.36] __rpm_callback+0x4d/0x170 [ 248.311120] ? dput+0x3f/0x1b0 [ 248.311123] rpm_callback+0x6d/0x80 [ 248.311126] ? __pfx_pci_pm_runtime_resume+0x10/0x10 [ 248.311129] rpm_resume+0x594/0x7e0 [ 248.311132] ? mntput+0x24/0x50 [ 248.31113
[Touch-packages] [Bug 2076023] Re: Failed to apply 'Match' directive in sshd_config with sshd-socket-generator
Thank you for the detailed bug report. I am not yet sure the best way to fix this, but I was able to reproduce using your instructions. ** Changed in: openssh (Ubuntu) Status: New => Confirmed ** Changed in: openssh (Ubuntu) Importance: Undecided => 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/2076023 Title: Failed to apply 'Match' directive in sshd_config with sshd-socket- generator Status in openssh package in Ubuntu: Confirmed Bug description: When using the Match statement in sshd_config or sshd_config.d/*.conf with socket activation(not classic method), sshd does not start as expected. Environment: Ubuntu: Ubuntu 24.04 LTS OpenSSH Server: 1:9.6p1-3ubuntu13.4 Steps to Reproduce: /etc/ssh/sshd_config ``` Include /etc/ssh/sshd_config.d/*.conf Port 22 Port 2 KbdInteractiveAuthentication no UsePAM yes X11Forwarding yes PrintMotd no AcceptEnv LANG LC_* Subsystem sftp/usr/lib/openssh/sftp-server Match LocalPort 2 PasswordAuthentication no PubkeyAuthentication yes ``` command: sudo systemctl daemon-reload && sudo systemctl restart ssh.socket Expected Behavior: sshd should listen on both ports 22 and 2. When connecting via port 2, password login should not be allowed and only public key authentication should be permitted. Actual Behavior: sshd only listens on port 22 and not on port 2. The configuration is not correctly applied. After daemon-reload, the output from journalctl is as follows: $ sudo journalctl -t (sd-exec- Aug 04 12:47:36 ults (sd-exec-[479259]: /usr/lib/systemd/system-generators/sshd-socket-generator failed with exit status 255. Additional Information: 1.Using sshd -T -C to test the configuration produces the following result: $ sudo sshd -T -C lport=22 | grep passwordauthentication passwordauthentication yes $ sudo sshd -T -C lport=2 | grep passwordauthentication passwordauthentication no 2.The output when manually running /usr/lib/systemd/system-generators/sshd-socket-generator is: $ sudo /usr/lib/systemd/system-generators/sshd-socket-generator ./ 'Match LocalPort' in configuration but 'lport' not in connection test specification. 3.I have test some cases, if sshd-socket-generator can not handle config rightly, sshd seems to run with default config. And I also noticed that there is no test case about the Match directive in https://git.launchpad.net/ubuntu/+source/openssh/tree/debian/tests/sshd-socket-generator. I guess the root cause of the issue lies in the sshd-socket-generator not correctly handling the Match directive. And a detailed assessment of potential security issues which caused by this bug is needed. If socket activation is to be widely adopted, this issue will undoubtedly be a significant stumbling block. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2076023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2075968] Re: cannot login after upgrade from xubuntu 22.04 to 24.04
No it was not. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2075968 Title: cannot login after upgrade from xubuntu 22.04 to 24.04 Status in pam package in Ubuntu: New Status in pam source package in Noble: New Bug description: After performing an upgrade, and then rebooting, I am no longer able to login with my user "ubuntu". I get an authentication failure with both the graphical login screen, and when attempting to login on a non-graphical tty. Dropping to a rescue shell, I can see this in the logs: root@xubuntu:~# journalctl -b --grep pam Aug 02 11:52:45 xubuntu systemd[1]: systemd 255.4-1ubuntu8.2 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OP> Aug 02 11:53:00 xubuntu lightdm[1422]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=115) by (uid=0) Aug 02 11:53:00 xubuntu (systemd)[1472]: pam_unix(systemd-user:session): session opened for user lightdm(uid=115) by lightdm(uid=0) Aug 02 11:53:00 xubuntu lightdm[1422]: gkr-pam: couldn't unlock the login keyring. Aug 02 11:53:01 xubuntu lightdm[1584]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "ubuntu" Aug 02 11:53:40 xubuntu lightdm[1584]: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=ubuntu Aug 02 11:53:42 xubuntu lightdm[1604]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "ubuntu" Aug 02 11:53:49 xubuntu lightdm[1604]: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=ubuntu Aug 02 11:53:51 xubuntu lightdm[1605]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "ubuntu" Aug 02 11:53:58 xubuntu lightdm[1607]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "root" Aug 02 11:53:59 xubuntu lightdm[1607]: gkr-pam: unable to locate daemon control file Aug 02 11:53:59 xubuntu lightdm[1607]: gkr-pam: stashed password to try later in open session Aug 02 11:53:59 xubuntu lightdm[1422]: pam_unix(lightdm-greeter:session): session closed for user lightdm Aug 02 11:53:59 xubuntu lightdm[1607]: pam_unix(lightdm:session): session opened for user root(uid=0) by (uid=0) Aug 02 11:54:00 xubuntu (systemd)[1614]: pam_unix(systemd-user:session): session opened for user root(uid=0) by root(uid=0) Aug 02 11:54:00 xubuntu lightdm[1607]: gkr-pam: unlocked login keyring Aug 02 11:54:10 xubuntu (sd-pam)[1473]: pam_unix(systemd-user:session): session closed for user lightdm Aug 02 11:55:01 xubuntu CRON[2417]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0) Aug 02 11:55:01 xubuntu CRON[2417]: pam_unix(cron:session): session closed for user root Other notes: (1) During the upgrade, the screen saver was disabled. I know this has been a bug in the past, but I do not believe it is the cause here. (2) A work around for this is to drop into a rescue shell, and from root, run e.g. `passwd ubuntu` to reset the user's password. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libpam-modules 1.5.3-5ubuntu5.1 ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8 Uname: Linux 6.8.0-39-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: XFCE Date: Fri Aug 2 11:55:51 2024 InstallationDate: Installed on 2024-07-30 (3 days ago) InstallationMedia: Xubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: pam UpgradeStatus: Upgraded to noble on 2024-08-02 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-04-23T07:30:10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2075968/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2075104] Re: user session is randomly terminated by systemd-oom when the system is left alone for a while
** Changed in: systemd (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2075104 Title: user session is randomly terminated by systemd-oom when the system is left alone for a while Status in systemd package in Ubuntu: New Bug description: I was surprised last week to find that my computer had logged me out when I had left it alone for some 15 minutes. I did not bother to research at the time and did not see any reason as the problem did not manifest again . Then today, it happens again. The circumstances are similar: I leave the system long enough for the screen to power off and come back to find myself kicked out of my session. Yes, kicked out, not simply locked out. I need to log in again and find that all running apps and open files have all been closed. My journal would appear to show that gnome-shell got stopped as a consequence of systemd-oomd killing several applications (see the included journalctl snippet - mind that the output is in reverse order (journalctl -r)). Should not oomd terminate single applications instead of complete user sessions? And I do have some doubts about the statistics listed in the journal. One of the killed apps is reported as consuming over 22GB or RAM (out of 32). I have been using that app for many years and cannot remember having see it use more than a few GB. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd-oomd 255.4-1ubuntu8.2 ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8 Uname: Linux 6.8.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jul 30 04:00:27 2024 InstallationDate: Installed on 2022-03-27 (855 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2075104/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055239] Re: Warning: The unit file, source configuration file or drop-ins of {apt-news, esm-cache}.service changed on disk. Run 'systemctl daemon-reload' to reload units.
This issue can be seen with any actual unit after e.g. enabling or
disabling a non-existent unit. For example,
root@n:~# systemctl status ssh.socket
● ssh.socket - OpenBSD Secure Shell server socket
Loaded: loaded (/usr/lib/systemd/system/ssh.socket; enabled; preset:
enabled)
Active: active (listening) since Wed 2024-07-31 19:51:18 UTC; 5min ago
Triggers: ● ssh.service
Listen: [::]:22 (Stream)
CGroup: /system.slice/ssh.socket
Jul 31 19:55:15 n systemd[1]: ssh.socket: Trying to enqueue job
ssh.socket/start/replace
Jul 31 19:55:15 n systemd[1]: ssh.socket: Installed new job ssh.socket/start as
734
Jul 31 19:55:15 n systemd[1]: ssh.socket: Enqueued job ssh.socket/start as 734
Jul 31 19:55:15 n systemd[1]: ssh.socket: Job 734 ssh.socket/start finished,
result=done
Jul 31 19:55:53 n systemd[1]: ssh.socket: Changed dead -> listening
Jul 31 19:56:05 n systemd[1]: ssh.socket: Trying to enqueue job
ssh.socket/start/replace
Jul 31 19:56:05 n systemd[1]: ssh.socket: Installed new job ssh.socket/start as
825
Jul 31 19:56:05 n systemd[1]: ssh.socket: Enqueued job ssh.socket/start as 825
Jul 31 19:56:05 n systemd[1]: ssh.socket: Job 825 ssh.socket/start finished,
result=done
Jul 31 19:56:20 n systemd[1]: ssh.socket: Changed dead -> listening
root@n:~# systemctl enable fdfldakfjdklfjdaljfa.service
Failed to enable unit: Unit file fdfldakfjdklfjdaljfa.service does not exist.
root@n:~# systemctl status ssh.socket
Warning: The unit file, source configuration file or drop-ins of ssh.socket
changed on disk. Run 'systemctl daemon-reload' to reload units.
● ssh.socket - OpenBSD Secure Shell server socket
Loaded: loaded (/usr/lib/systemd/system/ssh.socket; enabled; preset:
enabled)
Active: active (listening) since Wed 2024-07-31 19:51:18 UTC; 5min ago
Triggers: ● ssh.service
Listen: [::]:22 (Stream)
CGroup: /system.slice/ssh.socket
Jul 31 19:55:15 n systemd[1]: ssh.socket: Trying to enqueue job
ssh.socket/start/replace
Jul 31 19:55:15 n systemd[1]: ssh.socket: Installed new job ssh.socket/start as
734
Jul 31 19:55:15 n systemd[1]: ssh.socket: Enqueued job ssh.socket/start as 734
Jul 31 19:55:15 n systemd[1]: ssh.socket: Job 734 ssh.socket/start finished,
result=done
Jul 31 19:55:53 n systemd[1]: ssh.socket: Changed dead -> listening
Jul 31 19:56:05 n systemd[1]: ssh.socket: Trying to enqueue job
ssh.socket/start/replace
Jul 31 19:56:05 n systemd[1]: ssh.socket: Installed new job ssh.socket/start as
825
Jul 31 19:56:05 n systemd[1]: ssh.socket: Enqueued job ssh.socket/start as 825
Jul 31 19:56:05 n systemd[1]: ssh.socket: Job 825 ssh.socket/start finished,
result=done
Jul 31 19:56:20 n systemd[1]: ssh.socket: Changed dead -> listening
I have tested [1] in a PPA build, and the issue goes away.
It may have already been pointed out, but the reason this is seen with
apt-news.service and esm-cache.service specifically is because of the
hook defined in /etc/apt/apt.conf.d/20apt-esm-hook.conf which starts
these services. Besides that, there is nothing special about them which
makes this bug appear.
[1]
https://github.com/systemd/systemd/pull/32610/commits/d69cba3bfffc7b1e3197e2a34b459db13b1e1cb7
--
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/2055239
Title:
Warning: The unit file, source configuration file or drop-ins of {apt-
news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
to reload units.
Status in snapd:
New
Status in systemd package in Ubuntu:
Fix Released
Status in ubuntu-advantage-tools package in Ubuntu:
Invalid
Status in systemd source package in Noble:
Triaged
Status in ubuntu-advantage-tools source package in Noble:
Invalid
Bug description:
I recently started seeing the following warning messages when I run
`apt update`.
$ sudo apt update
Warning: The unit file, source configuration file or drop-ins of
apt-news.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Warning: The unit file, source configuration file or drop-ins of
esm-cache.service changed on disk. Run 'systemctl daemon-reload' to reload
units.
...
apt-news.service for example is in /lib/systemd/system/apt-
news.service and it's a static file managed by the package. Does the
package maintenance script call systemd related hooks to reload the
config whenever the package gets updated?
$ systemctl cat apt-news.service
# /usr/lib/systemd/system/apt-news.service
# APT News is hosted at https://motd.ubuntu.com/aptnews.json and can include
# timely information related to apt updates available to your system.
...
$ dpkg -S /lib/systemd/system/apt-news.service
ubuntu-pro-client: /lib/systemd/system/apt-news.service
ProblemType: BugDistroRelease: Ubuntu 24.04
Package: ubuntu-pro-client 31.1
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x
[Touch-packages] [Bug 2055239] Re: Warning: The unit file, source configuration file or drop-ins of {apt-news, esm-cache}.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Note that the patch is already present in v256, so this only needs to be
fixed in Noble.
** Tags removed: rls-nn-incoming
** Tags added: systemd-sru-next
** Also affects: systemd (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: ubuntu-advantage-tools (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
** Changed in: systemd (Ubuntu Noble)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Changed in: systemd (Ubuntu Noble)
Status: New => Triaged
** Changed in: ubuntu-advantage-tools (Ubuntu Noble)
Status: New => Invalid
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2055239
Title:
Warning: The unit file, source configuration file or drop-ins of {apt-
news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
to reload units.
Status in snapd:
New
Status in systemd package in Ubuntu:
Fix Released
Status in ubuntu-advantage-tools package in Ubuntu:
Invalid
Status in systemd source package in Noble:
Triaged
Status in ubuntu-advantage-tools source package in Noble:
Invalid
Bug description:
I recently started seeing the following warning messages when I run
`apt update`.
$ sudo apt update
Warning: The unit file, source configuration file or drop-ins of
apt-news.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Warning: The unit file, source configuration file or drop-ins of
esm-cache.service changed on disk. Run 'systemctl daemon-reload' to reload
units.
...
apt-news.service for example is in /lib/systemd/system/apt-
news.service and it's a static file managed by the package. Does the
package maintenance script call systemd related hooks to reload the
config whenever the package gets updated?
$ systemctl cat apt-news.service
# /usr/lib/systemd/system/apt-news.service
# APT News is hosted at https://motd.ubuntu.com/aptnews.json and can include
# timely information related to apt updates available to your system.
...
$ dpkg -S /lib/systemd/system/apt-news.service
ubuntu-pro-client: /lib/systemd/system/apt-news.service
ProblemType: BugDistroRelease: Ubuntu 24.04
Package: ubuntu-pro-client 31.1
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 28 13:06:35 2024
InstallationDate: Installed on 2024-01-08 (51 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240104)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=SourcePackage: ubuntu-advantage-tools
UpgradeStatus: No upgrade log present (probably fresh install)
apparmor_logs.txt:
cloud-id.txt-error:
Failed running command 'cloud-id' [exit(2)]. Message: REDACTED config part
/etc/cloud/cloud.cfg.d/99-installer.cfg, insufficient permissions
REDACTED config part /etc/cloud/cloud.cfg.d/90-installer-network.cfg,
insufficient permissions
REDACTED config part /etc/cloud/cloud.cfg.d/99-installer.cfg, insufficient
permissions
REDACTED config part /etc/cloud/cloud.cfg.d/90-installer-network.cfg,
insufficient permissions
livepatch-status.txt-error: Invalid command specified
'/snap/bin/canonical-livepatch status'.
uaclient.conf:
contract_url: https://contracts.canonical.com
log_level: debug
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/2055239/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2065964] Re: test-execute fails because of apparmor unprivileged userns restrictions
** Changed in: systemd (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2065964 Title: test-execute fails because of apparmor unprivileged userns restrictions Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Noble: Fix Released Bug description: [Impact] unit-tests in noble currently fails because test-execute fails with the following: 1633s exec-basic.service: Child 1934 belongs to exec-basic.service. 1633s exec-basic.service: Control process exited, code=exited, status=0/SUCCESS (success) 1633s exec-basic.service: Got final SIGCHLD for state start-post. 1633s exec-basic.service: Deactivated successfully. 1633s exec-basic.service: Service will not restart (restart setting) 1633s exec-basic.service: Changed start-post -> dead 1633s exec-basic.service: Consumed 49ms CPU time. 1633s Spawning process to nuke '/tmp/systemd-private-dbf1f9a2e08f4741900f145a35ce7e30-exec-basic.service-ItwK5c' 1633s Successfully forked off intermediary '(sd-rmrf)' as PID 1936. 1633s Spawning process to nuke '/var/tmp/systemd-private-dbf1f9a2e08f4741900f145a35ce7e30-exec-basic.service-V50z4Q' 1633s Successfully forked off intermediary '(sd-rmrf)' as PID 1937. 1633s src/test/test-execute.c:1121:test_exec_basic: exec-basic.service: can_unshare=no: exit status 0, expected 226 1633s Skipping PR_SET_MM, as we don't have privileges. 1633s Skipping PR_SET_MM, as we don't have privileges. 1633s (test-execute-unprivileged) terminated by signal ABRT. 1633s Assertion 'r >= 0' failed at src/test/test-execute.c:1412, function prepare_ns(). Aborting. 1633s [...] 1678s [1mOK: 288 SKIP: 6 FAIL: 1[0m 1679s autopkgtest [20:59:40]: test unit-tests: ---] 1679s autopkgtest [20:59:40]: test unit-tests: - - - - - - - - - - results - - - - - - - - - - 1679s unit-tests FAIL non-zero exit status 1 This is because some tests in test-execute run unprivileged, and try to user user namespaces. I fixed this upstream[1], so just backport the patch so that this test case no longer fails. [Test Plan] This only pertains to the unit-tests autopkgtest in systemd. Just check the result of the autopkgtest run. [Where problems could occur] This only changes the test-execute code to skip tests that require unprivileged userns whenever kernel.apparmor_restrict_unprivileged_userns=1. Hence, any problems would be limited to that test case within unit-tests. [Other information] Note that the upstream-2 test still has regular failures which need to be investigated, so this change will not get the systemd autopkgtests back to green. Since I already fixed this upstream, it is easy to backport, so it's worth making the incremental improvement for now. [1] https://github.com/systemd/systemd/commit/70aece819311f7ab76abdf473bc8f316c5bc58c6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2065964/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2067922] Re: on WSL systemd status fails output
** Changed in: systemd (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2067922 Title: on WSL systemd status fails output Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Noble: Fix Released Bug description: [Impact] WSL 24.04 / systemd 255.4-1ubuntu8 * Upstream report: https://github.com/microsoft/WSL/issues/8879 * Upstream PR: https://github.com/systemd/systemd/pull/32534 * Upstream commit: https://github.com/systemd/systemd-stable/commit/8e57759d6d80ef772d8e17a4559a6797e09af93a.patch In WSL, the cgroup.procs PID list for some reason contain a ton of zeros everywhere from unmapped PIDs. Whenever cg_read_pid encounters such a zero, it throws an error. This makes systemd near unusable inside of WSL. [Test Plan] On WSL running Ubuntu 24.04, run systemctl status. On an affected system, there will be an error saying "Failed to dump process list [...]". On a patched system, the command should work as expected. [Where problems could occur] This patch adds a flags parameter to cg_read_pid(), and adds a new flag, CGROUP_DONT_SKIP_UNMAPPED. The new default behavior of cg_read_pid() is that unmapped pids *will* be skipped. When this flag is set in a call to cg_read_pid(), encountering an unmapped pid will leave the caller to deal with it. There are several places where cg_read_pid() is called in systemd, so there are several places where this would come up. If we did see problems, it would likely because a caller is skipping the unmapped pids when it should not be. For callers that do not skip (i.e. pass CGROUP_DONT_SKIP_UNMAPPED), they either handle it cleanly, or propagate a different error to signal this case. [Original Description] WSL 24.04 / systemd 255.4-1ubuntu8 * Upstream report: https://github.com/microsoft/WSL/issues/8879 * Upstream PR: https://github.com/systemd/systemd/pull/32534 * Upstream commit: https://github.com/systemd/systemd-stable/commit/8e57759d6d80ef772d8e17a4559a6797e09af93a.patch In WSL, the cgroup.procs PID list for some reason contain a ton of zeros everywhere from unmapped PIDs. Whenever cg_read_pid encounters such a zero, it throws an error. This makes systemd near unusable inside of WSL. # Test Case install Ubuntu WSL 24.04 from the MS STore. This version has systemd already enabled. ## Expected Behavior systemctl status command to work ## Actual Behavior toor@XPS:~$ systemctl status Failed to dump process list for 'XPS', ignoring: Input/output error ● XPS State: degraded Units: 318 loaded (incl. loaded aliases) Jobs: 0 queued Failed: 1 units Since: Sat 2022-09-24 08:43:15 PDT; 14min ago systemd: 251.4-1ubuntu6 Tainted: cgroupsv1 CGroup: / To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2067922/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2075968] [NEW] cannot login after upgrade from xubuntu 22.04 to 24.04
Public bug reported: After performing an upgrade, and then rebooting, I am no longer able to login with my user "ubuntu". I get an authentication failure with both the graphical login screen, and when attempting to login on a non- graphical tty. Dropping to a rescue shell, I can see this in the logs: root@xubuntu:~# journalctl -b --grep pam Aug 02 11:52:45 xubuntu systemd[1]: systemd 255.4-1ubuntu8.2 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OP> Aug 02 11:53:00 xubuntu lightdm[1422]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=115) by (uid=0) Aug 02 11:53:00 xubuntu (systemd)[1472]: pam_unix(systemd-user:session): session opened for user lightdm(uid=115) by lightdm(uid=0) Aug 02 11:53:00 xubuntu lightdm[1422]: gkr-pam: couldn't unlock the login keyring. Aug 02 11:53:01 xubuntu lightdm[1584]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "ubuntu" Aug 02 11:53:40 xubuntu lightdm[1584]: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=ubuntu Aug 02 11:53:42 xubuntu lightdm[1604]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "ubuntu" Aug 02 11:53:49 xubuntu lightdm[1604]: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=ubuntu Aug 02 11:53:51 xubuntu lightdm[1605]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "ubuntu" Aug 02 11:53:58 xubuntu lightdm[1607]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "root" Aug 02 11:53:59 xubuntu lightdm[1607]: gkr-pam: unable to locate daemon control file Aug 02 11:53:59 xubuntu lightdm[1607]: gkr-pam: stashed password to try later in open session Aug 02 11:53:59 xubuntu lightdm[1422]: pam_unix(lightdm-greeter:session): session closed for user lightdm Aug 02 11:53:59 xubuntu lightdm[1607]: pam_unix(lightdm:session): session opened for user root(uid=0) by (uid=0) Aug 02 11:54:00 xubuntu (systemd)[1614]: pam_unix(systemd-user:session): session opened for user root(uid=0) by root(uid=0) Aug 02 11:54:00 xubuntu lightdm[1607]: gkr-pam: unlocked login keyring Aug 02 11:54:10 xubuntu (sd-pam)[1473]: pam_unix(systemd-user:session): session closed for user lightdm Aug 02 11:55:01 xubuntu CRON[2417]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0) Aug 02 11:55:01 xubuntu CRON[2417]: pam_unix(cron:session): session closed for user root Other notes: (1) During the upgrade, the screen saver was disabled. I know this has been a bug in the past, but I do not believe it is the cause here. (2) A work around for this is to drop into a rescue shell, and from root, run e.g. `passwd ubuntu` to reset the user's password. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libpam-modules 1.5.3-5ubuntu5.1 ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8 Uname: Linux 6.8.0-39-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: XFCE Date: Fri Aug 2 11:55:51 2024 InstallationDate: Installed on 2024-07-30 (3 days ago) InstallationMedia: Xubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: pam UpgradeStatus: Upgraded to noble on 2024-08-02 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-04-23T07:30:10 ** Affects: pam (Ubuntu) Importance: Critical Status: New ** Affects: pam (Ubuntu Noble) Importance: Critical Status: New ** Tags: amd64 apport-bug noble rls-nn-incoming ** Also affects: pam (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: pam (Ubuntu Noble) Importance: Undecided => Critical ** Changed in: pam (Ubuntu) Importance: Undecided => Critical ** Changed in: pam (Ubuntu Noble) Milestone: None => ubuntu-24.04.1 ** Tags added: rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2075968 Title: cannot login after upgrade from xubuntu 22.04 to 24.04 Status in pam package in Ubuntu: New Status in pam source package in Noble: New Bug description: After performing an upgrade, and then rebooting, I am no longer able to login with my user "ubuntu". I get an authentication failure with both the graphical login screen, and when attempting to login on a non-graphical tty. Dropping to a rescue shell, I can see this in the logs: root@xubuntu:~# journalctl -b --grep pam Aug 02 11:52:45 xubuntu systemd[1]: systemd 255.4-1ubuntu8.2 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMAC
[Touch-packages] [Bug 2064435] Re: Merge openssh from Debian unstable for oracular
checks for OpenSSL >= 3 in 9.4p1.
* Build-depend on pkgconf rather than pkg-config.
* Adjust debian/copyright to handle the 'placed in the public domain'
status of rijndael.* more explicitly.
-- Colin Watson Mon, 26 Feb 2024 12:26:57
+
openssh (1:9.6p1-3) unstable; urgency=medium
* Allow passing extra ssh-agent arguments via
'/usr/lib/openssh/agent-launch start', making it possible to override
things like identity lifetime using a systemd drop-in unit (closes:
#1059639).
* Don't try to start rescue-ssh.target in postinst (LP: #2047082).
-- Colin Watson Wed, 17 Jan 2024 22:50:07
+
openssh (1:9.6p1-2) unstable; urgency=medium
### Old Ubuntu Delta ###
openssh (1:9.6p1-3ubuntu13) noble; urgency=medium
[ Marco Trevisan (Treviño) ]
* debian: Remove dependency on libsystemd
As per the xz backdoor we learned that the least dependencies sshd have,
the best it is, so avoid to plug libsystemd (which also brings various
other dependencies) inside sshd for no reason:
- d/p/systemd-readiness.patch: Use upstream patch with no libsystemd
dependency
- d/p/systemd-socket-activation.patch: Import patch from debian that
mimics the libsystemd sd_listen_fds() code, as refactored by Colin
Watson.
- d/control: Remove dependencies on libsystemd-dev | libelogind-dev
- d/rules: Drop --with-systemd flag (new options are used by default)
[ Nick Rosbrook ]
* debian/patches: only set PAM_RHOST if remote host is not 'UNKNOWN'
(LP: #2060150)
* debian/openssh-server.postinst: don't re-enable ssh.socket if it was
disabled
(LP: #2059874)
* d/p/sshd-socket-generator.patch: do not always ignore ListenStream=22
(LP: #2059872)
-- Nick Rosbrook Fri, 05 Apr 2024 15:30:31 -0400
openssh (1:9.6p1-3ubuntu12) noble; urgency=medium
* No-change rebuild for CVE-2024-3094
-- Steve Langasek Sun, 31 Mar 2024
09:23:28 +
openssh (1:9.6p1-3ubuntu11) noble; urgency=medium
* d/t/ssh-gssapi: make the test a bit more rebust (LP: #2058276):
- deal with return codes
- match a more specific success expression from the logs
- add klist output in the case of failure
-- Andreas Hasenack Mon, 18 Mar 2024
10:25:15 -0300
openssh (1:9.6p1-3ubuntu10) noble; urgency=medium
* Build again with gnome.
-- Matthias Klose Sat, 16 Mar 2024 19:30:41 +0100
openssh (1:9.6p1-3ubuntu9) noble; urgency=medium
* d/p/gssapi.patch: fix method_gsskeyex structure and
userauth_gsskeyex function regarding changes introduced in upstream
commit dbb339f015c33d63484261d140c84ad875a9e548 ('prepare for
multiple names for authmethods') (LP: #2053146)
* d/t/{ssh-gssapi,util}: ssh-gssapi DEP8 test for gssapi-with-mic
and gssapi-keyex authentication methods
-- Andreas Hasenack Fri, 15 Mar 2024
16:18:01 -0300
openssh (1:9.6p1-3ubuntu8) noble; urgency=medium
* No-change rebuild against libcom-err2
-- Steve Langasek Tue, 12 Mar 2024
20:34:07 +
openssh (1:9.6p1-3ubuntu7) noble; urgency=medium
* No-change rebuild against libglib2.0-0t64
-- Steve Langasek Mon, 11 Mar 2024
23:25:42 +
openssh (1:9.6p1-3ubuntu6) noble; urgency=medium
* No-change rebuild against libglib2.0-0t64
-- Steve Langasek Fri, 08 Mar 2024
06:32:05 +
openssh (1:9.6p1-3ubuntu5) noble; urgency=medium
* debian/systemd/ssh.service: restore RuntimeDirectory=sshd (LP: #2055806)
We started using a tmpfile in Ubuntu when we invoked sshd -G in
openssh-server.postinst as a part of migration to systemd socket
activation.
Since we use a generator now, instead of invoking sshd -G, we no longer
need
this change.
-- Nick Rosbrook Thu, 07 Mar 2024 13:59:57 -0500
openssh (1:9.6p1-3ubuntu5~ppa2) noble; urgency=medium
* Build without gnome.
-- Matthias Klose Tue, 05 Mar 2024 15:53:05 +0100
openssh (1:9.6p1-3ubuntu4) noble; urgency=medium
* No-change rebuild against libssl3t64
-- Steve Langasek Mon, 04 Mar 2024
20:31:25 +
openssh (1:9.6p1-3ubuntu3) noble; urgency=medium
* Add sshd-socket-generator to generate ssh.socket drop-in configuration
instead of doing one-time generation on package upgrade:
- debian/control: Build-Depends: systemd-dev
- d/p/sshd-socket-generator.patch: add generator for socket activation
- debian/openssh-server.install: install sshd-socket-generator
- debian/openssh-server.postinst: handle migration to
sshd-socket-generator
- d/t/sshd-socket-generator: add dep8 test for sshd-socket-generator
- ssh.socket: adjust unit for socket activation by default
- debian/README.Debian: update ssh.socket documentation
- debian/rules: explicitly enable LTO
The armhf build was not using LT
[Touch-packages] [Bug 2064435] Re: Merge openssh from Debian unstable for oracular
for OpenSSL >= 3 in 9.4p1.
* Build-depend on pkgconf rather than pkg-config.
* Adjust debian/copyright to handle the 'placed in the public domain'
status of rijndael.* more explicitly.
-- Colin Watson Mon, 26 Feb 2024 12:26:57
+
openssh (1:9.6p1-3) unstable; urgency=medium
* Allow passing extra ssh-agent arguments via
'/usr/lib/openssh/agent-launch start', making it possible to override
things like identity lifetime using a systemd drop-in unit (closes:
#1059639).
* Don't try to start rescue-ssh.target in postinst (LP: #2047082).
-- Colin Watson Wed, 17 Jan 2024 22:50:07
+
openssh (1:9.6p1-2) unstable; urgency=medium
### Old Ubuntu Delta ###
openssh (1:9.6p1-3ubuntu13) noble; urgency=medium
[ Marco Trevisan (Treviño) ]
* debian: Remove dependency on libsystemd
As per the xz backdoor we learned that the least dependencies sshd have,
the best it is, so avoid to plug libsystemd (which also brings various
other dependencies) inside sshd for no reason:
- d/p/systemd-readiness.patch: Use upstream patch with no libsystemd
dependency
- d/p/systemd-socket-activation.patch: Import patch from debian that
mimics the libsystemd sd_listen_fds() code, as refactored by Colin
Watson.
- d/control: Remove dependencies on libsystemd-dev | libelogind-dev
- d/rules: Drop --with-systemd flag (new options are used by default)
[ Nick Rosbrook ]
* debian/patches: only set PAM_RHOST if remote host is not 'UNKNOWN'
(LP: #2060150)
* debian/openssh-server.postinst: don't re-enable ssh.socket if it was
disabled
(LP: #2059874)
* d/p/sshd-socket-generator.patch: do not always ignore ListenStream=22
(LP: #2059872)
-- Nick Rosbrook Fri, 05 Apr 2024 15:30:31 -0400
openssh (1:9.6p1-3ubuntu12) noble; urgency=medium
* No-change rebuild for CVE-2024-3094
-- Steve Langasek Sun, 31 Mar 2024
09:23:28 +
openssh (1:9.6p1-3ubuntu11) noble; urgency=medium
* d/t/ssh-gssapi: make the test a bit more rebust (LP: #2058276):
- deal with return codes
- match a more specific success expression from the logs
- add klist output in the case of failure
-- Andreas Hasenack Mon, 18 Mar 2024
10:25:15 -0300
openssh (1:9.6p1-3ubuntu10) noble; urgency=medium
* Build again with gnome.
-- Matthias Klose Sat, 16 Mar 2024 19:30:41 +0100
openssh (1:9.6p1-3ubuntu9) noble; urgency=medium
* d/p/gssapi.patch: fix method_gsskeyex structure and
userauth_gsskeyex function regarding changes introduced in upstream
commit dbb339f015c33d63484261d140c84ad875a9e548 ('prepare for
multiple names for authmethods') (LP: #2053146)
* d/t/{ssh-gssapi,util}: ssh-gssapi DEP8 test for gssapi-with-mic
and gssapi-keyex authentication methods
-- Andreas Hasenack Fri, 15 Mar 2024
16:18:01 -0300
openssh (1:9.6p1-3ubuntu8) noble; urgency=medium
* No-change rebuild against libcom-err2
-- Steve Langasek Tue, 12 Mar 2024
20:34:07 +
openssh (1:9.6p1-3ubuntu7) noble; urgency=medium
* No-change rebuild against libglib2.0-0t64
-- Steve Langasek Mon, 11 Mar 2024
23:25:42 +
openssh (1:9.6p1-3ubuntu6) noble; urgency=medium
* No-change rebuild against libglib2.0-0t64
-- Steve Langasek Fri, 08 Mar 2024
06:32:05 +
openssh (1:9.6p1-3ubuntu5) noble; urgency=medium
* debian/systemd/ssh.service: restore RuntimeDirectory=sshd (LP: #2055806)
We started using a tmpfile in Ubuntu when we invoked sshd -G in
openssh-server.postinst as a part of migration to systemd socket
activation.
Since we use a generator now, instead of invoking sshd -G, we no longer
need
this change.
-- Nick Rosbrook Thu, 07 Mar 2024 13:59:57 -0500
openssh (1:9.6p1-3ubuntu5~ppa2) noble; urgency=medium
* Build without gnome.
-- Matthias Klose Tue, 05 Mar 2024 15:53:05 +0100
openssh (1:9.6p1-3ubuntu4) noble; urgency=medium
* No-change rebuild against libssl3t64
-- Steve Langasek Mon, 04 Mar 2024
20:31:25 +
openssh (1:9.6p1-3ubuntu3) noble; urgency=medium
* Add sshd-socket-generator to generate ssh.socket drop-in configuration
instead of doing one-time generation on package upgrade:
- debian/control: Build-Depends: systemd-dev
- d/p/sshd-socket-generator.patch: add generator for socket activation
- debian/openssh-server.install: install sshd-socket-generator
- debian/openssh-server.postinst: handle migration to
sshd-socket-generator
- d/t/sshd-socket-generator: add dep8 test for sshd-socket-generator
- ssh.socket: adjust unit for socket activation by default
- debian/README.Debian: update ssh.socket documentation
- debian/rules: explicitly enable LTO
The armhf build was not using LTO, which ma
[Touch-packages] [Bug 2075104] Re: user session is randomly terminated by systemd-oom when the system is left alone for a while
Can you share the journal output that you're describing? And, can you share the output of the following commands? $ oomctl $ systemd-analyze cat-config systemd/oomd.conf $ systemctl cat -- '-.slice' $ systemctl cat -- user@$(id -u).service ** 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/2075104 Title: user session is randomly terminated by systemd-oom when the system is left alone for a while Status in systemd package in Ubuntu: Incomplete Bug description: I was surprised last week to find that my computer had logged me out when I had left it alone for some 15 minutes. I did not bother to research at the time and did not see any reason as the problem did not manifest again . Then today, it happens again. The circumstances are similar: I leave the system long enough for the screen to power off and come back to find myself kicked out of my session. Yes, kicked out, not simply locked out. I need to log in again and find that all running apps and open files have all been closed. My journal would appear to show that gnome-shell got stopped as a consequence of systemd-oomd killing several applications (see the included journalctl snippet - mind that the output is in reverse order (journalctl -r)). Should not oomd terminate single applications instead of complete user sessions? And I do have some doubts about the statistics listed in the journal. One of the killed apps is reported as consuming over 22GB or RAM (out of 32). I have been using that app for many years and cannot remember having see it use more than a few GB. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd-oomd 255.4-1ubuntu8.2 ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8 Uname: Linux 6.8.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jul 30 04:00:27 2024 InstallationDate: Installed on 2022-03-27 (855 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2075104/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2064435] Re: Merge openssh from Debian unstable for oracular
I have context for most of the delta here, so I will take this merge. ** 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/2064435 Title: Merge openssh from Debian unstable for oracular Status in openssh package in Ubuntu: New Bug description: Scheduled-For: Backlog Upstream: tbd Debian: 1:9.7p1-4 Ubuntu: 1:9.6p1-3ubuntu13 Other teams have maintained this package's merge in the past. If it turns out this needs a sync rather than a merge, please change the tag 'needs-merge' to 'needs-sync', and (optionally) update the title as desired. If this merge pulls in a new upstream version, also consider adding an entry to the Oracular Release Notes: https://discourse.ubuntu.com/c/release/38 ### New Debian Changes ### openssh (1:9.7p1-4) unstable; urgency=medium * Rework systemd readiness notification and socket activation patches to not link against libsystemd (the former via an upstream patch). * Force -fzero-call-used-regs=used not to be used on ppc64el (it's unsupported, but configure fails to detect this). -- Colin Watson Wed, 03 Apr 2024 12:06:08 +0100 openssh (1:9.7p1-3) unstable; urgency=medium * Fix gssapi-keyex declaration further (thanks, Andreas Hasenack; LP: #2053146). * Extend -fzero-call-used-regs check to catch m68k gcc bug (closes: #1067243). * debian/tests/regress: Set a different IP address for UNKNOWN. * Re-enable ssh-askpass-gnome on all architectures. * regress: Redirect conch stdin from /dev/zero (re-enables conch interop tests). * Drop 'Work around RSA SHA-2 signature issues in conch' patch (no longer needed now that Twisted is fixed). -- Colin Watson Sun, 31 Mar 2024 11:55:38 +0100 openssh (1:9.7p1-2) unstable; urgency=medium [ Simon McVittie ] * d/control, d/rules: Disable ssh-askpass-gnome on 32-bit, except i386 (closes: #1066847). -- Colin Watson Thu, 14 Mar 2024 11:45:12 + openssh (1:9.7p1-1) unstable; urgency=medium * Add the isolation-container restriction to the 'regress' autopkgtest. Our setup code wants to ensure that the haveged service is running, and furthermore at least the agent-subprocess test assumes that there's an init to reap zombie processes and doesn't work in (e.g.) autopkgtest-virt-unshare. * New upstream release (https://www.openssh.com/releasenotes.html#9.7p1): - ssh(1), sshd(8): add a 'global' ChannelTimeout type that watches all open channels and will close all open channels if there is no traffic on any of them for the specified interval. This is in addition to the existing per-channel timeouts added recently. This supports situations like having both session and x11 forwarding channels open where one may be idle for an extended period but the other is actively used. The global timeout could close both channels when both have been idle for too long (closes: #165185). - All: make DSA key support compile-time optional, defaulting to on. - sshd(8): don't append an unnecessary space to the end of subsystem arguments (bz3667) - ssh(1): fix the multiplexing 'channel proxy' mode, broken when keystroke timing obfuscation was added. (GHPR#463) - ssh(1), sshd(8): fix spurious configuration parsing errors when options that accept array arguments are overridden (bz3657). - ssh-agent(1): fix potential spin in signal handler (bz3670) - Many fixes to manual pages and other documentation. - Greatly improve interop testing against PuTTY. * Skip utimensat test on ZFS, since it seems to leave the atime set to 0. * Allow passing extra options to debian/tests/regress, for debugging. * Fix gssapi-keyex declaration, broken when rebasing onto 8.9p1 (LP: #2053146). -- Colin Watson Thu, 14 Mar 2024 10:47:58 + openssh (1:9.6p1-5) unstable; urgency=medium * Restore systemd template unit for per-connection sshd instances, although without any corresponding .socket unit for now; this is mainly for use with the forthcoming systemd-ssh-generator (closes: #1061516). It's now called sshd@.service, since unlike the main service there's no need to be concerned about compatibility with the slightly confusing 'ssh' service name that Debian has traditionally used. -- Colin Watson Wed, 06 Mar 2024 09:45:56 + openssh (1:9.6p1-4) unstable; urgency=medium * Add sshd_config checksums for 1:9.2p1-1 to ucf reference file, and add a test to ensure it doesn't get out of date again.
[Touch-packages] [Bug 2071815] Re: Investigate ASLR re-randomization being disabled for children
** 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/2071815 Title: Investigate ASLR re-randomization being disabled for children Status in openssh package in Ubuntu: Fix Committed Bug description: The systemd-socket-activation.patch patch has an Ubuntu delta to fix bug 2011458, but this results in ASLR not being re-randomized for children because the patch delta does "rexec_flag = 0;". This was discovered as part of the CVE-2024-6387 discovery by Qualys, and is mentioned in the disclosure itself: Side note: we discovered that Ubuntu 24.04 does not re-randomize the ASLR of its sshd children (it is randomized only once, at boot time); we tracked this down to the patch below, which turns off sshd's rexec_flag. This is generally a bad idea, but in the particular case of this signal handler race condition, it prevents sshd from being exploitable: the syslog() inside the SIGALRM handler does not call any of the malloc functions, because it is never the very first call to syslog(). This is also mentioned in the release notes of OpenSSH 9.8: Exploitation on non-glibc systems is conceivable but has not been examined. Systems that lack ASLR or users of downstream Linux distributions that have modified OpenSSH to disable per-connection ASLR re-randomisation (yes - this is a thing, no - we don't understand why) may potentially have an easier path to exploitation. We should investigate why that was needed, and if an alternative way of fixing the original bug can be done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2071815/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2074210] Re: systemd-coredump not installable on 24.04
Yeah, you need an entry enabling noble-updates for universe. ** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2074210 Title: systemd-coredump not installable on 24.04 Status in systemd package in Ubuntu: Invalid Bug description: $ sudo apt install systemd-coredump [sudo] password for paolo: Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: systemd-coredump : Depends: libsystemd-shared (= 255.4-1ubuntu8) but 255.4-1ubuntu8.2 is to be installed E: Unable to correct problems, you have held broken packages. There is no way to resolve that. libsystemd-shared cannot be downgraded ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd-coredump (not installed) ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8 Uname: Linux 6.8.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Fri Jul 26 10:10:31 2024 InstallationDate: Installed on 2023-10-25 (276 days ago) InstallationMedia: Xubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-04-25 (92 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2074210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055239] Re: Warning: The unit file, source configuration file or drop-ins of {apt-news, esm-cache}.service changed on disk. Run 'systemctl daemon-reload' to reload units.
** 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/2055239
Title:
Warning: The unit file, source configuration file or drop-ins of {apt-
news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
to reload units.
Status in snapd:
New
Status in systemd package in Ubuntu:
New
Status in ubuntu-advantage-tools package in Ubuntu:
Invalid
Bug description:
I recently started seeing the following warning messages when I run
`apt update`.
$ sudo apt update
Warning: The unit file, source configuration file or drop-ins of
apt-news.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Warning: The unit file, source configuration file or drop-ins of
esm-cache.service changed on disk. Run 'systemctl daemon-reload' to reload
units.
...
apt-news.service for example is in /lib/systemd/system/apt-
news.service and it's a static file managed by the package. Does the
package maintenance script call systemd related hooks to reload the
config whenever the package gets updated?
$ systemctl cat apt-news.service
# /usr/lib/systemd/system/apt-news.service
# APT News is hosted at https://motd.ubuntu.com/aptnews.json and can include
# timely information related to apt updates available to your system.
...
$ dpkg -S /lib/systemd/system/apt-news.service
ubuntu-pro-client: /lib/systemd/system/apt-news.service
ProblemType: BugDistroRelease: Ubuntu 24.04
Package: ubuntu-pro-client 31.1
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 28 13:06:35 2024
InstallationDate: Installed on 2024-01-08 (51 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240104)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=SourcePackage: ubuntu-advantage-tools
UpgradeStatus: No upgrade log present (probably fresh install)
apparmor_logs.txt:
cloud-id.txt-error:
Failed running command 'cloud-id' [exit(2)]. Message: REDACTED config part
/etc/cloud/cloud.cfg.d/99-installer.cfg, insufficient permissions
REDACTED config part /etc/cloud/cloud.cfg.d/90-installer-network.cfg,
insufficient permissions
REDACTED config part /etc/cloud/cloud.cfg.d/99-installer.cfg, insufficient
permissions
REDACTED config part /etc/cloud/cloud.cfg.d/90-installer-network.cfg,
insufficient permissions
livepatch-status.txt-error: Invalid command specified
'/snap/bin/canonical-livepatch status'.
uaclient.conf:
contract_url: https://contracts.canonical.com
log_level: debug
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/2055239/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2074210] Re: systemd-coredump not installable on 24.04
This sounds like your apt sources are messed up. Do you have noble- updates enabled for universe? Can you share the output of: $ apt policy systemd-coredump systemd $ cat /etc/apt/sources.list.d/* ** 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/2074210 Title: systemd-coredump not installable on 24.04 Status in systemd package in Ubuntu: Incomplete Bug description: $ sudo apt install systemd-coredump [sudo] password for paolo: Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: systemd-coredump : Depends: libsystemd-shared (= 255.4-1ubuntu8) but 255.4-1ubuntu8.2 is to be installed E: Unable to correct problems, you have held broken packages. There is no way to resolve that. libsystemd-shared cannot be downgraded ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd-coredump (not installed) ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8 Uname: Linux 6.8.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Fri Jul 26 10:10:31 2024 InstallationDate: Installed on 2023-10-25 (276 days ago) InstallationMedia: Xubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-04-25 (92 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2074210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2071815] Re: Investigate ASLR re-randomization being disabled for children
I don't think those *help*, but that's good to know for when we merge an upstream version that includes those patches. ** Changed in: openssh (Ubuntu) Status: Confirmed => In Progress ** Changed in: openssh (Ubuntu) Importance: Undecided => Medium -- 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/2071815 Title: Investigate ASLR re-randomization being disabled for children Status in openssh package in Ubuntu: In Progress Bug description: The systemd-socket-activation.patch patch has an Ubuntu delta to fix bug 2011458, but this results in ASLR not being re-randomized for children because the patch delta does "rexec_flag = 0;". This was discovered as part of the CVE-2024-6387 discovery by Qualys, and is mentioned in the disclosure itself: Side note: we discovered that Ubuntu 24.04 does not re-randomize the ASLR of its sshd children (it is randomized only once, at boot time); we tracked this down to the patch below, which turns off sshd's rexec_flag. This is generally a bad idea, but in the particular case of this signal handler race condition, it prevents sshd from being exploitable: the syslog() inside the SIGALRM handler does not call any of the malloc functions, because it is never the very first call to syslog(). This is also mentioned in the release notes of OpenSSH 9.8: Exploitation on non-glibc systems is conceivable but has not been examined. Systems that lack ASLR or users of downstream Linux distributions that have modified OpenSSH to disable per-connection ASLR re-randomisation (yes - this is a thing, no - we don't understand why) may potentially have an easier path to exploitation. We should investigate why that was needed, and if an alternative way of fixing the original bug can be done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2071815/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[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
