Linux – x11vnc server lets me connect at login screen, but after login, connection closes

Well, I think I managed to get a compromise solution for this:

using the following configuration I can get a login screen:

service vnc-1024x768x16
{
  protocol = tcp
  socket_type = stream
  wait = no
  user = user_name
  server = /usr/bin/Xvnc
  server_args = -inetd -query localhost -once -geometry 1024x768 -depth 16 -rfbport=5901 -rfbauth=/home/user_name/.vnc/passwd
  disable = no
}

Looking at this tutorial, I can observe that the solution is similar. I even noticed that they aren't using vncserver as I was looking for (since I use vncserver to run manually the VNC server, without xinetd).

Looking at the man page of vncserver, they say that in fact this program is a wrapper for Xvnc. However, when I run vncserver alone, it calls a program named Xtightvnc, not Xvnc.

Changing the 'server' line in the above configuration to call Xtightvnc instead of Xvnc gives me no connection, so I still will have to carry on with Xvnc.

The other big difference I noticed between using Xtightvnc and Xvnc is that the last one makes a pretty slow connection, so I still prefer Xtightvnc...

By now, I can handle this a little bit better, but any further ideas are welcome too...

BTW, I discovered that Xvnc is in fact RealVNC for my machine, not TightVNC as I desired, guess I'll have to look more on how to redirect things well, also on how to use Xtightvnc as I desire...

Thanks for reading...

just as a colophon... I finally got to get Xtightvnc to work. The problem? In the xinetd server_args configuration line doesn't accepts the '=' character for assigning value to parameters! :D so the final result is:

service vnc-1024x768x16
{
  protocol = tcp
  socket_type = stream
  wait = no
  user = user_name
  server = /usr/bin/Xvnc
  server_args = -inetd -query localhost -once -geometry 1024x768 -depth 16 -rfbport 5901 -rfbauth /home/user_name/.vnc/passwd
  disable = no
}

I also had to change the Xvnc soft link, which was pointing to Xvnc4 (realvnc) so it finally pointed to Xtightvnc...

You're using rvm, so the proper way to deal with ruby not being found is to use an rvm wrapper (on SysVinit and upstart systems).

First (optional) create an alias for your app to the gemset you want to use:

rvm alias create my_app ruby-2.1.4@my_gemset

Then create the wrapper(s) you want:

rvm wrapper my_app mongrel_rails

The wrapper is created in the $rvm_path/wrappers/my_app directory, and then you call it from your init script after switching users.

su user01 -c '/home/user01/.rvm/wrappers/my_app/mongrel_rails -e production -p 8088'

(Note that I've completely removed screen from this, as there's little good reason to be running this within a screen.)