mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1385] Can't killall firejailed chromium #948
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#948
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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 chromiumand now i can't kill it withkillall -9 chromiumeven as root, sayschromium: no process found. Without firejail it works just ok. Whilepkill -9 chromiumseems to work.@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.
@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:
@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
@Harvie commented on GitHub (Jul 17, 2017):
maybe it's some protection that prevents killall from killing processes in LXC containers when managing host machine.
@Harvie commented on GitHub (Jul 17, 2017):
Ha! It works when using
killall --ns 0.Can you please put this in firejail faq or somewhere?
@netblue30 commented on GitHub (Jul 19, 2017):
So, basically they added namespace support to killall. I'll add it to FAQ, thanks.
@chiraag-nataraj commented on GitHub (May 20, 2019):
@netblue30 Where do you want to put this info?
@matu3ba commented on GitHub (Jun 22, 2019):
@netblue30 Reminder to put #1385 into FAQ.
@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 :)
@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.
@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 🙂
@matu3ba commented on GitHub (Jun 22, 2019):
Refined in #2792. Will be closed after finishing.