harvest-dev team mailing list archive

[William Loucks <biloucks@xxxxxxx>]

** Tags added: vnc4 vnc4server

-- 
vnc4: vnc4server: libvnc.so crashes Xorg 1.4 on remote keypress or mouseclick
https://bugs.launchpad.net/bugs/247623
You received this bug notification because you are a member of harvest-
dev, which is the registrant for harvest.

Status in Harvest Service: New

Bug description:
Using the libvnc.so module in Xorg 1.4.

On first keypress or mouseclick by vnc client, Xorg log on vnc server side shows:

Backtrace:
0: /usr/bin/X11/X(xf86SigHandler+0x6a) [0x483d5a]
1: /lib/libc.so.6 [0x2aeb4a768100]
2: /usr/lib/xorg/modules/extensions//libvnc.so(_ZN14XserverDesktop8keyEventEjb+0x8b) [0x2aeb4cd1838b]
3: /usr/lib/xorg/modules/extensions//libvnc.so(_ZN3rfb16VNCSConnectionST8keyEventEjb+0x103) [0x2aeb4cd2f213]
4: /usr/lib/xorg/modules/extensions//libvnc.so(_ZN3rfb16VNCSConnectionST15processMessagesEv+0x30) [0x2aeb4cd2f300]
5: /usr/lib/xorg/modules/extensions//libvnc.so(_ZN14XserverDesktop13wakeupHandlerEP6fd_seti+0xf6) [0x2aeb4cd17c06]
6: /usr/lib/xorg/modules/extensions//libvnc.so [0x2aeb4cd0fdd9]
7: /usr/bin/X11/X(WakeupHandler+0x4e) [0x4526ee]
8: /usr/bin/X11/X(WaitForSomething+0x204) [0x560e04]
9: /usr/bin/X11/X(Dispatch+0x9a) [0x44e8aa]
10: /usr/bin/X11/X(main+0x47d) [0x436c1d]
11: /lib/libc.so.6(__libc_start_main+0xf4) [0x2aeb4a7541c4]
12: /usr/bin/X11/X(FontFileCompleteXLFD+0x279) [0x435f59]

Fatal server error:
Caught signal 11. Server aborting

>From the Debian bug 444697, there apparently is an ABI change in Xorg 1.4 that breaks this. The xorg-xerver bits in this package are too old (1.0.2) to work with 1.4.1 that is in the Hardy xserver-xorg-core package now.

Be advised that Debian bug 444697 "fixes" this bug by REMOVING libvnc.so. Quote:
"Removed libvnc.so that do not work with recent xorg. This is a workaround but solves the grave fault, closes: #444697."

This tacitly suggests that Xorg does not support libvnc.so at this time.
In any case bug 444697 does not solve the problem.
Debian merely removed the feature that fails and closes the bug. It is terribly irresponsible to close the bug after removing the feature that causes the bug from a project management standpoint--the non-working libvnc.so is now orphaned and completely untracked (there is no bug I can find that tracks non-working libvnc.so). The closing of this bug implies it to be fixed when it was not.