[GH-ISSUE #1185] systemd/firejail interaction #812

New issue

Closed

opened 2026-05-05 06:53:31 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-05-05 06:53:31 -06:00

Owner

Originally created by @netblue30 on GitHub (Mar 31, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1185

From wordpress (user Robert in Basic Usage):

Experiencing problems when firejail and transmission-daemon under systemd. The daemon is started from a systemd service file. Lots of messages like this are going in system log:

Feb 19 11:28:39 megat systemd[1]: transmission-daemon.service: Got notification message from PID 18737, but reception only permitted for main PID 18734

A partial solution was to include a further line in the transmission-daemon.service file "NotifyAccess=all"

Shutdown problem: Often (but not always), transmission-daemon will segfault and, whether it segfaults or not, the shutdown hangs for at least 90 seconds until some timeout mechanism finally kills all running processes.

The system runs a very vanilla installation running under KVM/QEMU, though I doubt if that’s relevant.

uname -a
Linux dl 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) x86_64 GNU/Linux

Originally created by @netblue30 on GitHub (Mar 31, 2017). Original GitHub issue: https://github.com/netblue30/firejail/issues/1185 From wordpress (user Robert in Basic Usage): Experiencing problems when firejail and transmission-daemon under systemd. The daemon is started from a systemd service file. Lots of messages like this are going in system log: Feb 19 11:28:39 megat systemd[1]: transmission-daemon.service: Got notification message from PID 18737, but reception only permitted for main PID 18734 A partial solution was to include a further line in the transmission-daemon.service file "NotifyAccess=all" Shutdown problem: Often (but not always), transmission-daemon will segfault and, whether it segfaults or not, the shutdown hangs for at least 90 seconds until some timeout mechanism finally kills all running processes. The system runs a very vanilla installation running under KVM/QEMU, though I doubt if that’s relevant. uname -a Linux dl 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) x86_64 GNU/Linux

gitea-mirror

2026-05-05 06:53:31 -06:00

closed this issue
added the
information_old
label

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#812

No description provided.

Rows
Columns