Electron-packager: Cannot launch bundled Electron 4.0 app on Linux via file manager

[coreybruce]

Compiled executable files for Linux are not compiled properly, not clickable executable and show up as a shared file with other bugs from it not being properly compiled also noticed other stuff on the Windows compiled binary missing the icon I set for it ect.

[malept]

Thanks for filing an issue! Unfortunately, I cannot reproduce your problem with the information provided. My steps (on a Linux host, for a Linux target):

git clone https://github.com/electron/electron-quick-start && cd electron-quick-start
# edit package.json to use exactly electron-4.0.0-beta.5
npm install
npm install --save-dev electron-packager
$(npm bin)/electron-packager .
./electron-quick-start-linux-x64/electron-quick-start

My Electron Packager version:

$ $(npm bin)/electron-packager --version
Electron Packager 12.2.0
Node v10.2.1
Host Operating system: linux (x64)

In order to help you with your problem, we're going to need more information about it. In particular:

• Console output when you run electron-packager with the environment variable DEBUG=electron-packager _(instructions for Windows and non-Windows)_. Please include the stack trace if one exists.

• What command line arguments are you passing? Alternatively, if you are using the API, what
  parameters are you passing to the packager() function?

• Please provide either a failing minimal testcase (with code) or detailed steps to reproduce your
  problem. Using electron-quick-start is a good starting point.

[coreybruce]

@malept I am using Electron 4.0.0 beta on Xubuntu 18.04 LTS with Node v10.12.0

Here is what it looks like when compiled
http://i.imgur.com/ezYmJKe.png

Meanwhile using Electron 3.0.6 works just fine and compiles properly with electron-packager as you can see here
http://i.imgur.com/Iu93L78.png

[malept]

It's runnable from the command line (which is why I was unable to reproduce in the first place), but I can reproduce the behavior of trying to run it from Nautilus and getting the error message `There is no application installed for "shared library" files." Screenshot:

Unfortunately, this is a bug in Electron itself, not Electron Packager. Upstream changed their build process for 4.0 and this may have been one of the unintended side effects. Can you please file a bug in the Electron issue tracker so those developers are made aware?

For a workaround, you can try using electron-installer-debian to create an installable .deb file (with .desktop launcher shortcut) or electron-installer-snap to create a snap file.

[coreybruce]

@malept It is runable yes bug yes. but it isn't correctly compiling. I will make a bug report on Electron to get this fixed.

Thank you for the help.

[mbigger]

same problem，how to solve it?
CentOS 7.4 X64

use the command
···
./electron
···
no response

https://github.com/electron/electron-quick-start/issues/293

[coreybruce]

Best solution unless you don't package it like I did for my software for Arch/Manjaro is to just make a desktop shortcut to it

[mbigger]

but even if i make a desktop shortcut for it, i cannot start it, when i double click the icon, no response.
i read this page
https://stackoverflow.com/questions/55060402/electron-executable-not-recognized-by-nautilus
, but it does not work on me.

this is the content of my desktop file:

[Desktop Entry]
Name=My Application
Exec=/root/electron-quick-start/node_modules/electron/dist/electron
Terminal=false
Type=Application
StartupNotify=true
Encoding=UTF-8

[codebytere]

@mbigger did you mean to ping me? i'm not sure what help i can be here, unfortunately

[mbigger]

@codebytere sorry ，i want to @coreybruce

[coreybruce]

That's because on your example desktop shortcut your not even linking it to your application you made also you need to right click the application and go into properties than tick "allow this file to run" or something similar so it can run.

You can also do chmod +x exampleapplication

[mbigger]

@coreybruce Of course , I did this , chmod +x , and allow it to run. The icon has changed to the same as an
executable program.

[krastanov-veselin]

Is this thread even serious, last comment is Jul 16 2019 and this is like a dealbreaker bug and it is closed for what reason?

[malept]

it is closed for what reason?

From https://github.com/electron/electron-packager/issues/901#issuecomment-433101967:

Unfortunately, this is a bug in Electron itself, not Electron Packager. Upstream changed their build process for 4.0 and this may have been one of the unintended side effects.

The related Electron issue: https://github.com/electron/electron/issues/15406