Oct 11 05:01:34 myserver gnome-session-binary: WARNING: software acceleration check failed: Child process exited with code 1 Oct 11 05:01:34 myserver gnome-session: gnome-session-binary: **WARNING: software acceleration check failed: Child process exited with code 1** Oct 11 05:01:34 myserver systemd: Started Remote desktop service (VNC). Oct 11 05:01:34 myserver vncserver: Log file is /home/justme/.vnc/myserver:1.log Oct 11 05:01:34 myserver vncserver: Starting applications specified in /home/justme/.vnc/xstartup Oct 11 05:01:34 myserver vncserver: New 'myserver:1 (justme)' desktop is myserver:1 Oct 11 05:01:31 myserver vncserver: You'll have to kill the Xvnc process manually Oct 11 05:01:31 myserver vncserver: Can't find file /home/justme/.vnc/myserver:1.pid Main PID: 1570 (code=exited, status=0/SUCCESS) Process: 1358 ExecStartPre=/usr/bin/vncserver -kill %i (code=exited, status=2) Process: 1410 ExecStart=/usr/bin/vncserver %i (code=exited, status=0/SUCCESS) Process: 2456 ExecStop=/usr/bin/vncserver -kill %i (code=exited, status=0/SUCCESS) Loaded: loaded enabled **vendor preset: disabled**)Īctive: inactive (dead) since Wed 05:04:32 EDT 21min ago I've looked in the log file and the only errors/warnings I've seen are: ~]# systemctl status - Remote desktop service (VNC) # Clean any existing files in /tmp/.X11-unix environmentĮxecStartPre=-/usr/bin/vncserver -kill %i # Use "-localhost" to prevent remote VNC clients connecting except when # Use "-nolisten tcp" to prevent X connections to your VNC server via TCP. # the help of ssh, you end up seeing what hostB makes available on port 590M # You can then point a VNC client on hostA at vncdisplay N of localhost and with # See the ssh man page for details on port forwarding) # (in fact, it ssh-connects to hostB and then connects to localhost (on hostB). # this will open a connection on port 590N of your hostA to hostB's port 590M # whose VNC output you want to view (host B) # the machine you want to view VNC on (host A) to the machine # limit connections to the local host and then tunnel from # untrusted! For a secure way of using VNC, you should Run `systemctl enable DO NOT RUN THIS SERVICE if your local area network is Replace with the actual user name and edit vncserver Here is the file: # The vncserver service unit file Don't get a desktop environment that I've edited according to CentOS 7 articles and documentation I've seen: I can check and uncheck those boxes, but that's it. Xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &īut this produces gray screen for the client with the following check boxes and text: Accept clipboard from viewers I had the VNC server working on a now retired CentOS 6 system, so I decided to try the xstart from that one: #!/bin/sh When I log into this same account from the console, it works perfectly fine. It gets prompted for the password, but it just provides a blank black screen. vnc/xstartup as supplied in my home directory: #!/bin/sh It is running for VNC: Xvnc TigerVNC 1.8.0 - built 01:32:32 I either get a blank black screen or text with checkboxes. I'm running CentOS 7.4 with Gnome and having problems getting the VNC server to serve a Desktop environment for the client.
0 Comments
Leave a Reply. |