[GH-ISSUE #1385] Can't killall firejailed chromium #948

Closed
opened 2026-05-05 07:12:19 -06:00 by gitea-mirror · 12 comments
Owner

Originally created by @Harvie on GitHub (Jul 15, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1385

I've executed chromium like firejail chromium and now i can't kill it with killall -9 chromium even as root, says chromium: no process found. Without firejail it works just ok. While pkill -9 chromium seems to work.

Originally created by @Harvie on GitHub (Jul 15, 2017). Original GitHub issue: https://github.com/netblue30/firejail/issues/1385 I've executed chromium like `firejail chromium` and now i can't kill it with `killall -9 chromium` even as root, says `chromium: no process found`. Without firejail it works just ok. While `pkill -9 chromium` seems to work.
gitea-mirror 2026-05-05 07:12:19 -06:00
Author
Owner

@netblue30 commented on GitHub (Jul 16, 2017):

In a terminal start chromium: "firejail chromium".

In a different terminal, do a "firejail --tree". What does it say? If "firejail --tree" finds it, killall should also find it.

<!-- gh-comment-id:315610398 --> @netblue30 commented on GitHub (Jul 16, 2017): In a terminal start chromium: "firejail chromium". In a different terminal, do a "firejail --tree". What does it say? If "firejail --tree" finds it, killall should also find it.
Author
Owner

@Harvie commented on GitHub (Jul 16, 2017):

The output is rather long, but it correctly litsts all chromium processes from any terminal i've tried. Also ps aux shows it. But it still can't be killed using killall.

it's latest archlinux:

firejail version 0.9.48

Compile time support:
	- AppArmor support is disabled
	- AppImage support is enabled
	- bind support is enabled
	- chroot support is enabled
	- file and directory whitelisting support is enabled
	- file transfer support is enabled
	- git install support is disabled
	- networking support is enabled
	- overlayfs support is enabled
	- private-home support is enabled
	- seccomp-bpf support is enabled
	- user namespace support is enabled
	- X11 sandboxing support is enabled
<!-- gh-comment-id:315611627 --> @Harvie commented on GitHub (Jul 16, 2017): The output is rather long, but it correctly litsts all chromium processes from any terminal i've tried. Also ps aux shows it. But it still can't be killed using killall. it's latest archlinux: ``` firejail version 0.9.48 Compile time support: - AppArmor support is disabled - AppImage support is enabled - bind support is enabled - chroot support is enabled - file and directory whitelisting support is enabled - file transfer support is enabled - git install support is disabled - networking support is enabled - overlayfs support is enabled - private-home support is enabled - seccomp-bpf support is enabled - user namespace support is enabled - X11 sandboxing support is enabled ```
Author
Owner

@netblue30 commented on GitHub (Jul 17, 2017):

tested on Debian stable, it seems to be working. It could be a problem with the newer killall you have on Arch. Run a "killall --version", over here I have 22.21

<!-- gh-comment-id:315783518 --> @netblue30 commented on GitHub (Jul 17, 2017): tested on Debian stable, it seems to be working. It could be a problem with the newer killall you have on Arch. Run a "killall --version", over here I have 22.21
Author
Owner

@Harvie commented on GitHub (Jul 17, 2017):

killall (PSmisc) 23.1
Copyright (C) 1993-2017 Werner Almesberger and Craig Small

PSmisc comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it under
the terms of the GNU General Public License.
For more information about these matters, see the files named COPYING.

maybe it's some protection that prevents killall from killing processes in LXC containers when managing host machine.

<!-- gh-comment-id:315885008 --> @Harvie commented on GitHub (Jul 17, 2017): ``` killall (PSmisc) 23.1 Copyright (C) 1993-2017 Werner Almesberger and Craig Small PSmisc comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under the terms of the GNU General Public License. For more information about these matters, see the files named COPYING. ``` maybe it's some protection that prevents killall from killing processes in LXC containers when managing host machine.
Author
Owner

@Harvie commented on GitHub (Jul 17, 2017):

Ha! It works when using killall --ns 0.

       -n, --ns
              Match against the PID namespace of the given PID. Use 0 to match against all namespaces.
              The default is to  match  against the current PID namespace.

Can you please put this in firejail faq or somewhere?

<!-- gh-comment-id:315885632 --> @Harvie commented on GitHub (Jul 17, 2017): Ha! It works when using `killall --ns 0`. ``` -n, --ns Match against the PID namespace of the given PID. Use 0 to match against all namespaces. The default is to match against the current PID namespace. ``` Can you please put this in firejail faq or somewhere?
Author
Owner

@netblue30 commented on GitHub (Jul 19, 2017):

So, basically they added namespace support to killall. I'll add it to FAQ, thanks.

<!-- gh-comment-id:316386482 --> @netblue30 commented on GitHub (Jul 19, 2017): So, basically they added namespace support to killall. I'll add it to FAQ, thanks.
Author
Owner

@chiraag-nataraj commented on GitHub (May 20, 2019):

@netblue30 Where do you want to put this info?

<!-- gh-comment-id:494033635 --> @chiraag-nataraj commented on GitHub (May 20, 2019): @netblue30 Where do you want to put this info?
Author
Owner

@matu3ba commented on GitHub (Jun 22, 2019):

@netblue30 Reminder to put #1385 into FAQ.

<!-- gh-comment-id:504609406 --> @matu3ba commented on GitHub (Jun 22, 2019): @netblue30 Reminder to put #1385 into [FAQ](https://firejail.wordpress.com/support/).
Author
Owner

@chiraag-nataraj commented on GitHub (Jun 22, 2019):

@matu3ba Or, we can put it in the Wiki! Actually, we could transition the FAQ to the Wiki, if that's okay with @netblue30? That way, the maintenance burden isn't just on one person :)

<!-- gh-comment-id:504609768 --> @chiraag-nataraj commented on GitHub (Jun 22, 2019): @matu3ba Or, we can put it in the Wiki! Actually, we could transition the FAQ to the Wiki, if that's okay with @netblue30? That way, the maintenance burden isn't just on one person :)
Author
Owner

@matu3ba commented on GitHub (Jun 22, 2019):

@chiraag-nataraj Sure. Could you ask netblue30 to give me Collaborator Access?
Closing and (nicely) tagging issues would be much easier.

<!-- gh-comment-id:504613463 --> @matu3ba commented on GitHub (Jun 22, 2019): @chiraag-nataraj Sure. Could you ask netblue30 to give me Collaborator Access? Closing and (nicely) tagging issues would be much easier.
Author
Owner

@chiraag-nataraj commented on GitHub (Jun 22, 2019):

@matu3ba I believe the wiki is open for all to edit? But please follow the directions on the home page of the wiki for adding new pages and we can take it from there 🙂

<!-- gh-comment-id:504613938 --> @chiraag-nataraj commented on GitHub (Jun 22, 2019): @matu3ba I believe the wiki is open for all to edit? But please follow the directions on the home page of the wiki for adding new pages and we can take it from there :slightly_smiling_face:
Author
Owner

@matu3ba commented on GitHub (Jun 22, 2019):

Refined in #2792. Will be closed after finishing.

<!-- gh-comment-id:504614457 --> @matu3ba commented on GitHub (Jun 22, 2019): Refined in #2792. Will be closed after finishing.
Sign in to join this conversation.
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#948
No description provided.