Skip to content
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: cannot access Arduino code #5990

Closed
6 tasks done
marek22k opened this issue Sep 6, 2023 · 2 comments · Fixed by #5991
Closed
6 tasks done

vscodium: cannot access Arduino code #5990

marek22k opened this issue Sep 6, 2023 · 2 comments · Fixed by #5991

Comments

@marek22k
Copy link
Contributor

marek22k commented Sep 6, 2023

Description

Opening code is not possible in VSCodium

Steps to Reproduce

Steps to reproduce the behavior

  1. Run in bash LC_ALL=C firejail /usr/bin/codium (LC_ALL=C to get a consistent
    output in English that can be understood by everybody)
  2. Open a file, e. g. /home/marek/Arduino/xinetd/platformio.init
  3. Scroll down to The editor could not be opened due to an unexpteted error: Unable to read file '/home/marek/Arduino/xinetd/platformio.init (NoPermissions (FileSystemError): Error: EACCES: permission denied, stat '/home/marek/Arduino/xinetd/platformio.ini')`

Expected behavior

File can be opened.

Actual behavior

File cannot be opened.

Behavior without a profile

File can be opened.

Environment

  • Parrot OS (Debian-based)
firejail version 0.9.72

Compile time support:
	- always force nonewprivs support is disabled
	- AppArmor support is enabled
	- AppImage support is enabled
	- chroot support is enabled
	- D-BUS proxy support is enabled
	- file transfer support is enabled
	- firetunnel support is disabled
	- IDS support is enabled
	- networking support is enabled
	- output logging is enabled
	- overlayfs support is disabled
	- private-home support is enabled
	- private-cache and tmpfs as user enabled
	- SELinux support is enabled
	- user namespace support is enabled
	- X11 sandboxing support is enabled

Checklist

  • The issues is caused by firejail (i.e. running the program by path (e.g. /usr/bin/vlc) "fixes" it).
  • I can reproduce the issue without custom modifications (e.g. globals.local).
  • The program has a profile. (If not, request one in https://github.com/netblue30/firejail/issues/1139)
  • The profile (and redirect profile if exists) hasn't already been fixed upstream.
  • I have performed a short search for similar issues (to avoid opening a duplicate).
    • I'm aware of browser-allow-drm yes/browser-disable-u2f no in firejail.config to allow DRM/U2F in browsers.

Log

Output of LC_ALL=C firejail /usr/bin/codium

$LC_ALL=C firejail /usr/bin/codium
Reading profile /etc/firejail/codium.profile
Reading profile /etc/firejail/vscodium.profile
Reading profile /etc/firejail/code.profile
Reading profile /etc/firejail/allow-common-devel.inc
Reading profile /etc/firejail/electron.profile
Reading profile /etc/firejail/disable-common.inc
Reading profile /etc/firejail/disable-programs.inc
Warning: networking feature is disabled in Firejail configuration file
Parent pid 23597, child pid 23598
Child process initialized in 49.94 ms

Parent is shutting down, bye...

Output of LC_ALL=C firejail --debug /usr/bin/codium

https://gist.github.com/marek22k/27d165ce082954678745178dcb7e2bad

@glitsj16
Copy link
Collaborator

glitsj16 commented Sep 6, 2023

Thank you for reporting.

Easy fix:

$ cat ~/.config/firejail/allow-common-devel.local
noblacklist ${HOME}/.arduino15
noblacklist ${HOME}/Arduino

If that indeed fixes it, can you open a PR?

@marek22k
Copy link
Contributor Author

marek22k commented Sep 6, 2023

It works. I have created a PR.

marek22k added a commit to marek22k/firejail that referenced this issue Sep 6, 2023
glitsj16 pushed a commit that referenced this issue Sep 6, 2023
@kmk3 kmk3 changed the title VSCodium: Opening code is not possible vscodium: cannot access Arduino code Sep 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants