vnc4server too slow with xinetd/gdm

Bug #227146 reported by GrantParnell
56
This bug affects 1 person
Affects Status Importance Assigned to Milestone
vnc4 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: vnc4server

Ubuntu version: Hardy
Package: vnc4server
Version: 4.1.1+xorg1.0.2-0ubuntu7
Workaround: Manually copy binaries and libraries from Fedora 8's vnc-server package (4.1.2 release 24.fc8)

/etc/services contains:-
vnc 5952/tcp # vnc

/etc/xinetd.d/vnc contains:-
service vnc
{
        socket_type = stream
        protocol = tcp
        wait = no
        user = nobody
        server = /usr/bin/Xvnc
        server_args = -inetd -query 127.0.0.1 -once -securitytypes=none -geometry 1008x700 -depth 16 -extension XFIXES
        disable = no
}

Ensure xdmcp is enabled in your gdm.conf or gdm.conf-custom
under [xdmcp] put Enable=true
then restart gdm and xinetd

client can connect with:-
vnc4viewer hostname:52

This will bring up a GDM login screen. The connection is very sluggish even when typing the username from a client machine on the same LAN or even the same host!

By copying the binaries, and dependent libraries from Fedora 8's vnc-server 4.1.2 acceptable performance is restored.
Files copied from fedora to same path in Ubuntu are:-
/usr/bin/Xvnc
/usr/bin/vncconfig
/usr/bin/vncpasswd
/usr/bin/vncserver
/usr/bin/x0vncserver
/usr/lib/xorg/modules/extensions/libvnc.so
/usr/lib/librfb.so.0
/usr/lib/librfb.so.0.0.0

Revision history for this message
GrantParnell (parngr) wrote :

I also reported this in the Ubuntu forums yesterday more as a query, but now I've proved it.

http://ubuntuforums.org/showthread.php?p=4885596

Revision history for this message
Martin Jackson (mhjacks) wrote :

I can confirm the behavior, using vnc4server and tightvnc client on Windows.

Interestingly, when I start the process as a normal user (e.g. su - mjackson -c "vncserver :2 -geometry 1280x800" the slowness doesn't seem to be an issue.

Revision history for this message
mabawsa (mabawsa) wrote :

I can confirm the behaviour and the workaround.

Revision history for this message
d-_-b (ludolph) wrote :

Workaround for people that don't have access to Fedora 8: http://ubuntuforums.org/showthread.php?p=5252422&posted=1#post5252422

Revision history for this message
Jason Merrill (jason-merrill) wrote :

This issue also affects tightvncserver. I couldn't find a new binary for 64 bit architectures, so I compiled and installed tightvnc1.2.9 from source. Unfortunately, the problem persists.

Revision history for this message
Jason Merrill (jason-merrill) wrote :

installed tightvnc1.3.9 from source, that is.

Revision history for this message
Jordan Erickson (lns) wrote :

I can confirm the Hardy packages from http://www.francescosantini.com/index.php?page=linux&lang=en fixed my issues of 'gnome-settings-daemon' constantly restarting and eventually crashing. I also marked my reported bug a duplicate of this one since similar issues were happening on both, and proposed fix on this bug also fixed my bug.

Thanks, and hope to get these packages in Hardy repos!!

- Jordan

Revision history for this message
Thomas Hotz (thotz-deactivatedaccount) wrote :

Ubuntu 8.04 LTS is EOL. Does this bug happen to supported Ubuntu versions?

Changed in vnc4 (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for vnc4 (Ubuntu) because there has been no activity for 60 days.]

Changed in vnc4 (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.