I am also having problems. I have followed the How To. I am on AMD64, I installed TightVNC (client and server via the USE flag). When loading the server via the vncserver program (script), everything works ok and I am able to connect locally (although only twm shows up, which is normal).

It fails when trying to use xinetd. Here is my conf:
In /etc/services:

It looks like /etc/hosts.allow is what was holding things up. I put an ALL:ALL in that file and everything is working. I am still not sure what specific line I need to put in /etc/hosts.allow so I don't have to leave it wide open, but other than that, it's working great.

Well, I got it set up no problem. Followed a bit of help from this guide and the one on the forums. Works great. I can log in under any name I want in the KDM list and the multiple port options tied to different resolutions gives me the resolution I want except one thing, most applications that aren't KDE based (such as mozilla-firefox, mozilla-thunderbird) don't work in 32-bit versions. It crashes and leaves an error saying "Cairo doesn't support the image format" and it lists the 32 color mode.

Is there really much of a difference between 24 and 32 bit color? 'Cause I was just going to say "forget it."_________________- Michael A. Leonetti

hello everyone!
I followed the guide and have it mostly working.
my problem is that after logging in and starting Gnome the keyboard mapping seems to go all wonky.
I tried logging in to a failsafe terminal and the keyboard is fine, but once I start gnome-settings-daemon the keys produce irregular characters.
For instance :
typing asdf produces abfh
typing zxcv produces */d,
pressing space produces a 7
pressing enter produces a space
typing 1234 produces 90-=

The keyboard settings in gnome are set correctly and work fine when logging in normally.
I get the following messages when starting gnome-settings-daemon from a failsafe terminal:

If you won't treat images or do some grafic stuff, you won't even notive the difference between the two color modes (In my opinion).
And I don't assume you are going to do that, logged in over a vnc connection?

Maybe this question has been aswered before here, and if so plz forgive me. I have used the tutorial and everything has worked fine. What i want to know is if there is a way to use xinetd and tightvnc and be able to resume a session. Because now, as soon as i close the window i have opened with vncviewer, the computer with vncserver shows "session closed for user...". I 've read somewhere that this can be achieved with x11vnc.

Ok, i have searched the posts and i see that this can be done, using realvnc and having a password in etc/xinetd.d/xvncserver. I have tried that, and although it seems to work fine, my session ends as soon as i exit the vncviewer window. My etc/xinetd.d/xvncserver file is:
service vnc-1024x768x24

The only thing i do is "vncviewer desktop:5972", then i enter the vncpasswd and then i have to enter my user username and passwd in xdm(which i don't think should be happening). But xhen i close the window, the session closes too. Any ideas?

I can log in if I manually run vncserver, or Xnest -ac -query 192.168.1.101 :1 or the GDM login manager from my other Gentoo box. No matter what I try VNC wants a password, and skips the gdm login. I haven't tried configuring one since it shouldn't be needed.

I am also having problems. I installed xinetd-2.3.14, tightvnc-1.3.9-r1 (client and server) and configured as indicated in the wiki in a pentium3 (x86) with Xfce4 and xdm. When launch the server via vncserver :1, everything works ok and I am able to connect from another computer in my home network.

It fails when trying the "automatic vncserver response" via xinetd. I launch

Code:

vncviewer pentium3:62

and the login manager screen appears, but after typing the username and password the window is closed and the session ends.

#
# This is the master xinetd configuration file. Settings in the
# default section will be inherited by all service configurations
# unless explicitly overridden in the service configuration. See
# xinetd.conf in the man pages for a more detailed explanation of
# these attributes.

defaults
{
# The next two items are intended to be a quick access place to
# temporarily enable or disable services.
#
# enabled =
# disabled =

Here are some of my config files. Hope they will be usefull for someone I use Tightvnc.
/etc/xinetd.d/xvncserver
-ac is required to connect without password. This fixes errors about magic cookies.
-fp (fontpath) is also required for the server to be able to start.
-co (rgbpath) is there to get rid of error message, but it is optional. You can verify your rgbpath from xorg.conf.

Does anyone know how to disable KDE4 desktop effects for a vnc session? I want to keep the effects when physically logging in to the desktop and automatically disable them for remote/vnc sessions. Perhaps even specifying a different theme might be useful too.

Is there some option I can add to the "startkde" part of my ~/.vnc/xstartup file?

I have a problem with configuring my vnc server.
I was following the tutorial on wiki (which is equal to the one in first post), but I can not see gnome login window in vncviewer. When I open it - it shows a grey window with graphic console, but no login prompt or something.

any ideas how to make gnome show up in vncviewer? do you guys need any files from my box to help with that, if you plan to do so?

Thanks
Anton

Try recompiling gdm (KDM XDM...) with the use flag "-ipv6." It seems that Xvnc doesn't play well in ipv6.

Change the runas user and save this as /etc/init.d/vncserver. Dont forget to set the vncpasswd & xstartup in ~/.vnc/

Code:

chmod +x /etc/init.d/vncserver

rc-update add vncserver default

/etc/init.d/vncserver start

Actually, you can get the windows manager to start any number of "terminals" on predefined displays. These act like real terminals, so if you don't log out of the session, the session stays open, the next time you connect. The risk/downside I was not able to resolve (though I really didn't try) is that if you disconnect he session on display :1, the next time you reconnect to that display, the session is completely open, exactly the way it was when you disconnected. There should be a way to lock the screen prior to disconnecting, or using a password protected screen saver that would protect the session.

I can post the relevant configuration for gdm, I think that I still have it for xdm. Both are pretty clearly described in the config files.

Hi, does anyone one know why i can't make sessions reusable (resume a session). I've follow the howto and also have read the full thread but there's no way to get session reusable. When i set wait = yes i can't connect to the server. i hope someoen can help, thanks in advanced

First I upgraded tightvnc to 1.3.10-r1
by adding =net-misc/tightvnc-1.3.10-r1 to /etc/portage/package.keywords

I've noticed that the -inetd flag suppresses all output from Xvnc
so you'll get more information from Xnvc if your running it directly by ommitting this flag temporarily
I also noticed that the fonts directory needs to be specified as well for this to work

e.g. for example to test that the parameters are correct for Xvnc try something like
(this only seems to work while xdm is stopped)

Hi, does anyone one know why i can't make sessions reusable (resume a session). I've follow the howto and also have read the full thread but there's no way to get session reusable. When i set wait = yes i can't connect to the server. i hope someoen can help, thanks in advanced

After about two hours of scratching my head, I've discovered an unusual problem: kde4 and vnc can't spawn sessions with a 32-bit colour depth. Setting the colour depth to 16-bit for my services defined in /etc/services and /etc/xinetd.d/xvncserver fixed the problem.

Hopefully this will help someone and prevent them from wasting so much time on a silly problem.

Hi, does anyone one know why i can't make sessions reusable (resume a session). I've follow the howto and also have read the full thread but there's no way to get session reusable. When i set wait = yes i can't connect to the server. i hope someoen can help, thanks in advanced

Me three Same exact output, a million different config options tried. I'm using TigerVNC and the TightVNC+SSH Java client to connect, FWIW, and it works fine using wait = no or the tigervnc initscript. Anyone any ideas?

as reported by Havin_it, langa and soya occured for me, when I edited the Xaccess file and wrote

Code:

192.168.0.* #any host [in my lan] can get a login window

instead of

Code:

* #any host can get a login window

I probably got something wrong there - I suppose, I would have to add localhost (127.0.0.1) to the configuration, but the docs are pretty sparse concerning this point. Anyway, after using the line with just the asterisk, it worked. The access restrictions of xinetd should, in addition, cover the 192.168.0.* setting. (You would use

Code:

only_from = 192.168.0.1/24

in your /etc/xinetd.conf file).

5. To make the whole thing work for me, I had to explicitely specify the Screen ":1" when starting the Xvnc server, as there was (or could be) a local X running on Screen :0. To do this, you would just add :1 to the server_args in the /etc/xinetd.d/xvncserver file:

I read, that it has to be the first argument, but I didn't test it another way.

6. Tigervnc is better than tightvnc (at least for me): Using tightvnc, I had some really ugly graphics glitches which did not only look bad but even made some texts unreadable. With tigervnc, they are all gone, just the task bar looks a little strange, but is usable anyway. Additionally, it seems to me, that the access is "smoother" in tigervnc.

You can follow the HowTo as it is, just emerge tigervnc instead of tightvnc. And there's one option you would have to add to the entries in /etc/xinetd.d/xvncserver:

(Concerning the :1, please see point 5.) If -SecurityTypes none is not set, the system expects a password set by vncpasswd. Otherwise, you can use your desktop environment's login and authentication mechanism as usual.

That's it. I hope, I didn't write too much stuff, that already seemed clear to everyone or was explained already.