Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#3896 - latest tightvnc does no longer work

Attached to Project: Arch Linux
Opened by Nikos Kouremenos (zeppelin) - Friday, 03 February 2006, 22:03 GMT
Last edited by Jason Chu (jason) - Thursday, 23 February 2006, 08:43 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To dorphell (dorphell)
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7.1 Noodle
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

vncserver
vncserver: couldn't find "Xvnc" on your PATH.

it worked with same pkgs ok before. also I coudln't find which pkg shipds this Xvnc bin
This task depends upon

Closed by  dorphell (dorphell)
Thursday, 23 February 2006, 22:22 GMT
Reason for closing:  Fixed
Additional comments about closing:  blah blah
Comment by Paul Mattal (paul) - Thursday, 09 February 2006, 15:52 GMT
I recently had trouble with tightvnc-1.2.9-2 in testing (running testing xorg). It was looking for the fonts in the old place.

Figured I'd put that in here, too, before assigning it!
Comment by Nikos Kouremenos (zeppelin) - Monday, 20 February 2006, 19:41 GMT
-1 shipped Xvnc -2 doesn't! please this is major (aka does not work)
Comment by Jason Chu (jason) - Thursday, 23 February 2006, 08:42 GMT
I was able to compile tightvnc version 1.3dev7 and have an Xvnc binary, but it was still looking in the wrong place for fonts.
Comment by Nikos Kouremenos (zeppelin) - Thursday, 23 February 2006, 14:38 GMT
Jason, the wrong place for fonts is al problem or upstream?
Comment by Jason Chu (jason) - Thursday, 23 February 2006, 15:39 GMT
Either way, it's something that needs to be fixed in the package.
Comment by Nikos Kouremenos (zeppelin) - Thursday, 23 February 2006, 15:43 GMT
of course :) I'm just curious how this go to extra without being fixed
Comment by dorphell (dorphell) - Thursday, 23 February 2006, 16:05 GMT
I'll take a look -- hopefully it's just a hardcoded fontpth that's /usr/X11R6/... that has to be changed.
Comment by Tom Killian (tomk) - Thursday, 23 February 2006, 19:48 GMT
The font path is not the problem. I've built and installed 1.3dev7 as well, and I just needed to change the font path, and optionally the rgb path, in vncserver. The missing Xvnc binary in 1.2.9 is the bogie here - presumably we won't be putting the dev version in the repos.
Comment by Nikos Kouremenos (zeppelin) - Thursday, 23 February 2006, 20:47 GMT
if the PKGBUILD maintainer dindn't do anything special, my guess goes with makepkg stripping docs or whatever?
Comment by dorphell (dorphell) - Thursday, 23 February 2006, 21:04 GMT
1.2.9-3 is up -- it now builds with Xvnc but has a not-so-pretty workaround for their (tightvnc devs) ugly X11R6 hardcoded paths all over the place.

-d
Comment by dorphell (dorphell) - Thursday, 23 February 2006, 21:33 GMT
zeppelin..

The Xvnc bin missing was not due to the Xorg upgrade, it was due to one of the recent gcc upgrades. GCC becomes less and less tolerable of ugly/abused code as it matures and tightvnc is the perfect target as it's pretty messy code. I patched it so it compiles without error (everything builds properly) but I won't be surprised if it breaks again with later GCC releases.

That said, the font issue *was* a result of the Xorg7 upgrade and the workaround was just a mod to the vncserver script.
Comment by Tom Killian (tomk) - Thursday, 23 February 2006, 21:34 GMT
Yeah, that's it - thanks dorphell. :) Who needs pretty anyway, as long as it works?
Comment by Nikos Kouremenos (zeppelin) - Thursday, 23 February 2006, 21:45 GMT
dorphell, congrats


tom, please do not say those words as they make me jump out of the window

Loading...