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

Failed to map shared segment #1618

Closed
jander049 opened this issue Nov 11, 2019 · 8 comments
Closed

Failed to map shared segment #1618

jander049 opened this issue Nov 11, 2019 · 8 comments
Labels
bug broken functionality, usability problems, unexpected errors desktop Desktop client related issues

Comments

@jander049
Copy link

When I try to launch the appimage I get the following error:
/tmp/.org.chromium.Chromium.z5bAif: failed to map segment from shared object

To Reproduce
This started happening this morning and now I see the error every time I try to start from the command line. When I click on the AppImage itself to launch it just fails silently.

Desktop (please complete the following information):

  • OS: Debian Testing
  • Desktop Environment, if applicable (on Linux)
  • XFCE 4.14

Additional context
I'm not sure but this could be because my /tmp directory is mounted with nosuid,noexec,nosuid permissions but it hasn't been a problem until now.

User namespaces are also disable on my system.

@jander049 jander049 added bug broken functionality, usability problems, unexpected errors desktop Desktop client related issues labels Nov 11, 2019
@charlag
Copy link
Contributor

charlag commented Nov 11, 2019

Hi

User namespaces are also disable on my system.
Did you see #1565 ? Can it be it?
I'm also not sure how it should run with noexec

@jander049
Copy link
Author

I have to use the no-sandbox option to run it and have been without issue until nown

@charlag
Copy link
Contributor

charlag commented Nov 11, 2019

We have updated Electron few versions ago already and enabled sandbox there.
As far as I understand it worked for you and it's a duplicate of #1565.
You can apply any of the solutions (suid binary, user namespaces or no sandbox).

@charlag charlag closed this as completed Nov 11, 2019
@charlag charlag added the state:duplicate this issue has been opened before and new information should go in the original label Nov 11, 2019
@jander049
Copy link
Author

It doesn't start for me even with the no sandbox option now, it used to up until this morning though. This is the full error I see:

A JavaScript error occurred in the main process
Uncaught Exception:
Error: /tmp/user/1000/.org.chromium.Chromium.N6ybiE: failed to map segment from shared object
at process.func (electron/js2c/asar.js:138:31)
at process.func [as dlopen] (electron/js2c/asar.js:138:31)
at Object.Module._extensions..node (internal/modules/cjs/loader.js:828:18)
at Object.func (electron/js2c/asar.js:138:31)
at Object.func [as .node] (electron/js2c/asar.js:147:18)
at Module.load (internal/modules/cjs/loader.js:645:32)
at Function.Module._load (internal/modules/cjs/loader.js:560:12)
at Module.require (internal/modules/cjs/loader.js:685:19)
at require (internal/modules/cjs/helpers.js:16:16)
at Object. (/tmp/user/1000/.mount_tutanoCpaaxi/resources/app.asar/node_modules/keytar/lib/keytar.js:1:14)
at Module._compile (internal/modules/cjs/loader.js:786:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:798:10)
at Module.load (internal/modules/cjs/loader.js:645:32)
at Function.Module._load (internal/modules/cjs/loader.js:560:12)
at Module.require (internal/modules/cjs/loader.js:685:19)
at require (internal/modules/cjs/helpers.js:16:16)

@charlag
Copy link
Contributor

charlag commented Nov 12, 2019

Okay, it's a different problem. Can you try setting TMPDIR as described here balena-io/etcher#1699 or here balena-io-modules/drivelist#209
?

@charlag charlag reopened this Nov 12, 2019
@charlag charlag removed the state:duplicate this issue has been opened before and new information should go in the original label Nov 12, 2019
@jander049
Copy link
Author

Yes this worked for me

TMPDIR=$XDG_RUNTIME_DIR /path/to/appimage

@charlag
Copy link
Contributor

charlag commented Nov 13, 2019

I wonder if we could fix it on our side somewhere. Judging by the stacktrace it seems like it's inside keytar somewhere.

@charlag
Copy link
Contributor

charlag commented Feb 18, 2020

@jander049 AppImage devs at AppImage/AppImageKit#1021 (comment) asked for an image, maybe you could make one for them

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug broken functionality, usability problems, unexpected errors desktop Desktop client related issues
Projects
None yet
Development

No branches or pull requests

3 participants