mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #3464] Atom 1.48.0 breaks with Firejail 0.9.58.2 #2178
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#2178
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 @kmotoko on GitHub (Jun 11, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3464
Bug and expected behavior
Upgrading from
atom1.46.0to1.48.0breaks startingatomunderfirejail.atomto start normally.No profile or disabling firejail
firejail --noprofile PROGRAMin a shell?atomstarts-up normally.whereis PROGRAM,firejail --list,stat $programpath)?atomstarts-up normally.Reproduce
Steps to reproduce the behavior:
firejail atomEnvironment
lsb_release -a)firejail --version) exclusive or used git commit (git rev-parse HEAD)To my knowledge:
git,GVFS TrashYes.
Additional context
I have a strong feeling that the issue is related to change in PR#20799, which fixes the Issue#20756.
My
atom.profile:My
atom.local:I gradually commented out certain entries in my
atom.profilejust to test, the following does not preventatomfrom starting-up:Checklist
find / -name 'firejail' 2>/dev/null/fd firejailto locate profiles ie in/usr/local/etc/firejail/PROGRAM.profile)debug output
@rusty-snake commented on GitHub (Jun 11, 2020):
Can you try https://github.com/netblue30/firejail/issues/2946#issue-490558630.
@kmotoko commented on GitHub (Jun 11, 2020):
@rusty-snake , adding the following returns the same error:
Running
firejail --ignore=nonewprivs --ignore=noroot --ignore=protocol --ignore=seccomp --ignore=caps.drop --caps.keep=sys_admin,sys_chroot /usr/bin/atomchanges the error to:@rusty-snake commented on GitHub (Jun 11, 2020):
Is
force-nonewprivsset in /etc/firejail/firejail.config?@kmotoko commented on GitHub (Jun 11, 2020):
It was commented out, I tried both
force-nonewprivs noandforce-nonewprivs yeswith no luck (the error did not change).@rusty-snake commented on GitHub (Jun 11, 2020):
What's in your globals.local?
@kmotoko commented on GitHub (Jun 11, 2020):
Nothing related actually:
@rusty-snake commented on GitHub (Jun 11, 2020):
I'm out of ideas for now. Maybe you need to also ignore
nogroups@kmotoko commented on GitHub (Jun 12, 2020):
That didn't work either. I will keep playing with the rules and post if I find something.
@rusty-snake commented on GitHub (Jun 12, 2020):
Because
--noprofileworks, we know that it is caused by one (or more) command in the profile. If you comment the full profile and then uncomment it line for line you will find it. However, I'm afraid, that it is a interaction between more commands, that is harder to debug.@Fred-Barclay commented on GitHub (Jun 12, 2020):
@rusty-snake I'm able to get it to work if I comment out
caps.drop allnonewprivsnorootprotocol unix,inet,inet6,netlinkseccompNaturally I want to tighten this down a bit but hopefully I can get a fix in within a day or so.
@Fred-Barclay commented on GitHub (Jun 12, 2020):
@kmotoko can you try with the new profile
cb67995230/etc/profile-a-l/atom.profile?Cheers!
Fred
@rusty-snake commented on GitHub (Jun 13, 2020):
This profile does not work with 0.9.58.2
@Fred-Barclay commented on GitHub (Jun 13, 2020):
@rusty-snake thanks for catching that! I'll put in a fix under etc-fixes for 0.9.58 and the other distro-supported releases (0.9.52, 0.9.58, and 0.9.60). This would skip 0.9.44, but since Debian 9 goes EOL in less than a month and 0.9.58 is in its backports, it may be better not to patch this one...
@Fred-Barclay commented on GitHub (Jun 13, 2020):
@kmotoko please try with this one:
55906959a9/etc-fixes/0.9.58/atom.profile