Public bug reported:
Ubuntu source package: systemd
Affected binary package: libsystemd-shared (amd64)
Release: Ubuntu 26.04.1 LTS (Resolute)
[Impact]
Please backport the upstream v259.10 correction to the JobTimeoutUSec
handler in src/core/dbus-unit.c. A client using
Manager.StartTransientUnit cannot set a finite whole-job deadline on the
affected builds. Our launcher requires a 20-second deadline for each of
three jobs: a guard service, its auxiliary mount, and a worker service.
The clock must start when systemd queues each job. If the worker waits
15 seconds for its mount, only 5 seconds of its budget remain.
JobRunningTimeoutSec starts after that wait. If the dependency never
becomes ready, the worker can spend its entire 20-second budget in the
queue without the running timer ever starting. The manager must own the
deadline because the submitting process can exit while the job is
pending. Expiry cancels the job. The launcher separately supervises
running processes and handles cleanup.
[Observed on the installed build]
On 18 November 2026, the Resolute system manager on amd64, with systemd
and libsystemd-shared 259.5-0ubuntu3.4 installed, received a
StartTransientUnit call. Both the primary guard service and the
auxiliary mount supplied the D-Bus variant JobTimeoutUSec, type t
(uint64), value 20000000. busctl exited 1 with empty stdout and this
stderr:
Call failed: Cannot set property JobTimeoutUSec, or unknown
property.
There was no job acknowledgement for that request. The reply did not
identify which occurrence triggered it. The launcher stopped before
requesting the worker.
[Verified in the resolute-updates archive build]
We fetched libsystemd-shared_259.9-0ubuntu0.1_amd64.deb directly from
archive.ubuntu.com. We verified the 9 November resolute-updates
InRelease signature, the SHA-256 of its main/binary-amd64/Packages
index, and the package size and SHA-256 against the matching index
entry.
Archive file size: 2473420 bytes
Archive file SHA-256:
c9b8ee0c0dff4f25a3d27b3d8ac344e7cc31d2f02fd65c75d818562a86aea8ab
Packaged libsystemd-core-259.so SHA-256:
79d808713511e465433af9478011ea1e6b58bcb37426307e75cc9c0a52c5b7e6
Offline disassembly of this exact build shows the cause. In
bus_unit_set_properties the JobTimeoutUSec branch calls
bus_set_transient_usec_fix_0 at 0xb4c8e. All four exits resume property
lookup at 0xb474d. No remaining name matches, so the manager reaches
sd_bus_error_setf at 0xb44e5 with
org.freedesktop.DBus.Error.PropertyReadOnly and the observed diagnostic.
The adjacent JobRunningTimeoutUSec handler reaches the handled-property
path on success. This is static evidence for 259.9-0ubuntu0.1. The live
failure above was on 259.5-0ubuntu3.4.
[Upstream fix]
In the v259.10 JobTimeoutUSec branch, an unconditional return r; after
the existing running-timeout bookkeeping passes the setter's result back
to the caller. This preserves both a recognized property and the
helper's error for invalid input.
Affected source:
https://github.com/systemd/systemd/blob/v259.9/src/core/dbus-unit.c#L2207-L2217
Corrected source:
https://github.com/systemd/systemd/blob/v259.10/src/core/dbus-unit.c#L2207-L2219
Ubuntu archive file:
https://archive.ubuntu.com/ubuntu/pool/main/s/systemd/libsystemd-shared_259.9-0ubuntu0.1_amd64.deb
[Proposed maintainer test plan — unrun]
1. In a disposable Resolute test VM with permission to manage system
units, send the minimal request below on the affected and proposed
builds. Use a fresh unit name for each run. On the affected build expect
the property diagnostic above. On the proposed build expect a job object
path and successful completion of /usr/bin/true.
busctl --system -- call org.freedesktop.systemd1 /org/freedesktop/systemd1 \
org.freedesktop.systemd1.Manager StartTransientUnit 'ssa(sv)a(sa(sv))' \
"sru-jobtimeout-$$.service" fail 2 \
ExecStart 'a(sasb)' 1 /usr/bin/true 1 /usr/bin/true false \
JobTimeoutUSec t 20000000 0
2. Verify the deadline while queued. In the VM use a fresh target
service with a start marker and a fresh Type=oneshot dependency that
sleeps for 35 seconds. Give the target Requires= and After= on that
dependency. Subscribe to JobRemoved before submitting the target, record
monotonic timestamps around the call, and retain the returned target job
identity. Check that the target waits while the dependency is
activating. Expect that target's JobRemoved result to be "timeout" about
20 seconds from submission, within scheduling tolerance, while the
dependency is still activating. The target's start marker must remain
absent. Clean up the test fixtures independently.
[Where problems could occur]
The change affects transient unit property handling across services
using this manager API. Check a wrongly typed JobTimeoutUSec still
returns an error, an omitted timeout retains the default, and an
explicitly supplied JobRunningTimeoutUSec retains its independent value
in either property order. The queue test above distinguishes correct
deadline enforcement from merely accepting or displaying the property.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2174933
Title:
[Resolute] StartTransientUnit rejects JobTimeoutUSec on amd64 (v259.10
backport requested)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2174933/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs