[GH-ISSUE #6720] firefox: add new tridactylrc config path #3345

New issue

Closed

opened 2026-05-05 09:55:47 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 09:55:47 -06:00

Owner

Originally created by @petRUShka on GitHub (Apr 27, 2025).
Original GitHub issue: https://github.com/netblue30/firejail/issues/6720

Description

Tridactyl: the default rc path isn't only
~/.tridactylrc but also ~/.config/tridactyl/tridactylrc.

Therefore, in /etc/profile-a-l/firefox-common-addons.profile:

# old
whitelist ${HOME}/.tridactylrc

must be replaced (or complemented) with:

# new
whitelist ${HOME}/.config/tridactyl/tridactylrc
whitelist ${HOME}/.tridactylrc   # optional legacy line

Proposed patch

diff --git a/etc/profile-a-l/firefox-common-addons.profile b/etc/profile-a-l/firefox-common-addons.profile
--- a/etc/profile-a-l/firefox-common-addons.profile
+++ b/etc/profile-a-l/firefox-common-addons.profile
@@
- whitelist ${HOME}/.tridactylrc
+ whitelist ${HOME}/.config/tridactyl/tridactylrc
+ whitelist ${HOME}/.tridactylrc

Originally created by @petRUShka on GitHub (Apr 27, 2025). Original GitHub issue: https://github.com/netblue30/firejail/issues/6720 ### Description Tridactyl: the default rc path isn't only `~/.tridactylrc` but also `~/.config/tridactyl/tridactylrc`. Therefore, in `/etc/profile-a-l/firefox-common-addons.profile`: ```ini # old whitelist ${HOME}/.tridactylrc ``` must be replaced (or complemented) with: ```ini # new whitelist ${HOME}/.config/tridactyl/tridactylrc whitelist ${HOME}/.tridactylrc # optional legacy line ``` ### Proposed patch ```diff diff --git a/etc/profile-a-l/firefox-common-addons.profile b/etc/profile-a-l/firefox-common-addons.profile --- a/etc/profile-a-l/firefox-common-addons.profile +++ b/etc/profile-a-l/firefox-common-addons.profile @@ - whitelist ${HOME}/.tridactylrc + whitelist ${HOME}/.config/tridactyl/tridactylrc + whitelist ${HOME}/.tridactylrc ```

gitea-mirror closed this issue

2026-05-05 09:55:48 -06:00

gitea-mirror commented

2026-05-05 09:55:49 -06:00

Author

Owner

@kmk3 commented on GitHub (Apr 30, 2025):

In general please avoid opening an issue if you are going to open a PR to close
it right after anyway (especially for trivial fixes), as any discussion is
likely going to happen in the PR, so the issue only adds noise.

In the future, it would be better to open just either an issue for discussion
or the PR directly.

For now leave this as is as the PR will close it.

@kmk3 commented on GitHub (Apr 30, 2025): In general please avoid opening an issue if you are going to open a PR to close it right after anyway (especially for trivial fixes), as any discussion is likely going to happen in the PR, so the issue only adds noise. In the future, it would be better to open just either an issue for discussion or the PR directly. For now leave this as is as the PR will close it.

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#3345

No description provided.

Rows
Columns