From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] TurboVNC is missing a jar file
Date: Sat, 30 Apr 2022 04:13:50 +0200 [thread overview]
Message-ID: <20220430021350.DgxcL_C0UI-IPN6gt3jfYSOUBXHHFJC040_3V_NoKSA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21066@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2332 bytes --]
Closed issue by Ypnose on void-packages repository
https://github.com/void-linux/void-packages/issues/21066
Description:
### System
* xuname:
`Void 5.4.24_1 x86_64 GenuineIntel notuptodate rDF`
* package:
```
$ xbps-query turbovnc
architecture: x86_64
conf_files:
/etc/turbovncserver-security.conf
/etc/turbovncserver.conf
conflicts:
tigervnc>=0
filename-sha256: ad87962defd010aee7b92f01722fc2fd0b1e424600cce4e7cde06a507411bcd7
filename-size: 2252KB
homepage: http://virtualgl.org
install-date: 2020-04-17 10:17 CEST
installed_size: 5383KB
license: GPL-2.0-or-later
maintainer: Orphaned <orphan@voidlinux.org>
metafile-sha256: bf59a0f05313474f03d4cb49afeb941a0f2091799991308e4b92334637763d84
pkgname: turbovnc
pkgver: turbovnc-2.2.4_1
repository: https://alpha.de.repo.voidlinux.org/current
run_depends:
perl>=0
libX11>=1.2_1
glibc>=2.29_1
freetype>=2.3.9_1
libjpeg-turbo>=1.3.0_2
zlib>=1.2.3_1
bzip2>=1.0.5_1
pam-libs>=1.1.6_3
libXext>=1.0.5_1
shlib-requires:
libX11.so.6
libc.so.6
libfreetype.so.6
libturbojpeg.so.0
libz.so.1
libbz2.so.1
libm.so.6
libpthread.so.0
libpam.so.0
libXext.so.6
libdl.so.2
short_desc: Optimized version of TightVNC VNC client
source-revisions: turbovnc:7500e76ad4
state: installed
```
### Expected behavior
`vncviewer` shows remote desktop.
### Actual behavior
```
$ vncviewer 127.0.0.1:0:
libjawt.so path: /usr/lib/jvm/java-1.8-openjdk/jre/lib/amd64
Error: Unable to access jarfile /VncViewer.jar
$ ls /usr/lib/jvm/java-1.8-openjdk/jre/lib/amd64
jli/ libawt_headless.so* libfreetype.so.6* libj2pcsc.so* libjava_crw_demo.so* libjsdt.so* liblcms.so* libnio.so* libsplashscreen.so* libzip.so*
jvm.cfg libawt_xawt.so* libhprof.so* libj2pkcs11.so* libjawt.so* libjsig.so* libmanagement.so* libnpt.so* libsunec.so* server/
libattach.so* libdt_socket.so* libinstrument.so* libjaas_unix.so* libjdwp.so* libjsound.so* libmlib_image.so* libsaproc.so* libunpack.so*
libawt.so* libfontmanager.so* libj2gss.so* libjava.so* libjpeg.so* libjsoundalsa.so* libnet.so* libsctp.so* libverify.so*
```
### Steps to reproduce the behavior
Run `vncviewer 127.0.0.1:0:`
prev parent reply other threads:[~2022-04-30 2:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 8:24 [ISSUE] " Ypnose
2021-06-01 4:27 ` masato9000
2022-04-16 2:02 ` github-actions
2022-04-30 2:13 ` github-actions [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220430021350.DgxcL_C0UI-IPN6gt3jfYSOUBXHHFJC040_3V_NoKSA@z \
--to=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).