I confirmed this in a minimal noble container by installing the
transmission-daemon package with no further modifications. The
installation stalled when trying to start the service, and afterwards I
saw:
root@noble:~# systemctl status transmission-daemon
× transmission-daemon.service - Transmission BitTorrent Daemon
Loaded: loaded (/usr/lib/systemd/system/transmission-daemon.service;
enabled; preset: enabled)
Active: failed (Result: timeout) since Tue 2026-06-09 13:46:44 UTC; 2s ago
Process: 1131 ExecStart=/usr/bin/transmission-daemon -f --log-level=error
(code=exited, status=0/SUCCESS)
Main PID: 1131 (code=exited, status=0/SUCCESS)
CPU: 154ms
Jun 09 13:45:14 noble systemd[1]: Starting transmission-daemon.service -
Transmission BitTorrent Daemon...
Jun 09 13:46:44 noble systemd[1]: transmission-daemon.service: start operation
timed out. Terminating.
Jun 09 13:46:44 noble systemd[1]: transmission-daemon.service: Failed with
result 'timeout'.
Jun 09 13:46:44 noble systemd[1]: Failed to start transmission-daemon.service -
Transmission BitTorrent Daemon.
root@noble:~# vim /usr/lib/systemd/system/transmission-daemon.service
** Tags added: dcr-incoming
** Changed in: transmission (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2104214
Title:
transmissions daemon not being detected as started up by systemctl
even though it is.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/2104214/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
