both clients are Linux mint 18, Keybord Layout german... Clients are on different maschines...

I was really wondering about the "3".... umlauts and the other things ok.. but 3???


Am 09.09.2016 um 12:17 schrieb Maxim Solodovnik:
I'll check ...
What keyboard layout do you have to test [3, - # + * ' _ ;]
I'm afraid it is computer/OS/keyboard specific :((((
Key codes in particular browser/OS are being captured by Flash, then
translated into universal Java key codes, then "pressed" by java

On Fri, Sep 9, 2016 at 3:55 PM, Peter Dähn <da...@vcrp.de> wrote:

"3" , german umlauts and ", - # + * ' _ ;" doesn't work...



Am 09.09.2016 um 10:53 schrieb Maxim Solodovnik:

hmmm

by I could use all keys except 3, german umlauts and ", - # + * ' _ ;",
dot
works...
you mean only umlauts doen't work? or ", - # + * ' _ ;" also doen't work?

On Fri, Sep 9, 2016 at 3:40 PM, Peter Dähn <da...@vcrp.de> wrote:

OK.. i started to test screensharing app...
I used screensharing with remotecontrol...

Open via remote a textfield on the whitheboard... I could use all keys
except 3, german umlauts and ", - # + * ' _ ;", dot works...

Is this reproducable?


Am 09.09.2016 um 09:42 schrieb Peter Dähn:

ok.. I will test it today and vote later the day... ;-)

Am 09.09.2016 um 09:41 schrieb Maxim Solodovnik:

about 12 hours according to my records :)
If no blockers will be reported I'll finish release this weekend

On Fri, Sep 9, 2016 at 2:37 PM, Peter Dähn <da...@vcrp.de> wrote:

Hi Maxim,

I could figure it out..

My fault... After import of my backup application.base.url was
changed to
the url of my live system... I just need to change this one to the
url of
my testsystem... sorry for bothering...

How long do I have till voting ends?

Greetings Peter

Am 09.09.2016 um 09:14 schrieb Maxim Solodovnik:

Another one is DSA so everything is OK

I see no issues with your build
try to uninstall/clean javaws

javaws --uninstall
javaws --clean

(or something like this)

and run jnlp again:
javaws public_XXX.jnlp

On Fri, Sep 9, 2016 at 2:10 PM, Peter Dähn <da...@vcrp.de <mailto:
da...@vcrp.de>> wrote:

       I hope screenshots are working...

       bcprov-jdk15on-1.55.jar

       openmeetings-screenshare-3.1.3-SNAPSHOT-full.jar


       openmeetings...jar seems to have a certificate build during
       compilation...
       bcprov...jar contains only on RSA file...

       Am 09.09.2016 um 08:51 schrieb Maxim Solodovnik:

       This one is not in effect "-Dold-backups.dwnd.skip=true"

everything
else is
       correct

       can you check
       bcprov-jdk15on-1.55.jar
       openmeetings-screenshare-3.1.3-SNAPSHOT-full.jar

       both should have signature in META-INF folder
       bcprov-jdk15on-1.55.jar should have 2 RSA files in META-INF


       On Fri, Sep 9, 2016 at 1:41 PM, Peter Dähn<da...@vcrp.de>
<mailto:
da...@vcrp.de>  wrote:

       you are right...

       mvn install -Dunpacked=true -DskipTests=true
-Dold-backups.dwnd.skip=true
       -Ddb=postgresql

       What do I need to add?

       Greetings Peter



       Am 09.09.2016 um 08:36 schrieb Maxim Solodovnik:

       I guess you build everything by yourself ....

       what maven command have you used?
       On Fri, Sep 9, 2016 at 1:33 PM, Peter Dähn<da...@vcrp.de>
<mailto:
da...@vcrp.de>  wrote:

       ok... i allready thougt it is a bad idea to translate
error-messages as

       well...

       Caused by: net.sourceforge.jnlp.LaunchException: fatal:
       initialize error: During verifiing  JARs  a fatal error has
occurred. An
       exception in JarCertVerifier
       was thrown. The problem could caused while try to read
cacerts or
       trusted.certs.: error in opening zip file

       I try to have a look at the jnlp-file.


       Am 09.09.2016 um 08:24 schrieb Maxim Solodovnik:

       I'm not really understand German, but I guess german error
in your

       screen-sharing application

       states something about missing file or maybe bad signature

       additionally could you check downloaded JNLP file and
ensure
jars listed
       in
       jnlp are the same as in webapps/openmeetings/screenshare

       On Fri, Sep 9, 2016 at 1:19 PM, Peter Dähn<da...@vcrp.de>
<mailto:da...@vcrp.de>  wrote:

       Hallo Maxim,

       here it is...

       webapps/openmeetings/screenshare$ ls -l
       insgesamt 17396
       -rw-rw-r-- 1 user user  3529599 Sep  7 13:42
bcprov-jdk15on-1.55.jar
       -rw-rw-r-- 1 user user     2499 Sep  7 13:41 icon.png
       -rw-rw-r-- 1 user user 14261276 Sep  7 13:42
       openmeetings-screenshare-3.1.3
       -SNAPSHOT-full.jar
       -rw-rw-r-- 1 user user    15981 Sep  7 13:41
splashicon.png

       Does it help?

       Greetings Peter



       Am 08.09.2016 um 09:45 schrieb Peter Dähn:

       Hi Maxim,

       unfortunately today I am out of office... I will answer
you

tomorrow
       morning

       Greetings Peter

       On Wed, 7 Sep 2016 23:31:29 +0700
           Maxim Solodovnik<solomax...@gmail.com> <mailto:
solomax...@gmail.com>  wrote:

       Hello Peter,

       What is the content of your
webapps/openmeetings/screenshare

folder?
       On Wed, Sep 7, 2016 at 7:12 PM, Peter Dähn<
da...@vcrp.de>
<mailto:da...@vcrp.de>  wrote:

       Hi there,

       compilation of 3.1.3RC1 worked. *Start OM failed
needed to
change

       -XX:MaxTenuringThreshold* in red5-highperf.sh to 15.

       Start without any error. Unfortunately I can not start
       screensharing client. No way to make an exception. I
use
       openjdk version "1.8.0_91" with Mint 18 64 Bit icedtea
       throws following exception:
       net.sourceforge.jnlp.LaunchException: Fatal:
       Initialisierungsfehler: Konnte Anwendung nicht
       initialisieren. Die Anwendung war nicht
initialisiert. Um
       weitere Informationen zu erhalten kann javaws von der
       Befehlszeile aus ausgeführt werden. at

net.sourceforge.jnlp.Launcher.
createApplication(Launcher.jav
a:813)
       at

net.sourceforge.jnlp.Launcher.
launchApplication(Launcher.jav
a:532)
       at net.sourceforge.jnlp.Launcher$
       TgThread.run(Launcher.java:936) Caused by:
       net.sourceforge.jnlp.
       LaunchException: Fatal:
       Initialisierungsfehler: Während des Versuchs, JARs zu
verifizieren,
       ist ein
       fataler Fehler aufgetreten. Eine Ausnahme in der
Klasse
       JarCertVerifier
       wurde abgefangen. Die Unlesbarkeit der Dateien cacerts
oder
       trusted.certs
       könnte eine Ursache dieser Ausnahmen sein.: error in
opening
zip
       file
              at net.sourceforge.jnlp.runtime.J
       NLPClassLoader.initializeResou
       rces(JNLPClassLoader.java:671)
              at net.sourceforge.jnlp.runtime.J
       NLPClassLoader.<init>(JNLPClas
       sLoader.java:285)
              at net.sourceforge.jnlp.runtime.J
       NLPClassLoader.createInstance(
       JNLPClassLoader.java:357)
              at net.sourceforge.jnlp.runtime.J
       NLPClassLoader.getInstance(JNL
       PClassLoader.java:429)
              at net.sourceforge.jnlp.runtime.J
       NLPClassLoader.getInstance(JNL
       PClassLoader.java:403)
              at

net.sourceforge.jnlp.Launcher.
createApplication(Launcher.jav
a:805)
              ... 2 more

       I made a 2nd try with oracle java version "1.8.0_101"

       java.lang.NullPointerException
              at

com.sun.deploy.security.CPCall
backHandler.getAllPCodeSources
       (Unknown
       Source)
              at com.sun.deploy.security.CPCall
       backHandler.access$700(Unknown
       Source)
              at
       com.sun.deploy.security.CPCal
lbackHandler$ParentCallback.
       strategy(Unknown

       Source)
              at

com.sun.deploy.security.CPCall
backHandler$ParentCallback.ope
       nClassPathElement(Unknown

       Source)
              at

com.sun.deploy.security.Deploy
URLClassPath$JarLoader.getJarF
       ile(Unknown
       Source)
              at

com.sun.deploy.security.Deploy
URLClassPath$JarLoader.access$
       800(Unknown
       Source)
              at

com.sun.deploy.security.DeployURLClassPath$JarLoader$1.run(
Unknown
       Source)
              at
java.security.AccessController.doPrivileged(Native
Method)
              at

com.sun.deploy.security.Deploy
URLClassPath$JarLoader.ensureO
       pen(Unknown
       Source)
              at

com.sun.deploy.security.Deploy
URLClassPath$JarLoader.<init>(
Unknown
       Source)
              at com.sun.deploy.security.Deploy
URLClassPath$3.run(Unknown
       Source)
              at
java.security.AccessController.doPrivileged(Native
Method)
              at com.sun.deploy.security.Deploy
       URLClassPath.getLoader(Unknown
       Source)
              at com.sun.deploy.security.Deploy
       URLClassPath.getLoader(Unknown
       Source)
              at com.sun.deploy.security.Deploy
URLClassPath.getResource(
       Unknown
       Source)
              at java.net.URLClassLoader$1.run(
URLClassLoader.java:365)
              at java.net.URLClassLoader$1.run(
URLClassLoader.java:362)
              at
java.security.AccessController.doPrivileged(Native
Method)
              at java.net.URLClassLoader.findCl
ass(URLClassLoader.java:361)
              at com.sun.jnlp.JNLPClassLoader.f
indClass(Unknown
Source)
              at java.lang.ClassLoader.loadClas
s(ClassLoader.java:424)
              at com.sun.jnlp.JNLPClassLoader.l
oadClass(Unknown
Source)
              at java.lang.ClassLoader.loadClas
s(ClassLoader.java:411)
              at com.sun.jnlp.JNLPClassLoader.l
oadClass(Unknown
Source)
              at java.lang.ClassLoader.loadClas
s(ClassLoader.java:357)
              at com.sun.javaws.Launcher.doLaunchApp(Unknown
Source)
              at com.sun.javaws.Launcher.run(Unknown Source)
              at java.lang.Thread.run(Thread.java:745)


       Does it work for others?

       Greetings Peter



       Am 07.09.2016 um 12:21 schrieb 小野圭二:

       +1

       2016-09-07 19:09 GMT+09:00 Alvaro<zurca...@gmail.com>
<mailto:zurca...@gmail.com>:

       +1

       ------------

       El mié, 07-09-2016 a las 00:20 +0700, Maxim
Solodovnik

escribió:

       Dear OpenMeetings Community,

       I would like to start a vote about releasing Apache
OpenMeetings

       3.1.3

       RC1

       Main changes are:

       Service release 3 for 3.1.0, provides security

improvements:

       * Both native and tunneled RTMPS works as expected

       Please NOTE java8 is required starting from this
version

       Please update to this release from any previous
OpenMeetings
       release

       Other fixes in localization, backup/restore,
invitations
etc.


       Readme:https://svn.apache.org/repos/a
       sf/openmeetings/application/

       tags/3.1.3RC1/README

       Changelog:https://svn.apache.org/repos/a

       sf/openmeetings/application/

       tags/3.1.3RC1/CHANGELOG

       List of fixed issues:

       https://issues.apache.org/jir

a/secure/ReleaseNote.jspa

<https://issues.apache.org/jira/secure/ReleaseNote.jspa>?

       projectId=12312720&version=12337950

       Release artifacts:
       https://dist.apache.org/repos/

dist/dev/openmeetings/3.1.3/rc1/
       <https://dist.apache.org/repos
/dist/dev/openmeetings/3.1.3/rc1/>

       Maven Staged repo:

https://repository.apache.org/
service/local/repositories/
       <https://repository.apache.org
/service/local/repositories/>

       orgapacheopenmeetings-1004/content/

       Tag:https://svn.apache.org/rep
os/asf/openmeetings/application/
       <https://svn.apache.org/repos/
asf/openmeetings/application/>

       tags/3.1.3RC1/

       PGP release keys (signed using

       C467526E):https://dist.apache.org/repos/dist/dev/

       <https://dist.apache.org/repos/dist/dev/>

       openmeetings/3.1.3/rc1/KEYS

       Vote will be open for 72 hours.

       [ ] +1  approve

       [ ] +0  no opinion

       [ ] -1  disapprove (and reason why)

       My vote is +1.






       --

       WBR

       Maxim aka solomax
--

WBR Maxim aka solomax

Reply via email to