Tichondrius, thanks for a great HOWTO!
KDE users: I've taken the liberty of adapting this to Kubuntu Edgy. The process is a bit different for KDM. If anyone's interested, I've posted the revised HOWTO in the Kubuntu forums.
Tichondrius, thanks for a great HOWTO!
KDE users: I've taken the liberty of adapting this to Kubuntu Edgy. The process is a bit different for KDM. If anyone's interested, I've posted the revised HOWTO in the Kubuntu forums.
Maybe a note could be added to the first HowTo page:
On edgy the font path is wrong in "server_args =..." in /etc/xinetd.d/Xvnc:
howto shows:
but I had to change it (as per another post in this thread) to:Code:-fp /usr/share/X11/fonts/misc
The symptom was vnc errors like:Code:-fp /usr/share/fonts/X11/misc
ReadFromRFBServer: rdr::SystemException: read: Connection reset by peer (104)
when trying to connect.
Also, when manually executing the vncserver command with the bad font path, I saw errors like: "Fatal Error" ... couldn't find font 'fixed'
I finally got this working on Edgy AMD64 -- yay! Here are the steps that worked for me, slightly different than the original howto above:
1. Install xinetd, vnc4server, xvncviewer. The regular vncserver package does not work which is why you need to install vnc4 (from universe).
2. Create the file /etc/xinetd.d/Xvnc and paste the following in:
Note that the snippet below has a few differences from the original howto: (1) the fontpath entry is specific to Edgy; (2) the server directive needs to be /usr/bin/Xvnc4, not Xvnc; (3) I used no security but you can use the password file from the original howto if you like. For my use case I didn't need it.
3. System - Admin - Login Window: On "Remote" tab, change Style: to something other than 'disabled'.Code:service Xvnc { type = UNLISTED disable = no socket_type = stream protocol = tcp wait = yes user = root server = /usr/bin/Xvnc4 server_args = -inetd :1 -query localhost -geometry 1024x768 -depth 16 -once -fp /usr/share/fonts/X11/misc -DisconnectClients=0 -NeverShared SecurityTypes=None port = 5901 }
4. Reboot.
Now I can VNC in using hostname:1 and it works like a charm. Good luck!
-Billy
I've done everything in the guide, but for some reason I get the following when I try to connect
ReadFromRFBSServer: rdr::EndOfStream
Any ideas what this is about?
I had the same problem yesterday then I reverted the vncserver package back to the previous version and the problem went away. In may case the problem happened after updating the package to the latest version, that's why I tried to go back...
Has anyone seen this problem before?
I've had X and VNC working before. I don't know what's happening. I'm sure it's something simple.
Now I get
ReadFromRFBServer: rdr::SystemException: read: Connection reset by peer (104)
instead. Even though I have changed the from /X11/fonts/ to fonts/X11/
Hi!
I had the "ReadFromRFBSServer: rdr::EndOfStream" error message. Removing "-query localhost" from the server_args line in /etc/xinetd.d/Xvnc file solved this problem.
Now, I can connect to the vnv4server, but I get that grey screen.
I don't know how to get the login screen back!
I have only ssh access to this machine now, so I cannot go to System>Administration>Login Window>Remote and select Same as Local as suggested by pkbarber in post #188
Is there a way to modify this setting from a config file?
Everything was working fine on my edgy box, untill I made some update from uate_manager. I did'nt write down which packages were being updated, though.
Any help will be appreciated....
François
Last edited by coulier; January 10th, 2007 at 05:16 PM.
I have a reasonably fresh install of 6.10 on AMD64 and the Xvnc4 setup recommended by billycub isn't working for me either - if the latest vnc4server package is broken, is there any way for me to get the previous one?
It's clearly listening on the right port:
tcp 0 0 0.0.0.0:5901 0.0.0.0:* LISTEN 4814/xinetd
But if I try to connect using a VNC client locally or remotely, they all seem to connect (and initially start drawing a gray screen) and then quickly get dropped, e.g.:
---------------
$ vncviewer localhost:1
VNC Viewer Free Edition 4.1.1 for X - built Jan 6 2007 09:47:04
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
Wed Jan 10 18:30:12 2007
CConn: connected to host localhost port 5901
CConnection: Server supports RFB protocol version 3.8
CConnection: Using RFB protocol version 3.8
TXImage: Using default colormap and visual, TrueColor, depth 24.
CConn: Using pixel format depth 6 (8bpp) rgb222
CConn: Using ZRLE encoding
Wed Jan 10 18:30:16 2007
main: write: Broken pipe (32)
------------
Does Xvnc4 have any logs anywhere?
To confirm the what reported in the previous message (from coulier) I restate what I reported before: my problems with vnc and resumable sessions (vncserver instanciated by xinetd) started Saturday when I updated vnc4server to the lastest version, once I reversed it back to the previous release the problem went away. Overall I still have problems using vnc though, few days ago I wrote a message in the forum to explain the issues but I didn't get any feedback so far. Briefly when I start a vnc session from ssh I get a gray screen on the vncviewer window, in my case the cause seems to be the fact that gnome fails to start. I do not know how to fix it, if someone has any suggestion...
Bookmarks