Where is home.vncxstartup

Show 1 more comment. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password.

Post as a guest Name. Email Required, but never shown. The Overflow Blog. Does ES6 make JavaScript frameworks obsolete? Podcast Do polyglots have an edge when it comes to mastering programming Featured on Meta.

Now live: A fully responsive profile. Related 1. Hot Network Questions. Question feed. Ask Ubuntu works best with JavaScript enabled. Accept all cookies Customize settings. 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.

What worked from me is ensuring that the PIDfile line was not present in the unit file and then I was able to get an Active status when I start the service. This is what my unit file looks like I'm new here so, apologies if I have violated any formatting rules for bash scripts :. And this is what my xstartup file looks like for gnome, I've commented out the default lines that come with the file:. Hello to anyone landing here. Please keep in mind this discussion was started in , and now it is 7 years later as I type this, Please keep in mind that some of the posts address this from various earlier versions of Red Hat Linux.

Comments Command line log: sudo systemctl start vncserver Jul 30 localhost. Hint: Some lines were ellipsized, use -l to show in full. Newbie 15 points. Log in to join the conversation. Red Hat Community Member 72 points. Jaromir Hradilek. Hi Itay, First of all, thank you very much for taking the time to report this issue.

SW Red Hat Guru points. Stephen Wadeley. Hello Bug was resolved and a new version published: Revision 0. Thank you. IE Newbie 15 points. Itay Eshet. Red Hat Active Contributor points. Won Young Choi. Install the app. For a better experience, please enable JavaScript in your browser before proceeding.

You are using an out of date browser. It may not display this or other websites correctly. You should upgrade or use an alternative browser. How do you config "xstartup" in vnc in order to start remote desktop with gnome? Thread starter admail2 Start date Jul 1, Hi, I tried the following 2 configuration but could not see the gnome desktop screen, in stead of a grey grid shown.

How do you config VNC to use gnome? Thanks so much. I think so: Code:.