Hi Giuseppe,
thank you for testing and giving your prompt reply.
I saw the same problem with jurt.jar like you now encountered with
jdom1.jar. I am afraid you have to open a bug against the appropriate
package.
Regarding tighvnc-java, it still will take me some time to get the new
package versio
Hello Sven,
Il giorno lun, 12/10/2020 alle 23.09 +0200, Sven Geuer ha scritto:
> Hello Guiseppe,
>
> I believe I solved the issue. I'll send you another unreleased version
> of tighvnc-java in a separate email for you to test it.
Indeed the problem seems to be solved, in fact, now a different
pr
Hello Guiseppe,
I believe I solved the issue. I'll send you another unreleased version
of tighvnc-java in a separate email for you to test it.
Sven
Am Mittwoch, den 07.10.2020, 07:52 +0200 schrieb Giuseppe Sacco:
> Hello Sven,
>
> Il giorno sab, 03/10/2020 alle 18.39 +0200, Sven Geuer ha scritt
Hello Sven,
Il giorno sab, 03/10/2020 alle 18.39 +0200, Sven Geuer ha scritto:
> Hello Guiseppe,
[...]
> As I don't possess any specific java knowledge I cannot judge whether
> this will fix the issue you reported. I will send you the deb file
> attached to a separate email and would like to ask y
Hello Guiseppe,
I am currently adopting the package and have a working unreleased
version of tightvnc-jave available, which was built applying openjdk-
11.
As I don't possess any specific java knowledge I cannot judge whether
this will fix the issue you reported. I will send you the deb file
atta
Package: tightvnc-java
Version: 1.2.7-9
Severity: important
Dear Maintainer,
the package seems to be incorrect for recent JDKs.
Here is an example of running a different program that uses the new
modules architecture. While scanning the java directory I get this
error message, and my application
6 matches
Mail list logo
