-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
No UI displayed on some Ubuntu 20.04 systems with 0.65.0 #7902
Comments
Thanks for reporting. The graphics information for that system would be helpful. Run nw there with: |
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. |
Our original reporter has tested as requested, and reports that he still sees no UI displayed at all, just the following console output:
|
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: Download 0.62.2: |
so I've been able to track and create a perimeter to reproduce that bug. 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. |
According to Note 31, should this be closed as resolved (here and in Redmine)? |
I ‘m not sure to agree that it should be closed. 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: 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. |
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. |
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
where screen 1 is of 1080 resolution, and 2 and 3 are 2160 resolution
|
I am not able to see any GUI issue on Ubuntu 20.04 on latest snapshot build shipped with nwjs-v.70.0 Platform: Tested with nwjs-v0.70.0-linux-x64.tar.gz Here is the output for nw command: ./nw Here is the output for nw --url=chrome://gpu ./nw --url=chrome://gpu WARNING: lavapipe is not a conformant vulkan implementation, testing use only. |
Note that in pgadmin 6.19 NW.js was updated to 0.72.0 and I don't see the problem anymore. |
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:
This is the console output from my own Ubuntu 20.04 installation, on which everything seems fine:
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:
Any assistance would be appreciated.
The text was updated successfully, but these errors were encountered: