[GH-ISSUE #2513] firejail doesn't detach #1633

Closed
opened 2026-05-05 08:17:13 -06:00 by gitea-mirror · 9 comments
Owner

Originally created by @vorticalbox on GitHub (Mar 4, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2513

I am running parrotOS and some times when I run a terminal command such as vscodeium . the terminal doesn't detach and just sits in the terminal.

└──╼ $vscodium .
Reading profile /etc/firejail/vscodium.profile
Reading profile /etc/firejail/disable-common.inc
Reading profile /etc/firejail/disable-passwdmgr.inc
Reading profile /etc/firejail/disable-programs.inc
Parent pid 3964, child pid 3966
Child process initialized in 76.81 ms
Originally created by @vorticalbox on GitHub (Mar 4, 2019). Original GitHub issue: https://github.com/netblue30/firejail/issues/2513 I am running parrotOS and some times when I run a terminal command such as vscodeium . the terminal doesn't detach and just sits in the terminal. ``` └──╼ $vscodium . Reading profile /etc/firejail/vscodium.profile Reading profile /etc/firejail/disable-common.inc Reading profile /etc/firejail/disable-passwdmgr.inc Reading profile /etc/firejail/disable-programs.inc Parent pid 3964, child pid 3966 Child process initialized in 76.81 ms ```
gitea-mirror 2026-05-05 08:17:13 -06:00
Author
Owner

@smitsohu commented on GitHub (Mar 12, 2019):

You mean the sandbox keeps running after you close the main app? If this happens there is still a process running inside the sandbox. Firejail only shuts down when the sandbox is empty.

You could run firejail --tree to get an idea what is going on.

<!-- gh-comment-id:472061760 --> @smitsohu commented on GitHub (Mar 12, 2019): You mean the sandbox keeps running after you close the main app? If this happens there is still a process running inside the sandbox. Firejail only shuts down when the sandbox is empty. You could run `firejail --tree` to get an idea what is going on.
Author
Owner

@vorticalbox commented on GitHub (Mar 12, 2019):

Normally when you run a command such as firejail firefox

The process stops in the terminal window but from time to it just stops at the last part until you close it

<!-- gh-comment-id:472069021 --> @vorticalbox commented on GitHub (Mar 12, 2019): Normally when you run a command such as firejail firefox The process stops in the terminal window but from time to it just stops at the last part until you close it
Author
Owner

@smitsohu commented on GitHub (Mar 12, 2019):

until you close it

You mean until you close the terminal ... ?

<!-- gh-comment-id:472073113 --> @smitsohu commented on GitHub (Mar 12, 2019): > until you close it You mean until you close the terminal ... ?
Author
Owner

@vorticalbox commented on GitHub (Mar 12, 2019):

Close the app.

normaly the command stops and drops you back into the shell not wait until thwbapp is closed

<!-- gh-comment-id:472077616 --> @vorticalbox commented on GitHub (Mar 12, 2019): Close the app. normaly the command stops and drops you back into the shell not wait until thwbapp is closed
Author
Owner

@smitsohu commented on GitHub (Mar 12, 2019):

normaly the command stops and drops you back into the shell not wait until thwbapp is closed

Actually this is what I would expect to happen. When you run firejail firefox the next time and you drop back right away into the shell, can you check the output of firejail --list if Firefox is indeed sandboxed?

<!-- gh-comment-id:472114226 --> @smitsohu commented on GitHub (Mar 12, 2019): > normaly the command stops and drops you back into the shell not wait until thwbapp is closed Actually this is what I would expect to happen. When you run `firejail firefox` the next time and you drop back right away into the shell, can you check the output of `firejail --list` if [Firefox is indeed sandboxed](https://firejail.wordpress.com/support/#firefox)?
Author
Owner

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

@vorticalbox, were you able to check this?

<!-- gh-comment-id:494306929 --> @chiraag-nataraj commented on GitHub (May 21, 2019): @vorticalbox, were you able to check this?
Author
Owner

@vorticalbox commented on GitHub (May 21, 2019):

I'm afraid not I haven't done any security testing at work that has required me to spin up my VM.

If I have time tomorrow I'll give it a go.

<!-- gh-comment-id:494524290 --> @vorticalbox commented on GitHub (May 21, 2019): I'm afraid not I haven't done any security testing at work that has required me to spin up my VM. If I have time tomorrow I'll give it a go.
Author
Owner

@rusty-snake commented on GitHub (May 22, 2019):

https://github.com/netblue30/firejail/issues/2698#issuecomment-493028100

firejail sh -c "sleep 1m &" didn't go in background. Not sure how firejail handel stdin/out and fg/bg.

<!-- gh-comment-id:494775916 --> @rusty-snake commented on GitHub (May 22, 2019): https://github.com/netblue30/firejail/issues/2698#issuecomment-493028100 > `firejail sh -c "sleep 1m &"` didn't go in background. Not sure how firejail handel stdin/out and fg/bg.
Author
Owner

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

@vorticalbox I'm going to go ahead and close this for now, but please feel free to re-open if you're able to test out our suggestion.

<!-- gh-comment-id:497878025 --> @chiraag-nataraj commented on GitHub (May 31, 2019): @vorticalbox I'm going to go ahead and close this for now, but please feel free to re-open if you're able to test out our suggestion.
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#1633
No description provided.