Root/.vnc/xstartup no such file

The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Learn more. Ask Question. Asked 5 years, 6 months ago. Active 5 years, 6 months ago. Viewed 14k times. I'm using ubuntu I have installed the VNC by using this command sudo apt-get install vnc4server I have tested the connection and it working and the terminal of other system got open. Now I'm trying for the VNC full desktop. I searched everywhere.

Improve this question. Necktwi 4 4 gold badges 11 11 silver badges 20 20 bronze badges. Belmin Fernandez Belmin Fernandez 8, 13 13 gold badges 43 43 silver badges 49 49 bronze badges. Just uncomment these two lines and restart your vncserver. Your default desktop will be started by vncserver — Serge.

I want it to be done by default for all new users. This is not clear from your question : wait a second Any suggestions on how to make the question clearer seems like you already have my answer but for others visiting the site Add a comment. Install vnc 2. Mine is listed below. No other action here, no need to kill vnc or anything. I'm a bit of a noob at this, so I don't have full insight as to why this works, but it does for me.

After I had made my initial posts above I did find a related Bugzilla. Problem solved. Following Martin's instructions verbatim did not work for me. I still needed to manually start the vnc server once as the user as per my steps. There is also another issue: this works fine if you vnc into the server, then just close the vnc window.

You can then reconnect. But if you vnc into the server, and then Log Out of the user account, the vnc service is killed and has to be manually restarted from an SSH session. It seems like the vnc service should not do this. I am ok with this issue because I am aware of it, but it is not really good behavior.

Leigh, I have also encountered the same issue you describe when logging out. I recall having to add an additional line or two in the service config section. Using that type of technique worked for me prior to the systemd changes. I was experimenting with this issue last night using the new version of systemd after a fresh rebuild of a server using tigervnc.

I'll see if I can confirm a working config for automatically restarting the service upon logout and post back here. I did play around with trying to get the service to restart automatically.

I haven't had any luck. I tried restart always or on-failure both ways but one at a time. Any ideas? A caution in regard to the vncserver issue with RHEL 7. Based on my setup none of the suggestions, I have tried, resolve issue without creating a bigger problem. On the surface the suggestion to change the ExecStart entry and add the User and Group entries looks good.

This does appear to allow the server to start cleanly and for it to be properly shutdown and restart provided you start with things clean. However, this configuration when using Gnome with screen locking active is unusable. I cannot unlock the session once the screen lock triggers. I start to type the password and it automatically jumps back to the beginning clearing out what I have entered.

With screen saver disabled it looks like the vnc session is fine but we need to maintain screen locking. At moment for me the best approach is to run with the traditional RHEL 7 recommend configuration and just keep in mind that it will not stop or restart properly and to watch for extraneous lock files. As long as I start it and let it run until reboot I have no functional issues although I do get the "resource limit was exceeded message".

I can't get this to work. I'm using the exact same service file as posted by Vincent Cojot. The service is actually starting and I'm able to connect to the machine from a vnc viewer client, but at the login screen I can't type in the password because the screen gets cleared every second. Hi Jhonathan, sorry to hear that you're still experiencing issues. The service file's only purpose is to get the service started. You may want to check what's in that file.

Also, I don't think you should see a login screen -after- connecting with the viewer password. It should bring you directly to the Xvnc desktop running under the user specified by the service file. Update: situation with starting up the server improved after a yum update and the instructions given in the VNC chapter of the sysadmin guide will work- to a point. The point being the number of VNC server service under which you'd be connecting from remote computer.

In practice, this will not work. Once you started VNC server on, say, display no. If you decided to start the service with, say: systemctl start vncserver If the service was started with 2. That seems to be the only part missing in the VNC chapter, everything else works as described. I have had some luck with this. When you connect to vncserver with your client, by default you are given a new X session with your own desktop.

This means that a person who is physically sitting in front of the server will not see your remote session, and vice-versa you cannot see or interact with the root :0 or physical desktop. If you would like to remote into a machine with vnc and actually see and interact with the root desktop you can use x11vnc , which provides access to the root :0 desktop by default.

A person sitting in front of the server will see your actions, such as the mouse moving etc. Additional options may be defined by the user, for a complete list enter a bad option which forces vncserver to display all available options.

TightVNC requires each user to have an. Xresources file in their home directory. Xresources file is missing if TightVNC reports an error message like:. You should create the correct file, and TightVNC will populate it automatically.

This can be done with the command:. Jump to: navigation , search.