-
Hi! I'm trying to run Standard Notes AppImage with Firejail, but getting errors with both
I have mentioned
You can see here some dbus errors in the bottom of output, and creating
However, JavaScript error persists, and app does not start (nothing happens).
Is there a way to fix it with |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 8 replies
-
You can not use To try to make it work:
|
Beta Was this translation helpful? Give feedback.
-
I've seen similar errors with (chrome-based) AppImage files before.
There is in fact a way to make --appimage work via the
One could create a ~/.config/firejail/standardnotes-desktop.local and place the needed firejail options there: $ cat ~/.config/firejail/standardnotes-desktop.local
# Firejail profile for standardnotes-desktop
# Persistent local customizations
?HAS_APPIMAGE: ignore noexec /tmp
private-opt standardnotes
Packaging seems to be a bit different depending on OS. But a simple additional redirect can handle this too: $ cat ~/.config/firejail/standard-notes.profile
# Firejail profile for standard-notes
# Redirect
include standardnotes-desktop.profile
With this redirect in place Firejail will pick up the correct profile. |
Beta Was this translation helpful? Give feedback.
-
(Offtopic)
Is ~/Software used by any program or did you create it? I would recommend placing AppImages in ~/Applications, as firejail makes it Related: |
Beta Was this translation helpful? Give feedback.
-
It looks correct, just one remark. The
You can indeed ignore these errors. They're 'to be expected' due to firejail's options and shouldn't affect performance/stability.
I don't have an answer to this one. But there are a few things you can try. The first one I would try is adding |
Beta Was this translation helpful? Give feedback.
-
LXQt as a DE seems to be relatively modular and self-contained, as it uses So it might use multiple config paths. Are there any other LXQt-related paths in your home directory? This might help finding them: cd
find . -maxdepth 5 -iname '*lxqt*' |
Beta Was this translation helpful? Give feedback.
I've seen similar errors with (chrome-based) AppImage files before.
There is in fact a way to make --appimage work via the
--no-sandbox
option. Note that this switch is not relating to the firejail sandbox but to the internal chrome-sandbox mechanism, and because of this it needs to be placed accordingly. For me the below does work: