Hello, in tmux-3.4 it is enough to start tmux, then I receive in the journal: > dbus-daemon[789]: [system] Rejected send message, 4 matched rules; type="method_call", sender=":1.10" (uid=1100 pid=892 comm="/usr/lib/systemd/systemd --user") interface="org.freedesktop.systemd1.Manager" member="AttachProcessesToUnit" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/usr/lib/systemd/systemd") > systemd[892]: tmux-spawn-4fe6e639-6bed-478b-990b-e7631c3330fb.scope: Couldn't move process 12556 to requested cgroup '/user.slice/user-1100.slice/user@1100.service/tmux-spawn-4fe6e639-6bed-478b-990b-e7631c3330fb.scope' (directly or via the system bus): Permission denied > systemd[892]: tmux-spawn-4fe6e639-6bed-478b-990b-e7631c3330fb.scope: Failed to add PIDs to scope's control group: Permission denied > systemd[892]: tmux-spawn-4fe6e639-6bed-478b-990b-e7631c3330fb.scope: Failed with result 'resources'. > systemd[892]: Failed to start tmux child pane 12556 launched by process 12544. The same happens for each newly opened pane. After a downgrade to tmux-3.3a-r1 the issue is gone. I haven't seen a similar issue (nor filed one) for upstream tmux.
I am unable to reproduce this.
Thanks for testing. So, I tried on 4 boxes and can't reproduce it there either, except on one of it, as described above. Since a simple downgrade of tmux helps, I was shooting on tmux-3.4 first. But it seems there is a second cause required to trigger the issue.
Okay, the thing is probably this: It seems that tmux-3.4 tries to move every tmux session into another cgroup. And it seems that this was not exactly the case in tmux-3.3 (thus tmux 3.3 had no issue here). To make process movement work in tmux-3.4 work, we need a proper session handling. In my case dbus-run-session has to be called explicitly before I log in. So this is not a tmux issue. Thanks.
