mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #118] Chromium profile broken under current git #78
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#78
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 @pyamsoft on GitHub (Nov 4, 2015).
Original GitHub issue: https://github.com/netblue30/firejail/issues/118
Chromium fails to launch because it depends on the usage of perl, which is blacklisted in the chromium script due to the incluson of the the disable-devel.inc file, which blacklists perl.
Most recent commit at time of filing:
cc29de3777@pyamsoft commented on GitHub (Nov 4, 2015):
This is infact caused from ArchLinux's configuration of chromium. The repository package comes with a perl script that is used to launch the browser, and the blacklisting of perl is causing said script to fail.
The issue can be remedied by creating a custom chromium profile which overrides the existing one, and adding a line to noblacklist /usr/bin/perl
This will be closed as it is not a bug in firejail.
@netblue30 commented on GitHub (Nov 4, 2015):
Fixed in Firejail - disable-devel.inc is commented out.
@pyamsoft commented on GitHub (Nov 4, 2015):
Wouldn't it be better to instead add the following at the top of the chromium.profile:
This way users will still benefit from the blacklisting of other devel items, but still be able to utilze the perl script when needed.
@netblue30 commented on GitHub (Nov 4, 2015):
I'll keep that in mind, thanks. There will be some more modifications going in there.