Forum / NoMachine for Linux / Empty screen on connection
- This topic has 2 replies, 2 voices, and was last updated 8 months ago by Britgirl.
-
AuthorPosts
-
April 25, 2024 at 20:26 #47959tmdagParticipant
Hi,
I’m working on Fedora systems, it started happening one day on F38 that on connection i was getting just an empty, black screen. No matter which machine I am connecting to, it was connecting “successfully” but showing just an empty, black screen.
I’ve recently updated two clients to Fedora 40 and this time it got little bit worse. Here are my steps:
– client01 connecting to server01, got connected, and presented with an empty, white screen. Tried re-connecting, and unable to connect at all (stuck at spinning “connecting to..”)
– client01 connecting to server02, got connected, and presented with an empty, white screen. Tried re-connecting, and unable to connect at all (stuck at spinning “connecting to..”)
– client02 connecting to server01, stuck at spinning “connecting to..”
– client02 connecting to server02, connected! OK.
– server01, turned OFF “use acceleration/use hardware encoding”
– client02 connecting to server01, connected! OK.
– client01 connecting to server01, connected! White/blank screen.
– client02 connecting to server01, stuck at spinning “connecting to..”
– server01, turned ON “use acceleration/use hardware encoding”
– client02 connecting to server01, connected! OK.
– client01 connecting to server01, connected! White/blank screen.
– client01 connecting (again) to server01, stuck at spinning “connecting to..”
– client02 connecting to server01, stuck at spinning “connecting to..”
In a summary:
client01 is unable to view any desktop at all. After server01 toggled settings/restarted, client01 could connect once but did display white screen, any next attempts resulted with “connecting”, unless server got restarted again.
client02 is able to connect to servers, BUT, after client01 connects to server01 (with white screen output), client02 is no longer able to connect to server01, until server01 is restarted.
client01:
6.8.7-300.fc40.x86_64
nomachine 8.11.3
GPU: Intel Raptor Lake-P [Iris Xe Graphics]
GPU: NVIDIA RTX A500 Laptop GPU
NVIDIA driver Version: 550.76
client02:
6.8.6-1.surface.fc40.x86_64
nomachine 8.11.3
GPU: Intel Alder Lake-UP3 GT2 [Iris Xe Graphics]
server01:
6.8.5-201.fc39.x86_64
nomachine 8.11.3
GPU: NVIDIA GeForce GTX TITAN X
NVIDIA driver Version: 550.67
server02:
4.9.201-tegra
nomachine 7.14.2
April 26, 2024 at 11:49 #47966BritgirlKeymasterHi,
can you try disabling HW decoding on client 01? Check the article here to know how to do this:
i) How to disable hardware decoding on the client side
https://kb.nomachine.com/AR07U01202ii) Then, if that doesn’t help, the logs from client01 would be useful. See the section of this document:
2. Fourth Step: Collect Client Side Logs
https://kb.nomachine.com/DT07S00243iii) Gather logs from server01 after reproducing the “Connecting to …” problem. For logs of the server, see the same document.
Submit everything to forum[at]nomachine[dot]com.
April 26, 2024 at 12:31 #47970BritgirlKeymasterI made a mistake in points i) and ii).
Please invert them, so you should:
i) send us logs from client01. See the section of this document:
2. Fourth Step: Collect Client Side Logs
https://kb.nomachine.com/DT07S00243ii) Try disabling hardware decoding on the client side, does this change anything?
https://kb.nomachine.com/AR07U01202iii) Send us server01 logs as already requested
-
AuthorPosts
Closed because the user did not provide further feedback. Please notify us if you confirm that it is resolved or open a new topic if you have the same problem.