Forum Replies Created
-
Posts
-
Graphics are Intel HD integrated on the i5 650 CPU, no discrete card. The driver config from lshw is:
configuration: depth=32 driver=i915 latency=0 resolution=1920,1080
glxinfo | grep “OpenGL version”:
OpenGL version string: 2.1 Mesa 24.0.9-0ubuntu0.1eglinfo | grep “EGL version”:
EGL version string: 1.5Adding “WaylandModes drm,egl,compositor” is effective! I see the desktop from my Windows client as I type this message.
Sad to report no change in my symptoms after updating clients and server to 8.14.2, setting
--eglcapture yesand restarting the computers.nxegl logs are attached.
FWIW, I do appreciate the effort spent on what is clearly a corner case of an unpaid user.
My server is not headless either. Full bog-standard Ubuntu GNOME desktop environment. The physical display is usually turned off, but I’ve had it both off and on for these recent tests. That’s how I can tell I’m getting keyboard and mouse control even though my client window is black.
Logs from $HOME/.nx/nxegl/ are attached, since they are small enough.
Tried today connecting from a fresh install on a totally separate Windows 11 box as the client. Same results, control but no video, consistent through all three possible values of ”Enable hardware accelerated decoding”.
To me this strongly suggests server rather than client side problems. No response here since I last uploaded server logs on 12 September.
<option key=”Enable hardware accelerated decoding” value=”false” /> did not work for me, same for “disabled” previously attempted.
No change after uninstalling and reinstalling both client and server. I can still connect and control but can’t see the remote desktop
New logs sent, but the symptom has changed – progress of a sort.
After an Ubuntu update and consequent mandatory restart of the server, I cannot reproduce the symptom. I now stay connected, and use the client side mouse and keyboard to control the server machine. I set up a physical display attached to the server DisplayPort where I can see it from the room with the client, and see the mouse move and letters when I type on the physical display – but the client window is black.
Thanks for following up!
Logs are attached. The archive was too big so I removed many sub-directories named for the host to which I was connecting and a long random string. These may be the “recording sub-directories” mentioned in the KB article, but I can’t find a definition for that term, so please let me know if you need more. I did keep some of these, including every one since the problem starred on 1 September and several just before.
Disabling hardware decoding did not affect the symptoms.