Public bug reported: ## Impact
On Ubuntu 24.04.5 LTS ARM64, with reported systemd package version `255.4-1ubuntu8.17`, `systemd-run` rejects the `JobTimeoutSec=3s` property when submitting a transient service. This prevents callers from applying a deadline that includes time spent waiting in the systemd job queue. Removing the property or replacing it with a service startup timeout would not provide equivalent protection. ## Observed behavior A bounded, benign transient-service experiment submitted the following property: `--property=JobTimeoutSec=3s` The operation failed before the test workload started: ``` Failed to start transient service unit: Cannot set property JobTimeoutUSec, or unknown property. ``` The caller returned exit status 2. No successful service activation was observed. ## Expected behavior The manager should accept `JobTimeoutSec=3s` for a transient service. A start job that remains queued for three seconds should time out before its `ExecStart` command runs. ## Diagnosis The systemd client converts `JobTimeoutSec` to the D-Bus property `JobTimeoutUSec`. In the published Ubuntu Noble `255.4-1ubuntu8.17` source, the transient- property handler processes `JobTimeoutUSec` but does not return the result afterward. The handler falls through, resulting in the observed property rejection. Upstream commit `041e70d7f70372f06e1651a6f2dfd82fa2a13b8e` adds the missing `return r;`. Ubuntu source: https://launchpad.net/ubuntu/+source/systemd/255.4-1ubuntu8.17 Upstream correction: https://github.com/systemd/systemd/commit/041e70d7f70372f06e1651a6f2dfd82fa2a13b8e The observed failure is consistent with this source-level defect. The exact running manager binary and loaded libraries have not been independently authenticated. ## Requested fix Please consider backporting the upstream correction through the Ubuntu Noble Stable Release Update (SRU) process. ## Suggested regression verification 1. Confirm that a benign transient service accepts `JobTimeoutSec=3s` and that the effective job timeout is three seconds. 2. Queue a benign transient service behind a dependency that remains activating for longer than three seconds. Verify that the queued job times out and that the service's `ExecStart` never runs. 3. Confirm that a comparable transient service without an explicit job timeout starts normally. ## Environment and evidence - Ubuntu 24.04.5 LTS - ARM64 / aarch64 virtual machine - Linux 6.8.0-139-generic - Reported systemd package: `255.4-1ubuntu8.17` - Isolated test environment The original 4,940-byte console transcript has been preserved and verified. SHA-256: `a897fa843242c8eb16f76d15d2d39f5f0ce6905c59efefbe42a105bf2c684adc` The transcript can be provided if required. ** 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/2175486 Title: Ubuntu 24.04 Noble: systemd-run rejects JobTimeoutSec=3s for transient services To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2175486/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
