mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #4132] Can't start newest slack #2547
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#2547
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 @enthusiasmus on GitHub (Mar 22, 2021).
Original GitHub issue: https://github.com/netblue30/firejail/issues/4132
Hi there!
Bug and expected behavior
I want to run slack via firejail. It won't run. It produces several different errors.
Reproduce
Steps to reproduce the behavior:
firejail slackowner and mode is correct
-rwsr-xr-x 1 root root 225432 Mär 16 01:16 /usr/lib/slack/chrome-sandboxWith
--noprofile:When using the latest slack.profile file, I receive the following error:
Environment
Debug output with old slack.profiles
With newest slack.profiles
Very hard for me to use slack via firejail. :-/ Any ideas? Thanks!
@CodeArtisan00 commented on GitHub (Mar 23, 2021):
#3806 #3807
firejail 0.9.58.2 doesn't have this. you may check by
find /etc/firejail/disable-shell.inc.You may use debian backport package btw.@rusty-snake commented on GitHub (Mar 23, 2021):
This should work with firejail from backports, so if you can upgrade.
@enthusiasmus commented on GitHub (Mar 24, 2021):
Thanks for your help! I downloaded the deb from this firejail repo and installed it.
but i'm not able to start slack
any further ideas?
@CodeArtisan00 commented on GitHub (Mar 24, 2021):
@enthusiasmus what happens if you run
firejail --ignore="include disable-shell.inc" --ignore=private-bin slack@enthusiasmus commented on GitHub (Mar 24, 2021):
this is what happens
@CodeArtisan00 commented on GitHub (Mar 24, 2021):
@enthusiasmus does
firejail --noprofilework?@enthusiasmus commented on GitHub (Mar 24, 2021):
it doesn't work :/
@CodeArtisan00 commented on GitHub (Mar 24, 2021):
can you try with
bashinstead ofzsh? just to check whether it works or not.@enthusiasmus commented on GitHub (Mar 24, 2021):
how can I try it with bash? :'-) I started a bash and executed firejail with bash, but it chooses zsh anyway
@CodeArtisan00 commented on GitHub (Mar 24, 2021):
I mean to say change your shell from
zshtobashEdit: you may try
firejail --shell=/bin/bash slack@enthusiasmus commented on GitHub (Mar 24, 2021):
done - but same here
@CodeArtisan00 commented on GitHub (Mar 24, 2021):
hmmm... something is wrong for sure. does
slackrun withoutfirejail?@enthusiasmus commented on GitHub (Mar 24, 2021):
Something I tried to avoid, because for me slack isn't trustworthy enough. But no, it doesn't start even without firejail - omg, sorry!
@enthusiasmus commented on GitHub (Mar 24, 2021):
I will try the previous release
@enthusiasmus commented on GitHub (Mar 24, 2021):
Currently only slack via snap works for my debian version - I doesn't make any sense to use here firejail, does it?
@CodeArtisan00 commented on GitHub (Mar 24, 2021):
Nope.
f4f6767458/RELNOTES (L105)@ghost commented on GitHub (Mar 24, 2021):
@enthusiasmus Just for the record, I've noticed the below in some of your output posted here:
I'm not saying your observation that slack isn't working properly even without firejail is incorrect. That can happen. But when trying to debug it's vital to pay attention to the fact that firecfg implies having symlinks in /usr/local/bin with the same name as those in /usr/bin. That's the way firejail can do its 'magic' internally (desktop integration). Bottomlin, when you try to run an application from the command line to add/ignore/test specific firejail options, use full paths to whatever app involved:
@CodeArtisan00 commented on GitHub (Apr 9, 2021):
Closing this as OP is using snap.