Closed ThomasTJdev closed 5 years ago
Yes. I know it happens (when defined firejail).
Most users dont seem too annoyed by this, but yeah can be improved. Firejail sees you downloaded files from internet and try to execute them server side and kinda dont like it probably because it looks potentially insecure, then intentionally blocks it. Maybe just document that it needs a restart when adding new plugins and firejail is active :grey_question:
BTW I am participating on https://eventol.flisol.org.ar/events/flisol-caba-2019/ this month, Sat 27, Maybe 2 talks, if approved, and 1 is about NimWC.
- it can be solved by a restart, then recompile.
This is a full restart. The force restart from the browser is not enough.
- it can also be solved by changing the default firejail config.
How? What config should be changed?
Most users dont seem too annoyed by this, but yeah can be improved.
When we ship NimWC with firejail as default in nimwc.nim.cfg
, I think main features such as plugins should work out of the box. We can change the firejail config to allow it as standard, otherwise we should clearly state it in the documentation.
BTW I am participating on https://eventol.flisol.org.ar/events/flisol-caba-2019/ this month, Sat 27, Maybe 2 talks, if approved, and 1 is about NimWC.
Nice 😃 Best of luck! It's a little to far away for me to come and see 😉
I'm having some difficulties starting plugins, when I have compiled with
-d:firejail
. When I start a plugin from the browser, it breaks during recompile with:Debugging shows the breakpoint to be:
But if I just run the command manually from
proc recompile*()
everything works as expected. (I have echo'ed the command to replicate it)I have tried working with the various config options, but I have had no luck. This happens on my local Arch and on a headless Ubuntu. Could you have a try @juancarlospaco ?