Worked for me.
BTW, to save people some clicks, the post is here.
Worked for me.
BTW, to save people some clicks, the post is here.
The localhost:1 works now poppi! As for the remote desktop VNC... all goes well for a split second and then the windows begin to pop up infinitely. Here's a screenshot to explain.
http://img443.imageshack.us/my.php?i...ncerrorcq8.jpg
What the heck is going on!?
Any help is MUCH appreciated, thanks!
First of all Dethecus, thank you for this!
I do have problems though. If I do vncviewer localhost:1 I dont get a GDM login window, just a blank screen with some checkboxes.
EDIT: FIXED. Followed the instructions here.
Last edited by nexxteh; October 4th, 2008 at 09:58 AM.
When I do the last command in part 2 of the tutorial "vncviewer localhost:1" I didnt have vncviewer. So I managed to figure that out and got it. After that when I type in the command I get...
VNC Viewer Free Edition 4.1.1 for X - built Apr 16 2008 13:02:40
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
Mon Oct 6 17:48:14 2008
CConn: connected to host localhost port 5901
main: read: Connection reset by peer (104)
Last edited by killdeer; October 6th, 2008 at 11:00 PM.
Hi guys, I'm getting the same issue, I followed the newer guide in post 458 but I'm still getting this
Then when I look in the syslog for messages I see the followingCode:VNC Viewer Free Edition 4.1.1 for X - built Apr 16 2008 13:02:40 Copyright (C) 2002-2005 RealVNC Ltd. See http://www.realvnc.com for information on VNC. Mon Oct 13 00:11:29 2008 CConn: connected to host localhost port 5901 Mon Oct 13 00:11:43 2008 main: read: Connection reset by peer (104) conor@linux:~$
Code:Oct 13 00:51:00 linux xinetd[9156]: warning: can't get client address: Transport endpoint is not connected Oct 13 00:51:00 linux xinetd[9157]: warning: can't get client address: Transport endpoint is not connected Oct 13 00:51:00 linux xinetd[9158]: warning: can't get client address: Transport endpoint is not connected Oct 13 00:51:00 linux xinetd[9159]: warning: can't get client address: Transport endpoint is not connected Oct 13 00:51:00 linux xinetd[9160]: warning: can't get client address: Transport endpoint is not connected Oct 13 00:51:00 linux xinetd[9161]: warning: can't get client address: Transport endpoint is not connected Oct 13 00:51:00 linux xinetd[9162]: warning: can't get client address: Transport endpoint is not connected Oct 13 00:51:00 linux xinetd[9163]: warning: can't get client address: Transport endpoint is not connected Oct 13 00:51:00 linux xinetd[9164]: warning: can't get client address: Transport endpoint is not connected Oct 13 00:51:00 linux xinetd[9170]: warning: can't get client address: Transport endpoint is not connected Oct 13 00:51:00 linux xinetd[6687]: Deactivating service Xvnc due to excessive incoming connections. Restarting in 10 seconds. Oct 13 00:51:10 linux xinetd[6687]: Activating service Xvnc Oct 13 00:55:39 linux xinetd[6687]: Exiting...
Last edited by conorgriffin; October 13th, 2008 at 01:08 AM.
I followed popie's instructions and it seems to work, However, when I try to connect from my laptop I get this error message from VNC viewer: "Error: couldn't find suitable pixmap format". How can I solve the problem?
I followed popie's instructions, everything went well until i rebooted and nothing had changed. I still can't vnc unless i log in the physical desktop, and then it only controls the physical desktop... Am I connecting wrong?
I really hate this side of Ubuntu.. So far i am unsuccessful at installing a vnc server.. This definitely needs to be address by the ubuntu admins in their documentation.
As far as getting the VNC server running, that is as simple as clicking in GNOME System>Preferences>Remote Desktop, then clicking Allow users to view your desktop, and Allow users to control your desktop under General Tab subsection Sharing.
Getting VNC to work independently of sessions on the physical display, is another issue, apparently.
Hello everyone, i am trying to get my laptop to run the vnc4server on Kubuntu 8.10; which as you may know uses KDE 4.1.3.
I followed the instructions exactly as described on post #458 of this thread and Im having the same type of problem as many other people have posted in this thread and in other forums:
To which my /var/log/syslog says:Code:diego@raziel:~$ vncviewer localhost:1 Connected to RFB server, using protocol version 3.8 vncviewer: read: Connection reset by peer
I made the following configurations in /etc/kde4/kdm/kdmrc:Code:Nov 11 21:09:35 raziel xinetd[15191]: warning: can't get client address: Transport endpoint is not connected
Is there anything new that i should take into account for 8.10? Did the vnc4server get any significant changes between last release and now?Code:[Xdmcp] Enable=true Port=177 Xaccess=/etc/kde4/kdm/Xaccess Willing=/etc/kde4/kdm/Xwilling
Thanks in advance.
Edit: Fixed the problem, had to edit /etc/kde4/kdm/Xaccess like this:
Now it works great! Thanks to the howto posters....Code:* #any host can get a login window * CHOOSER BROADCAST #any indirect host can get a chooser
Last edited by havok1977; November 13th, 2008 at 02:54 AM. Reason: Fixed...
Bookmarks