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

Hangs on startup with ENOENT #916

Closed
sidmani opened this issue Apr 7, 2021 · 4 comments
Closed

Hangs on startup with ENOENT #916

sidmani opened this issue Apr 7, 2021 · 4 comments

Comments

@sidmani
Copy link

sidmani commented Apr 7, 2021

Problem
Athens hangs on startup and just displays a white screen.

Screenshots/Demo
If I launch from a shell, I get the following trace:

no "source-map-support" (run "npm install source-map-support --save-dev" to get it)
09:49:03.798 › Athens starting... version=1.0.0-beta.65
09:49:03.854 › Checking for update
09:49:03.855 › Checking for update...
09:49:03.954 › Error: Error: ENOENT, dev-app-update.yml not found in /usr/lib/athens.asar
    at createError (electron/js2c/asar_bundle.js:5:1289)
    at e.readFile (electron/js2c/asar_bundle.js:5:8076)
    at go$readFile (/usr/lib/athens.asar/node_modules/graceful-fs/graceful-fs.js:110:14)
    at readFile (/usr/lib/athens.asar/node_modules/graceful-fs/graceful-fs.js:107:12)
    at /usr/lib/athens.asar/node_modules/electron-updater/node_modules/universalify/index.js:8:12
    at new Promise (<anonymous>)
    at readFile (/usr/lib/athens.asar/node_modules/electron-updater/node_modules/universalify/index.js:7:14)
    at AppImageUpdater.loadUpdateConfig (/usr/lib/athens.asar/node_modules/electron-updater/out/AppUpdater.js:602:67)
    at Lazy.<anonymous> (/usr/lib/athens.asar/node_modules/electron-updater/out/AppUpdater.js:211:58)
    at Lazy.get value [as value] (/usr/lib/athens.asar/node_modules/lazy-val/out/main.js:23:25)
09:49:03.955 › Error in auto-updater. Error: ENOENT, dev-app-update.yml not found in /usr/lib/athens.asar
(node:180702) UnhandledPromiseRejectionWarning: Error: ENOENT, dev-app-update.yml not found in /usr/lib/athens.asar
    at createError (electron/js2c/asar_bundle.js:5:1289)
    at e.readFile (electron/js2c/asar_bundle.js:5:8076)
    at go$readFile (/usr/lib/athens.asar/node_modules/graceful-fs/graceful-fs.js:110:14)
    at readFile (/usr/lib/athens.asar/node_modules/graceful-fs/graceful-fs.js:107:12)
    at /usr/lib/athens.asar/node_modules/electron-updater/node_modules/universalify/index.js:8:12
    at new Promise (<anonymous>)
    at readFile (/usr/lib/athens.asar/node_modules/electron-updater/node_modules/universalify/index.js:7:14)
    at AppImageUpdater.loadUpdateConfig (/usr/lib/athens.asar/node_modules/electron-updater/out/AppUpdater.js:602:67)
    at Lazy.<anonymous> (/usr/lib/athens.asar/node_modules/electron-updater/out/AppUpdater.js:211:58)
    at Lazy.get value [as value] (/usr/lib/athens.asar/node_modules/lazy-val/out/main.js:23:25)
(Use `electron --trace-warnings ...` to show where the warning was created)
(node:180702) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:180702) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Athens Version
1.0.0-beta65, although this happened before I updated from beta 61 as well. I'm on arch linux, kernel version 5.11.10-arch1-1.

@sid597
Copy link
Collaborator

sid597 commented Jun 10, 2021

@sidmani This does not happen in ~latest versions, if it does for you please reopen this issue.

@sid597 sid597 closed this as completed Jun 10, 2021
@homunkoloss
Copy link

homunkoloss commented Sep 12, 2021

@sid597 I am having this problem after my last system update on the newest release

~ athens
no "source-map-support" (run "npm install source-map-support --save-dev" to get it)
08:38:29.834 › Athens starting... version=1.0.0-beta.96
08:38:29.942 › Checking for update
08:38:29.944 › Checking for update...
(node:1607580) electron: The default of nativeWindowOpen is deprecated and will be changing from false to true in Electron 15.  See https://github.com/electron/electron/issues/28511 for more information.
(Use `electron --trace-warnings ...` to show where the warning was created)
libva error: /usr/lib/dri/iHD_drv_video.so init failed
08:38:29.947 › Error: Error: ENOENT, dev-app-update.yml not found in /usr/lib/athens.asar
    at createError (electron/js2c/asar_bundle.js:5:1289)
    at fsReadFileAsar (electron/js2c/asar_bundle.js:5:7482)
    at e.readFile (electron/js2c/asar_bundle.js:5:8550)
    at go$readFile (/usr/lib/athens.asar/node_modules/graceful-fs/graceful-fs.js:118:14)
    at Object.readFile (/usr/lib/athens.asar/node_modules/graceful-fs/graceful-fs.js:115:12)
    at /usr/lib/athens.asar/node_modules/universalify/index.js:8:12
    at new Promise (<anonymous>)
    at Object.readFile (/usr/lib/athens.asar/node_modules/universalify/index.js:7:14)
    at AppImageUpdater.loadUpdateConfig (/usr/lib/athens.asar/node_modules/electron-updater/out/AppUpdater.js:379:48)
    at Lazy.<anonymous> (/usr/lib/athens.asar/node_modules/electron-updater/out/AppUpdater.js:65:60)
08:38:29.948 › Error in auto-updater. Error: ENOENT, dev-app-update.yml not found in /usr/lib/athens.asar
(node:1607580) UnhandledPromiseRejectionWarning: Error: ENOENT, dev-app-update.yml not found in /usr/lib/athens.asar
    at createError (electron/js2c/asar_bundle.js:5:1289)
    at fsReadFileAsar (electron/js2c/asar_bundle.js:5:7482)
    at e.readFile (electron/js2c/asar_bundle.js:5:8550)
    at go$readFile (/usr/lib/athens.asar/node_modules/graceful-fs/graceful-fs.js:118:14)
    at Object.readFile (/usr/lib/athens.asar/node_modules/graceful-fs/graceful-fs.js:115:12)
    at /usr/lib/athens.asar/node_modules/universalify/index.js:8:12
    at new Promise (<anonymous>)
    at Object.readFile (/usr/lib/athens.asar/node_modules/universalify/index.js:7:14)
    at AppImageUpdater.loadUpdateConfig (/usr/lib/athens.asar/node_modules/electron-updater/out/AppUpdater.js:379:48)
    at Lazy.<anonymous> (/usr/lib/athens.asar/node_modules/electron-updater/out/AppUpdater.js:65:60)
(node:1607580) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:1607580) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
[1607613:0912/083829.953206:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.

Using Arch Linux, Electron Version is 14.0.0-1

@homunkoloss
Copy link

Downgrading to electron 13.2.3-1 fixes the issue for me.

@martin-braun
Copy link

martin-braun commented Mar 27, 2022

I have the same problem on MacOS:

00:10:52.597 › Athens starting... version=2.0.0-beta.24
00:10:52.824 › Checking for update
00:10:52.825 › Checking for update...
00:10:53.232 › Error: Error: ENOENT: no such file or directory, open '/Users/marty/Projects/martin-braun/athens/dev-app-update.yml'
00:10:53.233 › Error in auto-updater. Error: ENOENT: no such file or directory, open '/Users/marty/Projects/martin-braun/athens/dev-app-update.yml'
(node:86837) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open '/Users/marty/Projects/martin-braun/athens/dev-app-update.yml'
(Use `Electron --trace-warnings ...` to show where the warning was created)
(node:86837) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:86837) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
shadow-cljs - #5 ready!

This electron-builder is a mess in dev mode and it should be documented @sid597.

I found a "solution" in an issue of electron-builder that involves creating that dev-app-update.yml:

Maybe this will help someone for solving this issue. For me it worked creating the dev-app-update.yml manually in the top level of my electron app. I am using the two package.json way.

My directory structure then looks like this

.
├── app
│   ├── main
│   │   ├── main.js
│   │   └── update.js
│   ├── package.json
│   ├── renderer
│   │   ├── ...
│   │       └── main.jsx
│   └── yarn.lock
├── dev-app-update.yml
├── package.json
├── publish.sh
└── yarn.lock

And in dev-app-update.yml I inserted the following for using GitHub:

owner: yourGHName
repo: yourGHRepoName
provider: github

And then normally start your main entry file with electron main.js.

Originally posted by @alexanderwe in electron-userland/electron-builder#1505 (comment)

So for my fork I created the dev-app-update.yml like this:

owner: martin-braun
repo: athens
provider: github

Then the build runs, but it want's to download an update:

Error in auto-updater. HttpError: 404 
"method: GET url: https://github.com/martin-braun/athens/releases/download/v2.0.0-beta.24/latest-mac.yml\n\nPlease double check that your authentication token is correct. Due to security reasons, actual status maybe not reported, but 404.\n"

@sid597 @tangjeff0 This feels weird to me and I cannot see that it's documented at all. Why is the auto-updater even attempting to update on a dev build, please? Can this issue be re-opened and addressed, please?

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

No branches or pull requests

4 participants