For the missing includefiles error: you hit the bug where pacman loses track of moved files and deletes them. Reinstall xproto to get these back (I guess xproto is not the only proto package missing on your system)

Thanks for the suggestion, Jan. You're correct - apparently I needed to reinstall xproto (as well as libxmu, libxaw, and xextproto), but after I did that I'm now able to build the tightvnc package.

That said, however, my re-built package just confirms this bug: tightvnc (or at least the Xvnc inside of it) is still broken.

darose.. I re-opened this but don't know what to tell you.. I can't reproduce it on my end, so.. give me more information.

Anybody else having this problem?

Thanks for re-opening this. I'll fill in the details as best I can, but I don't have a lot of information as to what's wrong.

* I run Xvnc via xinetd
* I added a vncserver file to the /etc/xinetd.d/ directory (attached below)
* I added the services mentioned in the /etc/xinetd.d/vncserver file into /etc/services (attached below)
* I start the xinetd service
* I verify that xinetd is listening on ports 5950 through 5953 (see output below)
* I use either the RealVNC or TightVNC clients on a windows machine to try to connect to my server. I don't get a "connection failed" message, so I know that it's able to connect, but then the client terminates and the VNC windows never opens

I'm experiencing this behavior on 2 different machines.

This configuration had been working fine for many months but, as of recently, no longer works.

Unfortunately, I don't have any other output available about what's going wrong. Xvnc does not appear to produce a log file of any type.

Any idea what's wrong?

Thanks!

---

/etc/xinetd.d/vncserver
=======================
service vnc-640x480x8
{
protocol = tcp
socket_type = stream
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -once -geometry 640x480 -depth 8
# disable = yes
}

service vnc-800x600x8
{
protocol = tcp
socket_type = stream
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -once -geometry 800x600 -depth 8
# disable = yes
}

service vnc-800x600x16
{
protocol = tcp
socket_type = stream
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -once -geometry 800x600 -depth 16
# disable = yes
}

service vnc-1024x768x16
{
protocol = tcp
socket_type = stream
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -once -geometry 1024x768 -depth 16
# disable = yes
}

---

end portion of /etc/services
============================
vnc-640x480x8 5950/tcp
vnc-800x600x8 5951/tcp
vnc-800x600x16 5952/tcp
vnc-1024x768x16 5953/tcp

---

portion of output of sudo netstat -nap
======================================
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program
tcp 0 0 0.0.0.0:5952 0.0.0.0:* LISTEN 18897/xinetd
tcp 0 0 0.0.0.0:5953 0.0.0.0:* LISTEN 18897/xinetd
tcp 0 0 0.0.0.0:5950 0.0.0.0:* LISTEN 18897/xinetd
tcp 0 0 0.0.0.0:5951 0.0.0.0:* LISTEN 18897/xinetd

Sorry - forgot to mention:

When I wrote "I use either the RealVNC or TightVNC clients on a windows machine to try to connect to my server", I do this by telling the VNC client to open a connection to "darsys6:53"

Hmmm ... perhaps the problem here is more of that pacman bug. I took a look and saw that a bunch of key files were missing from my /etc/X11/xdm directory - such as Xaccess. I did a reinstall of the xorg-xdm package (as well as xproto, libxmu, libxaw, and xextproto) and they magically re-appeared. (Man, that pacman bug is NASTY! Really messed things up bad with this xorg upgrade!)

Unfortunately VNC is still broken, but I bet there's some other packages like this that need to be reinstalled that are giving me grief here. If you've got any suggestions, please send them along.

does it log anything ? if so please add them to the bug.

Not that I could see. I looked in daemon.log, kernel.log, everything.log, but there didn't appear to be anything relevant. And Xvnc doesn't seem to log to anything itself.

I'm really surprised that no one is able to recreate this. Like I mentioned earlier, I've experienced this problem on 2 different boxes.

I'm happy to assist with debugging this, if someone can provide some direction on how I might go about it. Feel free to email me.

Whoops - almost forgot! This is the output I get when I try to connect:

[darose@davidrlin ~]$ vncviewer $darsys6:53

VNC Viewer Free Edition 4.1.2 for X - built May 19 2006 20:31:34
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.

Thu Jun 22 09:34:26 2006
CConn: connected to host 10.1.0.1 port 5953

Thu Jun 22 09:34:27 2006
main: End of stream

status?