Package Details: turbovnc 2.2.6-1

Git Clone URL: https://aur.archlinux.org/turbovnc.git (read-only, click to copy)
Package Base: turbovnc
Description: An optimized version of TightVNC
Upstream URL: http://www.turbovnc.org/
Licenses: GPL
Conflicts: tigervnc, tigervnc-svn, tightvnc, turbovnc-bin
Replaces: turbovnc-bin
Submitter: kfgz
Maintainer: hcartiaux (mrmangosir)
Last Packager: hcartiaux
Votes: 27
Popularity: 0.009638
First Submitted: 2013-06-03 18:29
Last Updated: 2021-02-24 16:39

Dependencies (9)

Required by (0)

Sources (2)

Latest Comments

1 2 3 4 Next › Last »

patryk commented on 2020-12-21 10:28

I have had a problem with compilation because of jre14. Currently working solution is the installation of jdk13-openj9-bin and execute command archlinux-java set java-13-j9. When you force compilation with jre14 by hand then vncviewer generate many error logs.

AsmundEr commented on 2020-04-10 20:27

I can't get the Sourceforge download to work correctly anymore. Maybe they changed something?

But the project also hosts releases on Github, so perhaps it's better to get the tarball from there? Current one:

https://github.com/TurboVNC/turbovnc/archive/2.2.4.tar.gz

Edit: strangely enough, I encounter this problem only on one machine. Maybe our corporate domain blocks Sourceforge or something like this.

Markus00000 commented on 2019-06-25 15:12

If you get this error:

CMake Error at /usr/share/cmake-3.14/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
  Could NOT find Java (missing: Java_JAR_EXECUTABLE Java_JAVAC_EXECUTABLE
  Java_JAVAH_EXECUTABLE Java_JAVADOC_EXECUTABLE) (found version "1.8.0_222")
Call Stack (most recent call first):
  /usr/share/cmake-3.14/Modules/FindPackageHandleStandardArgs.cmake:378 (_FPHSA_FAILURE_MESSAGE)
  /usr/share/cmake-3.14/Modules/FindJava.cmake:332 (find_package_handle_standard_args)
  java/CMakeLists.txt:1 (find_package)

Check the default Java environment:

$ archlinux-java status

Then set it to a compatible one:

# archlinux-java set java-13-openjdk

hcartiaux commented on 2019-04-22 13:23

Both packages provide the same command /bin/vncviewer and /bin/vncserver ?

ozz commented on 2019-04-22 13:19

Then, test and send a patch

I was planning to but I'm asking WHY it's marked as conflicting. Is there a problem or unknown? Thanks

hcartiaux commented on 2019-04-22 12:19

@newbthenewbd Done, with the downside that we now depend indirectly on the JDK

hcartiaux commented on 2019-04-22 12:04

I'd like to be able to have both available like they are on other distros (eg. Ubuntu).

Then, test and send a patch

d.sa commented on 2019-04-21 11:01

FYI I hit this error.

CMake Error at /usr/share/cmake-3.14/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
  Could NOT find Java (missing: Java_JAR_EXECUTABLE Java_JAVAC_EXECUTABLE
  Java_JAVAH_EXECUTABLE Java_JAVADOC_EXECUTABLE) (found version "1.8.0_212")
Call Stack (most recent call first):
  /usr/share/cmake-3.14/Modules/FindPackageHandleStandardArgs.cmake:378 (_FPHSA_FAILURE_MESSAGE)
  /usr/share/cmake-3.14/Modules/FindJava.cmake:332 (find_package_handle_standard_args)
  java/CMakeLists.txt:1 (find_package)

ozz commented on 2019-04-13 22:13

Why does this conflict with TigerVNC? I'd like to be able to have both available like they are on other distros (eg. Ubuntu).

newbthenewbd commented on 2019-04-09 21:36

The jdk-openjdk requirement actually forces the usage of Java 11 to compile turbovnc. As far as I'm aware, to properly relax that requirement, java-environment should be made a dependency, instead.

If turbovnc does not work with Java 7 and older, the java-runtime and java-environment dependencies could also be changed into java-runtime>=8 and java-environment>=8, respectively.

Thanks for the hard work maintaining the package!