Repository navigation
Open
Description
Pre-flight checklist
- I have read the contribution documentation for this project.
- I agree to follow the code of conduct that this project uses.
- I have searched the issue tracker for a bug that matches the one I want to file, without success.
Electron Forge version
6.0.0-beta.63
Electron version
v18.0.4
Operating system
Fedora 35
Last known working Electron Forge version
No response
Expected behavior
I use electron-forge to build the default template Hello world app flatpak. The build process goes fine, installation of the flatpak goes fine. Running the flatpak should too.
Actual behavior
I run this command
flatpak run io.atom.electron.test1 I get this error
[13 zypak-sandbox] Failed to send spawn request to supervisor: Bad file descriptor (errno 9)
/app/bin/electron-wrapper: line 3: 3 Trace/breakpoint trap (core dumped) zypak-wrapper "test1" "$@"Steps to reproduce
Place this into your packages.json file under makers
{
"name": "@electron-forge/maker-flatpak",
"config": {
"files": []
}}run
npm run makethen go to the out/make/flatpak... directory and install the flatpak using
flatpak install --user io.atom...Then run the installed flatpak
Additional information
I found a potential fix by setting the zypak module manually as shown here
{
"name": "@electron-forge/maker-flatpak",
"config": {
"options": {
"categories": [
"Utility"
],
"icon": {
"512x512": "icon.png"
}
},
"modules": [
{
"name": "zypak",
"sources": [
{
"type": "git",
"url": "https://github.com/refi64/zypak",
"tag": "v2022.03"
}
]
}
]
}
}
If this is a known issue it should be documented properly.
Reacted by Francis De Brabandere
Activity
sarahstreza commentedon Jun 14, 2022
I ran into this issue on Arch Linux, the fix noted solved the issue for me.
koseduhemak commentedon Jun 29, 2022
Same problem here on Pop OS. Mentioned fix works for me as well.
GabeDuarteM commentedon May 19, 2024
I had this as well, but the potential fix mentioned didn't work.
What worked for me was to remove the
productNamefield from the package.json, not sure whyfelipecrs commentedon Aug 16, 2025
This worked for me too!
felipecrs commentedon Aug 16, 2025
But I found a better workaround for it -- set
packagerConfig.executableNameto the same value asnameinpackage.json. In my case:This issue seems to have something to do with the Flatpak always trying to invoke the binary using
nameeven though the binary is actually named afterproductName.