mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #3648] Regression: Error: no such executable /usr/bin/git #2300
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#2300
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 @chiraag-nataraj on GitHub (Sep 28, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3648
With firejail 0.9.62.4, my git profile works fine (attached). With current HEAD, the profile breaks and the error in the issue title is reported (obviously, /usr/bin/git exists). I will try to bisect later today when I have time.
common.inc
git.profile
ssh.profile
@chiraag-nataraj commented on GitHub (Sep 28, 2020):
git bisectis telling me that #3740f37648is bad:@chiraag-nataraj commented on GitHub (Sep 28, 2020):
Although something doesn't seem right...I was using a later version with that merge and it was fine. Going to dig in to see what's going on.
@chiraag-nataraj commented on GitHub (Sep 28, 2020):
The plot gets thicker. With the provided profile files, everything is fine. When I use my profile files that I linked to above (which, again, worked fine with 0.9.62.4), it breaks. So I guess it's not quite a regression, but it is some type of bug, I suspect...
@chiraag-nataraj commented on GitHub (Sep 29, 2020):
Not sure how or why, but the issue fixed itself. Closing.