-
Notifications
You must be signed in to change notification settings - Fork 567
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vscodium: missing profile redirect for codium #6461
Comments
Basic debugging information is missing; please follow the bug report template: |
I would happily do that, but it is not a BUG. It is a feature request to provide a profile for the latest version of a program. |
Moved |
Thanks, you can close this. |
Profiles are generally not separated by program versions (with limited Is there a new executable name for vscodium? If not, there already exists a profile for vscodium and it either works If it doesn't work, it's a bug.
Which directories and privileges? In what version of vscodium did they change? |
The executable is renamed to
Well then it is a BUG.
If I had a complete list for those, I would happily create and share the profile. You have to communicate with the developers for that.
Unfortunately I do not know this, I realized that firejail did not apply a profile recently while researching another issue. |
https://github.com/netblue30/firejail/blob/master/etc/profile-a-l/codium.profile added 3 years ago. Also in firejail/src/firecfg/firecfg.config Line 174 in 897f12d
So yes basic debugging information like your firejail version are missing. |
Here are my versions:
It seems that the package is old enough and includes outdated profiles. I will try to copy the upstream ones. The only profile installed is
This is probably something the Debian maintainer should do, so please close the report. |
@MiltiadisKoutsokeras on Sep 4:
Note that we do not maintain that version of firejail: Versions other than the latest usually have outdated profiles and may contain
I think it's unlikely to be upgraded on a stable Debian release. See also the recommended way to install firejail on Debian: |
Duplicate of #3871 |
Does not necessarily work, the profile may use commands unknown by your firejail version or include other profiles you don't have or with wrong content. |
Changes: * Sync bug_report.md with build_issue.md (reword items and add Linux kernel item) * Add a colon to the end of every item (to clarify where to add the information) * Add the Environment section to feature_request.md The last item is intended as a basic sanity check, as users using an outdated version of firejail may request something that was already implemented (for example, see netblue30#6461). Relates to netblue30#4515 netblue30#6423.
Changes: * Sync bug_report.md with build_issue.md (reword items and add Linux kernel item) * Add a colon to the end of every item (to clarify where to add the information) * Add the Environment section to feature_request.md The last item is intended as a basic sanity check, as users using an outdated version of firejail may request something that was already implemented (for example, see netblue30#6461). Relates to netblue30#4515 netblue30#6423.
Changes: * Sync bug_report.md with build_issue.md (reword items and add Linux kernel item) * Add a colon to the end of every item (to clarify where to add the information) * Add the Environment section to feature_request.md The last item is intended as a basic sanity check, as users using an outdated version of firejail may request something that was already implemented (for example, see #6461). Relates to #4515 #6423.
Is your feature request related to a problem? Please describe.
Firejail does not contain a profile to support the latest VSCodium in the apt package of Debian 11.
Describe the solution you'd like
I would like the Firejail installation to contain a profile that supports the latest VSCodium, as it does with past versions in files:
Describe alternatives you've considered
It would be possible to create a local custom file for latest VSCodium version but the program details have changed from the previous versions (whitelisted direcotries, privileges, etc.).
The text was updated successfully, but these errors were encountered: