mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #4212] Invalid --env setting, Failed to compile git version on Arch Linux with --enable-apparmor #2582
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#2582
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 @oogeek on GitHub (Apr 25, 2021).
Original GitHub issue: https://github.com/netblue30/firejail/issues/4212
Environment
I am using:
gcc 10.2.0
I have checked that it has the newest commits.
Additional context
I have tried two ways to compile it. One is to install it with
yay -S firejail-git, another is togit cloneand manually runconfigureandmakeChecklist
https://github.com/netblue30/firejail/issues/1139)--profile=PROFILENAMEis used to set the right profile.LC_ALL=en_US.UTF-8 LANG=en_US.UTF-8 PROGRAMto get english error-messages.browser-allow-drm yes/browser-disable-u2f noinfirejail.configto allow DRM/U2F in browsers.@rusty-snake commented on GitHub (Apr 25, 2021):
Do you get any error?
@oogeek commented on GitHub (Apr 25, 2021):
This comes from
yayinstall.@oogeek commented on GitHub (Apr 25, 2021):
Git clone
This is by first
./configure --prefix=/usr --enable-apparmorthen
make@oogeek commented on GitHub (Apr 25, 2021):
The weird thing to note is that I did succeed once and once only. I think I just use
./configurewith no parameters. I just don't know why.The reason why I tried to use git version is that I got error like
when using the
firejail 0.9.64.4-1from Arch Repo. It is really frustrating.Then I remember clearly that this error disappear after I installed the git version.
Now I tried to upgrade to the lastest git version and then...
@rusty-snake commented on GitHub (Apr 25, 2021):
FWIW: https://aur.archlinux.org/packages/firejail-git/#comment-748310
@oogeek commented on GitHub (Apr 25, 2021):
I have seen it but I think I have keep my Arch up to date. I just do another update check and it shows that everything is in sync. Not sure if something breaks again.
@ghost commented on GitHub (Apr 26, 2021):
@oogeek I'm on Arch Linux too and as collaborator here I build from git master several times per day. I have a custom PKGBUILD, but I've tested firejail-git from AUR also. That builds just fine for me, and it includes the --enable-apparmor switch you mention. So alas I cannot reproduce.
Have you tried building in a clean chroot yet? That's the best way to determine what's going on at your end, especially if you're not 100% sure your system is fully updated or something else in your setup causes this.
Can you show us the full command and output from env when you get this error? I think that's the problem you should focus on first.
@oogeek commented on GitHub (Apr 26, 2021):
@glitsj16 Thanks for your suggestion. I tried to build it in chroot and it works. Now I need to dig into the env and see what is wrong.
@ghost commented on GitHub (Apr 26, 2021):
@oogeek Well that's progress at least. Perhaps https://github.com/netblue30/firejail/issues/3678 and the other issues discussed in there can offer some context.
@oogeek commented on GitHub (Apr 26, 2021):
@glitsj16 This happens when I run almost every command. And the newly compiled git version in chroot fix it.
@oogeek commented on GitHub (Apr 26, 2021):
And this is
printenv. I tried to use command likefirejail --rmenv=soemthing commandbut it does not help.@rusty-snake commented on GitHub (Apr 26, 2021):
Duplicate of #3965
@oogeek commented on GitHub (Apr 26, 2021):
Thanks for mentioning the cause. 😄 Sorry for any inconvenience. Shall I close the issue?
@oogeek commented on GitHub (May 23, 2021):
So after reducing the packages on my Arch setup from 1500+ to 900+, the error disappears. It is really strange.