github-starred/firejail

Fork 0

mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 14:16:14 -06:00

bin #458

New issue

Closed

opened 2026-05-05 05:54:25 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 05:54:25 -06:00

Owner

Originally created by @Fred-Barclay on GitHub (Jul 30, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/667

This isn't exactly firecfg's fault, but whenever a programme is already installed to /usr/loca/bin, then firecfg fails to create a link/launcher for it.
For example, the debian package for gitter installs to /usr/local/bin/gitter by default. Even though gitter is listed in src/firecfg/firecfg.config, firecfg does not (re)create /usr/local/bin/gitter.

I don't know what to suggest about this but just wanted to point it out. 😄
Cheers!

Originally created by @Fred-Barclay on GitHub (Jul 30, 2016). Original GitHub issue: https://github.com/netblue30/firejail/issues/667 This isn't exactly firecfg's fault, but whenever a programme is already installed to /usr/loca/bin, then firecfg fails to create a link/launcher for it. For example, the debian package for gitter installs to /usr/local/bin/gitter by default. Even though gitter is listed in src/firecfg/firecfg.config, firecfg does not (re)create /usr/local/bin/gitter. I don't know what to suggest about this but just wanted to point it out. :smile: Cheers!

gitea-mirror

2026-05-05 05:54:25 -06:00

closed this issue
added the
bug
label

gitea-mirror commented

2026-05-05 05:54:31 -06:00

Author

Owner

@reinerh commented on GitHub (Jul 30, 2016):

That is also a bug in the package. They are not supposed to place files in /usr/local.

@reinerh commented on GitHub (Jul 30, 2016): That is also a bug in the package. They are not supposed to place files in /usr/local.

gitea-mirror commented

2026-05-05 05:54:33 -06:00

Author

Owner

@netblue30 commented on GitHub (Jul 31, 2016):

Bug!

@netblue30 commented on GitHub (Jul 31, 2016): Bug!

gitea-mirror commented

2026-05-05 05:54:35 -06:00

Author

Owner

@chiraag-nataraj commented on GitHub (Aug 19, 2018):

I ran into this issue recently as well, since I have both a distro-installed version of a program as well as a self-compiled (updated) version from Github (incidentally enough, it was because I patched the program to honor $TMPDIR so that I could use it with firejail!). I don't see how we can solve it though, at least not nicely. We could move the offending binary to /usr/bin, but that has issues in e.g. my case (where I have the same binary in two different places and want both versions). Or, we could emit a warning and skip it. How about we emit a warning and proceed without doing anything?

@chiraag-nataraj commented on GitHub (Aug 19, 2018): I ran into this issue recently as well, since I have both a distro-installed version of a program as well as a self-compiled (updated) version from Github (incidentally enough, it was because I patched the program to honor `$TMPDIR` so that I could use it with firejail!). I don't see how we can solve it though, at least not nicely. We could move the offending binary to `/usr/bin`, but that has issues in e.g. my case (where I have the same binary in two different places and _want_ both versions). Or, we could emit a warning and skip it. How about we emit a warning and proceed without doing anything?

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

No description provided.

Rows
Columns