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

@electron-forge/maker-flatpak error after project setup #1702

Closed
3 tasks done
denn-s opened this issue May 23, 2020 · 4 comments · Fixed by #1703
Closed
3 tasks done

@electron-forge/maker-flatpak error after project setup #1702

denn-s opened this issue May 23, 2020 · 4 comments · Fixed by #1703
Labels

Comments

@denn-s
Copy link

denn-s commented May 23, 2020

Preflight Checklist

  • I have read the contribution documentation for this project.
  • I agree to follow the code of conduct that this project follows, as appropriate.
  • I have searched the issue tracker for a bug that matches the one I want to file, without success.

Issue Details

  • Electron Forge Version:
    • 6.0.0-beta.51
  • Electron Version:
    • 9.0.0
  • Operating System:
    • Ubuntu 20.04 x64
  • Last Known Working Electron Forge version:

Expected Behavior

maker-flatpak should successfully build the flatpak

Actual Behavior

maker-flatpak process fails with the following error:
An unhandled error has occurred inside Forge: An error occured while making for target: flatpak flatpak-builder failed with status code 1 Error: flatpak-builder failed with status code 1 at ChildProcess.<anonymous> (/home/denn-s/VSCodeProjects/my-app/node_modules/@malept/flatpak-bundler/index.js:68:16) at ChildProcess.emit (events.js:315:20) at ChildProcess.EventEmitter.emit (domain.js:485:12) at maybeClose (internal/child_process.js:1051:16) at Socket.<anonymous> (internal/child_process.js:442:11) at Socket.emit (events.js:315:20) at Socket.EventEmitter.emit (domain.js:485:12) at Pipe.<anonymous> (net.js:670:12) error Command failed with exit code 1.

To Reproduce

  • yarn create electron-app my-app
  • yarn add --dev @electron-forge/maker-flatpak
  • add maker-flatpak to package.json as described in the forge config section of the docs:
    { "name": "@electron-forge/maker-flatpak", "config": { "options": { "categories": ["Video"], "mimeType": ["video/h264"] } } }
  • yarn make

Additional Information

I figured out a way to make @electron-forge/maker-flatpak work again. My research for a solution guided me towards the following result:

  • set up flatpak as described in the official flatpak electron example
  • change the maker config options:
    { "name": "@electron-forge/maker-flatpak", "config": { "options": { "base": "io.atom.electron.BaseApp", "base-version": "stable" } } }

If this is desired I could create a pull request in order to extend the documentation for maker-flatpak so that new users could set up a working flatpak configuration.

@denn-s denn-s added the bug label May 23, 2020
@malept
Copy link
Member

malept commented May 23, 2020

I've updated the documentation to reflect the relatively new external dependency: electron-forge/electron-forge-docs@2aa0f59

malept added a commit that referenced this issue May 23, 2020
Needed due to zypak sandboxing for Electron >= 5.

Fixes #1702.
@MangoChris
Copy link

Adding eu-string via elfutils doesn't fix this problem. Tested on Arch and Ubuntu 18.04.

@nbsp
Copy link

nbsp commented Jan 3, 2021

Also having this issue, although the error shows slightly different lines:

Error: flatpak failed with status code 1
    at ChildProcess.<anonymous> (/home/sfr/Documents/repositories/test/node_modules/@malept/flatpak-bundler/index.js:71:16)
    at ChildProcess.emit (node:events:376:20)
    at ChildProcess.EventEmitter.emit (node:domain:470:12)
    at maybeClose (node:internal/child_process:1063:16)
    at Socket.<anonymous> (node:internal/child_process:449:11)
    at Socket.emit (node:events:376:20)
    at Socket.EventEmitter.emit (node:domain:470:12)
    at Pipe.<anonymous> (node:net:666:12)

Tested on Arch, everything seems up-to-date.

@Progdrasil
Copy link

Still having this issue on Arch, eu-strip is in my path.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants