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 #2034] Slack profile does not allow to use microphone #1370

New issue
Closed
opened 2026-05-05 07:57:18 -06:00 by gitea-mirror · 9 comments
gitea-mirror commented 2026-05-05 07:57:18 -06:00
Owner
Copy link

Originally created by @elvetemedve on GitHub (Jul 6, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2034

The problem

When Slack is started in Firejail sandbox, I can't get microphone working. The application says no sound comes from the mic. However the speakers are working as I can hear the other party.
If I run Slack without the sandboxing it works well.

Steps to reproduce

  1. Start Slack with Firejail.
  2. Open a direct message to a non-bot participant.
  3. Click on the telephone icon to start a call.

Environment

Slack version: 3.2.1 (64 bit)
Firejail version: 0.9.54
Linux kernel: 4.17.3

Originally created by @elvetemedve on GitHub (Jul 6, 2018). Original GitHub issue: https://github.com/netblue30/firejail/issues/2034 # The problem When Slack is started in Firejail sandbox, I can't get microphone working. The application says no sound comes from the mic. However the speakers are working as I can hear the other party. If I run Slack without the sandboxing it works well. ## Steps to reproduce 1. Start Slack with Firejail. 1. Open a direct message to a non-bot participant. 1. Click on the telephone icon to start a call. ### Environment Slack version: 3.2.1 (64 bit) Firejail version: 0.9.54 Linux kernel: 4.17.3
gitea-mirror 2026-05-05 07:57:18 -06:00
gitea-mirror commented 2026-05-05 07:57:24 -06:00
Author
Owner
Copy link

@smitsohu commented on GitHub (Jul 7, 2018):

Can you try if it works with one of these?

firejail --ignore=private-dev slack
firejail --ignore=whitelist slack
firejail --noblacklist=/var slack

Just some wild guesses.

Otherwise you could go to /etc/firejail/slack.profile, comment out all options (add a # in front of each line), and then uncomment line after line until you find the one that stops the microphone from working.

<!-- gh-comment-id:403239441 --> @smitsohu commented on GitHub (Jul 7, 2018): Can you try if it works with one of these? ``` firejail --ignore=private-dev slack firejail --ignore=whitelist slack firejail --noblacklist=/var slack ``` Just some wild guesses. Otherwise you could go to /etc/firejail/slack.profile, comment out all options (add a # in front of each line), and then uncomment line after line until you find the one that stops the microphone from working.
gitea-mirror commented 2026-05-05 07:57:28 -06:00
Author
Owner
Copy link

@elvetemedve commented on GitHub (Jul 8, 2018):

@smitsohu The last one (firejail --noblacklist=/var slack) solved the issue. Thanks for the hint.

I'm wondering if it's Linux distro dependent. In that case I would add this exception to firejail.local file. Otherwise it would be nice to add it to the main firejail.profile file for everyone's benefit.

<!-- gh-comment-id:403291685 --> @elvetemedve commented on GitHub (Jul 8, 2018): @smitsohu The last one (`firejail --noblacklist=/var slack`) solved the issue. Thanks for the hint. I'm wondering if it's Linux distro dependent. In that case I would add this exception to `firejail.local` file. Otherwise it would be nice to add it to the main `firejail.profile` file for everyone's benefit.
gitea-mirror commented 2026-05-05 07:57:30 -06:00
Author
Owner
Copy link

@smitsohu commented on GitHub (Jul 8, 2018):

Maybe we can replace the blacklist /var with the less restrictive whitelist /etc/firejail/whitelist-var-common.inc. Would that work for you?

If you are interested in hunting it down further, you can also run in one terminal sudo journalctl -f and in another firejail --tracelog slack. Then all blacklist violations should get logged in the first terminal.

<!-- gh-comment-id:403293664 --> @smitsohu commented on GitHub (Jul 8, 2018): Maybe we can replace the `blacklist /var` with the less restrictive `whitelist /etc/firejail/whitelist-var-common.inc`. Would that work for you? If you are interested in hunting it down further, you can also run in one terminal `sudo journalctl -f `and in another `firejail --tracelog slack`. Then all blacklist violations should get logged in the first terminal.
gitea-mirror commented 2026-05-05 07:57:33 -06:00
Author
Owner
Copy link

@elvetemedve commented on GitHub (Jul 8, 2018):

I would help to track it down, but Slack does not start when I add the --tracelog switch. At least the application window is not showed up. Any idea why?

firejail --tracelog slack

Reading profile /etc/firejail/slack.profile
Reading profile /etc/firejail/slack.local
Reading profile /etc/firejail/disable-common.inc
Reading profile /etc/firejail/disable-devel.inc
Reading profile /etc/firejail/disable-interpreters.inc
Reading profile /etc/firejail/disable-passwdmgr.inc
Reading profile /etc/firejail/disable-programs.inc
Reading profile /etc/firejail/whitelist-common.inc
Parent pid 25675, child pid 25676
Warning: skipping crypto-policies for private /etc
Private /etc installed in 30.36 ms
1 program installed in 0.60 ms
Warning: /sbin directory link was not blacklisted
Warning: /usr/sbin directory link was not blacklisted
Blacklist violations are logged to syslog
Child process initialized in 97.13 ms
<!-- gh-comment-id:403294620 --> @elvetemedve commented on GitHub (Jul 8, 2018): I would help to track it down, but Slack does not start when I add the `--tracelog` switch. At least the application window is not showed up. Any idea why? `firejail --tracelog slack` ``` Reading profile /etc/firejail/slack.profile Reading profile /etc/firejail/slack.local Reading profile /etc/firejail/disable-common.inc Reading profile /etc/firejail/disable-devel.inc Reading profile /etc/firejail/disable-interpreters.inc Reading profile /etc/firejail/disable-passwdmgr.inc Reading profile /etc/firejail/disable-programs.inc Reading profile /etc/firejail/whitelist-common.inc Parent pid 25675, child pid 25676 Warning: skipping crypto-policies for private /etc Private /etc installed in 30.36 ms 1 program installed in 0.60 ms Warning: /sbin directory link was not blacklisted Warning: /usr/sbin directory link was not blacklisted Blacklist violations are logged to syslog Child process initialized in 97.13 ms ```
gitea-mirror commented 2026-05-05 07:57:36 -06:00
Author
Owner
Copy link

@SkewedZeppelin commented on GitHub (Jul 8, 2018):

As a rougher method you can use the following instead

firejail --allow-debuggers --profile=/etc/firejail/slack.profile strace -fv -o test.log /usr/bin/slack
grep "ENOENT" -v test.log | grep "/var" > var.txt
#open var.txt and try to find anything audio related

but I agree with @smitsohu, it should be safe to replace that line with whitelist-var-common.inc instead

<!-- gh-comment-id:403295417 --> @SkewedZeppelin commented on GitHub (Jul 8, 2018): As a rougher method you can use the following instead ``` firejail --allow-debuggers --profile=/etc/firejail/slack.profile strace -fv -o test.log /usr/bin/slack grep "ENOENT" -v test.log | grep "/var" > var.txt #open var.txt and try to find anything audio related ``` but I agree with @smitsohu, it should be safe to replace that line with whitelist-var-common.inc instead
gitea-mirror commented 2026-05-05 07:57:39 -06:00
Author
Owner
Copy link

@elvetemedve commented on GitHub (Jul 8, 2018):

@smitsohu, @SkewedZeppelin If I replace blacklist /var with whitelist /etc/firejail/whitelist-var-common.inc, Slack couldn't connect to the Internet.

Secondly strace revealed only some files in /var/cache/ directory which is not relevant. I also tried to run sudo lsof +D /var during the audio call (Slack wasn't sandboxed this time of course), but again no file was kept open by Slack processes.

<!-- gh-comment-id:403303581 --> @elvetemedve commented on GitHub (Jul 8, 2018): @smitsohu, @SkewedZeppelin If I replace `blacklist /var` with `whitelist /etc/firejail/whitelist-var-common.inc`, Slack couldn't connect to the Internet. Secondly `strace` revealed only some files in **/var/cache/** directory which is not relevant. I also tried to run `sudo lsof +D /var` during the audio call (Slack wasn't sandboxed this time of course), but again no file was kept open by Slack processes.
gitea-mirror commented 2026-05-05 07:57:42 -06:00
Author
Owner
Copy link

@SkewedZeppelin commented on GitHub (Jul 8, 2018):

@elvetemedve enoent might not be the best thing to search, can you skim the output of just the following?
grep "/var' test.log

As for not having Internet when using whitelist-var-common.inc, are you using systemd-resolved?

<!-- gh-comment-id:403318706 --> @SkewedZeppelin commented on GitHub (Jul 8, 2018): @elvetemedve enoent might not be the best thing to search, can you skim the output of just the following? `grep "/var' test.log` As for not having Internet when using whitelist-var-common.inc, are you using systemd-resolved?
gitea-mirror commented 2026-05-05 07:57:45 -06:00
Author
Owner
Copy link

@chiraag-nataraj commented on GitHub (Jul 8, 2018):

@elvetemedve I suspect there may be something in /var/run/ (probably the pulse files - on my system, they're in /var/run/user/1000/pulse/) which is necessary for this to work.

Interesting, I just tried firejail --blacklist=/var and parecord within it to see if pulseaudio was affected by the blacklisted /var, and it seems it wasn't - parecord worked just fine both outside and inside the jail. I will play around to see if a combination of options will cause pulseaudio to choke.

<!-- gh-comment-id:403318784 --> @chiraag-nataraj commented on GitHub (Jul 8, 2018): @elvetemedve I suspect there may be something in `/var/run/` (probably the pulse files - on my system, they're in `/var/run/user/1000/pulse/`) which is necessary for this to work. Interesting, I just tried `firejail --blacklist=/var` and `parecord` within it to see if `pulseaudio` was affected by the blacklisted `/var`, and it seems it wasn't - `parecord` worked just fine both outside and inside the jail. I will play around to see if a combination of options will cause `pulseaudio` to choke.
gitea-mirror commented 2026-05-05 07:57:47 -06:00
Author
Owner
Copy link

@smitsohu commented on GitHub (Aug 23, 2018):

@elvetemedve Thanks for the bug report

<!-- gh-comment-id:415227035 --> @smitsohu commented on GitHub (Aug 23, 2018): @elvetemedve Thanks for the bug report
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#1370
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?