mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #4708] minecraft-launcher fails with fatal error (Manjaro 5.13.19-2, nvidia) #2758
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#2758
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 @scitoast on GitHub (Nov 24, 2021).
Original GitHub issue: https://github.com/netblue30/firejail/issues/4708
Description
I just put minecraft on my completely fresh & newly updated Manjaro install. With the included minecraft-launcher firejail profile minecraft-launcher fails to start.
Steps to Reproduce
firecfg --fix-sound, logout and log back in, and thensudo firecfg)minecraft-launcherbegins loading and crashes.Observations
From the errors (see log below) it looks like there aren't permissions for the game to create or buffer something. Also (though it's irrelevant to the present bug report) it looks like /sbin and /usr/sbin are not blacklisted, which probably they should be.
Error log
Edited: I sanitized out a timestamp, pid, and some hash gibberish, just being paranoid.
Here is the output when I run minecraft-launcher from a terminal:
Final thoughts
Minecraft / java edition security has always been a concern of mine, esp. given that many players eventually load up "mods" created by random blokes. Before attempting to firejail minecraft, I spent an entire day sitting down attempting to create an AppArmor policy for it. This proved intractable (I eventually got mysterious errors about conflicting permissions I couldn't trace) and I'm convinced it's almost impossible with the tools presently available for profile creation.
Firejail works great for many apps in my experience, it would be amazing to have a sandboxed Minecraft. But I have no idea how to fix this one...thanks for your help.
@rusty-snake commented on GitHub (Nov 24, 2021):
What happens if you use
--noprofile? Is there still a AA profile (in enforce mode)?Since the errors indicate some chromium components, what happens with
firejail --ignore="caps.drop all" --ignore=nonewprivs --ignore=noroot --ignore=protocol --ignore=seccomp --ignore=tracelog /path/to/minecraft-launcher?@scitoast commented on GitHub (Nov 24, 2021):
Hi there!
firejail --noprofile /usr/bin/minecraft-launcherruns it successfully and I am able to start the game as well as run in window or fullscreen. Console logs a few errors but the game appears to run normally. Console output below from this:@scitoast commented on GitHub (Nov 24, 2021):
Follow up. I tried a variation,
firejail --ignore="caps.drop all" --ignore=protocol --ignore=seccomp --ignore=tracelog /usr/bin/minecraft-launcherThis also resulted in a GPU crash which recovered after a second and allowed normal gameplay. The console output appears to be exactly the same.
@rusty-snake commented on GitHub (Nov 24, 2021):
Ok now I'm interested, which of them work?
firejail --ignore="caps.drop all" --caps.keep=sys_admin,sys_chroot --ignore=protocol --ignore=seccomp --ignore=tracelog /usr/bin/minecraft-launcherfirejail --ignore="caps.drop all" --protocol=unix,inet,inet6,netlink,packet --ignore=seccomp --ignore=tracelog /usr/bin/minecraft-launcherfirejail --ignore="caps.drop all" --ignore=protocol --seccomp-error-action=log --ignore=tracelog /usr/bin/minecraft-launcherand follow https://github.com/netblue30/firejail/blob/master/etc/templates/syscalls.txt#L92@scitoast commented on GitHub (Nov 24, 2021):
Tried all 3 of these from launch & login through to gameplay.
Options (1), (2) and (3) all work! Doing the journal follow resulted in no blocked syscalls.
This made me suspicious, so I went to a console and simply typed a vanilla
minecraft-launcherwithout path specification. Now I'm very surprised. Minecraft loaded normally with the default firejail profile installed on the system!firejail --listshows it. This I tried several times in a row last night without getting it to load, but it is now loading consistently.Sorry for (possibly) wasting your time. I do not understand what happened, except perhaps this morning's reboot worked magic.
Edit: I wonder if it is possible that it hangs only when it needs to push an update, and has no trouble when no update is necessary. That is what it was trying to do last night.
@rusty-snake commented on GitHub (Nov 24, 2021):
It could also be a "Need to start it once without firejail after rebooting" issue.
@scitoast commented on GitHub (Nov 24, 2021):
Thank you, I'll remember it in the future.