Systemctl start transmission-daemon timeout

It does say ALLOWED, but I wonder if this specific error (disconnected path) is perhaps treated differently, even if the profile is in complain mode.

That being said, I can’t find an apparmor profile in the transmission-daemon package, do you know where it’s coming from? Does this return any results: grep transmission-daemon -r /etc/apparmor.d ?

UPDATE: found it, it’s in the apparmor package, in /etc/apparmor.d/transmission. I also reproduced the problem, and indeed it’s the disconnected path, even though the profile is in complain mode.

If you make this change, it should work:

--- /etc/apparmor.d/transmission.orig	2024-12-13 17:03:43.022484872 +0000
+++ /etc/apparmor.d/transmission	2024-12-13 17:03:48.479472153 +0000
@@ -5,7 +5,7 @@
 
 include <tunables/global>
 
-profile transmission-daemon /usr/bin/transmission-daemon flags=(complain) {
+profile transmission-daemon /usr/bin/transmission-daemon flags=(complain,attach_disconnected) {
   # Don't use abstractions/transmission-common here, as the
   # access needed is narrower than the user applications
   include <abstractions/base>

Please also file a bug here: https://bugs.launchpad.net/ubuntu/+source/transmission/+filebug

Feel free to link to this thread.

3 Likes