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

Heroic launcher requires exec access to /tmp to launch #3822

Open
jmccon115 opened this issue Jun 14, 2024 · 0 comments
Open

Heroic launcher requires exec access to /tmp to launch #3822

jmccon115 opened this issue Jun 14, 2024 · 0 comments
Labels
bug:unconfirmed Someone works on identifying the issue

Comments

@jmccon115
Copy link

Describe the bug

After applying OS hardening measures to Ubuntu 22.04 desktop environment, attempting to install and launch the Heroic games launcher resulted in a "failed to map segment from shared object" error. During investigation, I observed that it was attempting to execute content from the /tmp filsystem, which is configured with the noexec option per CIS compliance recommendations. After temporarily setting the /tmp filesystem to allow execution, HGL was able to launch. Can this application be updated so that exec is no longer required for /tmp?

Add logs

A JavaScript error occurred in the main process
Uncaught Exception:
Error: /tmp/.org.chromium.Chromium.1YUL3D: failed to map segment from shared object
    at process.func [as dlopen] (node:electron/js2c/node_init:2:2214)
    at Module._extensions..node (node:internal/modules/cjs/loader:1343:18)
    at Object.func [as .node] (node:electron/js2c/node_init:2:2441)
    at Module.load (node:internal/modules/cjs/loader:1098:32)
    at Module._load (node:internal/modules/cjs/loader:945:12)
    at c._load (node:electron/js2c/node_init:2:13672)
    at Module.require (node:internal/modules/cjs/loader:1122:19)
    at require (node:internal/modules/helpers:130:18)
    at load (/opt/Heroic/resources/app.asar/node_modules/node-gyp-build/node-gyp-build.js:22:10)
    at /opt/Heroic/resources/app.asar/node_modules/lzma-native/index.js:9:39

Steps to reproduce

  1. Edit the /tmp mount point in the /etc/fstab file to include the noexec option.
  2. Install and attempt to launch heroic

Expected behavior

I expected HGL to launch with OS hardening measures applied. The /tmp noexec limitation appears to be the only conflicting setting, but would recommend this dependency get removed.

Screenshots

No response

Heroic Version

Latest Stable

System Information

Ubuntu 22.04
Gigabyte AX370-Gaming-CF
AMD Ryzen 7 1700X
16GiB CMK16GX4M2A2400C16 (Corsair VENGEANCE LPX 16GB (2 x 8GB) DDR4 DRAM 2400MHz C16 Memory Kit)
Sabrent Rocket 4.0 500GB NVMe SSD
AMD/ATI Radeon RX480

Additional information

No response

@jmccon115 jmccon115 added the bug:unconfirmed Someone works on identifying the issue label Jun 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug:unconfirmed Someone works on identifying the issue
Projects
None yet
Development

No branches or pull requests

1 participant