Ubuntu
vnc4 package

vnc X extension module needs to be named libvnc.so

Bug #4498 reported by Andrew Jorgensen
14
Affects Status Importance Assigned to Milestone
vnc4 (Ubuntu)
Fix Released
Medium
Matthias Klose

Bug Description

The vnc4server package includes an Xserver extension /usr/X11R6/lib/modules/extensions/vnc.so which is used to provide VNC access directly into the running server. To be loaded into an Xorg server it needs to be named libvnc.so. It works fine if I create a symlink for it.

Daniel Holbach (dholbach)
Changed in vnc4:
assignee: nobody → motu
Matthias Klose (doko)
Changed in vnc4:
assignee: motu → doko
Revision history for this message
Barry deFreese (bddebian) wrote :

This is moderately in progress. I have requested a UVF exception to sync the latest package from Debian. Thanks for your report.

Changed in vnc4:
status: Unconfirmed → Confirmed
Revision history for this message
Matthias Klose (doko) wrote : Re: [Bug 4498] Re: vnc X extension module needs to be named libvnc.so

Barry deFreese schrieb:
> This is moderately in progress. I have requested a UVF exception to sync
> the latest package from Debian. Thanks for your report.

not sure if we do want that, the code is still based on xfree86 ...

Revision history for this message
Andrew Jorgensen (ajorg) wrote :

> not sure if we do want that, the code is still based on xfree86 ...

As the moment this package is uninstallable in dapper:

The following packages have unmet dependencies.
  vnc4server: Depends: xserver-common but it is not installable
E: Broken packages

Revision history for this message
Andrew Jorgensen (ajorg) wrote :

This appears to have been fixed in Dapper.

Changed in vnc4:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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