I have an incredibly simple packaged Electron app. All it does is open browser windows on the back of WebSocket events (serve a URL). When running the .exe from a network share location I notice the following:
the actual app is slower to launch browser windows to a usable state (this is after the app has "warmed up") - I haven't figured out what this is down to yet (can't launch DevTools)
can't launch DevTools
If I copy the same binaries to a local location - I don't see these issues. I had a search and couldn't find anything related to this - but is this an explainable issue? Is there anything built into electron that will copy the required bits over locally?
Related
Here's what happens:
Using a Macbook Pro, I use the Microsoft Remote Desktop Connection application to connect to my work computer, which is a Windows 10 machine
If I try to launch Spyder on my work computer, I get this error:
Load Library Error
However:
If I am at my work computer (i.e. physically at work instead of logging in remotely), I can launch Spyder successfully
If I leave Spyder open on my work computer, then go home and do a remote log-in to my work computer, I can use Spyder without issue. The problem/error described above arises only if I try to open Spyder through the remote connection.
This error only seems to affect Spyder and I can use all other programs without issue through a remote connection. As a workaround I've been using other IDEs and successfully running scripts, but I strongly prefer Spyder.
What I have tried so far (without success):
The 4 troubleshooting steps posted by Fazil M. to this Microsoft thread
Uninstalling/reinstalling Spyder using Conda
Restarting my work computer
System Information:
Work Computer OS: Windows 10, 64-bit
OS of computer through which I'm logging in to work computer: Mac OS X El Capitan 10.11.6
Spyder version: 4.1.1
Any thoughts as to what could be going on?
Update--More information and trials:
I checked out Issue #3736 on Spyder's GitHub. It says to download and add a file called opengl32sw.dll to the folder ~\Lib\site-packages\PyQt5\Qt\bin. But when I go to the PyQt5 folder, I do not see a subfolder for Qt. I tried placing it into the PyQt5 main folder, but that did not fix the problem.
I've heard this can be a graphics card issue too. On my machine I have two graphics cards: AMD RadeonT R5 430 and Intel(R) HD Graphics 630.
Darren's answer did not work for me. What did work was to:
First option: go into the device manager and disable the Intel HD Graphics card under "display adapters."
Second option:
run "Gpedit.msc"
navigate to Computer Configuration->Administrative
Templates->Windows Components->Remote Desktop Services->Remote
Desktop Session Host->Remote Session Environment
Disable "use WDDM graphics display driver for remote desktop
connections"
Restart the computer
See https://answers.microsoft.com/en-us/windows/forum/all/windows-10-1903-may-update-black-screen-with/23c8a740-0c79-4042-851e-9d98d0efb539
It took help from my organization's IT contractor, but I fixed the issue by doing the following:
Run a file called "gpedit.msc", which will open up a window for Local Group Policy Editor
In the tree menu on the left, navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment, and open the Remote Session Environment folder (not the subfolder within it)
Make sure the following are set to "Enabled":
"Use hardware graphics adapters for all Remote Desktop Services"
"Prioritize H.265/AVC444 graphics mode for Remote Desktop Connections"
"Configure H.264/AVC hardware encoding for Remote Desktop Connections"
Then restart the computer.
Since I was unable to get pass LoadLibrary 126 error using the solutions provided online and on here, I stepped back and realized the obvious workaround. The errors occurs when you open the program while you're using a remote session, right? The obvious solution is to launch the program while a remote session is not in progress. To do this while you're remoting, you should create a batch script to launch the program but make sure to include to a time delay before that (I used 'timeout 10 /nobreak' to do so). Run the batch script and, before your program launchs, disconnect from RDP. After enough time passes for the program to launch, you can reconnect to RDP and your program will be up and ready
What is The Correct(tm) way for an Electron application to run both as a desktop application and as a service?
I have looked high and low for this but to no avail. This is how I think it should work.
Create a launchd/systemd/windows service description that:
Sets ELECTRON_RUN_AS_NODE environment variable
Runs the packaged Electron application
Produces happiness?
Can the packaged Electron application run in this manner access the contents of the ASAR file? If it can, great.
Then just build and package two directories with the application. Both compiled for the ABI version Electron is on:
Directory electron_modules with binary modules compiled for an executable that reports being electron
Directory node_modules with binary modules compiled for an executable that reports being node
With the appropriate NODE_PATH also set in the service description, I should be all golden.
Right?
I am not 100% sure what the OP is asking but I found this question while looking for: how do I run an Electron application as a desktop application and also as a CLI service with no access to a display driver?
The answer from here is
Being based on Chromium, Electron requires a display driver to function. If Chromium can't find a display driver, Electron will fail to launch ... In essence, we need to use a virtual display driver.
The solution (on linux at least)
Install xvfb
Prefix your start command with xvfb-run e.g. xvfb-run node_modules/electron/dist/electron .
I'm a little newbie in the arch linux world, but i am a bit lost in this.
I have developped an electron app, simply one html page and one js page.
This application is a launcher for a machine the aim of this application is :
When i start the system, I must not see the wallpaper but directly the electron application.
The machine runs on Archlinux with LXDE environment.
I have been searching for a long time now, trying editing the /etc/xdg/LXDE/... lxsession/autostart
It is working, but the application takes 30 seconds to start....
I have been trying to change and run locally the application using chromium in command line in kiosk mode, but even chromium starts in 30 seconds.
I have been trying to use firefox instead, but it is the same situation.
The machine is composed of 4 cores intel, i don't think it is material beacause the system if very fast when i want to launch an application manually...
Sorry for my bad english,
I will appreciate, every information in order to know, how to privilege electron app boot within 1 second on arch linux / lxde
Thanks for advance,
Tom.
I have generated an app using electron-package. when running the exe generated in client's windows PC its not running. Is there any prerequisites to be installed in client PC? I haven't installed Node.
Try running your .exe from the command line. Maybe you'll be able to figure out what's causing your app to crash. I had the same problem, double-clicking the .exe would do nothing. When I ran the .exe from the command line (i.e. out\myApp-win32-x64\myApp.exe), I was able to see my app's console.log() and console.err(), and I realized what my problem was.
In my case, my app was using paths relative to process.cwd(), which were messed up when running the app directly from the .exe. That caused the app to crash even before showing the window, hence why nothing seemed to be running.
I can run Snap! by visiting the website http://snap.berkeley.edu/snapsource/snap.html, but is there a way for me to run it when I don't have an internet connection?
Snap! can be downloaded and run locally. When run locally, an internet connection is not necessary. This may be useful for students with a computer at home, but no reliable internet. Below are the instructions to download and run it.
Run Snap! from http://snap.berkeley.edu/snapsource/snap.html#
Click on the Snap! logo in the upper-left of the app.
Choose “Download source” from the menu
Save snap.zip locally on your computer.
Extract snap.zip.
Open snap.html in a web browser.
Every time you wish to run snap, you can do so by opening snap.html. No internet required.
Note that you cannot use cloud storage when running Snap! locally from snap.html. Also, the browser storage is not shared between running locally and running from the Berkeley website.
To transfer projects from a locally-run (offline) Snap! to the Berkeley-hosted (online) Snap!, you'll need to export the project from the locally-run Snap! window and import it in the Berkeley-hosted Snap! window.