I can also confirm that the updated vnc4server has some problems - I can use the version in edgy just fine, but after trying the update, I can't log into the VNC server from my Windows machine (using UltraVNC). It asks for a password and then just dies. If I downgrade it (sudo apt-get install vnc4server/edgy), then connections work again.
The log has some entries looking like this:
Jan 28 18:55:15 fane-desktop xinetd[5388]: warning: can't get client a
ddress: Transport endpoint is not connected
Jan 28 18:55:32 fane-desktop xinetd[5404]: warning: can't get client a
ddress: Transport endpoint is not connected
Jan 28 18:56:40 fane-desktop xinetd[5476]: warning: can't get client a
ddress: Transport endpoint is not connected
I'm running vnc4server from xinetd, as the message suggests.
Wouldn't reverting the update be reasonable, seeing that it causes problems with most people?
Hi,
I can also confirm that the updated vnc4server has some problems - I can use the version in edgy just fine, but after trying the update, I can't log into the VNC server from my Windows machine (using UltraVNC). It asks for a password and then just dies. If I downgrade it (sudo apt-get install vnc4server/edgy), then connections work again.
The log has some entries looking like this:
Jan 28 18:55:15 fane-desktop xinetd[5388]: warning: can't get client a
ddress: Transport endpoint is not connected
Jan 28 18:55:32 fane-desktop xinetd[5404]: warning: can't get client a
ddress: Transport endpoint is not connected
Jan 28 18:56:40 fane-desktop xinetd[5476]: warning: can't get client a
ddress: Transport endpoint is not connected
I'm running vnc4server from xinetd, as the message suggests.
Wouldn't reverting the update be reasonable, seeing that it causes problems with most people?