Urgent, show stopper: Blank Sign In window, impossible to use Eagle

Urgent, show stopper: Blank Sign In window, impossible to use Eagle

lsnc-e1
Enthusiast Enthusiast
724 Views
3 Replies
Message 1 of 4

Urgent, show stopper: Blank Sign In window, impossible to use Eagle

lsnc-e1
Enthusiast
Enthusiast

My offline period expired and eagle requires now a new sign in.

However, the sign in window is completely black.  Diagnostics to the terminal shows:

Sandboxing disabled by user.
[5620:5643:0312/094148.181803:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[5620:5643:0312/094148.181855:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[5620:5643:0312/094148.181892:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl4.digicert.com
[5620:5643:0312/094148.183827:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[5620:5643:0312/094148.183862:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[5620:5643:0312/094148.183899:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl4.digicert.com
[5620:5643:0312/094148.606429:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[5620:5643:0312/094148.606479:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[5620:5643:0312/094148.606522:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl4.digicert.com
[5620:5643:0312/094148.608187:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[5620:5643:0312/094148.608213:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[5620:5643:0312/094148.608244:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl4.digicert.com
[5620:5643:0312/094148.784804:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[5620:5643:0312/094148.784842:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[5620:5643:0312/094148.784873:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl4.digicert.com
[5620:5643:0312/094148.786199:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[5620:5643:0312/094148.786225:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[5620:5643:0312/094148.786260:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl4.digicert.com
js: Failed to set referrer policy: The value 'same-origin' is not one of 'always', 'default', 'never', 'origin-when-crossorigin', 'no-referrer', 'no-referrer-when-downgrade', 'origin', 'origin-when-cross-origin', or 'unsafe-url'. The referrer policy has been left unchanged.
[5620:5643:0312/094149.015576:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[5620:5643:0312/094149.015620:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[5620:5643:0312/094149.015664:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl4.digicert.com
[5620:5643:0312/094149.017379:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[5620:5643:0312/094149.017418:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[5620:5643:0312/094149.017457:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl4.digicert.com
js: Uncaught SyntaxError: Unexpected token {
[5620:5644:0312/094149.918654:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[5620:5644:0312/094149.918695:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[5620:5644:0312/094149.918724:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl4.digicert.com
[5620:5644:0312/094149.920080:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[5620:5644:0312/094149.920110:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[5620:5644:0312/094149.920138:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl4.digicert.com

 

% uname -a

Linux e595 5.3.0-40-generic #32~18.04.1-Ubuntu SMP Mon Feb 3 14:05:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

% lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic

This is quite urgent as this completely prevents me from working!!!

I suspect that the line "js: Uncaught SyntaxError: Unexpected token {" is the culprit.

Reply
Reply
0 Likes
725 Views
3 Replies
Replies (3)
Message 2 of 4

lsnc-e1
Enthusiast
Enthusiast

Found the real problem.  The old faithful Linux problem, which is solved with:

export LIBGL_ALWAYS_SOFTWARE=1 ./eagle

Well, you have my Linux version info.

Something should be done to make it a little bit easier to solve these.

Reply
Reply
0 Likes
Message 3 of 4

Anonymous
Not applicable

I had a similar problem in EAGLE 9.5.2 and 9.6.0. Schematic and Layout windows worked fine, but the Control Panel Window was black. When (blindly) switching from Home to the Preview tab, everything gets drawn again with a window resize, with the home tab, everything went black again. Also the license information and the about windows were black, but the settings windows were not.

Starting eagle with "LIBGL_ALWAYS_SOFTWARE=1 ./eagle" once seems to have fixed it permanently, now I don't have to use this prefix and it still works

Reply
Reply
0 Likes
Message 4 of 4

Anonymous
Not applicable

@Anonymous wrote:

Starting eagle with "LIBGL_ALWAYS_SOFTWARE=1 ./eagle" once seems to have fixed it permanently, now I don't have to use this prefix and it still works


It wasn't fixed permanently, only in the terminal were I used the prefix before. Still have to use the prefix in every new terminal.

Reply
Reply
0 Likes