mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #2692] Atom ain't sandboxed #1693
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#1693
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 @CodeArtisan00 on GitHub (May 12, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2692
Specs- Manjaro(KDE): kernel-4.19.36-1, Firejail-0.9.58.2-1, Atom-1.36.0-2
When I try to run atom from context menu,desktop or menubar, atom is not sanboxed though firejail has already made symlink. Firejail atom does sandbox atom though. How can I fix it?
@SkewedZeppelin commented on GitHub (May 12, 2019):
atom.desktop has a hardcoded exec line as
Exec=env /usr/bin/atomdid you run
firecfg --fix? if so, maybe firecfg can't handleExecwith extra bits like that@CodeArtisan00 commented on GitHub (May 13, 2019):
yup... firecfg --fix didn't fix it... so there is no way to resolve it,at this moment
@SkewedZeppelin commented on GitHub (May 13, 2019):
You can manually copy
/usr/share/applications/atom.desktopto~/.local/share/applcationsand edit the
Execline to beExec=atom@CodeArtisan00 commented on GitHub (May 14, 2019):
didn't work...
@chiraag-nataraj commented on GitHub (May 20, 2019):
@Neo00001 Can you do a
which atom?@matu3ba commented on GitHub (May 20, 2019):
Same issue with surf for default path.
For the firecfg output: A hint to fix the binary location (and the options where to place it exactly) would be useful.
@chiraag-nataraj commented on GitHub (May 21, 2019):
How are you installing
surfthough? At least in the default Debian package, it doesn't come with a.desktopfile...@chiraag-nataraj commented on GitHub (May 21, 2019):
Also, @Neo00001, you should file a bug at https://github.com/atom/atom/issues to tell them to stop using the absolute path in the desktop file.
@chiraag-nataraj commented on GitHub (May 28, 2019):
@Neo00001 What is the output of
which atom?@matu3ba How are you installing
surf? As I remarked in my previous comment, the version ofsurfI can install doesn't come with a.desktopfile, which is what we're talking about here. Does your version ofsurfcome with a.desktopfile (menu entry)?@matu3ba commented on GitHub (May 28, 2019):
@chiraag-nataraj Yes, for a packaged surf that is the case.
@chiraag-nataraj commented on GitHub (May 28, 2019):
@matu3ba, which distribution are you running?
@CodeArtisan00 commented on GitHub (May 28, 2019):
Sorry,man. But I've uninstalled atom long ago & don't have any intention to re-install it again.
@chiraag-nataraj commented on GitHub (May 28, 2019):
@Neo00001 🤷♂️ Okay, I guess I'll close this for now. If you ever start using it again (or if someone else is running into this), please feel free to re-open.
@matu3ba, please open a new issue with more details and we can figure it out there, thanks!