github-starred/firejail
2
0
Fork 0
mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 14:16:14 -06:00
Code Issues 531 Projects Packages Wiki Activity Actions 6

[GH-ISSUE #3861] firejail --list shows nothing #2429

New issue
Closed
opened 2026-05-05 09:06:12 -06:00 by gitea-mirror · 6 comments
gitea-mirror commented 2026-05-05 09:06:12 -06:00
Owner
Copy link

Originally created by @Self-Perfection on GitHub (Jan 1, 2021).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3861

Write clear, concise and in textual form.

Bug and expected behavior
firejail --list shows nothing (no error messages, nothing at all) regardless of existence of running firejail sandboxes.
It used to work about a year ago, with firejail 0.9.60. But does not show anything with current 0.9.64

Environment

$ lsb_release -a
LSB Version:    1.4
Distributor ID: Arch
Description:    Arch Linux
Release:        rolling
Codename:       n/a
$ firejail --version 
firejail version 0.9.64

Compile time support:
        - AppArmor support is enabled
        - AppImage support is enabled
        - chroot support is enabled
        - D-BUS proxy support is enabled
        - file and directory whitelisting support is enabled
        - file transfer support is enabled
        - firetunnel support is enabled
        - networking support is enabled
        - overlayfs support is enabled
        - private-home support is enabled
        - SELinux support is disabled
        - user namespace support is enabled
        - X11 sandboxing support is enabled

Additional context
I don't know how firejail lists active sandboxes. I suppose it somehow interacts with /run/firejail but I could not spot any differences in this aspect with another Ubuntu 20.04 system where firejail --list works.

Checklist

  • The upstream profile (and redirect profile if exists) have no changes fixing it.
  • The program has a profile. (If not, request one in https://github.com/netblue30/firejail/issues/1139)
  • A short search for duplicates was performed.
  • If it is a AppImage, --profile=PROFILENAME is used to set the right profile.
  • Used LC_ALL=en_US.UTF-8 LANG=en_US.UTF-8 PROGRAM to get english error-messages.
  • I'm aware of browser-allow-drm yes/browser-disable-u2f no in firejail.config to allow DRM/U2F in browsers.
Originally created by @Self-Perfection on GitHub (Jan 1, 2021). Original GitHub issue: https://github.com/netblue30/firejail/issues/3861 Write clear, concise and in textual form. **Bug and expected behavior** `firejail --list` shows nothing (no error messages, nothing at all) regardless of existence of running firejail sandboxes. It used to work about a year ago, with firejail 0.9.60. But does not show anything with current 0.9.64 **Environment** ``` $ lsb_release -a LSB Version: 1.4 Distributor ID: Arch Description: Arch Linux Release: rolling Codename: n/a $ firejail --version firejail version 0.9.64 Compile time support: - AppArmor support is enabled - AppImage support is enabled - chroot support is enabled - D-BUS proxy support is enabled - file and directory whitelisting support is enabled - file transfer support is enabled - firetunnel support is enabled - networking support is enabled - overlayfs support is enabled - private-home support is enabled - SELinux support is disabled - user namespace support is enabled - X11 sandboxing support is enabled ``` **Additional context** I don't know how firejail lists active sandboxes. I suppose it somehow interacts with `/run/firejail` but I could not spot any differences in this aspect with another Ubuntu 20.04 system where `firejail --list` works. **Checklist** - [x] The upstream profile (and redirect profile if exists) have no changes fixing it. - [x] The program has a profile. (If not, request one in `https://github.com/netblue30/firejail/issues/1139`) - [x] A short search for duplicates was performed. - [x] If it is a AppImage, `--profile=PROFILENAME` is used to set the right profile. - [x] Used `LC_ALL=en_US.UTF-8 LANG=en_US.UTF-8 PROGRAM` to get english error-messages. - [ ] I'm aware of `browser-allow-drm yes`/`browser-disable-u2f no` in `firejail.config` to allow DRM/U2F in browsers.
gitea-mirror commented 2026-05-05 09:06:15 -06:00
Author
Owner
Copy link

@SkewedZeppelin commented on GitHub (Jan 1, 2021):

firejail --list shows nothing

Are you using hidepid?

<!-- gh-comment-id:753389911 --> @SkewedZeppelin commented on GitHub (Jan 1, 2021): > firejail --list shows nothing Are you using hidepid?
gitea-mirror commented 2026-05-05 09:06:16 -06:00
Author
Owner
Copy link

@Self-Perfection commented on GitHub (Jan 4, 2021):

@SkewedZeppelin Hi
Indeed I do use hidepid. But I am quite sure half a year ago hidepid was already enabled and firejail --list worked.

<!-- gh-comment-id:754000148 --> @Self-Perfection commented on GitHub (Jan 4, 2021): @SkewedZeppelin Hi Indeed I do use hidepid. But I am quite sure half a year ago hidepid was already enabled and `firejail --list` worked.
gitea-mirror commented 2026-05-05 09:06:17 -06:00
Author
Owner
Copy link

@rusty-snake commented on GitHub (Jan 4, 2021):

Maybe sudo firejail --list?

<!-- gh-comment-id:754008250 --> @rusty-snake commented on GitHub (Jan 4, 2021): Maybe `sudo firejail --list`?
gitea-mirror commented 2026-05-05 09:06:18 -06:00
Author
Owner
Copy link

@Self-Perfection commented on GitHub (Jan 4, 2021):

sudo firejail --list does not show anything either.

But searching for "hidepid" gave me #1927 which is very much related. It gave me advice to try firemon --list and this command works and shows list of sandboxes. At least I have workaround now.

<!-- gh-comment-id:754010384 --> @Self-Perfection commented on GitHub (Jan 4, 2021): `sudo firejail --list` does not show anything either. But searching for "hidepid" gave me #1927 which is very much related. It gave me advice to try `firemon --list` and this command works and shows list of sandboxes. At least I have workaround now.
gitea-mirror commented 2026-05-05 09:06:20 -06:00
Author
Owner
Copy link

@smitsohu commented on GitHub (Jan 4, 2021):

Indeed I do use hidepid. But I am quite sure half a year ago hidepid was already enabled and firejail --list worked.

yeah, it's caused by a change in the kernel. It should be fixed in git master.

<!-- gh-comment-id:754184252 --> @smitsohu commented on GitHub (Jan 4, 2021): > Indeed I do use hidepid. But I am quite sure half a year ago hidepid was already enabled and firejail --list worked. yeah, it's caused by a change in the kernel. It should be fixed in git master.
gitea-mirror commented 2026-05-05 09:06:21 -06:00
Author
Owner
Copy link

@Self-Perfection commented on GitHub (Mar 9, 2021):

With firejail 0.9.64.4 and kernel 5.11.2-arch1-1 I now get expected output from firejail --list. Firemon stopped showing list but gives useful hint:

$ firemon --list
Error: /proc is mounted hidepid, you would need to be root to run this command

Seems OK to me and this issue seems to be resolved.

<!-- gh-comment-id:794210828 --> @Self-Perfection commented on GitHub (Mar 9, 2021): With firejail 0.9.64.4 and kernel 5.11.2-arch1-1 I now get expected output from `firejail --list`. Firemon stopped showing list but gives useful hint: ``` $ firemon --list Error: /proc is mounted hidepid, you would need to be root to run this command ``` Seems OK to me and this issue seems to be resolved.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
serialize_remounts_v2
landlock_v4
landlock
release-0.9.64
release-0.9.62
gitlab_ci
LTSbase
fred_ctests
docs
0.9.80
0.9.80-rc1
0.9.78
0.9.76
0.9.76-rc4
0.9.76-rc3
0.9.76-rc2
0.9.76-rc1
0.9.74
landlock-split
0.9.72
0.9.72rc1
0.9.70
0.9.68
0.9.68rc1
0.9.66
0.9.66rc1
0.9.64.4
0.9.64.2
0.9.64
0.9.64rc1
0.9.62.4
0.9.62.2
0.9.62
0.9.56.2-LTS
0.9.60
0.9.60-rc1
0.9.58.2
0.9.58
0.9.58-rc1
0.9.56-LTS-release
0.9.56-LTS
0.9.56
0.9.56-rc1
0.9.54
0.9.54-rc2
0.9.54-rc1
0.9.52
0.9.38.12
0.9.50
0.9.50-rc1
0.9.48
0.9.46
0.9.46-rc1
0.9.44.10
0.9.44.8
0.9.44.6
0.9.38.10
0.9.44.4
0.9.38.8
0.9.44.2
0.9.44
0.9.44-rc1
0.9.38.4
0.9.42
0.9.42-rc2
0.9.38.2
0.9.42-rc1
disable-globalcfg
0.9.40
0.9.40-rc1
0.9.38
0.9.38-rc1
0.9.36
0.9.36-rc1
0.9.34
0.9.34-rc1
0.9.32
0.9.32-rc1
0.9.30
0.9.30-rc1
Labels
Clear 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

Mirrored from GitHub Pull Request

  
question

   
question_old

   
removal

   
runtime-permissions

   
sandbox-ipc

   
security

   
stale

   
wiki

   
wiki

   
wontfix

   
wordpress

   
workaround
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
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#2429
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?