mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #481] Firejail fails to launch several applications after system update #341
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#341
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 @ghost on GitHub (Apr 25, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/481
After updating my system today firejail fails to launch most applications, unless I use --noprofile to disable the generic profile.
Checking syslog:
Running Debian sid
Firejail from the repo:
The generic profile:
The last updates:
Any suggestion?
I understand this may not be a bug with firejail, but this was my starting point.
@liloman commented on GitHub (Apr 26, 2016):
It was broken for me yesterday It seemed something related to the new checkings on get*uid. I just checkout to former commits and problem solved.
@ghost commented on GitHub (Apr 26, 2016):
Hi, nobeljone.
Invoking firejail with those arguments makes it work again. Thanks for the tip!
I find strange that if I comment the
seccompandcaps.drop allin thegeneric.profilethe problem still persists.Hi, liloman.
Do you mean that this behaviour does not happen with former commits?
@netblue30 commented on GitHub (Apr 27, 2016):
I'll set a Sid system here and take a look, thanks for letting me know.
@liloman: what commits you checked out?
@irregulator commented on GitHub (May 1, 2016):
Both Iceweasel and Icedove are failing to start because default seccomp filter blacklists 'mount' syscall.
I am running firejail version "0.9.40
rc2", compiled out ofdeb8u1" and iceweasel version "38.8.0esr-1~deb8u1"2bd593cbebin master branch. I'm also running Debian testing with icedove version "38.7.0-1Firejail execution example and audit logs indicating the problem are:
I've also managed to launch both icedove and iceweasel like so:
i.e. not dropping 'mount' syscall
@netblue30 commented on GitHub (May 1, 2016):
Moving the discussion here: https://github.com/netblue30/firejail/issues/494
@Wadkar07 commented on GitHub (May 22, 2018):
hey hello,
i am new to linux and github, i am using parrot sec os and i am facing a problem of firejail:
Reading profile /etc/firejail/wine.profile
Reading profile /etc/firejail/disable-common.inc
Reading profile /etc/firejail/disable-devel.inc
Reading profile /etc/firejail/disable-programs.inc
Parent pid 12326, child pid 12327
Child process initialized in 778.40 ms
Usage: wine PROGRAM [ARGUMENTS...] Run the specified program
wine --help Display this help and exit
wine --version Output version information and exit
Parent is shutting down, bye...