VNC access was working fine on leap 15.3. After updating to 15.4 it no longer works. I can launch vncserver and connect remotely, but all I end up with is a black screen and am unable to interact with the desktop. The VNC settings in yast make no difference at all. It doesn’t matter if I set it to allow remote access with or without session management, or just set it to disable remote management completely. I can still launch a vnc server, and the same behavior exists in every case. I tried switching from SDDM to xdm (lightdm doesn’t work), and that makes no difference either. Any thoughts/suggestions?
Make sure that you’re using Xorg rather than Wayland - AFAIK, VNC requires X and doesn’t work with Wayland.
I am using Xorg. Need 20 characters for response.
Hello,
which type of VNC session are you using on the server?
There is a documentation for leap 15.4 see
On tumbleweed I use persistent VNC session with tigervnc. I start the vncserver with
# systemctl start vnccserver@:x
where :X is the session number defined in /etc/tigervnc/vncserver.users
This is something new in tumbleweed and I dont’t known if it is already present in Leap 15.4
Regards
Is local GUI login session active for the same user? Try as completely different user that is not logged in at the same time.
I managed to get VNC working with from vncserver, but I’d like to be able to use vncmanager for session management. However, this doesn’t appear to be working as intended. I can get it to work only under the following specific circumstance:
Step 1) login to the desktop session at the physical machine using the gdm display manager.
Step 2) restart vncmanager.
Step 3) connect to VNC session using a viewer.
At this point I will be presented with a login screen.
Step 4) log out of the physical desktop session and log into the VNC session.
This will work, and I must stay connected the entire time. If I disconnect, I will be unable to reconnect as I get a blank screen on the next connection attempt. The above steps are the only way I can get it to work, any other combination of steps or other display managers will fail.
Anyone have any ideas as to why it is behaving this way? Thanks.