After some recent package upgrades (gcc? xorg? the kernel?) the tight vnc package on my machine no longer appears to be working. Xvnc appears to not be able to start, with the only evidence being the following line in my logs:

kdm[20631]: Unknown session exit code 0 (sig 11) from manager process


FYI - I'm using the following configuration in xinet.d to lauch vnc:

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
}

The whole setup (i.e., KDM with XDMCP + xinetd + Xvnc) was working up until very recently (I probably last tried it a couple of weeks ago) and I haven't made any changes in the configuration for months - maybe even over a year - so I don't think the problem is something that changed on my end.


I also tried building the tightvnc package myself from scratch via ABS, but that also didn't work. It initially looked like the package was getting built fine. But after I changed all the "make" lines to "make || return 1" I saw that there's error messages that's causing the Xvnc portion of the build to fail:

...
fserve.c:455: error: 'fd_set' has no member named 'fds_bits'
...
WaitFor.c: In function 'WaitForSomething':
WaitFor.c:174: error: 'fd_set' has no member named 'fds_bits'
...


Any idea what the problem might be and/or how to fix it? I realize that this package hasn't been upgraded in a couple of years (!), so it's entirely possible that it hasn't been buildable for some time now. However, this is the first that I'm seeing the existing built package be broken. I unfortunately have a need for tightvnc since 1) the other vnc package (real vnc) doesn't include Xvnc, and 2) I'm unable to use NX here since I don't have admin rights to install the client on my Windows box.

Thanks,

DR