The screen goes to sleep after 10 minutes and doesn't wake up properly

[yezifeng]

Hello everyone,

I want to try to install proxmox7.4-1. I didn't do anything for 10 minutes, and the installation interface went into sleep mode. Then wake up via mouse or keyboard, it looks like there is a rendering issue?

What is the problem? How should it be solved? Please help!

 

[Chris]

HI,
should be enough to reload the page, seems that the browser only refreshes part of the output.

 

[yezifeng]

HI,
should be enough to reload the page, seems that the browser only refreshes part of the output.

Thanks for your quick reply!

Any suggestions for this?

I know older versions don't have that problem (like proxmox 5.4).

Is there anything special about the screen?

 

[Chris]

Doesn't refreshing the screen solve this? Which part of the screen is redrawn is something the PVE installer is not concerned with, this has to be done by the browser.

 

[yezifeng]

Doesn't refreshing the screen solve this? Which part of the screen is redrawn is something the PVE installer is not concerned with, this has to be done by the browser.

Thanks for the suggestion, but unfortunately, it doesn't work. Refreshing the browser didn't fix it.

It doesn't look like a browser loading issue.

After pressing Ctrl+Alt+F2 and Ctrl+Alt+F4 shortcuts, it can reload the complete page.

 

[Neobin]

Which version is your PVE-host? Can you please provide the output of: pveversion -v from it?

See also:
https://forum.proxmox.com/threads/proxmox-ve-8-0-beta-released.128677/post-564687

 

[RolandK]

bugreport at https://bugzilla.proxmox.com/show_bug.cgi?id=4786

 

[yezifeng]

Which version is your PVE-host? Can you please provide the output of: pveversion -v from it?

See also:
https://forum.proxmox.com/threads/proxmox-ve-8-0-beta-released.128677/post-564687

Sure. But I don't think it's a PVE-host version issue.

root@vcloud:~# pveversion -v
proxmox-ve: 6.0-2 (running kernel: 5.0.15-1-pve)
pve-manager: 6.0-4 (running version: 6.0-4/2a719255)
pve-kernel-5.0: 6.0-5
pve-kernel-helper: 6.0-5
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph-fuse: 12.2.11+dfsg1-2.1
corosync: 3.0.2-pve2
criu: 3.11-3
glusterfs-client: 5.5-3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.10-pve1
libpve-access-control: 6.0-2
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-2
libpve-guest-common-perl: 3.0-1
libpve-http-server-perl: 3.0-2
libpve-storage-perl: 6.0-5
libqb0: 1.0.5-1
lvm2: 2.03.02-pve3
lxc-pve: 3.1.0-61
lxcfs: 3.0.3-pve60
novnc-pve: 1.0.0-60
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.0-5
pve-cluster: 6.0-4
pve-container: 3.0-3
pve-docs: 6.0-4
pve-edk2-firmware: 2.20190614-1
pve-firewall: 4.0-5
pve-firmware: 3.0-2
pve-ha-manager: 3.0-2
pve-i18n: 2.0-2
pve-qemu-kvm: 4.0.0-3
pve-xtermjs: 3.13.2-1
qemu-server: 6.0-5
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.1-pve1

 

[RolandK]

> Sure. But I don't think it's a PVE-host version issue.

correct