nuclear: does not work with --no-sandbox #4422
Comments
|
Did you set What do you get with |
|
No, I didn't. |
|
The "The SUID sandbox helper binary was found, but is not configured correctly." Issue should be gone since f4f6767. What does Does it work with
nuclear.profile has |
|
|
|
Why does it install a seccomp filter? It should not do this. It must not do this. |
|
There is no
From where does it come? |
|
The two profiles match those in the repo and there is no electron.local or nuclear.local (well I just created that file but it doesn't contain anything; I copy-pasted their contents to make sure they are the same). How to find out from where it comes? I edited the issue description to show the complete error which takes a while to load. The nuclear I installed via .deb file is v0.6.6 (sha256sum |
|
|
|
Because it talks about js files and npm you maybe need to allow this stuff ( |
|
Output of the above command: |
It must not do this. Can you post the first lines, e.g which files it reads. |
|
Sure, would have posted them already if there was something strange in there (electron.profile and nuclear.profile have their default content) |
This is empty as I got you
and this must only contain |
|
Yes, it's empty...I even moved out #commented out lines. |
Neither firejail nor your package manager write to $HOME/.config/firejail resp. $HOME. Anyway "It only includes whitelists of /var/ directories". |
|
I'm sure that I haven't created that file or only created it because it was part of some guide to get something to work with the file's contents to be pasted in or the file to be copied but forgot about it. This is the file's contents, I don't think it's why it doesn't run: /home/username/.config/firejail/whitelist-var-common.local doesn't exist. Any ideas how to get Nuclear to work? Also attaching /etc/firejail/whitelist-var-common.inc has the following contents: |
|
What does the disable-common.local contain? |
|
Only |
In disable-common.local? Since when? |
|
I think since before I recently tried to get Nuclear running again. It was just a note that's most likely irrelevant as these are commented out anyway but it's what I'd try to (re)include if everything works fine otherwise. |
|
So it was already commented when you got "Dropping all capabilities". Btw does it work without firejail or with --noprofile? |
|
I commented it out at this point. The output of Haven't tried running it without a firejail profile and it doesn't seem like there's an easy way to generate a VM of the current system. |
|
Now it does start but it still shows these errors (and takes a bit too long to launch). So I think this file was generated / overwritten somehow (however its metadata has modified & created in June 2020). Maybe it's working now because of the upgrade from Debian 10 to 11. Looks like the issue can be closed. The output of (After |
kmk3
changed the title
#3883 and #3806 could be related
When running
firejail --profile=/etc/firejail/nuclear.profile nuclearI getThe SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /opt/nuclear/chrome-sandbox is owned by root and has mode 4755.When appending
--no-sandboxto the command it shows these errors:Is there another way one is supposed to solve this electron problem or is the nuclear.profile broken?
Bug and expected behavior
It should run the Nuclear music player or display an error message that tells the user exactly what to do / run to make it work.
No profile and disabling firejail
Reproduce
Steps to reproduce the behavior:
Environment
Debian10 stable
Firejail version 0.9.64.4
Additional context
Checklist
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.The text was updated successfully, but these errors were encountered: