A Javascript error occured in the main process

kauffj commented

2017-04-02 15:49:23 +02:00

(Migrated from github.com)

(I migrated, also known as copy/pasted, this issue from here.)

The Issue

Steps to reproduce

just start the App in KDE Manjaro rolling release 17
then close the app
the error apear after 2-3 seconds on screen

Expected behaviour

App should close normally, without any error apearint

Actual behaviour

After closing the App in Manjaro KDE 17.0 Stable Rolling release, this error apear:

A Javascript error occured in the main process

Uncaught Exception:
TypeError: Cannot read property 'loadURL' of null
at ChildProcess.subpy.on (/opt/LBRY/resources/app/main.js:58:10)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:191:7)
at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)

System Configuration

About

Your copy of LBRY is up to date.

daemon (lbrynet) 0.9.1
wallet (lbryum) 2.7.13
interface 0.9.1
Platform Linux (Linux-4.10.4-1-MANJARO-x86_64-with-ManjaroLinux-17.0-Gellivara)

Screenshots

(I migrated, also known as copy/pasted, this issue from [here](https://github.com/lbryio/lbry/issues/585).) ## The Issue ### Steps to reproduce 1. just start the App in KDE Manjaro rolling release 17 2. then close the app 3. the error apear after 2-3 seconds on screen ### Expected behaviour App should close normally, without any error apearint ### Actual behaviour After closing the App in Manjaro KDE 17.0 Stable Rolling release, this error apear: A Javascript error occured in the main process Uncaught Exception: TypeError: Cannot read property 'loadURL' of null at ChildProcess.subpy.on (/opt/LBRY/resources/app/main.js:58:10) at emitTwo (events.js:106:13) at ChildProcess.emit (events.js:191:7) at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12) ## System Configuration   About Your copy of LBRY is up to date. daemon (lbrynet) 0.9.1 wallet (lbryum) 2.7.13 interface 0.9.1 Platform Linux (Linux-4.10.4-1-MANJARO-x86_64-with-ManjaroLinux-17.0-Gellivara) ## Screenshots  ![auswahl_395](https://cloud.githubusercontent.com/assets/5913218/24585546/85e25500-178d-11e7-8e3c-47e070eec14b.png)

👍 1

Snarkly commented

2017-04-03 20:58:18 +02:00

(Migrated from github.com)

I'm having this same problem. I'm using Linux Mint 18.1 Serena Cinnamon 64-bit. This error message pops up a second or two right after I close LBRY. 😞

I'm having this same problem. I'm using Linux Mint 18.1 Serena Cinnamon 64-bit. This error message pops up a second or two right after I close LBRY. 😞 ![lbry](https://cloud.githubusercontent.com/assets/8492776/24625619/a6738aa0-187d-11e7-86a1-1cb0596e60e4.png)

PetSte commented

2017-04-22 03:53:45 +02:00

(Migrated from github.com)

I've got the same problem since updating to the latest LBRY version (0.9.1). I'm running LBRY on Windows 10.

👍 2

alexliebowitz commented

2017-05-04 11:04:07 +02:00

(Migrated from github.com)

@kauffj: I can no longer reproduce this on Linux, either on a dev build or RC8. Is it still happening for you?

PetSte commented

2017-05-05 05:26:39 +02:00

(Migrated from github.com)

Not sure if I can reply to this mail, but I'll try. I just reproduced the problem on my Windows 10. So for me, it's still there.

-------- Oorspronkelijk bericht --------
Van: alexliebowitz notifications@github.com
Datum: 04-05-17 11:04 (GMT+01:00)
Aan: lbryio/lbry-app lbry-app@noreply.github.com
Onderwerp: Re: [lbryio/lbry-app] A Javascript error occured in the main process (#30)

@kauffjhttps://github.com/kauffj: I can no longer reproduce this on Linux, either on a dev build or RC8. Is it still happening for you?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/lbryio/lbry-app/issues/30#issuecomment-299132121, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Aaf0JIHGtXULpqbQlwsBwV7WzS4S7M2Hks5r2ZSHgaJpZM4MwzqZ.

Not sure if I can reply to this mail, but I'll try. I just reproduced the problem on my Windows 10. So for me, it's still there. -------- Oorspronkelijk bericht -------- Van: alexliebowitz <notifications@github.com> Datum: 04-05-17 11:04 (GMT+01:00) Aan: lbryio/lbry-app <lbry-app@noreply.github.com> Onderwerp: Re: [lbryio/lbry-app] A Javascript error occured in the main process (#30) @kauffj<https://github.com/kauffj>: I can no longer reproduce this on Linux, either on a dev build or RC8. Is it still happening for you? — You are receiving this because you commented. Reply to this email directly, view it on GitHub<https://github.com/lbryio/lbry-app/issues/30#issuecomment-299132121>, or mute the thread<https://github.com/notifications/unsubscribe-auth/Aaf0JIHGtXULpqbQlwsBwV7WzS4S7M2Hks5r2ZSHgaJpZM4MwzqZ>.

alexliebowitz commented

2017-05-05 08:13:33 +02:00

(Migrated from github.com)

@PetSte: 0.10.0 just came out with many changes, including some in parts of the code related to this. Could you give it another shot with 0.10.0? Thanks.

@PetSte: 0.10.0 [just came out](https://github.com/lbryio/lbry-app/releases/tag/v0.10.0) with many changes, including some in parts of the code related to this. Could you give it another shot with 0.10.0? Thanks.

PetSte commented

2017-05-05 21:00:56 +02:00

(Migrated from github.com)

Alex,

After downloading v10 manually (from Github), like you asked, lbry doesn't seem to recognize me anymore. I'm asked to enter my email and early acces verification code, and I get the error 'could not authenticate user'. I'm positive the code is correct.

So now I can't ue LBRY or acces my wallet anymore. Any solutions?

-------- Oorspronkelijk bericht --------
Van: alexliebowitz notifications@github.com
Datum: 05-05-17 08:13 (GMT+01:00)
Aan: lbryio/lbry-app lbry-app@noreply.github.com
Onderwerp: Re: [lbryio/lbry-app] A Javascript error occured in the main process (#30)

@PetStehttps://github.com/PetSte: 0.10.0 just came outhttps://github.com/lbryio/lbry-app/releases/tag/v0.10.0 with many changes, including some in parts of the code related to this. Could you give it another shot with 0.10.0? Thanks.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/lbryio/lbry-app/issues/30#issuecomment-299390869, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Aaf0JIx6oqySctb9YmC0g3NptShl3UQ0ks5r2r4NgaJpZM4MwzqZ.

Alex, After downloading v10 manually (from Github), like you asked, lbry doesn't seem to recognize me anymore. I'm asked to enter my email and early acces verification code, and I get the error 'could not authenticate user'. I'm positive the code is correct. So now I can't ue LBRY or acces my wallet anymore. Any solutions? -------- Oorspronkelijk bericht -------- Van: alexliebowitz <notifications@github.com> Datum: 05-05-17 08:13 (GMT+01:00) Aan: lbryio/lbry-app <lbry-app@noreply.github.com> Onderwerp: Re: [lbryio/lbry-app] A Javascript error occured in the main process (#30) @PetSte<https://github.com/PetSte>: 0.10.0 just came out<https://github.com/lbryio/lbry-app/releases/tag/v0.10.0> with many changes, including some in parts of the code related to this. Could you give it another shot with 0.10.0? Thanks. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://github.com/lbryio/lbry-app/issues/30#issuecomment-299390869>, or mute the thread<https://github.com/notifications/unsubscribe-auth/Aaf0JIx6oqySctb9YmC0g3NptShl3UQ0ks5r2r4NgaJpZM4MwzqZ>.

Snarkly commented

2017-05-06 01:01:35 +02:00

(Migrated from github.com)

I just upgraded and I'm having the same problem PetSte is having.

kauffj commented

2017-05-06 15:34:04 +02:00

(Migrated from github.com)

@PetSte @Snarkly 😞

Can you send your email addresses to jeremy@lbry.io?

If you're comfortable using the command line interface you can still move your credits. Otherwise, you'll have to wait until we get a fix out.

If you are comfortable using the CLI, it'd be helpful if you could send me the output of the status command as well.

And sending a wallet address wouldn't hurt either 😉

@PetSte @Snarkly :disappointed: Can you send your email addresses to jeremy@lbry.io? If you're comfortable using the [command line interface](https://github.com/lbryio/lbry/releases) you can still move your credits. Otherwise, you'll have to wait until we get a fix out. If you are comfortable using the CLI, it'd be helpful if you could send me the output of the `status` command as well. And sending a wallet address wouldn't hurt either :wink:

👍 1

Snarkly commented

2017-05-06 22:48:23 +02:00

(Migrated from github.com)

I sent you my email using proton mail. I also open LBRY using the command terminal and I took this screenshot for you. There were a few errors I noticed in the command terminal.

I sent you my email using proton mail. I also open LBRY using the command terminal and I took this screenshot for you. There were a few errors I noticed in the command terminal. ![lbry](https://cloud.githubusercontent.com/assets/8492776/25775801/c1ba8e9a-327b-11e7-8272-5fe905dad211.png)

Snarkly commented

2017-05-09 03:31:45 +02:00

(Migrated from github.com)

Thanks for the verification code kauffj, it seemed to work fine. Also when I closed LBRY I noticed I didn't get the javascript error I was getting before.

PetSte commented

2017-05-09 20:08:42 +02:00

(Migrated from github.com)

Was this a special verification code or did you simply lose/mistake your own code? If it's the former, could you send me one as well, Jeremy? I've sent you my email address earlier.

kauffj commented

2017-05-09 20:26:25 +02:00

(Migrated from github.com)

@PetSte no new code, you should be able to get in fine. I take it you are still seeing this even on the latest version? If so, I'll try to dig deeper.

PetSte commented

2017-05-09 20:37:49 +02:00

(Migrated from github.com)

I don't get the Javascript error, but that's probably only because I can't seem to login. I'm still getting the 'could not authenticate user' error.

kauffj commented

2017-06-09 02:32:02 +02:00

(Migrated from github.com)

0.12 will drop the necessity of codes and fix existing verification issues.

Rows
Columns

A Javascript error occured in the main process #30

The Issue

Steps to reproduce

Expected behaviour

Actual behaviour

System Configuration

Screenshots