joplin-desktop not running with /tmp mounted as noexec

[RomainMorlevat]

When trying to run joplin-desktop from my computer, "nothing happens". My /tmp is a mounted like that:
none /tmp tmpfs defaults,nosuid,nodev,noexec 0 0
I've identified the noexec to be responsible. If I run TMPDIR="/home/tmp" joplin-desktop it works.
I found that it comes from Electron but it may be an app config issue: see this comment of @MarshallOfSound
I also found that @roman-r-m referred to noexec here but without a solution.

Environment

Joplin version: 2.8.8
Platform: x64
OS specifics: ArchLinux

Steps to reproduce

1. mount /tmp with noexec option (you can do it with sudo mount -o remount,noexec /tmp)
2. run joplin-desktop

Describe what you expected to happen

I expect Joplin to run properly.

Logfile

This is the output of joplin-desktop --open-dev-tools --debug --log-level debug:
From terminal:

[13298:1116/080415.630860:ERROR:node_bindings.cc(245)] Error parsing Node.js cli flags 
xdg-settings: invalid application name
Try 'xdg-settings --help' for more information.
(node:13298) electron: The default of nativeWindowOpen is deprecated and will be changing from false to true in Electron 15.  See https://github.com/electron/electron/issues/28511 for more information.
(Use `@joplinapp-desktop --trace-warnings ...` to show where the warning was created)
[13332:1116/080416.114437:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.

From app/browser's console:

Uncaught Error: /tmp/.org.chromium.Chromium.jJsEsr: failed to map segment from shared object
    at process.func [as dlopen] (electron/js2c/asar_bundle.js:5)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:1143)
    at Object.func [as .node] (electron/js2c/asar_bundle.js:5)
    at Module.load (internal/modules/cjs/loader.js:940)
    at Module._load (internal/modules/cjs/loader.js:781)
    at Function.f._load (electron/js2c/asar_bundle.js:5)
    at Function.o._load (electron/js2c/renderer_init.js:29)
    at Module.require (internal/modules/cjs/loader.js:964)
    at require (internal/modules/cjs/helpers.js:88)
    at Object.<anonymous> (/usr/share/joplin-desktop/resources/app.asar/node_modules/sqlite3/lib/sqlite3-binding.js:4)

[FMRed]

Same here.
Tried 2.8.8 and 2.9.3 appimage versions.
OS: Arch

[github-actions]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[RomainMorlevat]

I still have the issue.

[github-actions]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[RomainMorlevat]

I still have the issue.

[RomainMorlevat]

Still go the issue with:

Joplin 2.9.17 (prod, linux)
Révision : 0266536 (master)

App is build from AUR (not AppImage version).

Electron v22.0.3

[github-actions]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[RomainMorlevat]

Still got the issue.

[github-actions]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[RomainMorlevat]

Still got the issue.

[github-actions]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[RomainMorlevat]

Still got the issue with Joplin version 2.10.18

[github-actions]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[RomainMorlevat]

Still got the issue.

joplin v2.10.19
electron v22.3.13

[RomainMorlevat]

Just a work around for those who need it:
In /usr/bin/joplin-desktop, add a TMPDIR on the last line with a path that can be exec:

...
TMPDIR="/home/USERNAME/TMPDIR" ./@joplinapp-desktop "$@"

That way joplin-desktop run into that TMPDIR and no in /tmp/.

[github-actions]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[github-actions]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, feel free to create a new issue with up-to-date information.