No UI displayed on some Ubuntu 20.04 systems with 0.65.0 #7902

dpage · 2022-06-09T10:22:49Z

NWJS Version : 0.65.0
Operating System : Ubuntu 20.04

Expected behavior

Windows should be displayed.

Actual behavior

No windows are displayed.

How to reproduce

I work on the pgAdmin project (https://www.pgadmin.org), which uses NWJS as its runtime environment. With our latest release we've had a number of users of Ubuntu 20.04 complain that the application won't start (https://redmine.postgresql.org/issues/7442). Other users and our own testing have seen everything working as expected. Our previous release used NWJS 0.61.0 which the same users report works fine.

I've asked them to download NWJS directly and try running it with no changes whatsoever (e.g. just download, unpack, and run the nw binary) and they see the same problem. This is the console output from a user reporting the problem:

[0609/000740.366695:ERROR:zip_reader.cc(153)] Cannot open ZIP from file handle 3
[0609/000740.366852:ERROR:zip.cc(202)] Cannot open ZIP from file handle 3
[0609/000740.367044:ERROR:zip.cc(179)] Cannot open '/home/cesar/Téléchargements/nwjs-v0.65.0-linux-x64/package.nw': FILE_ERROR_NOT_FOUND: Aucun fichier ou dossier de ce type (2)
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[17224:17224:0609/000742.729131:ERROR:CONSOLE(0)] "Unchecked runtime.lastError: Invalid value for bounds. Bounds must be at least 50% within visible screen space.", source: chrome-extension://aafddpmiffkameplnjkglahmbnbgidce/_generated_background_page.html (0)
[17259:17266:0609/000757.499111:ERROR:cert_verify_proc_builtin.cc(603)] No net_fetcher for performing AIA chasing.

This is the console output from my own Ubuntu 20.04 installation, on which everything seems fine:

dpage@ubuntu:~/Downloads$ ./nwjs-v0.65.0-linux-x64/nw 
[0609/104107.124432:ERROR:zip_reader.cc(153)] Cannot open ZIP from file handle 3
[0609/104107.124531:ERROR:zip.cc(202)] Cannot open ZIP from file handle 3
[0609/104107.124587:ERROR:zip.cc(179)] Cannot open '/home/dpage/Downloads/nwjs-v0.65.0-linux-x64/package.nw': FILE_ERROR_NOT_FOUND: No such file or directory (2)
[158130:158130:0609/104107.566783:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[158130:158130:0609/104107.566865:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[158130:158130:0609/104107.566886:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[158130:158130:0609/104107.566913:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[158130:158130:0609/104107.566930:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[158130:158130:0609/104107.566954:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[158130:158130:0609/104107.567000:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[158130:158130:0609/104107.567035:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[158130:158130:0609/104107.567059:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[158130:158130:0609/104107.567084:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[158130:158130:0609/104107.567117:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[158130:158130:0609/104107.567142:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[158130:158130:0609/104107.567165:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[158130:158130:0609/104107.567195:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[158130:158130:0609/104107.567222:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[158130:158130:0609/104107.567244:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[158130:158130:0609/104107.567269:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[158130:158130:0609/104107.567296:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[158130:158130:0609/104107.567320:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[158130:158130:0609/104107.567344:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[158130:158130:0609/104107.567367:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[158131:158136:0609/104112.428945:ERROR:cert_verify_proc_builtin.cc(603)] No net_fetcher for performing AIA chasing.
[158131:158136:0609/104112.770983:ERROR:cert_verify_proc_builtin.cc(603)] No net_fetcher for performing AIA chasing.

There is speculation in pgAdmin ticket that this is being caused by the kernel version in use (HWE vs. stable), but so far I've only been able to reproduce a different issue (with Linux ubuntu 5.4.0-117-generic #132-Ubuntu SMP Thu Jun 2 00:39:06 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux) which displayed a plain white NWJS window (Linux ubuntu 5.13.0-48-generic #54~20.04.1-Ubuntu SMP Thu Jun 2 23:37:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux works fine), and dumped errors like the following repeatedly to the console:

[0609/110635.588000:ERROR:zip_reader.cc(153)] Cannot open ZIP from file handle 3
[0609/110635.588087:ERROR:zip.cc(202)] Cannot open ZIP from file handle 3
[0609/110635.588133:ERROR:zip.cc(179)] Cannot open '/home/dpage/Downloads/nwjs-v0.65.0-linux-x64/package.nw': FILE_ERROR_NOT_FOUND: No such file or directory (2)
[3168:3168:0609/110636.001964:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[3168:3168:0609/110636.002043:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[3168:3168:0609/110636.002062:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[3168:3168:0609/110636.002079:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[3168:3168:0609/110636.002095:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[3168:3168:0609/110636.002110:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[3168:3168:0609/110636.002126:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[3168:3168:0609/110636.002148:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[3168:3168:0609/110636.002173:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[3168:3168:0609/110636.002189:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[3168:3168:0609/110636.002201:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[3168:3168:0609/110636.002215:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[3168:3168:0609/110636.002228:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[3168:3168:0609/110636.002241:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[3168:3168:0609/110636.002254:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[3168:3168:0609/110636.002268:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[3168:3168:0609/110636.002352:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[3168:3168:0609/110636.002396:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[3168:3168:0609/110636.002413:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[3168:3168:0609/110636.002468:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[3168:3168:0609/110636.002505:ERROR:gbm_wrapper.cc(292)] Failed to export buffer to dma_buf: No such file or directory (2)
[3168:3168:0609/110636.196280:ERROR:shared_context_state.cc(76)] Skia shader compilation error
------------------------
#version 400

out vec4 sk_FragColor;
uniform sampler2D uTextureSampler_0_S0;
noperspective in vec2 vTextureCoords_S0;
flat in float vTexIndex_S0;
noperspective in vec4 vinColor_S0;
void main() {
    vec4 outputColor_S0;
    outputColor_S0 = vinColor_S0;
    vec4 texColor;
    {
        texColor = texture(uTextureSampler_0_S0, vTextureCoords_S0, -0.5).xxxx;
    }
    vec4 outputCoverage_S0 = texColor;
    {
        sk_FragColor = outputColor_S0 * outputCoverage_S0;
    }
}

Errors:
0:1(10): error: GLSL 4.00 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.40, 1.50, 3.30, 1.00 ES, and 3.00 ES

[3168:3168:0609/110636.196716:ERROR:shared_context_state.cc(76)] Skia shader compilation error
------------------------
#version 400

uniform vec2 u_skRTFlip;
out vec4 sk_FragColor;
uniform mat3 umatrix_S1_c0;
uniform vec4 uscale_S1_c1_c0_c0[2];
uniform vec4 ubias_S1_c1_c0_c0[2];
uniform float uthreshold_S1_c1_c0_c0;
uniform mat3 umatrix_S1_c1_c0_c1;
uniform vec4 uleftBorderColor_S1_c1_c0;
uniform vec4 urightBorderColor_S1_c1_c0;
uniform float urange_S1;
uniform sampler2D uTextureSampler_0_S1;
flat in vec4 vcolor_S0;
noperspective in vec2 vTransformedCoords_8_S0;
void main() {
    vec4 sk_FragCoord = vec4(gl_FragCoord.x, u_skRTFlip.x + u_skRTFlip.y * gl_FragCoord.y, gl_FragCoord.z, gl_FragCoord.w);
    vec4 outputColor_S0;
    outputColor_S0 = vcolor_S0;
    vec4 output_S1;
    vec4 _31_input = outputColor_S0;
    vec4 _32_input = _31_input;
    vec2 _35_tmp_3_coords = vTransformedCoords_8_S0;
    vec4 _36_t = vec4(_35_tmp_3_coords.x + 9.9999997473787516e-06, 1.0, 0.0, 0.0);
    vec4 _37_outColor;
    if (_36_t.x < 0.0) {
        _37_outColor = uleftBorderColor_S1_c1_c0;
    } else if (_36_t.x > 1.0) {
        _37_outColor = urightBorderColor_S1_c1_c0;
    } else {
        vec2 _39_tmp_1_coords = vec2(_36_t.x, 0.0);
        float _40_t = _39_tmp_1_coords.x;
        vec4 _41_s;
        vec4 _42_b;
        if (_40_t < uthreshold_S1_c1_c0_c0) {
            _41_s = uscale_S1_c1_c0_c0[0];
            _42_b = ubias_S1_c1_c0_c0[0];
        } else {

...
[plus 8MB more similar output, before I could hit Ctrl+C]

Any assistance would be appreciated.

The text was updated successfully, but these errors were encountered:

rogerwang · 2022-06-09T15:59:56Z

Thanks for reporting. The graphics information for that system would be helpful. Run nw there with: nw --url=chrome://gpu

dpage-edb · 2022-06-10T09:23:50Z

Hi @rogerwang,

I tried running that on my system with the 5.4.0-117-generic kernel which displayed the plain white window and then proceeded to dump many MB of output to the console and just got more console output and a transparent window:

I have requested that the users who are seeing no window at all (the ones originally reporting issues) try the same and I will update here with their findings when I get them.

Please note that we also have another user who has reported a similar issue on Pop!_OS 22.04 LTS (Ubuntu 22.04). In their case, it works with the Xorg server, but not Wayland (and our previous release with NWJS 0.61.0 works fine in both cases). I've tried both Xorg and Wayland on my Ubuntu 20.04 system, and both are broken in the same way with the 5.4.0-117-generic kernel.

Thanks.

dpage-edb · 2022-06-10T10:32:35Z

Our original reporter has tested as requested, and reports that he still sees no UI displayed at all, just the following console output:

./nw --url=chrome://gpu
[0610/121804.665679:ERROR:zip_reader.cc(153)] Cannot open ZIP from file handle 3
[0610/121804.666412:ERROR:zip.cc(202)] Cannot open ZIP from file handle 3
[0610/121804.666821:ERROR:zip.cc(179)] Cannot open '/home/msustic/Desktop/nwjs-v0.65.0-linux-x64/package.nw': FILE_ERROR_NOT_FOUND: No such file or directory (2)
[45816:45816:0610/121805.220917:ERROR:CONSOLE(0)] "Unchecked runtime.lastError: Invalid value for bounds. Bounds must be at least 50% within visible screen space.", source: chrome-extension://aafddpmiffkameplnjkglahmbnbgidce/_generated_background_page.html (0)
[45848:45858:0610/121810.297087:ERROR:cert_verify_proc_builtin.cc(603)] No net_fetcher for performing AIA chasing.

JohnLego · 2022-06-11T00:23:42Z

NW.js currently has a bug that generates a file called "debug.log" when "package.nw" is not found in the current directory. I'd highly recommend using version 0.62.2 as it is the last NW.js version that is usable. It still has Chromium 99, but it is better than nothing.

The "debug.log" bug:
#7882

Download 0.62.2:
https://dl.nwjs.io/v0.62.2/

vin-d · 2022-06-15T09:03:46Z

so I've been able to track and create a perimeter to reproduce that bug.
more details on the pgadmin issue tracker https://redmine.postgresql.org/issues/7442#note-28
(it needs an account to be viewed -_- )

Basically was introduced in between 0.64.1 and 0.65.0 and is linked to the display management (and most likely the usage of the windowing coordinate system) when the nwjs window opens.
in a display placement where the bug appears you get the log
"Unchecked runtime.lastError: Invalid value for bounds. Bounds must be at least 50% within visible screen space.", source: chrome-extension://aafddpmiffkameplnjkglahmbnbgidce/_generated_background_page.html (0)

ayushmanchhabra · 2022-08-05T17:35:24Z

According to Note 31, should this be closed as resolved (here and in Redmine)?

cc @rogerwang @dpage @dpage-edb

vin-d · 2022-08-05T19:08:29Z

I ‘m not sure to agree that it should be closed.
Concerning PGAdmin they have just packaged an old release of nwjs to stop having the problem, but that also mean they won’t be able to integrate new nwjs releases.

To fix this, nwjs should be able to set the default position of a new window to a displayable coordinate. Not at 0;0

Because 0;0 on my displays setup is not valid space:
My screen setup is the following:
One 19201080 display on the left,
One 38402160 on the right,
And the bottom borders or both displays are aligned. So basically from coordinate 0;0 to 1920;1080 (the space above my full HD display) is invalid display space.

Previous working nwjs versions were opening by default in the center of my main display (the 3840*2160 one) and that’s what have changed.

vin-d · 2022-08-05T19:11:00Z

If you want to reproduce in a vm you should then have the ability to have 2 virtual displays so you can arrange them in a non square setup. I’m not sure you can do that with most vm softwares.

ayushmanchhabra · 2022-08-05T20:14:02Z

It's possible that #7884 is the cause of this. I'll try to reproduce on my end.

vin-d · 2022-09-13T09:12:47Z

It's possible that #7884 is the cause of this. I'll try to reproduce on my end.

Yes I think that's it.

my desktop structure made from 3 displays being like that

*                |--------------------------------|--------------------------------|
                 |                                |                                |
|----------------|                2               |                3               |
|        1       |    primary display             |                                |
|----------------|--------------------------------|--------------------------------|

where screen 1 is of 1080 resolution, and 2 and 3 are 2160 resolution

is my (0;0) coordinate, and nwjs tries to open the window there and crashes.
If I move displays so that (0;0) is displayable area then I have no crash.
which relates with the log

... Bounds must be at least 50% within visible screen

FaharAbbasRizvi · 2022-11-03T08:32:36Z

I am not able to see any GUI issue on Ubuntu 20.04 on latest snapshot build shipped with nwjs-v.70.0

Platform:
Ubuntu 20.04

Tested with nwjs-v0.70.0-linux-x64.tar.gz

Here is the output for nw command:

./nw
[14287:14306:1103/012608.752260:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[14287:14306:1103/012608.752358:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[14287:14306:1103/012608.783080:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[14287:14306:1103/012608.783169:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[14321:14343:1103/012609.261591:ERROR:command_buffer_proxy_impl.cc(128)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.

Here is the output for nw --url=chrome://gpu

./nw --url=chrome://gpu
[14380:14399:1103/012750.640435:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[14380:14399:1103/012750.640537:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[14380:14399:1103/012750.670683:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[14380:14399:1103/012750.670763:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
Warning: loader_scanned_icd_add: Driver /usr/lib/x86_64-linux-gnu/libvulkan_radeon.so supports Vulkan 1.2, but only supports loader interface version 4. Interface version 5 or newer required to support this version of Vulkan (Policy #LDP_DRIVER_7)
Warning: loader_scanned_icd_add: Driver /usr/lib/x86_64-linux-gnu/libvulkan_intel.so supports Vulkan 1.2, but only supports loader interface version 4. Interface version 5 or newer required to support this version of Vulkan (Policy #LDP_DRIVER_7)
Warning: loader_scanned_icd_add: Driver /usr/lib/x86_64-linux-gnu/libvulkan_lvp.so supports Vulkan 1.1, but only supports loader interface version 1. Interface version 5 or newer required to support this version of Vulkan (Policy #LDP_DRIVER_7)
Warning: loader_add_to_layer_list: Explicit layer VK_LAYER_MESA_device_select is using an old API version 1.2 versus application requested 1.3
Warning: terminator_CreateInstance: Driver /usr/lib/x86_64-linux-gnu/libvulkan_lvp.so supports interface version 1 but still exposes VkSurfaceKHR create/destroy entrypoints (Policy #LDP_DRIVER_8)
error: XDG_RUNTIME_DIR not set in the environment.
error: XDG_RUNTIME_DIR not set in the environment.
Error: eglChooseConfig returned zero configs
at Create (../../third_party/dawn/src/dawn/native/opengl/ContextEGL.cpp:53)

WARNING: lavapipe is not a conformant vulkan implementation, testing use only.

vin-d · 2023-01-18T15:19:11Z

Note that in pgadmin 6.19 NW.js was updated to 0.72.0 and I don't see the problem anymore.
pgadmin-org/pgadmin4#5116 (comment)
I assume this ticket can be closed.

ayushmanchhabra added the bug label Aug 5, 2022

ayushmanchhabra mentioned this issue Aug 8, 2022

New fullscreen windows do not respect the primary screen under Linux #7937

Open

3 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

No UI displayed on some Ubuntu 20.04 systems with 0.65.0 #7902

No UI displayed on some Ubuntu 20.04 systems with 0.65.0 #7902

dpage commented Jun 9, 2022

rogerwang commented Jun 9, 2022

dpage-edb commented Jun 10, 2022 •

edited

Loading

dpage-edb commented Jun 10, 2022

JohnLego commented Jun 11, 2022 •

edited

Loading

vin-d commented Jun 15, 2022

ayushmanchhabra commented Aug 5, 2022 •

edited

Loading

vin-d commented Aug 5, 2022

vin-d commented Aug 5, 2022 •

edited

Loading

ayushmanchhabra commented Aug 5, 2022 •

edited

Loading

vin-d commented Sep 13, 2022

FaharAbbasRizvi commented Nov 3, 2022

vin-d commented Jan 18, 2023

No UI displayed on some Ubuntu 20.04 systems with 0.65.0 #7902

No UI displayed on some Ubuntu 20.04 systems with 0.65.0 #7902

Comments

dpage commented Jun 9, 2022

Expected behavior

Actual behavior

How to reproduce

rogerwang commented Jun 9, 2022

dpage-edb commented Jun 10, 2022 • edited Loading

dpage-edb commented Jun 10, 2022

JohnLego commented Jun 11, 2022 • edited Loading

vin-d commented Jun 15, 2022

ayushmanchhabra commented Aug 5, 2022 • edited Loading

vin-d commented Aug 5, 2022

vin-d commented Aug 5, 2022 • edited Loading

ayushmanchhabra commented Aug 5, 2022 • edited Loading

vin-d commented Sep 13, 2022

FaharAbbasRizvi commented Nov 3, 2022

vin-d commented Jan 18, 2023

dpage-edb commented Jun 10, 2022 •

edited

Loading

JohnLego commented Jun 11, 2022 •

edited

Loading

ayushmanchhabra commented Aug 5, 2022 •

edited

Loading

vin-d commented Aug 5, 2022 •

edited

Loading

ayushmanchhabra commented Aug 5, 2022 •

edited

Loading