mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #248] Whitelist ~/.cache/fontconfig/ by default #176
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#176
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 @Lymia on GitHub (Jan 21, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/248
I noticed that some programs like Firefox take forever to launch under firejail, and eat up 100% of a core while launching, while test cases like "firejail bash" didn't.
I investigated a bit, and it seems that white-listing ~/.cache/fontconfig/ makes Firefox launch a lot faster. Without it, I believe Firefox's rebuilding the font cache on every startup.
@Saren-Arterius commented on GitHub (Jan 21, 2016):
also ~/.config/fontconfig/
@netblue30 commented on GitHub (Jan 21, 2016):
It is already fixed in git for the next release. Thanks.
@Lymia commented on GitHub (Jan 21, 2016):
Is it? I don't see ~/.cache/fontconfig anywhere in the tree, only ~/.config/fontconfig. It's a different directory.
$ grep -r "fontconfig"
etc/conkeror.profile:whitelist ~/.fontconfig
etc/whitelist-common.inc:whitelist ~/.fontconfig
etc/whitelist-common.inc:whitelist ~/.config/fontconfig
@netblue30 commented on GitHub (Jan 23, 2016):
OOPS! I put it in now, thanks!