topic Re: Black window on start in EAGLE Forum

Black window on start

MESO-DI — Wed, 14 Feb 2018 23:45:21 GMT

I'm currently getting a black window instead of the login screeen. This started happening without changing my version of Eagle (8.6). Installing 8.6.1 did not resolve the issue. Only versions prior version 8 are still working. I'm using Ubuntu 17.10.

I'm assuming this has to do with the webview component. I had similar issues with Chrome on Windows.

Re: Black window on start

jorge_garcia — Thu, 15 Feb 2018 21:23:57 GMT

Hello @MESO-DI,

I hope you're doing well. Try starting EAGLE from the command line on Ubuntu, do you get any error messages? We released 8.6.2 recently and we will be releasing 8.6.3 soon so I encourage you to try those out to see if they behave differently. I currently run Linux Mint and it's working well, I know it's not the same as Ubuntu but it's close ;).

Please let me know if there's anything else I can do for you.

Best Regards,

Re: Black window on start

MESO-DI — Fri, 16 Feb 2018 13:59:35 GMT

Console output of Eagle 8.6.3 (same issue with the black window):

[4118:4138:0216/145726.081728:ERROR:nss_util.cc(808)] After loading Root Certs, loaded==false: NSS error code: -8018
[4118:4131:0216/145726.582842:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[4118:4131:0216/145726.582874:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[4118:4131:0216/145726.582912:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl.ws.symantec.com
[4118:4131:0216/145726.584118:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[4118:4131:0216/145726.584139:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[4118:4131:0216/145726.584164:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl.ws.symantec.com
[4118:4131:0216/145727.137435:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[4118:4131:0216/145727.137459:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[4118:4131:0216/145727.137479:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl.ws.symantec.com
[4118:4131:0216/145727.138289:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[4118:4131:0216/145727.138303:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[4118:4131:0216/145727.138321:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl.ws.symantec.com
[4118:4131:0216/145727.437126:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[4118:4131:0216/145727.437149:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[4118:4131:0216/145727.437180:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl.ws.symantec.com
[4118:4131:0216/145727.438000:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[4118:4131:0216/145727.438014:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[4118:4131:0216/145727.438034:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl.ws.symantec.com

I dont think it has anything to do with any particular version as 8.6 worked fine for many days and just started this behaviour recently.

Re: Black window on start

jorge_garcia — Fri, 16 Feb 2018 20:43:03 GMT

Hi @MESO-DI,

Is this all of it? I feel like there was more to it normally there would be some commands mentioning Qt and things like that. If possible post the entire result even if it's really long since one line could make all the difference.

Best Regards,

Re: Black window on start

MESO-DI — Sat, 17 Feb 2018 12:40:16 GMT

Yes this is all the output that I get when launching from cli.

Re: Black window on start

jorge_garcia — Tue, 20 Feb 2018 22:25:53 GMT

Hi @MESO-DI,

I'm going to ping a developer to jump on this thread, If you can post a picture of your CLI interface from when you type in ./eagle(or similar) forward. I encourage you to update to 8.6.3 since we had some bug fixes in that release. Let me know if there's anything else I can do for you.

Best Regards,

Re: Black window on start

Anonymous — Thu, 22 Feb 2018 17:50:20 GMT

Has this issue been resolved? I am having a similar promlem under Linux Mint 18.1 Cinnamon 64-bit running Eagle from the command line I get:

mam1@ShopMint ~/Applications/eagle-8.6.0 $ ./eagle
QApplication: invalid style override passed, ignoring it.
[24895:24907:0222/122559.593491:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[24895:24907:0222/122559.593505:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[24895:24907:0222/122559.593514:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl.ws.symantec.com
[24895:24907:0222/122559.594389:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[24895:24907:0222/122559.594397:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[24895:24907:0222/122559.594404:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl.ws.symantec.com
[24895:24907:0222/122559.962514:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[24895:24907:0222/122559.962562:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[24895:24907:0222/122559.962603:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl.ws.symantec.com
[24895:24907:0222/122559.966840:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[24895:24907:0222/122559.966872:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[24895:24907:0222/122559.966910:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl.ws.symantec.com
[24895:24907:0222/122600.548973:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[24895:24907:0222/122600.549019:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[24895:24907:0222/122600.549062:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl.ws.symantec.com
[24895:24907:0222/122600.553302:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[24895:24907:0222/122600.553335:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[24895:24907:0222/122600.553372:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl.ws.symantec.com
mam1@ShopMint ~/Applications/eagle-8.6.0 $

I know that this is being caused by something in the configuration of my system because if I create a new copy of Mint in VirtualBox and do an install of Eagle there is no problem. I would like to correct the problem in my system. If you could point me in the right direction it would be greatly appreciated.

Mark

Re: Black window on start

jorge_garcia — Thu, 22 Feb 2018 21:02:11 GMT

Hi @Anonymous and @MESO-DI,

Thanks for all of your posts. I'm going to get one of our devs to look at this. If I recall symnatec is a maker of anti-virus software and the like. By any chance to either or both of you interact with symnatec software at all (I don't think they make anything for linux, but maybe at the company level you guys have it?).

The other thing you guys should try is go into the EAGLE installation folder and check the readme file. There is an option to have EAGLE switch to CPU render, something like:

export LIBGL_ALWAYS_SOFTWARE=1

./eagle

Let me know if that works for you guys.

Either the developer or myself will be responding shortly.

Best Regards,

Re: Black window on start

MESO-DI — Thu, 22 Feb 2018 23:27:33 GMT

No Symantec products at our company. Also having this issue at home and at work (I work on a laptop) I will try out the CPU renderer but I'm fairly certain that this is a caching issue of some sorts as you are utilizing chromium for the login window and I experienced a pretty much exact same issue with chrome on all sorts of different devices and the only solution was to get rid of all chrome directories where users session stuff is saved.
Is there maybe a directory that Eagle saves temp data to? Given that all version of 8.x from the past few months suddenly started having this issue without changing my system I suspect there being some files left over that shouldn't be there.

Re: Black window on start

MESO-DI — Fri, 23 Feb 2018 13:47:19 GMT

As you asked here the full log when launching from cli:

~/eagle-8.6.3$ ./eagle 
[12446:12465:0223/144215.029294:ERROR:nss_util.cc(808)] After loading Root Certs, loaded==false: NSS error code: -8018
[12446:12458:0223/144215.556648:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[12446:12458:0223/144215.556706:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[12446:12458:0223/144215.556758:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl.ws.symantec.com
[12446:12458:0223/144215.559346:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[12446:12458:0223/144215.559385:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[12446:12458:0223/144215.559427:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl.ws.symantec.com
[12446:12458:0223/144215.903345:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[12446:12458:0223/144215.903458:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[12446:12458:0223/144215.903548:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl.ws.symantec.com
[12446:12458:0223/144215.906563:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[12446:12458:0223/144215.906610:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[12446:12458:0223/144215.906683:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl.ws.symantec.com
[12446:12458:0223/144216.244130:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[12446:12458:0223/144216.244154:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[12446:12458:0223/144216.244171:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl.ws.symantec.com
[12446:12458:0223/144216.245061:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[12446:12458:0223/144216.245074:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[12446:12458:0223/144216.245089:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl.ws.symantec.com
^C

and when no network is connected:

~/eagle-8.6.3$ ./eagle 
[12690:12709:0223/144356.536310:ERROR:nss_util.cc(808)] After loading Root Certs, loaded==false: NSS error code: -8018
^C

It would be nice if a dev could have a look at this soon. Atm I'm only able to work with Eagle 7 which is a workaround but quite a few important features are missing obviously.

Re: Black window on start

Anonymous — Fri, 23 Feb 2018 14:32:25 GMT

I agree that the problem is caused by there being some files left over that shouldn't be there. I believe that this is confirmed by seeing no problem on a fresh install of MInt. I have never installed any Symantec products on my machines.

Could the developers provide us with a list of ALL (include hidden) files that Eagle puts on a machine?

Thanks.

Mark

Re: Black window on start

hudriwudri — Fri, 23 Feb 2018 15:04:21 GMT

Symantec is also one of the main Certificate authorities, it also provides the web certificates for autodesk.com . nss_ocsp also points in that direction: nss stands for Network Security Services, ocsp is Online Certificate Status Protocol.

So it tries to validate a certificate and fails. The question is why it is failing, and why it behaves differently on different machines. Sorry I can't be of more help.

Re: Black window on start

MESO-DI — Fri, 23 Feb 2018 19:59:26 GMT

Yes thats what I also thought about today. There was also the news that Google want to distrust Symantec certificates in March. Maybe that is related in any way?

Re: Black window on start

MESO-DI — Fri, 23 Feb 2018 22:00:43 GMT

I got a little further. After finding this bug report:

https://bugs.chromium.org/p/chromium/issues/detail?id=486360

I deleted the nssdb folder in ~/.pki then when I launched eagle the old errors were gone but instead I got this. So this is definitely some sort of certificate issue. Now its the same issue as @Anonymous reported.

~/eagle-8.6.3$ ./eagle 
[8618:8631:0223/221823.685440:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[8618:8631:0223/221823.685480:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[8618:8631:0223/221823.685505:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl.ws.symantec.com
[8618:8631:0223/221823.686739:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[8618:8631:0223/221823.686761:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[8618:8631:0223/221823.686783:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl.ws.symantec.com
[8618:8631:0223/221824.053472:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[8618:8631:0223/221824.053504:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[8618:8631:0223/221824.053530:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl.ws.symantec.com
[8618:8631:0223/221824.054726:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[8618:8631:0223/221824.054747:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[8618:8631:0223/221824.054773:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl.ws.symantec.com
[8618:8631:0223/221824.729476:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[8618:8631:0223/221824.729500:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[8618:8631:0223/221824.729522:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl.ws.symantec.com
[8618:8631:0223/221824.730447:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[8618:8631:0223/221824.730463:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[8618:8631:0223/221824.730483:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl.ws.symantec.com
[8618:8630:0223/221824.742914:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[8618:8630:0223/221824.742942:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[8618:8630:0223/221824.742981:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl.ws.symantec.com
[8618:8630:0223/221824.744113:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[8618:8630:0223/221824.744139:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.ws.symantec.com
[8618:8630:0223/221824.744166:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl.ws.symantec.com

My version of libnss3 is 2:3.32-1ubuntu3. Maybe eagle is using the shared library and a system update broke it? That could explain why a fresh install would have fixed the issue for @Anonymous.

Re: Black window on start

jorge_garcia — Mon, 26 Feb 2018 22:50:29 GMT

Hi @MESO-DI,

I hope you're doing well. Try deleting the cached subscriptions on your machine and start EAGLE again.

Our developers are looking into this as we speak. I'll post as soon as I have more info.

Let me know if there's anything else I can do for you.

Best Regards,

Re: Black window on start

MESO-DI — Tue, 27 Feb 2018 00:11:28 GMT

Hi Jorge,

thanks for your response, what exactly do you mean by deleting the cached subscriptions? As in delete all folders that contain a version of Eagle?

Re: Black window on start

timonsku — Tue, 27 Feb 2018 15:48:09 GMT

Today I tried Eagle 8.5 and that was working fine. The main window was opening, then it asked me to login and that login window was working fine, no black weirdness. Maybe the certificates changed between 8.6 and 8.5?

E: MESO-DI here, I used my private account by accident.

Re: Black window on start

jorge_garcia — Tue, 27 Feb 2018 19:57:57 GMT

Hi @MESO-DI,

I hope you're doing well. I'm going to suggest reinstalling EAGLE, delete any folders that contain the EAGLE executable or it's files and install 8.6.3 again. I'll send you the path to where the subscriptions are cached privately. Delete everything in those folders, just to start with a clean slate.

Let me know if there's anything else I can do for you. If anyone else needs the path let me know.

Best Regards,

Re: Black window on start

Anonymous — Tue, 27 Feb 2018 21:21:40 GMT

Please share the path with me. Although Eagle is running fine in my VM I would like to get working on my native system.

Thanks.

Re: Black window on start

timonsku — Thu, 01 Mar 2018 13:29:17 GMT

Deleting the Eagle folder in ~/.local/share/ didn't make a difference unfortunately for Eagle 8.6+. 8.5 is still working fine I just had to login again.