i'll check on the update system to be sure. i did upgrade using the fedup procedure. thought i had run yum's cleanup options to tighten things up a bit. i'll recheck though.
ok, i'll keep the current Xvnc/tigervnc server as is on that fc20 vm. i'm using on win7_64 notebook both "TigerVNC Viewer 32bit v1.3.0(20130704)" & "TigerVNC Viewer 64bit v1.3.80(20140404)". just seeing which i like better. appreciate your reply. must be an issue with this particular fc20 vm. i'll start there wb > On Sun, May 4, 2014 at 6:01 PM, mYLists <emylists...@gmail.com>wrote: > > this nightly build, i should just copy the files in the > tigervnc-Linux-x86_64-1.3.80-20140404svn5177.tar.gz over my "Xvnc > TigerVNC 1.3.0 - built Mar 19 2014 17:10:53" installed files? > I'm surprised that you're seeing this problem with fc20. Is your > system completely up to date? I thought they had integrated all of > Pierre's Fltk patches into Fedora's build of Fltk... See this > bugzilla report for details: > https://bugzilla.redhat.com/show_bug.cgi?id=920573. > To answer your question though, I think that all you need is the > vncviewer. I would not recommend overwriting anything else. The > "cross-compatible" build is really nothing more than the contents of > the EL5 rpm unpacked. Xvnc should work but, will likely have > degraded performance and possibly exhibit incompatible behavior with > newer window managers & software because it's compiled & statically > linked against much older versions of Xorg and it's supporting > libraries. Additionally, fc20 uses vastly different init scripts, > etc. that will almost certainly break. > > i ask because using yum to install the rpm didn't work for me ... > []# yum update > tigervnc-server-1.3.80-17.20140404svn5177.el6.x86_64.rpm > > Resolving Dependencies -->> Running transaction check --->> Package tigervnc-server.x86_64 0:1.3.0-14.fc20 will be updated --->> Package tigervnc-server.x86_64 0:1.3.80-17.20140404svn5177.el6 will be an update -->> Processing Dependency: libgnutls.so.26(GNUTLS_1_4)(64bit) for package: tigervnc-server-1.3.80-17.20140404svn5177.el6.x86_64 -->> Processing Dependency: libgnutls.so.26()(64bit) for package: tigervnc-server-1.3.80-17.20140404svn5177.el6.x86_64 -->> Finished Dependency Resolution > Error: Package: > tigervnc-server-1.3.80-17.20140404svn5177.el6.x86_64 > (/tigervnc-server-1.3.80-17.20140404svn5177.el6.x86_64) > Requires: libgnutls.so.26(GNUTLS_1_4)(64bit) > Error: Package: > tigervnc-server-1.3.80-17.20140404svn5177.el6.x86_64 > (/tigervnc-server-1.3.80-17.20140404svn5177.el6.x86_64) > Requires: libgnutls.so.26()(64bit) > > []# locate libgnutls.so > /usr/lib/libgnutls.so.28 > /usr/lib/libgnutls.so.28.20.4 > /usr/lib64/libgnutls.so > /usr/lib64/libgnutls.so.28 > /usr/lib64/libgnutls.so.28.20.4 > i have libgnutls.so already installed so i'm not clear on why the > "Requires: libgnutls.so.26()(64bit)" msg displays unless it has to do with a > 64bit issue? > []#uname -a > 3.12.8-300.fc20.x86_64 #1 SMP Thu Jan 16 01:07:50 UTC 2014 x86_64 x86_64 > x86_64 GNU/Linux > That's because you're trying to install an rpm built for EL6 onto > fc20. As the error message notes, the binaries are linked against > gnutls.so.26 while your system has gnutls.so.28. > -brian -- Bill Key fingerprint = DB4D 251B FE8A BDCD 2BE4 E889 13F1 78D0 A386 B32B --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce _______________________________________________ Tigervnc-users mailing list Tigervnc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-users