This applies to both 13.2 and 13.1 I believe.
I searched both this forum and Google land, found many in my situation but no clear solutions.
I was having issues connecting to a vnc server on a remote (on my LAN in my case) 13.2/KDE box.
The xinetd.service was running, but attempts to connect from another 13.2/KDE box, using KRDC or vncviewer, yielded
a Greeter backsplash and then an immediate disconnect pop-up.
Running sudo systemctl status xinetd showed the vnc server starting up and shutting down immediately, but with no useful info.
I did find in /var/log/messages (and journalctl) a message line:
kdm: localhost:2[27897]: Abnormal termination of greeter for display localhost:2, code 1, signal 0
Lacking a better strategy, I pasted that message into Google, which led me here
Following the strategy used by the Bug reporter, I made the following modification to my xinetd.d configuration
cat /etc/xinetd.d/vnc
# default: off
# description: This serves out a VNC connection which starts at a KDM login \
# prompt. This VNC connection has a resolution of 1024x768, 16bit depth.
service vnc1
{
socket_type = stream
protocol = tcp
wait = no
#cjm hacking a solution? This will run as root
# user = nobody
user = root
server = /usr/bin/Xvnc
server_args = -noreset -inetd -once -query localhost -geometry 1024x768 -securitytypes none
type = UNLISTED
port = 5901
}
You need to modify all vnc servers you want to use.
After changes, restart the service
sudo systemctl restart xinetd
I can now access the remote server from KDRC, get the Greeter Login and proceed.
I am unsure if this has any particularly enhanced security risks, hope someone with knowledge will comment.
I have not found any discussion on why running as user=nobody fails.
Hope this will help others who find this.