Package Details: realvnc-vnc-viewer 7.13.0-1

Git Clone URL: https://aur.archlinux.org/realvnc-vnc-viewer.git (read-only, click to copy)
Package Base: realvnc-vnc-viewer
Description: VNC remote desktop client software by RealVNC
Upstream URL: https://www.realvnc.com/
Keywords: realvnc viewer vnc
Licenses: custom
Conflicts: tigervnc, tightvnc, turbovnc
Submitter: ava1ar
Maintainer: Kewl
Last Packager: Kewl
Votes: 58
Popularity: 0.085768
First Submitted: 2017-09-11 23:40 (UTC)
Last Updated: 2024-11-21 16:11 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

SergeantSagara commented on 2022-03-02 19:08 (UTC)

Ah, thanks. Maybe libxcrypt-compat should be made a dependency of realvnc-vnc-viewer now?

xujiyong commented on 2022-03-02 07:55 (UTC)

That's because the libxcrypt-compat is in core packages now.

https://archlinux.org/packages/core/x86_64/libxcrypt-compat/

Install it with the pacman, everything will be back to normal.

SergeantSagara commented on 2022-03-02 07:23 (UTC)

Maybe as a workaround, the PKGBUILD can just patch the vncviewer binary (where patchelf becomes a build dependency)? It's not a great solution (because compatibility is a thing with shared objects), but it's a nice workaround for out-of-the-box support till RealVNC offers builds against newer libcrypt. Looks like libxcrypt-compat is no longer available on the AUR.

https://aur.archlinux.org/packages/libxcrypt-compat -> returns 404.

SergeantSagara commented on 2022-03-02 07:10 (UTC)

This is what I am doing as a workaround. I think patchelf is a better solution than creating a symlink just because the symlink suggests that libcrypt.so.1 is actually available (when it isn't/falsely pointing to libcrypt.so.2.0.0).

sudo patchelf --replace-needed libcrypt.so.1 libcrypt.so.2 /usr/bin/vncviewer

Kewl commented on 2022-02-15 14:33 (UTC)

One can also install libxcrypt-compatin the meantime, I am looking for the best solution before amending the package.

zeroconf commented on 2022-02-15 03:33 (UTC) (edited on 2022-02-15 03:34 (UTC) by zeroconf)

With realvnc-vnc-viewer 6.21.1109-1 and recent updates, there will be an issue:

vncviewer 
vncviewer: error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory

Then search shows

find /usr -type f -iname "*libcrypt.so*"
/usr/lib32/libcrypt.so.2.0.0
/usr/lib/libcrypt.so.2.0.0

Solution:

sudo ln -s /usr/lib/libcrypt.so.2.0.0 /usr/lib/libcrypt.so.1

Hopefully it would be possible to update realvnc-vnc-viewer against newer library version in order to avoid such issue.

jose1711 commented on 2021-11-11 07:56 (UTC)

@allexj

isn't "i couldn't find the way to execute" and "i could open it .. searching in the apps" contradictory in fact? i do see .desktop file being included so.. are you trying to say that it did not appear in any of the app categories? what WM are you using?

allexj commented on 2021-11-11 07:43 (UTC)

I couldn't find the way to execute it. I found out that I could open it typing in terminal "vncviewer" or searching in the apps for "VNC Viewer"

BenTheTechGuy commented on 2021-02-18 22:13 (UTC) (edited on 2021-05-04 22:16 (UTC) by BenTheTechGuy)

aarch64 can be added as an architecture since RealVNC now has a build that is available in the raspbian-arm64 repos. http://archive.raspberrypi.org/debian/pool/main/r/realvnc-vnc/realvnc-vnc-viewer_6.20.530.42683_arm64.deb

Edit: Due to versioning and upstream conflicts I made my own package.

Kewl commented on 2020-12-17 22:38 (UTC)

@jose1711 binary name is an upstream choice, then this seems like a good idea you can submit to tightvncviewer and/or realvnc. If they are ok with it it's fine, if it's too complicated or causes issues from their point of view it would be good to know. Also if you have examples of official packages changing binary names, I will follow the best practices from TUs.

« First ‹ Previous 1 2 3 4 5 Next › Last »