mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #3634] Discord 0.0.12 not starting #2286
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#2286
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 @r1bnc on GitHub (Sep 18, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3634
Write clear, concise and in textual form.
Bug and expected behavior
Discord 0.0.12 installed via deb package from the official Discord website won't run with firejail, it does work when the noprofile flag is set and without firejail.
Start normally
No profile or disabling firejail
firejail --noprofile PROGRAMin a shell?it runs fine.
whereis PROGRAM,firejail --list,stat $programpath)?Reproduce
Steps to reproduce the behavior:
firejail PROGRAMERROREnvironment
Linux distribution and version (ie output of
lsb_release -a)Distributor ID: Debian
Description: Debian GNU/Linux 10 (buster)
Release: 10
Codename: buster
Firejail version (output of
firejail --version) exclusive or used git commit (git rev-parse HEAD)firejail version 0.9.62.4
firejail from buster-backports repo:
Compile time support:
What other programs interact with the affected program for the functionality?
Are these listed in the profile?
Additional context
Other context about the problem like related errors to understand the problem.
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 (Sep 18, 2020):
Likely a duplicate, can you check other issues.
#2946, #3589, #3528, #3328, #3247, #3260, #2878, #3448, #2547, #2518
@ScoreUnder commented on GitHub (Oct 13, 2020):
For a workaround, you can copy
/etc/firejail/discord-common.profileto~/.config/firejail/and comment out theseccompline, and discord should be able to start up again.While you're at it, you may or may not also want to comment out the "novideo" line if you want to use your webcam in discord.
Bear in mind that, of course, both of these things will be less secure than the original profile. But it's still more secure than running discord unprotected, so I think it's an acceptable workaround if you're running it either way.
@rusty-snake commented on GitHub (Oct 13, 2020):
two remarks
~/.config/firejail/discord-common.localand addignore seccompandignore novideo.d08fb3b5db/etc/templates/syscalls.txt (L89-L106)Would you suggest to remove it upstream?
@rydalt commented on GitHub (Oct 13, 2020):
It was chroot.
seccomp !chrootfixes it, at least on Arch Linux. I'll try it on my OpenSUSE machine later today, if I don't comment then it works there too.And on the topic of webcams, it depends on upsteam's policy about breaking functionality in software. Personally, I prefer that discord can't use my webcam by default if I make the effort to run it in firejail, but technically it's supposed to be able to and I'm equally capable of blocking it from using my webcam myself.
@ScoreUnder commented on GitHub (Oct 13, 2020):
@rusty-snake thanks for the info, I didn't know about either of those (in fact I was despairing because there seemed to be no antonym to
novideo, and the.localfiles are included before the rest of the profile, which in most other programs means they have lower priority).I used ptrace to figure out the syscalls it makes and used the journalctl method you mentioned to find out the missing ones (somehow ptrace doesn't get them all?), and ended up with this:
Probably overkill if you're just blacklisting but maybe it's worth something to someone. (edit: added inotify for file dialog)
@rusty-snake commented on GitHub (Oct 13, 2020):
Mostly a balance between security and usability.
Security:
Usability
I would allow it as it is main-feature (as I understand) and camera should be blocked some higher (HW, BIOS, kernel) IMHO. Users can still block it.
yes, firejail does the most with
ignore <line>That's even trickier because some options have a last-will-win and some a firts-will-win.
The issue with
seccomp.keepis that it is likely to fail on new versions (binary and libraries) or different distros. However it works fine if added to locals. You can use syscalls.sh to easily generate it or most of your programs.@rusty-snake commented on GitHub (Nov 9, 2020):
I'm closing here due to inactivity, please fell free to request to reopen if you still have this issue.