[PR #2199] [MERGED] Fix #2142: Firefox appimage fails because it needs non-default seccomp #4220

Closed
opened 2026-05-05 10:15:59 -06:00 by gitea-mirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/netblue30/firejail/pull/2199
Author: @crass
Created: 10/16/2018
Status: Merged
Merged: 10/17/2018
Merged by: @netblue30

Base: masterHead: fix-2142-firefox-sandbox-appimage


📝 Commits (1)

  • f74fa71 Do not override user provided seccomp lists when in chroot/overlay/appimage, but to use the default if none is provided.

📊 Changes

1 file changed (+1 additions, -10 deletions)

View changed files

📝 src/firejail/sandbox.c (+1 -10)

📄 Description

Do not override user provided seccomp lists when in chroot/overlay/appimage, but to use the default if none is provided. This is a more general fix. I see no reason we are forcing users to use a default seccomp filter with those options. There should be a default if no seccomp filter is provided, but if one is provided, it should not be ignored in favor of the default. This allows the firefox appimage to work, because its sandboxing need chroot, which is disabled in the @default seccomp filter (see #2142).


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/netblue30/firejail/pull/2199 **Author:** [@crass](https://github.com/crass) **Created:** 10/16/2018 **Status:** ✅ Merged **Merged:** 10/17/2018 **Merged by:** [@netblue30](https://github.com/netblue30) **Base:** `master` ← **Head:** `fix-2142-firefox-sandbox-appimage` --- ### 📝 Commits (1) - [`f74fa71`](https://github.com/netblue30/firejail/commit/f74fa71cf9d549b1607ca5b0c9fb2442e31f72ab) Do not override user provided seccomp lists when in chroot/overlay/appimage, but to use the default if none is provided. ### 📊 Changes **1 file changed** (+1 additions, -10 deletions) <details> <summary>View changed files</summary> 📝 `src/firejail/sandbox.c` (+1 -10) </details> ### 📄 Description Do not override user provided seccomp lists when in chroot/overlay/appimage, but to use the default if none is provided. This is a more general fix. I see no reason we are forcing users to use a default seccomp filter with those options. There should be a default if no seccomp filter is provided, but if one is provided, it should not be ignored in favor of the default. This allows the firefox appimage to work, because its sandboxing need chroot, which is disabled in the @default seccomp filter (see #2142). --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
gitea-mirror 2026-05-05 10:15:59 -06:00
Sign in to join this conversation.
No milestone
No project
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#4220
No description provided.