[jira] [Commented] (OPENMEETINGS-2782) Add blur background filter options on video sharing - AI-ML
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17812959#comment-17812959 ] Sebastian Wagner commented on OPENMEETINGS-2782: Maybe, I'm not sure. Does this method provide different levels of blur and also ability to set a custom background image? Is this relying on server side rendering/CPU power or is it completely client side? Does it just detect faces or the entire body, whats the actual algorithm to detect face/body ? Maybe something the student/project can include in some investigation when doing this project and compare this with tensorflow. > Add blur background filter options on video sharing - AI-ML > --- > > Key: OPENMEETINGS-2782 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2782 > Project: Openmeetings > Issue Type: New Feature > Components: Audio/Video >Reporter: Sebastian Wagner >Priority: Major > Labels: gsoc, gsoc2024, mentor > > OpenMeetings uses webRTC and HTML5 video to share audio video. Purely browser > based. > One feature missing is the ability to blur your webcam's camera background. > There are multiple ways to achieve it, Google Meet seems to use: > [https://www.tensorflow.org/] > Tensorflow are AI/ML models, they provide precompiled models into JS, for > detection of face/body it seems: > [https://github.com/tensorflow/tfjs-models/tree/master/body-segmentation] is > the best model. > Since Chrome 14 there is also a Background Blur API (relying on operating > system APIs): [https://developer.chrome.com/blog/background-blur] - but that > doesn't seem to be widely or reliable supported by operating systems yet. > The project would be about adding the background blur into a simple demo and > then integrate into the OpenMeetings project. Additionally other types of > backgrounds can be added. > Tensorflow TFJS is under the Apache 2.0 License (See > [LICENSE|https://github.com/tensorflow/tfjs-models/blob/master/LICENSE]) and > should be possible to redistribute with Apache OpenMeetings. > Other live demos and examples: > https://blog.francium.tech/edit-live-video-background-with-webrtc-and-tensorflow-js-c67f92307ac5 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OPENMEETINGS-2782) Add blur background filter options on video sharing - AI-ML
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner updated OPENMEETINGS-2782: --- Description: OpenMeetings uses webRTC and HTML5 video to share audio video. Purely browser based. One feature missing is the ability to blur your webcam's camera background. There are multiple ways to achieve it, Google Meet seems to use: [https://www.tensorflow.org/] Tensorflow are AI/ML models, they provide precompiled models into JS, for detection of face/body it seems: [https://github.com/tensorflow/tfjs-models/tree/master/body-segmentation] is the best model. Since Chrome 14 there is also a Background Blur API (relying on operating system APIs): [https://developer.chrome.com/blog/background-blur] - but that doesn't seem to be widely or reliable supported by operating systems yet. The project would be about adding the background blur into a simple demo and then integrate into the OpenMeetings project. Additionally other types of backgrounds can be added. Tensorflow TFJS is under the Apache 2.0 License (See [LICENSE|https://github.com/tensorflow/tfjs-models/blob/master/LICENSE]) and should be possible to redistribute with Apache OpenMeetings. Other live demos and examples: https://blog.francium.tech/edit-live-video-background-with-webrtc-and-tensorflow-js-c67f92307ac5 was: OpenMeetings uses webRTC and HTML5 video to share audio video. Purely browser based. One feature missing is the ability to blur your webcam's camera background. There are multiple ways to achieve it, Google Meet seems to use: [https://www.tensorflow.org/] Tensorflow are AI/ML models, they provide precompiled models into JS, for detection of face/body it seems: [https://github.com/tensorflow/tfjs-models/tree/master/body-segmentation] is the best model. Since Chrome 14 there is also a Background Blur API (relying on operating system APIs): [https://developer.chrome.com/blog/background-blur] - but that doesn't seem to be widely or reliable supported by operating systems yet. The project would be about adding the background blur into a simple demo and then integrate into the OpenMeetings project. Additionally other types of backgrounds can be added > Add blur background filter options on video sharing - AI-ML > --- > > Key: OPENMEETINGS-2782 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2782 > Project: Openmeetings > Issue Type: New Feature > Components: Audio/Video >Reporter: Sebastian Wagner >Priority: Major > Labels: gsoc, gsoc2024, mentor > > OpenMeetings uses webRTC and HTML5 video to share audio video. Purely browser > based. > One feature missing is the ability to blur your webcam's camera background. > There are multiple ways to achieve it, Google Meet seems to use: > [https://www.tensorflow.org/] > Tensorflow are AI/ML models, they provide precompiled models into JS, for > detection of face/body it seems: > [https://github.com/tensorflow/tfjs-models/tree/master/body-segmentation] is > the best model. > Since Chrome 14 there is also a Background Blur API (relying on operating > system APIs): [https://developer.chrome.com/blog/background-blur] - but that > doesn't seem to be widely or reliable supported by operating systems yet. > The project would be about adding the background blur into a simple demo and > then integrate into the OpenMeetings project. Additionally other types of > backgrounds can be added. > Tensorflow TFJS is under the Apache 2.0 License (See > [LICENSE|https://github.com/tensorflow/tfjs-models/blob/master/LICENSE]) and > should be possible to redistribute with Apache OpenMeetings. > Other live demos and examples: > https://blog.francium.tech/edit-live-video-background-with-webrtc-and-tensorflow-js-c67f92307ac5 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OPENMEETINGS-2782) Add blur background filter options on video sharing - AI-ML
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner reassigned OPENMEETINGS-2782: -- Assignee: (was: Maxim Solodovnik) > Add blur background filter options on video sharing - AI-ML > --- > > Key: OPENMEETINGS-2782 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2782 > Project: Openmeetings > Issue Type: New Feature > Components: Audio/Video >Reporter: Sebastian Wagner >Priority: Major > Labels: gsoc, gsoc2024, mentor > > OpenMeetings uses webRTC and HTML5 video to share audio video. Purely browser > based. > One feature missing is the ability to blur your webcam's camera background. > There are multiple ways to achieve it, Google Meet seems to use: > [https://www.tensorflow.org/] > Tensorflow are AI/ML models, they provide precompiled models into JS, for > detection of face/body it seems: > [https://github.com/tensorflow/tfjs-models/tree/master/body-segmentation] is > the best model. > Since Chrome 14 there is also a Background Blur API (relying on operating > system APIs): [https://developer.chrome.com/blog/background-blur] - but that > doesn't seem to be widely or reliable supported by operating systems yet. > The project would be about adding the background blur into a simple demo and > then integrate into the OpenMeetings project. Additionally other types of > backgrounds can be added > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OPENMEETINGS-2782) Add blur background filter options on video sharing - AI-ML
Sebastian Wagner created OPENMEETINGS-2782: -- Summary: Add blur background filter options on video sharing - AI-ML Key: OPENMEETINGS-2782 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2782 Project: Openmeetings Issue Type: New Feature Components: Audio/Video Reporter: Sebastian Wagner Assignee: Maxim Solodovnik OpenMeetings uses webRTC and HTML5 video to share audio video. Purely browser based. One feature missing is the ability to blur your webcam's camera background. There are multiple ways to achieve it, Google Meet seems to use: [https://www.tensorflow.org/] Tensorflow are AI/ML models, they provide precompiled models into JS, for detection of face/body it seems: [https://github.com/tensorflow/tfjs-models/tree/master/body-segmentation] is the best model. Since Chrome 14 there is also a Background Blur API (relying on operating system APIs): [https://developer.chrome.com/blog/background-blur] - but that doesn't seem to be widely or reliable supported by operating systems yet. The project would be about adding the background blur into a simple demo and then integrate into the OpenMeetings project. Additionally other types of backgrounds can be added -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OPENMEETINGS-2749) Hazelcast warning in JDK17
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Wagner resolved OPENMEETINGS-2749.
Resolution: Fixed
> Hazelcast warning in JDK17
> --
>
> Key: OPENMEETINGS-2749
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2749
> Project: Openmeetings
> Issue Type: Bug
> Components: Performance
>Affects Versions: 7.0.0
>Reporter: Sebastian Wagner
>Assignee: Sebastian Wagner
>Priority: Minor
> Fix For: 7.0.0
>
>
> When starting up in JDK17 Hazelcast shows a warning:
> {code:java}
> WARNING: Hazelcast is starting in a Java modular environment (Java 9 and
> newer) but without proper access to required Java packages. Use additional
> Java arguments to provide Hazelcast access to Java internal API. The internal
> API access is used to get the best performance results. Arguments to be used:
> --add-modules java.se --add-exports java.base/jdk.internal.ref=ALL-UNNAMED
> --add-opens java.base/java.lang=ALL-UNNAMED --add-opens
> java.base/sun.nio.ch=ALL-UNNAMED --add-opens
> java.management/sun.management=ALL-UNNAMED --add-opens
> jdk.management/com.sun.management.internal=ALL-UNNAMED {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (OPENMEETINGS-2748) Embedded Jetty fails to initialise openmeetings webapp in JDK17
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Wagner resolved OPENMEETINGS-2748.
Resolution: Fixed
> Embedded Jetty fails to initialise openmeetings webapp in JDK17
> ---
>
> Key: OPENMEETINGS-2748
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2748
> Project: Openmeetings
> Issue Type: Bug
> Components: Builds
>Affects Versions: 7.0.0
>Reporter: Sebastian Wagner
>Assignee: Sebastian Wagner
>Priority: Minor
> Fix For: 7.0.0
>
>
> If starting up OpenMeetings with
> {code:java}
> mvn install -P allModules,quick,mysql jetty:run-exploded
> -Dwicket.configuration=DEVELOPMENT {code}
> Jetty fails to initialise the OpenMeetings webapp Exception below.
> If you navigate to [http://localhost:5080/openmeetings/] you will get a
> path/webapp not found exception.
> {code:java}
> jquerypp-1.0.1.jar!/META-INF/resources],UNAVAILABLE}{/Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT}
> java.lang.ExceptionInInitializerError
> at org.apache.wicket.proxy.cglib.CglibProxyFactory.createProxy
> (CglibProxyFactory.java:72)
> at org.apache.wicket.proxy.LazyInitProxyFactory.createProxy
> (LazyInitProxyFactory.java:160)
> at
> org.apache.wicket.spring.injection.annot.AnnotProxyFieldValueFactory.getFieldValue
> (AnnotProxyFieldValueFactory.java:166)
> at org.apache.wicket.injection.Injector.inject (Injector.java:111)
> at
> org.apache.wicket.spring.injection.annot.SpringComponentInjector.inject
> (SpringComponentInjector.java:124)
> at
> org.apache.openmeetings.web.user.record.RecordingResourceReference.
> (RecordingResourceReference.java:52)
> at
> org.apache.openmeetings.web.user.record.Mp4RecordingResourceReference.
> (Mp4RecordingResourceReference.java:34)
> at org.apache.openmeetings.web.app.Application.init (Application.java:334)
> at org.apache.wicket.Application.initApplication (Application.java:766)
> at org.apache.wicket.protocol.http.WicketFilter.init
> (WicketFilter.java:441)
> at org.apache.wicket.protocol.ws.javax.JavaxWebSocketFilter.init
> (JavaxWebSocketFilter.java:48)
> at org.apache.wicket.protocol.http.WicketFilter.init
> (WicketFilter.java:365)
> at org.eclipse.jetty.servlet.FilterHolder.initialize
> (FilterHolder.java:140)
> at org.eclipse.jetty.servlet.ServletHandler.lambda$initialize$0
> (ServletHandler.java:750)
> at java.util.Spliterators$ArraySpliterator.forEachRemaining
> (Spliterators.java:992)
> at java.util.stream.Streams$ConcatSpliterator.forEachRemaining
> (Streams.java:734)
> at java.util.stream.ReferencePipeline$Head.forEach
> (ReferencePipeline.java:762)
> at org.eclipse.jetty.servlet.ServletHandler.initialize
> (ServletHandler.java:774)
> at org.eclipse.jetty.servlet.ServletContextHandler.startContext
> (ServletContextHandler.java:379)
> at org.eclipse.jetty.webapp.WebAppContext.startWebapp
> (WebAppContext.java:1449)
> at org.eclipse.jetty.maven.plugin.JettyWebAppContext.startWebapp
> (JettyWebAppContext.java:328)
> at org.eclipse.jetty.webapp.WebAppContext.startContext
> (WebAppContext.java:1414)
> at org.eclipse.jetty.server.handler.ContextHandler.doStart
> (ContextHandler.java:916)
> at org.eclipse.jetty.servlet.ServletContextHandler.doStart
> (ServletContextHandler.java:288)
> at org.eclipse.jetty.webapp.WebAppContext.doStart (WebAppContext.java:524)
> at org.eclipse.jetty.maven.plugin.JettyWebAppContext.doStart
> (JettyWebAppContext.java:397)
> at org.eclipse.jetty.util.component.AbstractLifeCycle.start
> (AbstractLifeCycle.java:73)
> at org.eclipse.jetty.util.component.ContainerLifeCycle.start
> (ContainerLifeCycle.java:169)
> at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart
> (ContainerLifeCycle.java:117)
> at org.eclipse.jetty.server.handler.AbstractHandler.doStart
> (AbstractHandler.java:97)
> at org.eclipse.jetty.util.component.AbstractLifeCycle.start
> (AbstractLifeCycle.java:73)
> at org.eclipse.jetty.util.component.ContainerLifeCycle.start
> (ContainerLifeCycle.java:169)
> at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart
> (ContainerLifeCycle.java:117)
> at org.eclipse.jetty.server.handler.AbstractHandler.doStart
> (AbstractHandler.java:97)
> at org.eclipse.jetty.util.component.AbstractLifeCycle.start
> (AbstractLifeCycle.java:73)
> at org.eclipse.jetty.util.component.ContainerLifeCycle.start
> (ContainerLifeCycle.java:169)
> at org.eclipse.jetty.server.Server.start (Server.java:423)
> at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart
>
[jira] [Commented] (OPENMEETINGS-2749) Hazelcast warning in JDK17
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17573322#comment-17573322
]
Sebastian Wagner commented on OPENMEETINGS-2749:
True, I've just send a PR to also fix it in the Build Instructions for when
running the embedded Jetty. So should be fine then.
> Hazelcast warning in JDK17
> --
>
> Key: OPENMEETINGS-2749
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2749
> Project: Openmeetings
> Issue Type: Bug
> Components: Performance
>Affects Versions: 7.0.0
>Reporter: Sebastian Wagner
>Assignee: Sebastian Wagner
>Priority: Minor
> Fix For: 7.0.0
>
>
> When starting up in JDK17 Hazelcast shows a warning:
> {code:java}
> WARNING: Hazelcast is starting in a Java modular environment (Java 9 and
> newer) but without proper access to required Java packages. Use additional
> Java arguments to provide Hazelcast access to Java internal API. The internal
> API access is used to get the best performance results. Arguments to be used:
> --add-modules java.se --add-exports java.base/jdk.internal.ref=ALL-UNNAMED
> --add-opens java.base/java.lang=ALL-UNNAMED --add-opens
> java.base/sun.nio.ch=ALL-UNNAMED --add-opens
> java.management/sun.management=ALL-UNNAMED --add-opens
> jdk.management/com.sun.management.internal=ALL-UNNAMED {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (OPENMEETINGS-2749) Hazelcast warning in JDK17
Sebastian Wagner created OPENMEETINGS-2749:
--
Summary: Hazelcast warning in JDK17
Key: OPENMEETINGS-2749
URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2749
Project: Openmeetings
Issue Type: Bug
Components: Performance
Affects Versions: 7.0.0
Reporter: Sebastian Wagner
Assignee: Sebastian Wagner
Fix For: 7.0.0
When starting up in JDK17 Hazelcast shows a warning:
{code:java}
WARNING: Hazelcast is starting in a Java modular environment (Java 9 and newer)
but without proper access to required Java packages. Use additional Java
arguments to provide Hazelcast access to Java internal API. The internal API
access is used to get the best performance results. Arguments to be used:
--add-modules java.se --add-exports java.base/jdk.internal.ref=ALL-UNNAMED
--add-opens java.base/java.lang=ALL-UNNAMED --add-opens
java.base/sun.nio.ch=ALL-UNNAMED --add-opens
java.management/sun.management=ALL-UNNAMED --add-opens
jdk.management/com.sun.management.internal=ALL-UNNAMED {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (OPENMEETINGS-2748) Embedded Jetty fails to initialise openmeetings webapp in JDK17
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Wagner updated OPENMEETINGS-2748:
---
Priority: Minor (was: Major)
> Embedded Jetty fails to initialise openmeetings webapp in JDK17
> ---
>
> Key: OPENMEETINGS-2748
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2748
> Project: Openmeetings
> Issue Type: Bug
> Components: Builds
>Affects Versions: 7.0.0
>Reporter: Sebastian Wagner
>Assignee: Sebastian Wagner
>Priority: Minor
> Fix For: 7.0.0
>
>
> If starting up OpenMeetings with
> {code:java}
> mvn install -P allModules,quick,mysql jetty:run-exploded
> -Dwicket.configuration=DEVELOPMENT {code}
> Jetty fails to initialise the OpenMeetings webapp Exception below.
> If you navigate to [http://localhost:5080/openmeetings/] you will get a
> path/webapp not found exception.
> {code:java}
> jquerypp-1.0.1.jar!/META-INF/resources],UNAVAILABLE}{/Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT}
> java.lang.ExceptionInInitializerError
> at org.apache.wicket.proxy.cglib.CglibProxyFactory.createProxy
> (CglibProxyFactory.java:72)
> at org.apache.wicket.proxy.LazyInitProxyFactory.createProxy
> (LazyInitProxyFactory.java:160)
> at
> org.apache.wicket.spring.injection.annot.AnnotProxyFieldValueFactory.getFieldValue
> (AnnotProxyFieldValueFactory.java:166)
> at org.apache.wicket.injection.Injector.inject (Injector.java:111)
> at
> org.apache.wicket.spring.injection.annot.SpringComponentInjector.inject
> (SpringComponentInjector.java:124)
> at
> org.apache.openmeetings.web.user.record.RecordingResourceReference.
> (RecordingResourceReference.java:52)
> at
> org.apache.openmeetings.web.user.record.Mp4RecordingResourceReference.
> (Mp4RecordingResourceReference.java:34)
> at org.apache.openmeetings.web.app.Application.init (Application.java:334)
> at org.apache.wicket.Application.initApplication (Application.java:766)
> at org.apache.wicket.protocol.http.WicketFilter.init
> (WicketFilter.java:441)
> at org.apache.wicket.protocol.ws.javax.JavaxWebSocketFilter.init
> (JavaxWebSocketFilter.java:48)
> at org.apache.wicket.protocol.http.WicketFilter.init
> (WicketFilter.java:365)
> at org.eclipse.jetty.servlet.FilterHolder.initialize
> (FilterHolder.java:140)
> at org.eclipse.jetty.servlet.ServletHandler.lambda$initialize$0
> (ServletHandler.java:750)
> at java.util.Spliterators$ArraySpliterator.forEachRemaining
> (Spliterators.java:992)
> at java.util.stream.Streams$ConcatSpliterator.forEachRemaining
> (Streams.java:734)
> at java.util.stream.ReferencePipeline$Head.forEach
> (ReferencePipeline.java:762)
> at org.eclipse.jetty.servlet.ServletHandler.initialize
> (ServletHandler.java:774)
> at org.eclipse.jetty.servlet.ServletContextHandler.startContext
> (ServletContextHandler.java:379)
> at org.eclipse.jetty.webapp.WebAppContext.startWebapp
> (WebAppContext.java:1449)
> at org.eclipse.jetty.maven.plugin.JettyWebAppContext.startWebapp
> (JettyWebAppContext.java:328)
> at org.eclipse.jetty.webapp.WebAppContext.startContext
> (WebAppContext.java:1414)
> at org.eclipse.jetty.server.handler.ContextHandler.doStart
> (ContextHandler.java:916)
> at org.eclipse.jetty.servlet.ServletContextHandler.doStart
> (ServletContextHandler.java:288)
> at org.eclipse.jetty.webapp.WebAppContext.doStart (WebAppContext.java:524)
> at org.eclipse.jetty.maven.plugin.JettyWebAppContext.doStart
> (JettyWebAppContext.java:397)
> at org.eclipse.jetty.util.component.AbstractLifeCycle.start
> (AbstractLifeCycle.java:73)
> at org.eclipse.jetty.util.component.ContainerLifeCycle.start
> (ContainerLifeCycle.java:169)
> at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart
> (ContainerLifeCycle.java:117)
> at org.eclipse.jetty.server.handler.AbstractHandler.doStart
> (AbstractHandler.java:97)
> at org.eclipse.jetty.util.component.AbstractLifeCycle.start
> (AbstractLifeCycle.java:73)
> at org.eclipse.jetty.util.component.ContainerLifeCycle.start
> (ContainerLifeCycle.java:169)
> at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart
> (ContainerLifeCycle.java:117)
> at org.eclipse.jetty.server.handler.AbstractHandler.doStart
> (AbstractHandler.java:97)
> at org.eclipse.jetty.util.component.AbstractLifeCycle.start
> (AbstractLifeCycle.java:73)
> at org.eclipse.jetty.util.component.ContainerLifeCycle.start
> (ContainerLifeCycle.java:169)
> at org.eclipse.jetty.server.Server.start (Server.java:423)
> at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart
>
[jira] [Created] (OPENMEETINGS-2748) Embedded Jetty fails to initialise openmeetings webapp in JDK17
Sebastian Wagner created OPENMEETINGS-2748:
--
Summary: Embedded Jetty fails to initialise openmeetings webapp in
JDK17
Key: OPENMEETINGS-2748
URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2748
Project: Openmeetings
Issue Type: Bug
Components: Builds
Affects Versions: 7.0.0
Reporter: Sebastian Wagner
Assignee: Sebastian Wagner
Fix For: 7.0.0
If starting up OpenMeetings with
{code:java}
mvn install -P allModules,quick,mysql jetty:run-exploded
-Dwicket.configuration=DEVELOPMENT {code}
Jetty fails to initialise the OpenMeetings webapp Exception below.
If you navigate to [http://localhost:5080/openmeetings/] you will get a
path/webapp not found exception.
{code:java}
jquerypp-1.0.1.jar!/META-INF/resources],UNAVAILABLE}{/Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT}
java.lang.ExceptionInInitializerError
at org.apache.wicket.proxy.cglib.CglibProxyFactory.createProxy
(CglibProxyFactory.java:72)
at org.apache.wicket.proxy.LazyInitProxyFactory.createProxy
(LazyInitProxyFactory.java:160)
at
org.apache.wicket.spring.injection.annot.AnnotProxyFieldValueFactory.getFieldValue
(AnnotProxyFieldValueFactory.java:166)
at org.apache.wicket.injection.Injector.inject (Injector.java:111)
at org.apache.wicket.spring.injection.annot.SpringComponentInjector.inject
(SpringComponentInjector.java:124)
at
org.apache.openmeetings.web.user.record.RecordingResourceReference.
(RecordingResourceReference.java:52)
at
org.apache.openmeetings.web.user.record.Mp4RecordingResourceReference.
(Mp4RecordingResourceReference.java:34)
at org.apache.openmeetings.web.app.Application.init (Application.java:334)
at org.apache.wicket.Application.initApplication (Application.java:766)
at org.apache.wicket.protocol.http.WicketFilter.init (WicketFilter.java:441)
at org.apache.wicket.protocol.ws.javax.JavaxWebSocketFilter.init
(JavaxWebSocketFilter.java:48)
at org.apache.wicket.protocol.http.WicketFilter.init (WicketFilter.java:365)
at org.eclipse.jetty.servlet.FilterHolder.initialize (FilterHolder.java:140)
at org.eclipse.jetty.servlet.ServletHandler.lambda$initialize$0
(ServletHandler.java:750)
at java.util.Spliterators$ArraySpliterator.forEachRemaining
(Spliterators.java:992)
at java.util.stream.Streams$ConcatSpliterator.forEachRemaining
(Streams.java:734)
at java.util.stream.ReferencePipeline$Head.forEach
(ReferencePipeline.java:762)
at org.eclipse.jetty.servlet.ServletHandler.initialize
(ServletHandler.java:774)
at org.eclipse.jetty.servlet.ServletContextHandler.startContext
(ServletContextHandler.java:379)
at org.eclipse.jetty.webapp.WebAppContext.startWebapp
(WebAppContext.java:1449)
at org.eclipse.jetty.maven.plugin.JettyWebAppContext.startWebapp
(JettyWebAppContext.java:328)
at org.eclipse.jetty.webapp.WebAppContext.startContext
(WebAppContext.java:1414)
at org.eclipse.jetty.server.handler.ContextHandler.doStart
(ContextHandler.java:916)
at org.eclipse.jetty.servlet.ServletContextHandler.doStart
(ServletContextHandler.java:288)
at org.eclipse.jetty.webapp.WebAppContext.doStart (WebAppContext.java:524)
at org.eclipse.jetty.maven.plugin.JettyWebAppContext.doStart
(JettyWebAppContext.java:397)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:73)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start
(ContainerLifeCycle.java:169)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart
(ContainerLifeCycle.java:117)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart
(AbstractHandler.java:97)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:73)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start
(ContainerLifeCycle.java:169)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart
(ContainerLifeCycle.java:117)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart
(AbstractHandler.java:97)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:73)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start
(ContainerLifeCycle.java:169)
at org.eclipse.jetty.server.Server.start (Server.java:423)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart
(ContainerLifeCycle.java:110)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart
(AbstractHandler.java:97)
at org.eclipse.jetty.server.Server.doStart (Server.java:387)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:73)
at org.eclipse.jetty.maven.plugin.AbstractJettyMojo.startJetty
(AbstractJettyMojo.java:449)
at
[jira] [Commented] (OPENMEETINGS-2743) Jetty mode does not work with JDK17 / Source code level
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17556019#comment-17556019
]
Sebastian Wagner commented on OPENMEETINGS-2743:
It seems to fail on a Wicket:
{code:java}
java.lang.ExceptionInInitializerError
at org.apache.wicket.proxy.cglib.CglibProxyFactory.createProxy
(CglibProxyFactory.java:72){code}
and
{code:java}
java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
throws java.lang.ClassFormatError accessible: module java.base does not "opens
java.lang" to unnamed module @23092aba {code}
> Jetty mode does not work with JDK17 / Source code level
>
>
> Key: OPENMEETINGS-2743
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2743
> Project: Openmeetings
> Issue Type: Bug
>Affects Versions: 7.0.0
>Reporter: Sebastian Wagner
>Assignee: Maxim Solodovnik
>Priority: Major
> Fix For: 7.0.0
>
>
> This is master as of 19/06/2022
> When doing a compile and then run jetty as run-exploded
> {code:java}
> mvn clean install -P allModules,quick,mysql
> cd openmeetings-web
> mvn install -P allModules,quick,mysql jetty:run-exploded
> -Dwicket.configuration=DEVELOPMENT {code}
> Jetty throws an error and the server doesn't completely start. Webapp is not
> deployed (404 when accessing via URL). So jetty is running but the webapp
> failed to init.
> Exception in console:
> {code:java}
> [WARNING] Failed startup of context
> o.e.j.m.p.JettyWebAppContext@42c5d861{/openmeetings,[file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/modernizr-2.8.3-1.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/splide-3.6.12.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/typeaheadjs-0.11.1.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/animate.css-3.7.2.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/inputmask-4.0.0.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/spin-js-2.1.0.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/jquery-3.6.0.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/jasny-bootstrap-3.1.3-2.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/font-awesome-6.1.1.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/popper.js-1.16.1-lts.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/bootstrap-5.1.3.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/summernote-0.8.20.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/bootstrap-italia-1.6.2.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/jquery-ui-1.13.1.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/momentjs-2.24.0.jar!/META-INF/resources,
>
>
[jira] [Comment Edited] (OPENMEETINGS-2743) Jetty mode does not work with JDK17 / Source code level
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17556017#comment-17556017
]
Sebastian Wagner edited comment on OPENMEETINGS-2743 at 6/18/22 11:55 PM:
--
This is said to be related to a dependency is using a deprecated Java 16/17
API, e.g.:
[https://segmentfault.com/a/119040985737/en]
I'm not sure what dependency it is though
was (Author: sebawagner):
This is said to be related to a dependency is using a deprecated Java API, e.g.:
[https://segmentfault.com/a/119040985737/en]
I'm not sure what dependency it is though
> Jetty mode does not work with JDK17 / Source code level
>
>
> Key: OPENMEETINGS-2743
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2743
> Project: Openmeetings
> Issue Type: Bug
>Affects Versions: 7.0.0
>Reporter: Sebastian Wagner
>Assignee: Maxim Solodovnik
>Priority: Major
> Fix For: 7.0.0
>
>
> This is master as of 19/06/2022
> When doing a compile and then run jetty as run-exploded
> {code:java}
> mvn clean install -P allModules,quick,mysql
> cd openmeetings-web
> mvn install -P allModules,quick,mysql jetty:run-exploded
> -Dwicket.configuration=DEVELOPMENT {code}
> Jetty throws an error and the server doesn't completely start. Webapp is not
> deployed (404 when accessing via URL). So jetty is running but the webapp
> failed to init.
> Exception in console:
> {code:java}
> [WARNING] Failed startup of context
> o.e.j.m.p.JettyWebAppContext@42c5d861{/openmeetings,[file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/modernizr-2.8.3-1.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/splide-3.6.12.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/typeaheadjs-0.11.1.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/animate.css-3.7.2.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/inputmask-4.0.0.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/spin-js-2.1.0.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/jquery-3.6.0.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/jasny-bootstrap-3.1.3-2.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/font-awesome-6.1.1.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/popper.js-1.16.1-lts.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/bootstrap-5.1.3.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/summernote-0.8.20.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/bootstrap-italia-1.6.2.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/jquery-ui-1.13.1.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/momentjs-2.24.0.jar!/META-INF/resources,
>
>
[jira] [Commented] (OPENMEETINGS-2743) Jetty mode does not work with JDK17 / Source code level
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17556017#comment-17556017
]
Sebastian Wagner commented on OPENMEETINGS-2743:
This is said to be related to a dependency is using a deprecated Java API, e.g.:
[https://segmentfault.com/a/119040985737/en]
I'm not sure what dependency it is though
> Jetty mode does not work with JDK17 / Source code level
>
>
> Key: OPENMEETINGS-2743
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2743
> Project: Openmeetings
> Issue Type: Bug
>Affects Versions: 7.0.0
>Reporter: Sebastian Wagner
>Assignee: Maxim Solodovnik
>Priority: Major
> Fix For: 7.0.0
>
>
> This is master as of 19/06/2022
> When doing a compile and then run jetty as run-exploded
> {code:java}
> mvn clean install -P allModules,quick,mysql
> cd openmeetings-web
> mvn install -P allModules,quick,mysql jetty:run-exploded
> -Dwicket.configuration=DEVELOPMENT {code}
> Jetty throws an error and the server doesn't completely start. Webapp is not
> deployed (404 when accessing via URL). So jetty is running but the webapp
> failed to init.
> Exception in console:
> {code:java}
> [WARNING] Failed startup of context
> o.e.j.m.p.JettyWebAppContext@42c5d861{/openmeetings,[file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/modernizr-2.8.3-1.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/splide-3.6.12.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/typeaheadjs-0.11.1.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/animate.css-3.7.2.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/inputmask-4.0.0.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/spin-js-2.1.0.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/jquery-3.6.0.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/jasny-bootstrap-3.1.3-2.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/font-awesome-6.1.1.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/popper.js-1.16.1-lts.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/bootstrap-5.1.3.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/summernote-0.8.20.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/bootstrap-italia-1.6.2.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/jquery-ui-1.13.1.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/momentjs-2.24.0.jar!/META-INF/resources,
>
> jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/tempusdominus-bootstrap-4-5.39.0.jar!/META-INF/resources,
>
>
[jira] [Created] (OPENMEETINGS-2743) Jetty mode does not work with JDK17 / Source code level
Sebastian Wagner created OPENMEETINGS-2743:
--
Summary: Jetty mode does not work with JDK17 / Source code level
Key: OPENMEETINGS-2743
URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2743
Project: Openmeetings
Issue Type: Bug
Affects Versions: 7.0.0
Reporter: Sebastian Wagner
Assignee: Maxim Solodovnik
Fix For: 7.0.0
This is master as of 19/06/2022
When doing a compile and then run jetty as run-exploded
{code:java}
mvn clean install -P allModules,quick,mysql
cd openmeetings-web
mvn install -P allModules,quick,mysql jetty:run-exploded
-Dwicket.configuration=DEVELOPMENT {code}
Jetty throws an error and the server doesn't completely start. Webapp is not
deployed (404 when accessing via URL). So jetty is running but the webapp
failed to init.
Exception in console:
{code:java}
[WARNING] Failed startup of context
o.e.j.m.p.JettyWebAppContext@42c5d861{/openmeetings,[file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/,
jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/modernizr-2.8.3-1.jar!/META-INF/resources,
jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/splide-3.6.12.jar!/META-INF/resources,
jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/typeaheadjs-0.11.1.jar!/META-INF/resources,
jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/animate.css-3.7.2.jar!/META-INF/resources,
jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/inputmask-4.0.0.jar!/META-INF/resources,
jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/spin-js-2.1.0.jar!/META-INF/resources,
jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/jquery-3.6.0.jar!/META-INF/resources,
jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/jasny-bootstrap-3.1.3-2.jar!/META-INF/resources,
jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/font-awesome-6.1.1.jar!/META-INF/resources,
jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/popper.js-1.16.1-lts.jar!/META-INF/resources,
jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/bootstrap-5.1.3.jar!/META-INF/resources,
jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/summernote-0.8.20.jar!/META-INF/resources,
jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/bootstrap-italia-1.6.2.jar!/META-INF/resources,
jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/jquery-ui-1.13.1.jar!/META-INF/resources,
jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/momentjs-2.24.0.jar!/META-INF/resources,
jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/tempusdominus-bootstrap-4-5.39.0.jar!/META-INF/resources,
jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/jquery-ui-touch-punch-0.2.3-2.jar!/META-INF/resources,
jar:file:///Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT/WEB-INF/lib/jquerypp-1.0.1.jar!/META-INF/resources],UNAVAILABLE}{/Users/sebastianwagner/Documents/work/openmeetings/_REPO/openmeetings/openmeetings-web/target/openmeetings-web-7.0.0-SNAPSHOT}
java.lang.ExceptionInInitializerError
at org.apache.wicket.proxy.cglib.CglibProxyFactory.createProxy
(CglibProxyFactory.java:72)
at
[jira] [Created] (OPENMEETINGS-2742) Create maven module to isolate KMS integration
Sebastian Wagner created OPENMEETINGS-2742: -- Summary: Create maven module to isolate KMS integration Key: OPENMEETINGS-2742 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2742 Project: Openmeetings Issue Type: Improvement Components: Kurento Affects Versions: 7.0.0 Reporter: Sebastian Wagner Assignee: Sebastian Wagner Fix For: 7.0.0 As discussed in [https://lists.apache.org/thread/cm65ltlsjnbt4h030j7zwz5rv1dh21cx] Create a maven module for KMS relevant code. This is a pre-step before porting to KMS 6.18, which will be a separated Jira/task -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (OPENMEETINGS-2735) OpenMeetings doesn't reconnect to KMS if KMS is not running at boot time
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17535993#comment-17535993
]
Sebastian Wagner commented on OPENMEETINGS-2735:
I moved this to v7.0.0 for now
> OpenMeetings doesn't reconnect to KMS if KMS is not running at boot time
>
>
> Key: OPENMEETINGS-2735
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2735
> Project: Openmeetings
> Issue Type: Bug
>Affects Versions: 6.3.0, 7.0.0
>Reporter: Sebastian Wagner
>Assignee: Maxim Solodovnik
>Priority: Major
> Fix For: 7.0.0
>
>
> Steps to reproduce:
> Start OM (KMS offline)
> Start KMS
> Result:
> OM does not attempt to reconnect
>
> Error log
> {code:java}
> DEBUG 05-12 20:27:49.364 o.a.o.d.d.r.PollDao:104 [Thread-49] - :: hasPoll ::
> 5
> DEBUG 05-12 20:27:49.368 o.a.o.d.d.r.PollDao:98 [Thread-49] - :: getArchived
> :: 5
> WARN 05-12 20:27:49.370 o.a.o.c.r.KurentoHandler:135 [Thread-49] - Media
> Server is not accessible
> WARN 05-12 20:27:49.371 o.a.o.c.r.KurentoHandler:135 [Thread-49] - Media
> Server is not accessible
> DEBUG 05-12 20:27:49.527 o.a.o.d.u.AuthLevelUtil:41 [tp455226533-167] - Level
> ADMIN :: [GRANTED]
> WARN 05-12 20:27:51.099 o.a.o.c.r.KurentoHandler:135 [tp455226533-267] -
> Media Server is not accessible
> WARN 05-12 20:28:02.240 o.k.j.c.JsonRpcClient:270 [beatExec-e10-t0] - Error
> sending heartbeat to server. Exception: Timeout trying to connect to
> websocket server ws://127.0.0.1:/kurento
> WARN 05-12 20:28:02.241 o.k.j.c.JsonRpcClient:287 [beatExec-e10-t0] -
> Stopping heartbeat and closing client: failure during heartbeat mechanism
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (OPENMEETINGS-2735) OpenMeetings doesn't reconnect to KMS if KMS is not running at boot time
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Wagner updated OPENMEETINGS-2735:
---
Fix Version/s: 7.0.0
(was: 6.3.0)
> OpenMeetings doesn't reconnect to KMS if KMS is not running at boot time
>
>
> Key: OPENMEETINGS-2735
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2735
> Project: Openmeetings
> Issue Type: Bug
>Affects Versions: 6.3.0, 7.0.0
>Reporter: Sebastian Wagner
>Assignee: Maxim Solodovnik
>Priority: Major
> Fix For: 7.0.0
>
>
> Steps to reproduce:
> Start OM (KMS offline)
> Start KMS
> Result:
> OM does not attempt to reconnect
>
> Error log
> {code:java}
> DEBUG 05-12 20:27:49.364 o.a.o.d.d.r.PollDao:104 [Thread-49] - :: hasPoll ::
> 5
> DEBUG 05-12 20:27:49.368 o.a.o.d.d.r.PollDao:98 [Thread-49] - :: getArchived
> :: 5
> WARN 05-12 20:27:49.370 o.a.o.c.r.KurentoHandler:135 [Thread-49] - Media
> Server is not accessible
> WARN 05-12 20:27:49.371 o.a.o.c.r.KurentoHandler:135 [Thread-49] - Media
> Server is not accessible
> DEBUG 05-12 20:27:49.527 o.a.o.d.u.AuthLevelUtil:41 [tp455226533-167] - Level
> ADMIN :: [GRANTED]
> WARN 05-12 20:27:51.099 o.a.o.c.r.KurentoHandler:135 [tp455226533-267] -
> Media Server is not accessible
> WARN 05-12 20:28:02.240 o.k.j.c.JsonRpcClient:270 [beatExec-e10-t0] - Error
> sending heartbeat to server. Exception: Timeout trying to connect to
> websocket server ws://127.0.0.1:/kurento
> WARN 05-12 20:28:02.241 o.k.j.c.JsonRpcClient:287 [beatExec-e10-t0] -
> Stopping heartbeat and closing client: failure during heartbeat mechanism
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (OPENMEETINGS-2735) OpenMeetings doesn't reconnect to KMS if KMS is not running at boot time
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17535992#comment-17535992
]
Sebastian Wagner commented on OPENMEETINGS-2735:
It is not stable reproduce-able and the error is in the KMS package I suspect.
Not in the OpenMeetings side.
> OpenMeetings doesn't reconnect to KMS if KMS is not running at boot time
>
>
> Key: OPENMEETINGS-2735
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2735
> Project: Openmeetings
> Issue Type: Bug
>Affects Versions: 6.3.0, 7.0.0
>Reporter: Sebastian Wagner
>Assignee: Maxim Solodovnik
>Priority: Major
> Fix For: 7.0.0
>
>
> Steps to reproduce:
> Start OM (KMS offline)
> Start KMS
> Result:
> OM does not attempt to reconnect
>
> Error log
> {code:java}
> DEBUG 05-12 20:27:49.364 o.a.o.d.d.r.PollDao:104 [Thread-49] - :: hasPoll ::
> 5
> DEBUG 05-12 20:27:49.368 o.a.o.d.d.r.PollDao:98 [Thread-49] - :: getArchived
> :: 5
> WARN 05-12 20:27:49.370 o.a.o.c.r.KurentoHandler:135 [Thread-49] - Media
> Server is not accessible
> WARN 05-12 20:27:49.371 o.a.o.c.r.KurentoHandler:135 [Thread-49] - Media
> Server is not accessible
> DEBUG 05-12 20:27:49.527 o.a.o.d.u.AuthLevelUtil:41 [tp455226533-167] - Level
> ADMIN :: [GRANTED]
> WARN 05-12 20:27:51.099 o.a.o.c.r.KurentoHandler:135 [tp455226533-267] -
> Media Server is not accessible
> WARN 05-12 20:28:02.240 o.k.j.c.JsonRpcClient:270 [beatExec-e10-t0] - Error
> sending heartbeat to server. Exception: Timeout trying to connect to
> websocket server ws://127.0.0.1:/kurento
> WARN 05-12 20:28:02.241 o.k.j.c.JsonRpcClient:287 [beatExec-e10-t0] -
> Stopping heartbeat and closing client: failure during heartbeat mechanism
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (OPENMEETINGS-2735) OpenMeetings doesn't reconnect to KMS if KMS is not running at boot time
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17535986#comment-17535986
]
Sebastian Wagner commented on OPENMEETINGS-2735:
No this is master.
Yeah I have not really seen this before.
I tried to run the same scenario again, but this time the heartbeat seems to
continue and not stop.
Looks like this is an issue in JsonRpcClient which is a Kurento Package.
> OpenMeetings doesn't reconnect to KMS if KMS is not running at boot time
>
>
> Key: OPENMEETINGS-2735
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2735
> Project: Openmeetings
> Issue Type: Bug
>Affects Versions: 6.3.0, 7.0.0
>Reporter: Sebastian Wagner
>Assignee: Maxim Solodovnik
>Priority: Major
> Fix For: 6.3.0
>
>
> Steps to reproduce:
> Start OM (KMS offline)
> Start KMS
> Result:
> OM does not attempt to reconnect
>
> Error log
> {code:java}
> DEBUG 05-12 20:27:49.364 o.a.o.d.d.r.PollDao:104 [Thread-49] - :: hasPoll ::
> 5
> DEBUG 05-12 20:27:49.368 o.a.o.d.d.r.PollDao:98 [Thread-49] - :: getArchived
> :: 5
> WARN 05-12 20:27:49.370 o.a.o.c.r.KurentoHandler:135 [Thread-49] - Media
> Server is not accessible
> WARN 05-12 20:27:49.371 o.a.o.c.r.KurentoHandler:135 [Thread-49] - Media
> Server is not accessible
> DEBUG 05-12 20:27:49.527 o.a.o.d.u.AuthLevelUtil:41 [tp455226533-167] - Level
> ADMIN :: [GRANTED]
> WARN 05-12 20:27:51.099 o.a.o.c.r.KurentoHandler:135 [tp455226533-267] -
> Media Server is not accessible
> WARN 05-12 20:28:02.240 o.k.j.c.JsonRpcClient:270 [beatExec-e10-t0] - Error
> sending heartbeat to server. Exception: Timeout trying to connect to
> websocket server ws://127.0.0.1:/kurento
> WARN 05-12 20:28:02.241 o.k.j.c.JsonRpcClient:287 [beatExec-e10-t0] -
> Stopping heartbeat and closing client: failure during heartbeat mechanism
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (OPENMEETINGS-2735) OpenMeetings doesn't reconnect to KMS if KMS is not running at boot time
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17535966#comment-17535966
]
Sebastian Wagner commented on OPENMEETINGS-2735:
I think this should be looked at before releasing
> OpenMeetings doesn't reconnect to KMS if KMS is not running at boot time
>
>
> Key: OPENMEETINGS-2735
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2735
> Project: Openmeetings
> Issue Type: Bug
>Affects Versions: 6.3.0, 7.0.0
>Reporter: Sebastian Wagner
>Assignee: Maxim Solodovnik
>Priority: Major
> Fix For: 6.3.0
>
>
> Steps to reproduce:
> Start OM (KMS offline)
> Start KMS
> Result:
> OM does not attempt to reconnect
>
> Error log
> {code:java}
> DEBUG 05-12 20:27:49.364 o.a.o.d.d.r.PollDao:104 [Thread-49] - :: hasPoll ::
> 5
> DEBUG 05-12 20:27:49.368 o.a.o.d.d.r.PollDao:98 [Thread-49] - :: getArchived
> :: 5
> WARN 05-12 20:27:49.370 o.a.o.c.r.KurentoHandler:135 [Thread-49] - Media
> Server is not accessible
> WARN 05-12 20:27:49.371 o.a.o.c.r.KurentoHandler:135 [Thread-49] - Media
> Server is not accessible
> DEBUG 05-12 20:27:49.527 o.a.o.d.u.AuthLevelUtil:41 [tp455226533-167] - Level
> ADMIN :: [GRANTED]
> WARN 05-12 20:27:51.099 o.a.o.c.r.KurentoHandler:135 [tp455226533-267] -
> Media Server is not accessible
> WARN 05-12 20:28:02.240 o.k.j.c.JsonRpcClient:270 [beatExec-e10-t0] - Error
> sending heartbeat to server. Exception: Timeout trying to connect to
> websocket server ws://127.0.0.1:/kurento
> WARN 05-12 20:28:02.241 o.k.j.c.JsonRpcClient:287 [beatExec-e10-t0] -
> Stopping heartbeat and closing client: failure during heartbeat mechanism
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (OPENMEETINGS-2735) OpenMeetings doesn't reconnect to KMS if KMS is not running at boot time
Sebastian Wagner created OPENMEETINGS-2735:
--
Summary: OpenMeetings doesn't reconnect to KMS if KMS is not
running at boot time
Key: OPENMEETINGS-2735
URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2735
Project: Openmeetings
Issue Type: Bug
Affects Versions: 6.3.0, 7.0.0
Reporter: Sebastian Wagner
Assignee: Maxim Solodovnik
Fix For: 6.3.0
Steps to reproduce:
Start OM (KMS offline)
Start KMS
Result:
OM does not attempt to reconnect
Error log
{code:java}
DEBUG 05-12 20:27:49.364 o.a.o.d.d.r.PollDao:104 [Thread-49] - :: hasPoll :: 5
DEBUG 05-12 20:27:49.368 o.a.o.d.d.r.PollDao:98 [Thread-49] - :: getArchived
:: 5
WARN 05-12 20:27:49.370 o.a.o.c.r.KurentoHandler:135 [Thread-49] - Media
Server is not accessible
WARN 05-12 20:27:49.371 o.a.o.c.r.KurentoHandler:135 [Thread-49] - Media
Server is not accessible
DEBUG 05-12 20:27:49.527 o.a.o.d.u.AuthLevelUtil:41 [tp455226533-167] - Level
ADMIN :: [GRANTED]
WARN 05-12 20:27:51.099 o.a.o.c.r.KurentoHandler:135 [tp455226533-267] - Media
Server is not accessible
WARN 05-12 20:28:02.240 o.k.j.c.JsonRpcClient:270 [beatExec-e10-t0] - Error
sending heartbeat to server. Exception: Timeout trying to connect to websocket
server ws://127.0.0.1:/kurento
WARN 05-12 20:28:02.241 o.k.j.c.JsonRpcClient:287 [beatExec-e10-t0] -
Stopping heartbeat and closing client: failure during heartbeat mechanism {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Resolved] (OPENMEETINGS-2728) Update project website media server config docu
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner resolved OPENMEETINGS-2728. Resolution: Fixed > Update project website media server config docu > --- > > Key: OPENMEETINGS-2728 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2728 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Fix For: 7.0.0 > > > The MediaServer documentation page could need a bit of an uplift. > Also the banner is outdated. And the fix with current-event as URL doesn't > work anymore. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (OPENMEETINGS-2728) Update project website media server config docu
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner updated OPENMEETINGS-2728: --- Summary: Update project website media server config docu (was: Update project website media server config) > Update project website media server config docu > --- > > Key: OPENMEETINGS-2728 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2728 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Fix For: 7.0.0 > > > The MediaServer documentation page could need a bit of an uplift. > Also the banner is outdated. And the fix with current-event as URL doesn't > work anymore. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (OPENMEETINGS-2728) Update project website media server config
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner updated OPENMEETINGS-2728: --- Summary: Update project website media server config (was: Update project website and banner) > Update project website media server config > -- > > Key: OPENMEETINGS-2728 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2728 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Fix For: 7.0.0 > > > The MediaServer documentation page could need a bit of an uplift. > Also the banner is outdated. And the fix with current-event as URL doesn't > work anymore. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (OPENMEETINGS-2726) Give quick poll popup some border styles
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner resolved OPENMEETINGS-2726. Resolution: Fixed > Give quick poll popup some border styles > > > Key: OPENMEETINGS-2726 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2726 > Project: Openmeetings > Issue Type: Improvement > Components: UI >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Fix For: 7.0.0 > > Attachments: image-2022-04-24-11-31-37-735.png > > > The Quick poll fixed popup looks bit un-styled: > !image-2022-04-24-11-31-37-735.png! -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (OPENMEETINGS-2727) Add tooltip to whiteboard tab-buttons to add and scroll tabbar
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner resolved OPENMEETINGS-2727. Resolution: Fixed > Add tooltip to whiteboard tab-buttons to add and scroll tabbar > -- > > Key: OPENMEETINGS-2727 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2727 > Project: Openmeetings > Issue Type: Improvement > Components: UI, WhiteBoard >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Fix For: 7.0.0 > > Attachments: image-2022-04-25-13-23-03-641.png, > image-2022-04-25-13-23-14-699.png > > > The current whiteboard tabbar buttons to add and scroll pre/next for the > whiteboard do not have any tooltip. > !image-2022-04-25-13-23-03-641.png! !image-2022-04-25-13-23-14-699.png! > A tooltip will better explain. Especially with the scroll right icon, it is > not really clear cause it looks like the arrow to the right is related to the > tools in the panel. Rather then the whiteboard buttons. > Also the pre/next buttons make only sense if there is more than 1 whiteboard. > Ideally they should only enable when there is something to scroll. But let's > maybe start to just enable them if there is more than 1 whiteboard. So at > least they are disabled by default and don't confuse the user on what they > will do. > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (OPENMEETINGS-2725) User and files tab bar doesn't show text, mouse-over seems slightly too big
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner resolved OPENMEETINGS-2725. Resolution: Fixed > User and files tab bar doesn't show text, mouse-over seems slightly too big > --- > > Key: OPENMEETINGS-2725 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2725 > Project: Openmeetings > Issue Type: Bug > Components: UI >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Fix For: 7.0.0 > > Attachments: image-2022-04-24-10-47-16-499.png, > image-2022-04-24-10-49-04-043.png > > > Version latest master 24-04-2022 > Browser Chrome latest > > The Tab bar user and files header doesn't show the text: > !image-2022-04-24-10-47-16-499.png! > This only happens when browser is at max viewport (browser width higher then > the biggest viewport ) > It also appears when you mouseover the un-selected files tab the button width > exceeds the width available and overlaps with the minimise-sidepanel button: > !image-2022-04-24-10-49-04-043.png! -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (OPENMEETINGS-2728) Update project website and banner
Sebastian Wagner created OPENMEETINGS-2728: -- Summary: Update project website and banner Key: OPENMEETINGS-2728 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2728 Project: Openmeetings Issue Type: Improvement Components: Documentation Affects Versions: 7.0.0 Reporter: Sebastian Wagner Assignee: Sebastian Wagner Fix For: 7.0.0 The MediaServer documentation page could need a bit of an uplift. Also the banner is outdated. And the fix with current-event as URL doesn't work anymore. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (OPENMEETINGS-2727) Add tooltip to whiteboard tab-buttons to add and scroll tabbar
Sebastian Wagner created OPENMEETINGS-2727: -- Summary: Add tooltip to whiteboard tab-buttons to add and scroll tabbar Key: OPENMEETINGS-2727 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2727 Project: Openmeetings Issue Type: Improvement Components: UI, WhiteBoard Affects Versions: 7.0.0 Reporter: Sebastian Wagner Assignee: Sebastian Wagner Fix For: 7.0.0 Attachments: image-2022-04-25-13-23-03-641.png, image-2022-04-25-13-23-14-699.png The current whiteboard tabbar buttons to add and scroll pre/next for the whiteboard do not have any tooltip. !image-2022-04-25-13-23-03-641.png! !image-2022-04-25-13-23-14-699.png! A tooltip will better explain. Especially with the scroll right icon, it is not really clear cause it looks like the arrow to the right is related to the tools in the panel. Rather then the whiteboard buttons. Also the pre/next buttons make only sense if there is more than 1 whiteboard. Ideally they should only enable when there is something to scroll. But let's maybe start to just enable them if there is more than 1 whiteboard. So at least they are disabled by default and don't confuse the user on what they will do. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (OPENMEETINGS-2726) Give quick poll popup some border styles
Sebastian Wagner created OPENMEETINGS-2726: -- Summary: Give quick poll popup some border styles Key: OPENMEETINGS-2726 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2726 Project: Openmeetings Issue Type: Bug Components: UI Affects Versions: 7.0.0 Reporter: Sebastian Wagner Assignee: Sebastian Wagner Fix For: 7.0.0 Attachments: image-2022-04-24-11-31-37-735.png The Quick poll fixed popup looks bit un-styled: !image-2022-04-24-11-31-37-735.png! -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (OPENMEETINGS-2726) Give quick poll popup some border styles
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner updated OPENMEETINGS-2726: --- Issue Type: Improvement (was: Bug) > Give quick poll popup some border styles > > > Key: OPENMEETINGS-2726 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2726 > Project: Openmeetings > Issue Type: Improvement > Components: UI >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Fix For: 7.0.0 > > Attachments: image-2022-04-24-11-31-37-735.png > > > The Quick poll fixed popup looks bit un-styled: > !image-2022-04-24-11-31-37-735.png! -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (OPENMEETINGS-2725) User and files tab bar doesn't show text, mouse-over seems slightly too big
Sebastian Wagner created OPENMEETINGS-2725: -- Summary: User and files tab bar doesn't show text, mouse-over seems slightly too big Key: OPENMEETINGS-2725 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2725 Project: Openmeetings Issue Type: Bug Components: UI Affects Versions: 7.0.0 Reporter: Sebastian Wagner Assignee: Sebastian Wagner Fix For: 7.0.0 Attachments: image-2022-04-24-10-47-16-499.png, image-2022-04-24-10-49-04-043.png Version latest master 24-04-2022 Browser Chrome latest The Tab bar user and files header doesn't show the text: !image-2022-04-24-10-47-16-499.png! This only happens when browser is at max viewport (browser width higher then the biggest viewport ) It also appears when you mouseover the un-selected files tab the button width exceeds the width available and overlaps with the minimise-sidepanel button: !image-2022-04-24-10-49-04-043.png! -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (OPENMEETINGS-2720) Bad signatures and checksums
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17489833#comment-17489833
]
Sebastian Wagner commented on OPENMEETINGS-2720:
Try again with the GPG tool maybe now. I saw my public key may not have been
synced to all servers. GPG service added a new public server it seemed.
> Bad signatures and checksums
>
>
> Key: OPENMEETINGS-2720
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2720
> Project: Openmeetings
> Issue Type: Bug
> Components: Release
>Affects Versions: 6.2.0
>Reporter: Georg Pfuetzenreuter
>Assignee: Sebastian Wagner
>Priority: Major
> Labels: newbie, security
> Fix For: 6.2.0
>
> Attachments: image-2022-02-09-19-43-44-551.png,
> image-2022-02-09-19-44-33-748.png, image-2022-02-09-19-45-40-112.png
>
>
> Hi,
> Hoping this has not already been discussed in a ticket my search query did
> not cover.
> I noticed all the SHA512 sums do not match the archive files, and the
> signatures all verify as BAD - besides the SHA512 files not being formatted
> properly:
>
> {code:java}
> ## TAR binary
> $ sha512sum -c apache-openmeetings-6.2.0.tar.gz
> sha512sum: apache-openmeetings-6.2.0.tar.gz: no properly formatted SHA512
> checksum lines found
> $ cat apache-openmeetings-6.2.0.tar.gz.sha512
> 37a42ce7b4ee954013c09820e6501f8996d357327cebeff1e8b125ba3dc74f86f961d2175c81ec7951ce30b255ec833f3118465b838aa543dac3b7a9f85452ca
>
>
> $ sha512sum apache-openmeetings-6.2.0.tar.gz
> 69373cf1bb1c2a7344a0e8554bccdb999dd360dda0c6fe653c0936a38c3e4a7c62c95a0a33734d0a88e01bf53930fd5d38efaadce42f88ce57dbb88572f82dda
> apache-openmeetings-6.2.0.tar.gz
> $ gpg --verify apache-openmeetings-6.2.0.tar.gz.asc
> apache-openmeetings-6.2.0.tar.gz
> gpg: Signature made Thu 21 Oct 2021 10:20:02 AM CEST
> gpg: using RSA key BF13CF11F9C90CBE441309AB005516BF93A30395
> gpg: BAD signature from "Sebastian Wagner " [unknown]
> ## ZIP binary
> $ sha512sum -c apache-openmeetings-6.2.0.zip.sha512
> sha512sum: apache-openmeetings-6.2.0.zip.sha512: no properly formatted SHA512
> checksum lines found
> $ cat apache-openmeetings-6.2.0.zip.sha512
> 95271a35856ea2f80795f30a032f4677f2e5232dcf329ad727897ff48144a31fccfd320b250c4f9ce147c5b7c31f8d437fe487e29df9eb4e3181c36a3546d585
>
>
> $ sha512sum apache-openmeetings-6.2.0.zip
> 7270b3c006d2a1000caa1c1e4f1cc850c74631a821343b8433d81605d048907742b5ced76db02154cad0a215726335ebbb1fc55e741b9474c6d4a09eb51bf645
> apache-openmeetings-6.2.0.zip
> $ gpg --verify apache-openmeetings-6.2.0.zip.asc
> apache-openmeetings-6.2.0.zip
> gpg: Signature made Thu 21 Oct 2021 10:20:04 AM CEST
> gpg: using RSA key BF13CF11F9C90CBE441309AB005516BF93A30395
> gpg: BAD signature from "Sebastian Wagner " [unknown]
> ## TAR SOURCE
> $ sha512sum -c apache-openmeetings-6.2.0-src.tar.gz.sha512
> sha512sum: apache-openmeetings-6.2.0-src.tar.gz.sha512: no properly formatted
> SHA512 checksum lines found
> $ cat apache-openmeetings-6.2.0-src.tar.gz.sha512
> dc93c6ea409a560c588babac09d0eea3008ce0c4656061c10b8a0b10ed6a832dea010a7855df8f238dfaf80fdf8b13f57966b7c169952ada8063baaa5f3779c9
> $ sha512sum apache-openmeetings-6.2.0-src.tar.gz
> 7debb392b67eec85c6444dd64d0ca3ecc3753025a2bf96cac8224085caded9cfac016c0844f420a280676bdf366daecc01d1fd4377f42d8ad8e8025b42427f83
> apache-openmeetings-6.2.0-src.tar.gz
> $ gpg --verify apache-openmeetings-6.2.0-src.tar.gz.asc
> apache-openmeetings-6.2.0-src.tar.gz
> gpg: Signature made Thu 21 Oct 2021 10:20:04 AM CEST
> gpg: using RSA key BF13CF11F9C90CBE441309AB005516BF93A30395
> gpg: BAD signature from "Sebastian Wagner " [unknown]
> ##ZIP SOURCE
> $ sha512sum -c apache-openmeetings-6.2.0-src.zip.sha512
> sha512sum: apache-openmeetings-6.2.0-src.zip.sha512: no properly formatted
> SHA512 checksum lines found
> $ cat apache-openmeetings-6.2.0-src.zip.sha512
> 86f1ee26f0edd3ee3c4de078380951e634e2c207b1e3653ea6f3b0c4569320effc8d195e7afb8353401a6e8cba6be3d6dcda58c4bfcffef41de7889d778098d5
> $ gpg --verify apache-openmeetings-6.2.0-src.zip.asc
> apache-openmeetings-6.2.0-src.zip
> gpg: Signature made Thu 21 Oct 2021 10:20:04 AM CEST
> gpg: using RSA key BF13CF11F9C90CBE441309AB005516BF93A30395
> gpg: BAD signature from "Sebastian Wagner " [unknown]
> {code}
> I acquired the files and the public keys using the links on this page:
>
[jira] [Commented] (OPENMEETINGS-2720) Bad signatures and checksums
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17489283#comment-17489283
]
Sebastian Wagner commented on OPENMEETINGS-2720:
I just doubled checked. See below:
File: apache-openmeetings-6.2.0.zip
Signature:
!image-2022-02-09-19-44-33-748.png!
Checksum:
{code:java}
cat
/Users/Sebastian.wagner/Documents/mywork/openmeetings/_REPO/dblcheck/apache-openmeetings-6.2.0.zip.sha512.txt
95271a35856ea2f80795f30a032f4677f2e5232dcf329ad727897ff48144a31fccfd320b250c4f9ce147c5b7c31f8d437fe487e29df9eb4e3181c36a3546d585%
Sebastian.wagner@LM-C02D32DCMD6R dblcheck % shasum -a 512
apache-openmeetings-6.2.0.zip
95271a35856ea2f80795f30a032f4677f2e5232dcf329ad727897ff48144a31fccfd320b250c4f9ce147c5b7c31f8d437fe487e29df9eb4e3181c36a3546d585
apache-openmeetings-6.2.0.zip
{code}
Both matches.
File: apache-openmeetings-6.2.0.tar.gz
Signature:
!image-2022-02-09-19-45-40-112.png!
CHecksum
{code:java}
shasum -a 512 apache-openmeetings-6.2.0.tar.gz
37a42ce7b4ee954013c09820e6501f8996d357327cebeff1e8b125ba3dc74f86f961d2175c81ec7951ce30b255ec833f3118465b838aa543dac3b7a9f85452ca
apache-openmeetings-6.2.0.tar.gz
Sebastian.wagner@LM-C02D32DCMD6R dblcheck % cat
/Users/Sebastian.wagner/Documents/mywork/openmeetings/_REPO/dblcheck/apache-openmeetings-6.2.0.tar.gz.sha512.txt
37a42ce7b4ee954013c09820e6501f8996d357327cebeff1e8b125ba3dc74f86f961d2175c81ec7951ce30b255ec833f3118465b838aa543dac3b7a9f85452ca%
{code}
Both match
I am not too sure on how the GPG verification goes wrong for you.
> Bad signatures and checksums
>
>
> Key: OPENMEETINGS-2720
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2720
> Project: Openmeetings
> Issue Type: Bug
> Components: Release
>Affects Versions: 6.2.0
>Reporter: Georg Pfuetzenreuter
>Assignee: Sebastian Wagner
>Priority: Major
> Labels: newbie, security
> Fix For: 6.2.0
>
> Attachments: image-2022-02-09-19-43-44-551.png,
> image-2022-02-09-19-44-33-748.png, image-2022-02-09-19-45-40-112.png
>
>
> Hi,
> Hoping this has not already been discussed in a ticket my search query did
> not cover.
> I noticed all the SHA512 sums do not match the archive files, and the
> signatures all verify as BAD - besides the SHA512 files not being formatted
> properly:
>
> {code:java}
> ## TAR binary
> $ sha512sum -c apache-openmeetings-6.2.0.tar.gz
> sha512sum: apache-openmeetings-6.2.0.tar.gz: no properly formatted SHA512
> checksum lines found
> $ cat apache-openmeetings-6.2.0.tar.gz.sha512
> 37a42ce7b4ee954013c09820e6501f8996d357327cebeff1e8b125ba3dc74f86f961d2175c81ec7951ce30b255ec833f3118465b838aa543dac3b7a9f85452ca
>
>
> $ sha512sum apache-openmeetings-6.2.0.tar.gz
> 69373cf1bb1c2a7344a0e8554bccdb999dd360dda0c6fe653c0936a38c3e4a7c62c95a0a33734d0a88e01bf53930fd5d38efaadce42f88ce57dbb88572f82dda
> apache-openmeetings-6.2.0.tar.gz
> $ gpg --verify apache-openmeetings-6.2.0.tar.gz.asc
> apache-openmeetings-6.2.0.tar.gz
> gpg: Signature made Thu 21 Oct 2021 10:20:02 AM CEST
> gpg: using RSA key BF13CF11F9C90CBE441309AB005516BF93A30395
> gpg: BAD signature from "Sebastian Wagner " [unknown]
> ## ZIP binary
> $ sha512sum -c apache-openmeetings-6.2.0.zip.sha512
> sha512sum: apache-openmeetings-6.2.0.zip.sha512: no properly formatted SHA512
> checksum lines found
> $ cat apache-openmeetings-6.2.0.zip.sha512
> 95271a35856ea2f80795f30a032f4677f2e5232dcf329ad727897ff48144a31fccfd320b250c4f9ce147c5b7c31f8d437fe487e29df9eb4e3181c36a3546d585
>
>
> $ sha512sum apache-openmeetings-6.2.0.zip
> 7270b3c006d2a1000caa1c1e4f1cc850c74631a821343b8433d81605d048907742b5ced76db02154cad0a215726335ebbb1fc55e741b9474c6d4a09eb51bf645
> apache-openmeetings-6.2.0.zip
> $ gpg --verify apache-openmeetings-6.2.0.zip.asc
> apache-openmeetings-6.2.0.zip
> gpg: Signature made Thu 21 Oct 2021 10:20:04 AM CEST
> gpg: using RSA key BF13CF11F9C90CBE441309AB005516BF93A30395
> gpg: BAD signature from "Sebastian Wagner " [unknown]
> ## TAR SOURCE
> $ sha512sum -c apache-openmeetings-6.2.0-src.tar.gz.sha512
> sha512sum: apache-openmeetings-6.2.0-src.tar.gz.sha512: no properly formatted
> SHA512 checksum lines found
> $ cat apache-openmeetings-6.2.0-src.tar.gz.sha512
> dc93c6ea409a560c588babac09d0eea3008ce0c4656061c10b8a0b10ed6a832dea010a7855df8f238dfaf80fdf8b13f57966b7c169952ada8063baaa5f3779c9
> $ sha512sum apache-openmeetings-6.2.0-src.tar.gz
>
[jira] [Updated] (OPENMEETINGS-2720) Bad signatures and checksums
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Wagner updated OPENMEETINGS-2720:
---
Attachment: image-2022-02-09-19-45-40-112.png
> Bad signatures and checksums
>
>
> Key: OPENMEETINGS-2720
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2720
> Project: Openmeetings
> Issue Type: Bug
> Components: Release
>Affects Versions: 6.2.0
>Reporter: Georg Pfuetzenreuter
>Assignee: Sebastian Wagner
>Priority: Major
> Labels: newbie, security
> Fix For: 6.2.0
>
> Attachments: image-2022-02-09-19-43-44-551.png,
> image-2022-02-09-19-44-33-748.png, image-2022-02-09-19-45-40-112.png
>
>
> Hi,
> Hoping this has not already been discussed in a ticket my search query did
> not cover.
> I noticed all the SHA512 sums do not match the archive files, and the
> signatures all verify as BAD - besides the SHA512 files not being formatted
> properly:
>
> {code:java}
> ## TAR binary
> $ sha512sum -c apache-openmeetings-6.2.0.tar.gz
> sha512sum: apache-openmeetings-6.2.0.tar.gz: no properly formatted SHA512
> checksum lines found
> $ cat apache-openmeetings-6.2.0.tar.gz.sha512
> 37a42ce7b4ee954013c09820e6501f8996d357327cebeff1e8b125ba3dc74f86f961d2175c81ec7951ce30b255ec833f3118465b838aa543dac3b7a9f85452ca
>
>
> $ sha512sum apache-openmeetings-6.2.0.tar.gz
> 69373cf1bb1c2a7344a0e8554bccdb999dd360dda0c6fe653c0936a38c3e4a7c62c95a0a33734d0a88e01bf53930fd5d38efaadce42f88ce57dbb88572f82dda
> apache-openmeetings-6.2.0.tar.gz
> $ gpg --verify apache-openmeetings-6.2.0.tar.gz.asc
> apache-openmeetings-6.2.0.tar.gz
> gpg: Signature made Thu 21 Oct 2021 10:20:02 AM CEST
> gpg: using RSA key BF13CF11F9C90CBE441309AB005516BF93A30395
> gpg: BAD signature from "Sebastian Wagner " [unknown]
> ## ZIP binary
> $ sha512sum -c apache-openmeetings-6.2.0.zip.sha512
> sha512sum: apache-openmeetings-6.2.0.zip.sha512: no properly formatted SHA512
> checksum lines found
> $ cat apache-openmeetings-6.2.0.zip.sha512
> 95271a35856ea2f80795f30a032f4677f2e5232dcf329ad727897ff48144a31fccfd320b250c4f9ce147c5b7c31f8d437fe487e29df9eb4e3181c36a3546d585
>
>
> $ sha512sum apache-openmeetings-6.2.0.zip
> 7270b3c006d2a1000caa1c1e4f1cc850c74631a821343b8433d81605d048907742b5ced76db02154cad0a215726335ebbb1fc55e741b9474c6d4a09eb51bf645
> apache-openmeetings-6.2.0.zip
> $ gpg --verify apache-openmeetings-6.2.0.zip.asc
> apache-openmeetings-6.2.0.zip
> gpg: Signature made Thu 21 Oct 2021 10:20:04 AM CEST
> gpg: using RSA key BF13CF11F9C90CBE441309AB005516BF93A30395
> gpg: BAD signature from "Sebastian Wagner " [unknown]
> ## TAR SOURCE
> $ sha512sum -c apache-openmeetings-6.2.0-src.tar.gz.sha512
> sha512sum: apache-openmeetings-6.2.0-src.tar.gz.sha512: no properly formatted
> SHA512 checksum lines found
> $ cat apache-openmeetings-6.2.0-src.tar.gz.sha512
> dc93c6ea409a560c588babac09d0eea3008ce0c4656061c10b8a0b10ed6a832dea010a7855df8f238dfaf80fdf8b13f57966b7c169952ada8063baaa5f3779c9
> $ sha512sum apache-openmeetings-6.2.0-src.tar.gz
> 7debb392b67eec85c6444dd64d0ca3ecc3753025a2bf96cac8224085caded9cfac016c0844f420a280676bdf366daecc01d1fd4377f42d8ad8e8025b42427f83
> apache-openmeetings-6.2.0-src.tar.gz
> $ gpg --verify apache-openmeetings-6.2.0-src.tar.gz.asc
> apache-openmeetings-6.2.0-src.tar.gz
> gpg: Signature made Thu 21 Oct 2021 10:20:04 AM CEST
> gpg: using RSA key BF13CF11F9C90CBE441309AB005516BF93A30395
> gpg: BAD signature from "Sebastian Wagner " [unknown]
> ##ZIP SOURCE
> $ sha512sum -c apache-openmeetings-6.2.0-src.zip.sha512
> sha512sum: apache-openmeetings-6.2.0-src.zip.sha512: no properly formatted
> SHA512 checksum lines found
> $ cat apache-openmeetings-6.2.0-src.zip.sha512
> 86f1ee26f0edd3ee3c4de078380951e634e2c207b1e3653ea6f3b0c4569320effc8d195e7afb8353401a6e8cba6be3d6dcda58c4bfcffef41de7889d778098d5
> $ gpg --verify apache-openmeetings-6.2.0-src.zip.asc
> apache-openmeetings-6.2.0-src.zip
> gpg: Signature made Thu 21 Oct 2021 10:20:04 AM CEST
> gpg: using RSA key BF13CF11F9C90CBE441309AB005516BF93A30395
> gpg: BAD signature from "Sebastian Wagner " [unknown]
> {code}
> I acquired the files and the public keys using the links on this page:
> [https://openmeetings.apache.org/downloads.html]
> Given that it shows the same behavior on all files I assume the issue is not
> on my end.
> Is this project still
[jira] [Updated] (OPENMEETINGS-2720) Bad signatures and checksums
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Wagner updated OPENMEETINGS-2720:
---
Attachment: image-2022-02-09-19-44-33-748.png
> Bad signatures and checksums
>
>
> Key: OPENMEETINGS-2720
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2720
> Project: Openmeetings
> Issue Type: Bug
> Components: Release
>Affects Versions: 6.2.0
>Reporter: Georg Pfuetzenreuter
>Assignee: Sebastian Wagner
>Priority: Major
> Labels: newbie, security
> Fix For: 6.2.0
>
> Attachments: image-2022-02-09-19-43-44-551.png,
> image-2022-02-09-19-44-33-748.png
>
>
> Hi,
> Hoping this has not already been discussed in a ticket my search query did
> not cover.
> I noticed all the SHA512 sums do not match the archive files, and the
> signatures all verify as BAD - besides the SHA512 files not being formatted
> properly:
>
> {code:java}
> ## TAR binary
> $ sha512sum -c apache-openmeetings-6.2.0.tar.gz
> sha512sum: apache-openmeetings-6.2.0.tar.gz: no properly formatted SHA512
> checksum lines found
> $ cat apache-openmeetings-6.2.0.tar.gz.sha512
> 37a42ce7b4ee954013c09820e6501f8996d357327cebeff1e8b125ba3dc74f86f961d2175c81ec7951ce30b255ec833f3118465b838aa543dac3b7a9f85452ca
>
>
> $ sha512sum apache-openmeetings-6.2.0.tar.gz
> 69373cf1bb1c2a7344a0e8554bccdb999dd360dda0c6fe653c0936a38c3e4a7c62c95a0a33734d0a88e01bf53930fd5d38efaadce42f88ce57dbb88572f82dda
> apache-openmeetings-6.2.0.tar.gz
> $ gpg --verify apache-openmeetings-6.2.0.tar.gz.asc
> apache-openmeetings-6.2.0.tar.gz
> gpg: Signature made Thu 21 Oct 2021 10:20:02 AM CEST
> gpg: using RSA key BF13CF11F9C90CBE441309AB005516BF93A30395
> gpg: BAD signature from "Sebastian Wagner " [unknown]
> ## ZIP binary
> $ sha512sum -c apache-openmeetings-6.2.0.zip.sha512
> sha512sum: apache-openmeetings-6.2.0.zip.sha512: no properly formatted SHA512
> checksum lines found
> $ cat apache-openmeetings-6.2.0.zip.sha512
> 95271a35856ea2f80795f30a032f4677f2e5232dcf329ad727897ff48144a31fccfd320b250c4f9ce147c5b7c31f8d437fe487e29df9eb4e3181c36a3546d585
>
>
> $ sha512sum apache-openmeetings-6.2.0.zip
> 7270b3c006d2a1000caa1c1e4f1cc850c74631a821343b8433d81605d048907742b5ced76db02154cad0a215726335ebbb1fc55e741b9474c6d4a09eb51bf645
> apache-openmeetings-6.2.0.zip
> $ gpg --verify apache-openmeetings-6.2.0.zip.asc
> apache-openmeetings-6.2.0.zip
> gpg: Signature made Thu 21 Oct 2021 10:20:04 AM CEST
> gpg: using RSA key BF13CF11F9C90CBE441309AB005516BF93A30395
> gpg: BAD signature from "Sebastian Wagner " [unknown]
> ## TAR SOURCE
> $ sha512sum -c apache-openmeetings-6.2.0-src.tar.gz.sha512
> sha512sum: apache-openmeetings-6.2.0-src.tar.gz.sha512: no properly formatted
> SHA512 checksum lines found
> $ cat apache-openmeetings-6.2.0-src.tar.gz.sha512
> dc93c6ea409a560c588babac09d0eea3008ce0c4656061c10b8a0b10ed6a832dea010a7855df8f238dfaf80fdf8b13f57966b7c169952ada8063baaa5f3779c9
> $ sha512sum apache-openmeetings-6.2.0-src.tar.gz
> 7debb392b67eec85c6444dd64d0ca3ecc3753025a2bf96cac8224085caded9cfac016c0844f420a280676bdf366daecc01d1fd4377f42d8ad8e8025b42427f83
> apache-openmeetings-6.2.0-src.tar.gz
> $ gpg --verify apache-openmeetings-6.2.0-src.tar.gz.asc
> apache-openmeetings-6.2.0-src.tar.gz
> gpg: Signature made Thu 21 Oct 2021 10:20:04 AM CEST
> gpg: using RSA key BF13CF11F9C90CBE441309AB005516BF93A30395
> gpg: BAD signature from "Sebastian Wagner " [unknown]
> ##ZIP SOURCE
> $ sha512sum -c apache-openmeetings-6.2.0-src.zip.sha512
> sha512sum: apache-openmeetings-6.2.0-src.zip.sha512: no properly formatted
> SHA512 checksum lines found
> $ cat apache-openmeetings-6.2.0-src.zip.sha512
> 86f1ee26f0edd3ee3c4de078380951e634e2c207b1e3653ea6f3b0c4569320effc8d195e7afb8353401a6e8cba6be3d6dcda58c4bfcffef41de7889d778098d5
> $ gpg --verify apache-openmeetings-6.2.0-src.zip.asc
> apache-openmeetings-6.2.0-src.zip
> gpg: Signature made Thu 21 Oct 2021 10:20:04 AM CEST
> gpg: using RSA key BF13CF11F9C90CBE441309AB005516BF93A30395
> gpg: BAD signature from "Sebastian Wagner " [unknown]
> {code}
> I acquired the files and the public keys using the links on this page:
> [https://openmeetings.apache.org/downloads.html]
> Given that it shows the same behavior on all files I assume the issue is not
> on my end.
> Is this project still maintained?
> If so, it would be
[jira] [Updated] (OPENMEETINGS-2720) Bad signatures and checksums
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Wagner updated OPENMEETINGS-2720:
---
Attachment: image-2022-02-09-19-43-44-551.png
> Bad signatures and checksums
>
>
> Key: OPENMEETINGS-2720
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2720
> Project: Openmeetings
> Issue Type: Bug
> Components: Release
>Affects Versions: 6.2.0
>Reporter: Georg Pfuetzenreuter
>Assignee: Sebastian Wagner
>Priority: Major
> Labels: newbie, security
> Fix For: 6.2.0
>
> Attachments: image-2022-02-09-19-43-44-551.png
>
>
> Hi,
> Hoping this has not already been discussed in a ticket my search query did
> not cover.
> I noticed all the SHA512 sums do not match the archive files, and the
> signatures all verify as BAD - besides the SHA512 files not being formatted
> properly:
>
> {code:java}
> ## TAR binary
> $ sha512sum -c apache-openmeetings-6.2.0.tar.gz
> sha512sum: apache-openmeetings-6.2.0.tar.gz: no properly formatted SHA512
> checksum lines found
> $ cat apache-openmeetings-6.2.0.tar.gz.sha512
> 37a42ce7b4ee954013c09820e6501f8996d357327cebeff1e8b125ba3dc74f86f961d2175c81ec7951ce30b255ec833f3118465b838aa543dac3b7a9f85452ca
>
>
> $ sha512sum apache-openmeetings-6.2.0.tar.gz
> 69373cf1bb1c2a7344a0e8554bccdb999dd360dda0c6fe653c0936a38c3e4a7c62c95a0a33734d0a88e01bf53930fd5d38efaadce42f88ce57dbb88572f82dda
> apache-openmeetings-6.2.0.tar.gz
> $ gpg --verify apache-openmeetings-6.2.0.tar.gz.asc
> apache-openmeetings-6.2.0.tar.gz
> gpg: Signature made Thu 21 Oct 2021 10:20:02 AM CEST
> gpg: using RSA key BF13CF11F9C90CBE441309AB005516BF93A30395
> gpg: BAD signature from "Sebastian Wagner " [unknown]
> ## ZIP binary
> $ sha512sum -c apache-openmeetings-6.2.0.zip.sha512
> sha512sum: apache-openmeetings-6.2.0.zip.sha512: no properly formatted SHA512
> checksum lines found
> $ cat apache-openmeetings-6.2.0.zip.sha512
> 95271a35856ea2f80795f30a032f4677f2e5232dcf329ad727897ff48144a31fccfd320b250c4f9ce147c5b7c31f8d437fe487e29df9eb4e3181c36a3546d585
>
>
> $ sha512sum apache-openmeetings-6.2.0.zip
> 7270b3c006d2a1000caa1c1e4f1cc850c74631a821343b8433d81605d048907742b5ced76db02154cad0a215726335ebbb1fc55e741b9474c6d4a09eb51bf645
> apache-openmeetings-6.2.0.zip
> $ gpg --verify apache-openmeetings-6.2.0.zip.asc
> apache-openmeetings-6.2.0.zip
> gpg: Signature made Thu 21 Oct 2021 10:20:04 AM CEST
> gpg: using RSA key BF13CF11F9C90CBE441309AB005516BF93A30395
> gpg: BAD signature from "Sebastian Wagner " [unknown]
> ## TAR SOURCE
> $ sha512sum -c apache-openmeetings-6.2.0-src.tar.gz.sha512
> sha512sum: apache-openmeetings-6.2.0-src.tar.gz.sha512: no properly formatted
> SHA512 checksum lines found
> $ cat apache-openmeetings-6.2.0-src.tar.gz.sha512
> dc93c6ea409a560c588babac09d0eea3008ce0c4656061c10b8a0b10ed6a832dea010a7855df8f238dfaf80fdf8b13f57966b7c169952ada8063baaa5f3779c9
> $ sha512sum apache-openmeetings-6.2.0-src.tar.gz
> 7debb392b67eec85c6444dd64d0ca3ecc3753025a2bf96cac8224085caded9cfac016c0844f420a280676bdf366daecc01d1fd4377f42d8ad8e8025b42427f83
> apache-openmeetings-6.2.0-src.tar.gz
> $ gpg --verify apache-openmeetings-6.2.0-src.tar.gz.asc
> apache-openmeetings-6.2.0-src.tar.gz
> gpg: Signature made Thu 21 Oct 2021 10:20:04 AM CEST
> gpg: using RSA key BF13CF11F9C90CBE441309AB005516BF93A30395
> gpg: BAD signature from "Sebastian Wagner " [unknown]
> ##ZIP SOURCE
> $ sha512sum -c apache-openmeetings-6.2.0-src.zip.sha512
> sha512sum: apache-openmeetings-6.2.0-src.zip.sha512: no properly formatted
> SHA512 checksum lines found
> $ cat apache-openmeetings-6.2.0-src.zip.sha512
> 86f1ee26f0edd3ee3c4de078380951e634e2c207b1e3653ea6f3b0c4569320effc8d195e7afb8353401a6e8cba6be3d6dcda58c4bfcffef41de7889d778098d5
> $ gpg --verify apache-openmeetings-6.2.0-src.zip.asc
> apache-openmeetings-6.2.0-src.zip
> gpg: Signature made Thu 21 Oct 2021 10:20:04 AM CEST
> gpg: using RSA key BF13CF11F9C90CBE441309AB005516BF93A30395
> gpg: BAD signature from "Sebastian Wagner " [unknown]
> {code}
> I acquired the files and the public keys using the links on this page:
> [https://openmeetings.apache.org/downloads.html]
> Given that it shows the same behavior on all files I assume the issue is not
> on my end.
> Is this project still maintained?
> If so, it would be fantastic if the signatures and checksums
[jira] [Assigned] (OPENMEETINGS-2720) Bad signatures and checksums
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Wagner reassigned OPENMEETINGS-2720:
--
Assignee: Sebastian Wagner (was: Maxim Solodovnik)
> Bad signatures and checksums
>
>
> Key: OPENMEETINGS-2720
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2720
> Project: Openmeetings
> Issue Type: Bug
> Components: Release
>Affects Versions: 6.2.0
>Reporter: Georg Pfuetzenreuter
>Assignee: Sebastian Wagner
>Priority: Major
> Labels: newbie, security
>
> Hi,
> Hoping this has not already been discussed in a ticket my search query did
> not cover.
> I noticed all the SHA512 sums do not match the archive files, and the
> signatures all verify as BAD - besides the SHA512 files not being formatted
> properly:
>
> {code:java}
> ## TAR binary
> $ sha512sum -c apache-openmeetings-6.2.0.tar.gz
> sha512sum: apache-openmeetings-6.2.0.tar.gz: no properly formatted SHA512
> checksum lines found
> $ cat apache-openmeetings-6.2.0.tar.gz.sha512
> 37a42ce7b4ee954013c09820e6501f8996d357327cebeff1e8b125ba3dc74f86f961d2175c81ec7951ce30b255ec833f3118465b838aa543dac3b7a9f85452ca
>
>
> $ sha512sum apache-openmeetings-6.2.0.tar.gz
> 69373cf1bb1c2a7344a0e8554bccdb999dd360dda0c6fe653c0936a38c3e4a7c62c95a0a33734d0a88e01bf53930fd5d38efaadce42f88ce57dbb88572f82dda
> apache-openmeetings-6.2.0.tar.gz
> $ gpg --verify apache-openmeetings-6.2.0.tar.gz.asc
> apache-openmeetings-6.2.0.tar.gz
> gpg: Signature made Thu 21 Oct 2021 10:20:02 AM CEST
> gpg: using RSA key BF13CF11F9C90CBE441309AB005516BF93A30395
> gpg: BAD signature from "Sebastian Wagner " [unknown]
> ## ZIP binary
> $ sha512sum -c apache-openmeetings-6.2.0.zip.sha512
> sha512sum: apache-openmeetings-6.2.0.zip.sha512: no properly formatted SHA512
> checksum lines found
> $ cat apache-openmeetings-6.2.0.zip.sha512
> 95271a35856ea2f80795f30a032f4677f2e5232dcf329ad727897ff48144a31fccfd320b250c4f9ce147c5b7c31f8d437fe487e29df9eb4e3181c36a3546d585
>
>
> $ sha512sum apache-openmeetings-6.2.0.zip
> 7270b3c006d2a1000caa1c1e4f1cc850c74631a821343b8433d81605d048907742b5ced76db02154cad0a215726335ebbb1fc55e741b9474c6d4a09eb51bf645
> apache-openmeetings-6.2.0.zip
> $ gpg --verify apache-openmeetings-6.2.0.zip.asc
> apache-openmeetings-6.2.0.zip
> gpg: Signature made Thu 21 Oct 2021 10:20:04 AM CEST
> gpg: using RSA key BF13CF11F9C90CBE441309AB005516BF93A30395
> gpg: BAD signature from "Sebastian Wagner " [unknown]
> ## TAR SOURCE
> $ sha512sum -c apache-openmeetings-6.2.0-src.tar.gz.sha512
> sha512sum: apache-openmeetings-6.2.0-src.tar.gz.sha512: no properly formatted
> SHA512 checksum lines found
> $ cat apache-openmeetings-6.2.0-src.tar.gz.sha512
> dc93c6ea409a560c588babac09d0eea3008ce0c4656061c10b8a0b10ed6a832dea010a7855df8f238dfaf80fdf8b13f57966b7c169952ada8063baaa5f3779c9
> $ sha512sum apache-openmeetings-6.2.0-src.tar.gz
> 7debb392b67eec85c6444dd64d0ca3ecc3753025a2bf96cac8224085caded9cfac016c0844f420a280676bdf366daecc01d1fd4377f42d8ad8e8025b42427f83
> apache-openmeetings-6.2.0-src.tar.gz
> $ gpg --verify apache-openmeetings-6.2.0-src.tar.gz.asc
> apache-openmeetings-6.2.0-src.tar.gz
> gpg: Signature made Thu 21 Oct 2021 10:20:04 AM CEST
> gpg: using RSA key BF13CF11F9C90CBE441309AB005516BF93A30395
> gpg: BAD signature from "Sebastian Wagner " [unknown]
> ##ZIP SOURCE
> $ sha512sum -c apache-openmeetings-6.2.0-src.zip.sha512
> sha512sum: apache-openmeetings-6.2.0-src.zip.sha512: no properly formatted
> SHA512 checksum lines found
> $ cat apache-openmeetings-6.2.0-src.zip.sha512
> 86f1ee26f0edd3ee3c4de078380951e634e2c207b1e3653ea6f3b0c4569320effc8d195e7afb8353401a6e8cba6be3d6dcda58c4bfcffef41de7889d778098d5
> $ gpg --verify apache-openmeetings-6.2.0-src.zip.asc
> apache-openmeetings-6.2.0-src.zip
> gpg: Signature made Thu 21 Oct 2021 10:20:04 AM CEST
> gpg: using RSA key BF13CF11F9C90CBE441309AB005516BF93A30395
> gpg: BAD signature from "Sebastian Wagner " [unknown]
> {code}
> I acquired the files and the public keys using the links on this page:
> [https://openmeetings.apache.org/downloads.html]
> Given that it shows the same behavior on all files I assume the issue is not
> on my end.
> Is this project still maintained?
> If so, it would be fantastic if the signatures and checksums could be
> repaired.
> If not, I suggest placing a notice on the download
[jira] [Resolved] (OPENMEETINGS-2720) Bad signatures and checksums
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Wagner resolved OPENMEETINGS-2720.
Fix Version/s: 6.2.0
Resolution: Fixed
> Bad signatures and checksums
>
>
> Key: OPENMEETINGS-2720
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2720
> Project: Openmeetings
> Issue Type: Bug
> Components: Release
>Affects Versions: 6.2.0
>Reporter: Georg Pfuetzenreuter
>Assignee: Sebastian Wagner
>Priority: Major
> Labels: newbie, security
> Fix For: 6.2.0
>
>
> Hi,
> Hoping this has not already been discussed in a ticket my search query did
> not cover.
> I noticed all the SHA512 sums do not match the archive files, and the
> signatures all verify as BAD - besides the SHA512 files not being formatted
> properly:
>
> {code:java}
> ## TAR binary
> $ sha512sum -c apache-openmeetings-6.2.0.tar.gz
> sha512sum: apache-openmeetings-6.2.0.tar.gz: no properly formatted SHA512
> checksum lines found
> $ cat apache-openmeetings-6.2.0.tar.gz.sha512
> 37a42ce7b4ee954013c09820e6501f8996d357327cebeff1e8b125ba3dc74f86f961d2175c81ec7951ce30b255ec833f3118465b838aa543dac3b7a9f85452ca
>
>
> $ sha512sum apache-openmeetings-6.2.0.tar.gz
> 69373cf1bb1c2a7344a0e8554bccdb999dd360dda0c6fe653c0936a38c3e4a7c62c95a0a33734d0a88e01bf53930fd5d38efaadce42f88ce57dbb88572f82dda
> apache-openmeetings-6.2.0.tar.gz
> $ gpg --verify apache-openmeetings-6.2.0.tar.gz.asc
> apache-openmeetings-6.2.0.tar.gz
> gpg: Signature made Thu 21 Oct 2021 10:20:02 AM CEST
> gpg: using RSA key BF13CF11F9C90CBE441309AB005516BF93A30395
> gpg: BAD signature from "Sebastian Wagner " [unknown]
> ## ZIP binary
> $ sha512sum -c apache-openmeetings-6.2.0.zip.sha512
> sha512sum: apache-openmeetings-6.2.0.zip.sha512: no properly formatted SHA512
> checksum lines found
> $ cat apache-openmeetings-6.2.0.zip.sha512
> 95271a35856ea2f80795f30a032f4677f2e5232dcf329ad727897ff48144a31fccfd320b250c4f9ce147c5b7c31f8d437fe487e29df9eb4e3181c36a3546d585
>
>
> $ sha512sum apache-openmeetings-6.2.0.zip
> 7270b3c006d2a1000caa1c1e4f1cc850c74631a821343b8433d81605d048907742b5ced76db02154cad0a215726335ebbb1fc55e741b9474c6d4a09eb51bf645
> apache-openmeetings-6.2.0.zip
> $ gpg --verify apache-openmeetings-6.2.0.zip.asc
> apache-openmeetings-6.2.0.zip
> gpg: Signature made Thu 21 Oct 2021 10:20:04 AM CEST
> gpg: using RSA key BF13CF11F9C90CBE441309AB005516BF93A30395
> gpg: BAD signature from "Sebastian Wagner " [unknown]
> ## TAR SOURCE
> $ sha512sum -c apache-openmeetings-6.2.0-src.tar.gz.sha512
> sha512sum: apache-openmeetings-6.2.0-src.tar.gz.sha512: no properly formatted
> SHA512 checksum lines found
> $ cat apache-openmeetings-6.2.0-src.tar.gz.sha512
> dc93c6ea409a560c588babac09d0eea3008ce0c4656061c10b8a0b10ed6a832dea010a7855df8f238dfaf80fdf8b13f57966b7c169952ada8063baaa5f3779c9
> $ sha512sum apache-openmeetings-6.2.0-src.tar.gz
> 7debb392b67eec85c6444dd64d0ca3ecc3753025a2bf96cac8224085caded9cfac016c0844f420a280676bdf366daecc01d1fd4377f42d8ad8e8025b42427f83
> apache-openmeetings-6.2.0-src.tar.gz
> $ gpg --verify apache-openmeetings-6.2.0-src.tar.gz.asc
> apache-openmeetings-6.2.0-src.tar.gz
> gpg: Signature made Thu 21 Oct 2021 10:20:04 AM CEST
> gpg: using RSA key BF13CF11F9C90CBE441309AB005516BF93A30395
> gpg: BAD signature from "Sebastian Wagner " [unknown]
> ##ZIP SOURCE
> $ sha512sum -c apache-openmeetings-6.2.0-src.zip.sha512
> sha512sum: apache-openmeetings-6.2.0-src.zip.sha512: no properly formatted
> SHA512 checksum lines found
> $ cat apache-openmeetings-6.2.0-src.zip.sha512
> 86f1ee26f0edd3ee3c4de078380951e634e2c207b1e3653ea6f3b0c4569320effc8d195e7afb8353401a6e8cba6be3d6dcda58c4bfcffef41de7889d778098d5
> $ gpg --verify apache-openmeetings-6.2.0-src.zip.asc
> apache-openmeetings-6.2.0-src.zip
> gpg: Signature made Thu 21 Oct 2021 10:20:04 AM CEST
> gpg: using RSA key BF13CF11F9C90CBE441309AB005516BF93A30395
> gpg: BAD signature from "Sebastian Wagner " [unknown]
> {code}
> I acquired the files and the public keys using the links on this page:
> [https://openmeetings.apache.org/downloads.html]
> Given that it shows the same behavior on all files I assume the issue is not
> on my end.
> Is this project still maintained?
> If so, it would be fantastic if the signatures and checksums could be
> repaired.
> If not, I suggest placing a notice
[jira] [Commented] (OPENMEETINGS-2720) Bad signatures and checksums
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488591#comment-17488591
]
Sebastian Wagner commented on OPENMEETINGS-2720:
we fixed this. It has to do with the formatting of the file. There is some
whitespace missing.
Please look at the output of the makign the checksum and the file content. The
checksums are not literally made for the md5sum tool. There isn't really an
agreed format for the md5 checksum file.
But previous and later releases are fixing the checksum so that also md5sum
tool will accept those files.
> Bad signatures and checksums
>
>
> Key: OPENMEETINGS-2720
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2720
> Project: Openmeetings
> Issue Type: Bug
> Components: Release
>Affects Versions: 6.2.0
>Reporter: Georg Pfuetzenreuter
>Assignee: Maxim Solodovnik
>Priority: Major
> Labels: newbie, security
>
> Hi,
> Hoping this has not already been discussed in a ticket my search query did
> not cover.
> I noticed all the SHA512 sums do not match the archive files, and the
> signatures all verify as BAD - besides the SHA512 files not being formatted
> properly:
>
> {code:java}
> ## TAR binary
> $ sha512sum -c apache-openmeetings-6.2.0.tar.gz
> sha512sum: apache-openmeetings-6.2.0.tar.gz: no properly formatted SHA512
> checksum lines found
> $ cat apache-openmeetings-6.2.0.tar.gz.sha512
> 37a42ce7b4ee954013c09820e6501f8996d357327cebeff1e8b125ba3dc74f86f961d2175c81ec7951ce30b255ec833f3118465b838aa543dac3b7a9f85452ca
>
>
> $ sha512sum apache-openmeetings-6.2.0.tar.gz
> 69373cf1bb1c2a7344a0e8554bccdb999dd360dda0c6fe653c0936a38c3e4a7c62c95a0a33734d0a88e01bf53930fd5d38efaadce42f88ce57dbb88572f82dda
> apache-openmeetings-6.2.0.tar.gz
> $ gpg --verify apache-openmeetings-6.2.0.tar.gz.asc
> apache-openmeetings-6.2.0.tar.gz
> gpg: Signature made Thu 21 Oct 2021 10:20:02 AM CEST
> gpg: using RSA key BF13CF11F9C90CBE441309AB005516BF93A30395
> gpg: BAD signature from "Sebastian Wagner " [unknown]
> ## ZIP binary
> $ sha512sum -c apache-openmeetings-6.2.0.zip.sha512
> sha512sum: apache-openmeetings-6.2.0.zip.sha512: no properly formatted SHA512
> checksum lines found
> $ cat apache-openmeetings-6.2.0.zip.sha512
> 95271a35856ea2f80795f30a032f4677f2e5232dcf329ad727897ff48144a31fccfd320b250c4f9ce147c5b7c31f8d437fe487e29df9eb4e3181c36a3546d585
>
>
> $ sha512sum apache-openmeetings-6.2.0.zip
> 7270b3c006d2a1000caa1c1e4f1cc850c74631a821343b8433d81605d048907742b5ced76db02154cad0a215726335ebbb1fc55e741b9474c6d4a09eb51bf645
> apache-openmeetings-6.2.0.zip
> $ gpg --verify apache-openmeetings-6.2.0.zip.asc
> apache-openmeetings-6.2.0.zip
> gpg: Signature made Thu 21 Oct 2021 10:20:04 AM CEST
> gpg: using RSA key BF13CF11F9C90CBE441309AB005516BF93A30395
> gpg: BAD signature from "Sebastian Wagner " [unknown]
> ## TAR SOURCE
> $ sha512sum -c apache-openmeetings-6.2.0-src.tar.gz.sha512
> sha512sum: apache-openmeetings-6.2.0-src.tar.gz.sha512: no properly formatted
> SHA512 checksum lines found
> $ cat apache-openmeetings-6.2.0-src.tar.gz.sha512
> dc93c6ea409a560c588babac09d0eea3008ce0c4656061c10b8a0b10ed6a832dea010a7855df8f238dfaf80fdf8b13f57966b7c169952ada8063baaa5f3779c9
> $ sha512sum apache-openmeetings-6.2.0-src.tar.gz
> 7debb392b67eec85c6444dd64d0ca3ecc3753025a2bf96cac8224085caded9cfac016c0844f420a280676bdf366daecc01d1fd4377f42d8ad8e8025b42427f83
> apache-openmeetings-6.2.0-src.tar.gz
> $ gpg --verify apache-openmeetings-6.2.0-src.tar.gz.asc
> apache-openmeetings-6.2.0-src.tar.gz
> gpg: Signature made Thu 21 Oct 2021 10:20:04 AM CEST
> gpg: using RSA key BF13CF11F9C90CBE441309AB005516BF93A30395
> gpg: BAD signature from "Sebastian Wagner " [unknown]
> ##ZIP SOURCE
> $ sha512sum -c apache-openmeetings-6.2.0-src.zip.sha512
> sha512sum: apache-openmeetings-6.2.0-src.zip.sha512: no properly formatted
> SHA512 checksum lines found
> $ cat apache-openmeetings-6.2.0-src.zip.sha512
> 86f1ee26f0edd3ee3c4de078380951e634e2c207b1e3653ea6f3b0c4569320effc8d195e7afb8353401a6e8cba6be3d6dcda58c4bfcffef41de7889d778098d5
> $ gpg --verify apache-openmeetings-6.2.0-src.zip.asc
> apache-openmeetings-6.2.0-src.zip
> gpg: Signature made Thu 21 Oct 2021 10:20:04 AM CEST
> gpg: using RSA key BF13CF11F9C90CBE441309AB005516BF93A30395
> gpg: BAD signature from "Sebastian Wagner " [unknown]
> {code}
> I
[jira] [Commented] (OPENMEETINGS-2697) Add optional configuration so that Global chat shows messages only from users that are in same group
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17436394#comment-17436394 ] Sebastian Wagner commented on OPENMEETINGS-2697: Global chat, the one displayed when entering the dashboard and browsing pages within OpenMeetings (e.g. going to private messages, calendar or list of rooms). There is currently no ability to configure that to be "group only". All chat messages are public. Which makes it hard if there are two separated group of users on a single server instance and you would like to prevent them from mixing. E.g. if you have two separated groups from different companies using the same OpenMeetings instance. They don't want to see chat messages from a different company on the same OpenMeetings server. Which makes the "group" feature difficult to use for that use-case. You would need to have complete separated servers. Which may not be worth it (e.g. if each company only have 5-10 users). > Add optional configuration so that Global chat shows messages only from users > that are in same group > > > Key: OPENMEETINGS-2697 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2697 > Project: Openmeetings > Issue Type: Task > Components: Chat >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > When posting a message in the global chat with user1 that is only member of > group1, and then logging in with user2 that is only member of group2 then you > should not see user1 messages in the group chat. (Global chat is the chat on > the dashboard) > This is not consistent to other parts of OpenMeetings. User1 and user2 are > not be able to search/find each other when searching for users when using > other parts of OpenMeetings (Private messages, Calendar, other parts of > OpenMeetings) > Otherwise you can't separated groups. Via the global chat you can add users > across groups that should not see each other. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2697) Add optional configuration so that Global chat shows messages only from users that are in same group
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17436391#comment-17436391 ] Sebastian Wagner commented on OPENMEETINGS-2697: If there are other ways to achieve the same, happy to hear. > Add optional configuration so that Global chat shows messages only from users > that are in same group > > > Key: OPENMEETINGS-2697 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2697 > Project: Openmeetings > Issue Type: Task > Components: Chat >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > When posting a message in the global chat with user1 that is only member of > group1, and then logging in with user2 that is only member of group2 then you > should not see user1 messages in the group chat. (Global chat is the chat on > the dashboard) > This is not consistent to other parts of OpenMeetings. User1 and user2 are > not be able to search/find each other when searching for users when using > other parts of OpenMeetings (Private messages, Calendar, other parts of > OpenMeetings) > Otherwise you can't separated groups. Via the global chat you can add users > across groups that should not see each other. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2697) Add optional configuration so that Global chat shows messages only from users that are in same group
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17436370#comment-17436370
]
Sebastian Wagner commented on OPENMEETINGS-2697:
{quote}Now I'm confused :(
You create JIRA stating: "When posting a message in the global chat with user1
that is only member of group1, and then logging in with user2 that is only
member of group2 then you should not see user1 messages in the group chat."
I read this as: "only messages from own group should be visible to user"
Then you wrote: " this chat is the only place where you can see users of other
groups. Which I think is right. You should be able to contact, invite or access
users in other groups."
Which sounds to me like messages from all users should be visible
(no option to contact otherwise )
{quote}
I meant _only messages from own group should be visible to user_
=> yes. but if that is not desired to have the ability to configure it and make
it optional
{quote}Global chat is Global chat
nothing to change
{quote}
The reason I'm asking is around having the ability to make it possible to
separate users in groups. Which is almost working. The global chat seems to be
one of the only places that doesn't quite work.
> Add optional configuration so that Global chat shows messages only from users
> that are in same group
>
>
> Key: OPENMEETINGS-2697
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2697
> Project: Openmeetings
> Issue Type: Task
> Components: Chat
>Affects Versions: 7.0.0
>Reporter: Sebastian Wagner
>Priority: Major
> Fix For: 7.0.0
>
>
> When posting a message in the global chat with user1 that is only member of
> group1, and then logging in with user2 that is only member of group2 then you
> should not see user1 messages in the group chat. (Global chat is the chat on
> the dashboard)
> This is not consistent to other parts of OpenMeetings. User1 and user2 are
> not be able to search/find each other when searching for users when using
> other parts of OpenMeetings (Private messages, Calendar, other parts of
> OpenMeetings)
> Otherwise you can't separated groups. Via the global chat you can add users
> across groups that should not see each other.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OPENMEETINGS-2697) Add optional configuration so that Global chat shows messages only from users that are in same group
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner updated OPENMEETINGS-2697: --- Summary: Add optional configuration so that Global chat shows messages only from users that are in same group (was: Global chat should not show messages from users that are not in your group) > Add optional configuration so that Global chat shows messages only from users > that are in same group > > > Key: OPENMEETINGS-2697 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2697 > Project: Openmeetings > Issue Type: Task > Components: Chat >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > When posting a message in the global chat with user1 that is only member of > group1, and then logging in with user2 that is only member of group2 then you > should not see user1 messages in the group chat. (Global chat is the chat on > the dashboard) > This is not consistent to other parts of OpenMeetings. User1 and user2 are > not be able to search/find each other when searching for users when using > other parts of OpenMeetings (Private messages, Calendar, other parts of > OpenMeetings) > Otherwise you can't separated groups. Via the global chat you can add users > across groups that should not see each other. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2697) Global chat should not show messages from users that are not in your group
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17435774#comment-17435774 ] Sebastian Wagner commented on OPENMEETINGS-2697: How about adding a configuration so that you can optionally change the behaviour? Cause I think this chat is the only place where you can see users of other groups. Which I think is right. You should be able to contact, invite or access users in other groups. > Global chat should not show messages from users that are not in your group > -- > > Key: OPENMEETINGS-2697 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2697 > Project: Openmeetings > Issue Type: Task > Components: Chat >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > When posting a message in the global chat with user1 that is only member of > group1, and then logging in with user2 that is only member of group2 then you > should not see user1 messages in the group chat. (Global chat is the chat on > the dashboard) > This is not consistent to other parts of OpenMeetings. User1 and user2 are > not be able to search/find each other when searching for users when using > other parts of OpenMeetings (Private messages, Calendar, other parts of > OpenMeetings) > Otherwise you can't separated groups. Via the global chat you can add users > across groups that should not see each other. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OPENMEETINGS-2697) Global chat should not show messages from users that are not in your group
Sebastian Wagner created OPENMEETINGS-2697: -- Summary: Global chat should not show messages from users that are not in your group Key: OPENMEETINGS-2697 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2697 Project: Openmeetings Issue Type: Task Components: Chat Affects Versions: 7.0.0 Reporter: Sebastian Wagner Fix For: 7.0.0 When posting a message in the global chat with user1 that is only member of group1, and then logging in with user2 that is only member of group2 then you should not see user1 messages in the group chat. (Global chat is the chat on the dashboard) This is not consistent to other parts of OpenMeetings. User1 and user2 are not be able to search/find each other when searching for users when using other parts of OpenMeetings (Private messages, Calendar, other parts of OpenMeetings) Otherwise you can't separated groups. Via the global chat you can add users across groups that should not see each other. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (OPENMEETINGS-2695) Update website screenshots
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner resolved OPENMEETINGS-2695. Resolution: Fixed > Update website screenshots > -- > > Key: OPENMEETINGS-2695 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2695 > Project: Openmeetings > Issue Type: Task > Components: Documentation >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Fix For: 7.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OPENMEETINGS-2695) Update website screenshots
Sebastian Wagner created OPENMEETINGS-2695: -- Summary: Update website screenshots Key: OPENMEETINGS-2695 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2695 Project: Openmeetings Issue Type: Task Components: Documentation Affects Versions: 7.0.0 Reporter: Sebastian Wagner Assignee: Sebastian Wagner Fix For: 7.0.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (OPENMEETINGS-2692) Update manifest file path to use application.base.url
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Wagner resolved OPENMEETINGS-2692.
Resolution: Fixed
> Update manifest file path to use application.base.url
> -
>
> Key: OPENMEETINGS-2692
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2692
> Project: Openmeetings
> Issue Type: Task
> Components: Mobile client
>Affects Versions: 7.0.0
>Reporter: Sebastian Wagner
>Assignee: Sebastian Wagner
>Priority: Major
> Fix For: 6.2.0
>
>
> Address webapp path.
>
> [~solomax]:
> {quote}this might be very inaccurate
> for ex. OpenmeetingsVariables.getApplicationName() == OpenMeetings - Next
>
> I believe it's better to use application.base.url for this
>
> And since this is calculated I would create and pass variable or create
> method for this
> {quote}
>
> See: [https://github.com/apache/openmeetings/pull/164#discussion_r730433443]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OPENMEETINGS-2280) Android landscape mode cannot sign up as virtual keyboard covers UI
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner updated OPENMEETINGS-2280: --- Fix Version/s: (was: 7.0.0) 6.2.0 > Android landscape mode cannot sign up as virtual keyboard covers UI > --- > > Key: OPENMEETINGS-2280 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2280 > Project: Openmeetings > Issue Type: Bug > Components: UI >Affects Versions: 5.0.0-M3, 5.0.0-M4 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Fix For: 6.2.0 > > > In Android, when in landscape mode, when going to the sign up screen the > virtual keyboard covers the UI. And the UI doesn't allow scrolling, so you > can't go to the bottom of the screen to see the captch. > Needs screenshot -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (OPENMEETINGS-2681) Gap in taking space of screen and part of conference moving into negative margin outside viewport
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner resolved OPENMEETINGS-2681. Resolution: Fixed > Gap in taking space of screen and part of conference moving into negative > margin outside viewport > - > > Key: OPENMEETINGS-2681 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2681 > Project: Openmeetings > Issue Type: Bug >Affects Versions: 6.1.0, 6.2.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Fix For: 6.2.0 > > Attachments: image-2021-10-09-16-19-47-929.png, > image-2021-10-09-16-20-37-082.png, image-2021-10-09-16-26-05-161.png, > image-2021-10-09-16-26-22-561.png > > > When entering the conference room there are some calculations happening that > end up making: > *On the bottom of the screen there is an around 4px margin on all of the > elements to the edge of the browser:* > !image-2021-10-09-16-19-47-929.png|width=264,height=101! > => There shouldn't be a 4px white gap between the "Activities and actions" > and the browser window. > *The menu bar is not completely visible, roughly 4px are outside of the > visible area:* > !image-2021-10-09-16-20-37-082.png! > => There should be equal margin under the menu items and above. But there > isn't. > *You can also see the effect when you enter and exit a room and then look at > the menu logo:* > Before entering the room the logo is displayed correctly: > !image-2021-10-09-16-26-05-161.png! > When exiting the room the logo is moved outside of the viewport by 4-6pixels: > !image-2021-10-09-16-26-22-561.png! > > > ==> The reason for both is that somehow when the whiteboard is loaded the > entire body of the HTML is moved into a 4-6px negative margin. > You can verify that by disabling the whiteboard. The effect is gone. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OPENMEETINGS-2681) Gap in taking space of screen and part of conference moving into negative margin outside viewport
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner updated OPENMEETINGS-2681: --- Fix Version/s: (was: 7.0.0) 6.2.0 > Gap in taking space of screen and part of conference moving into negative > margin outside viewport > - > > Key: OPENMEETINGS-2681 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2681 > Project: Openmeetings > Issue Type: Bug >Affects Versions: 6.1.0, 6.2.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Fix For: 6.2.0 > > Attachments: image-2021-10-09-16-19-47-929.png, > image-2021-10-09-16-20-37-082.png, image-2021-10-09-16-26-05-161.png, > image-2021-10-09-16-26-22-561.png > > > When entering the conference room there are some calculations happening that > end up making: > *On the bottom of the screen there is an around 4px margin on all of the > elements to the edge of the browser:* > !image-2021-10-09-16-19-47-929.png|width=264,height=101! > => There shouldn't be a 4px white gap between the "Activities and actions" > and the browser window. > *The menu bar is not completely visible, roughly 4px are outside of the > visible area:* > !image-2021-10-09-16-20-37-082.png! > => There should be equal margin under the menu items and above. But there > isn't. > *You can also see the effect when you enter and exit a room and then look at > the menu logo:* > Before entering the room the logo is displayed correctly: > !image-2021-10-09-16-26-05-161.png! > When exiting the room the logo is moved outside of the viewport by 4-6pixels: > !image-2021-10-09-16-26-22-561.png! > > > ==> The reason for both is that somehow when the whiteboard is loaded the > entire body of the HTML is moved into a 4-6px negative margin. > You can verify that by disabling the whiteboard. The effect is gone. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OPENMEETINGS-2686) Can't click buttons to share you webcam or microphone on mobile screen in portrait mode
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner updated OPENMEETINGS-2686: --- Fix Version/s: (was: 7.0.0) 6.2.0 > Can't click buttons to share you webcam or microphone on mobile screen in > portrait mode > --- > > Key: OPENMEETINGS-2686 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2686 > Project: Openmeetings > Issue Type: Task > Components: Mobile client >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 6.2.0 > > Attachments: image-2021-10-10-11-19-36-961.png, > image-2021-10-10-11-20-01-343.png > > > When using a Mobile phone in portrait mode - the buttons to share webcam or > microphone are really hard to click on a touch screen. > 9 out of 10 you will hit something other than the icon/button you intended. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OPENMEETINGS-2693) Update config for manifest icons to be able to customise icon easily
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner updated OPENMEETINGS-2693: --- Fix Version/s: (was: 7.0.0) 6.2.0 > Update config for manifest icons to be able to customise icon easily > > > Key: OPENMEETINGS-2693 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2693 > Project: Openmeetings > Issue Type: Task > Components: Mobile client >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 6.2.0 > > > Update documentation to be able to easily update the icon for the manifest > file -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (OPENMEETINGS-2681) Gap in taking space of screen and part of conference moving into negative margin outside viewport
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner reopened OPENMEETINGS-2681: > Gap in taking space of screen and part of conference moving into negative > margin outside viewport > - > > Key: OPENMEETINGS-2681 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2681 > Project: Openmeetings > Issue Type: Bug >Affects Versions: 6.1.0, 6.2.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Fix For: 7.0.0 > > Attachments: image-2021-10-09-16-19-47-929.png, > image-2021-10-09-16-20-37-082.png, image-2021-10-09-16-26-05-161.png, > image-2021-10-09-16-26-22-561.png > > > When entering the conference room there are some calculations happening that > end up making: > *On the bottom of the screen there is an around 4px margin on all of the > elements to the edge of the browser:* > !image-2021-10-09-16-19-47-929.png|width=264,height=101! > => There shouldn't be a 4px white gap between the "Activities and actions" > and the browser window. > *The menu bar is not completely visible, roughly 4px are outside of the > visible area:* > !image-2021-10-09-16-20-37-082.png! > => There should be equal margin under the menu items and above. But there > isn't. > *You can also see the effect when you enter and exit a room and then look at > the menu logo:* > Before entering the room the logo is displayed correctly: > !image-2021-10-09-16-26-05-161.png! > When exiting the room the logo is moved outside of the viewport by 4-6pixels: > !image-2021-10-09-16-26-22-561.png! > > > ==> The reason for both is that somehow when the whiteboard is loaded the > entire body of the HTML is moved into a 4-6px negative margin. > You can verify that by disabling the whiteboard. The effect is gone. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OPENMEETINGS-2692) Update manifest file path to use application.base.url
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Wagner updated OPENMEETINGS-2692:
---
Fix Version/s: (was: 7.0.0)
6.2.0
> Update manifest file path to use application.base.url
> -
>
> Key: OPENMEETINGS-2692
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2692
> Project: Openmeetings
> Issue Type: Task
> Components: Mobile client
>Affects Versions: 7.0.0
>Reporter: Sebastian Wagner
>Assignee: Sebastian Wagner
>Priority: Major
> Fix For: 6.2.0
>
>
> Address webapp path.
>
> [~solomax]:
> {quote}this might be very inaccurate
> for ex. OpenmeetingsVariables.getApplicationName() == OpenMeetings - Next
>
> I believe it's better to use application.base.url for this
>
> And since this is calculated I would create and pass variable or create
> method for this
> {quote}
>
> See: [https://github.com/apache/openmeetings/pull/164#discussion_r730433443]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OPENMEETINGS-2685) Login form on Mobile screens not mobile-friendly sizes of buttons
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner updated OPENMEETINGS-2685: --- Fix Version/s: (was: 7.0.0) 6.2.0 > Login form on Mobile screens not mobile-friendly sizes of buttons > - > > Key: OPENMEETINGS-2685 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2685 > Project: Openmeetings > Issue Type: New Feature > Components: iOS, Mobile client >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 6.2.0 > > Attachments: image-2021-10-10-10-39-43-085.png, > image-2021-10-10-11-15-24-791.png > > > You can hardly click into the input boxes when on a mobile device: > !image-2021-10-10-10-39-43-085.png|width=253,height=447! > It is very difficult to click anything. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OPENMEETINGS-2684) Rotating device landscape in iOS leaves whitespace and doesn't use full height
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner updated OPENMEETINGS-2684: --- Fix Version/s: (was: 7.0.0) 6.2.0 > Rotating device landscape in iOS leaves whitespace and doesn't use full height > -- > > Key: OPENMEETINGS-2684 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2684 > Project: Openmeetings > Issue Type: New Feature > Components: iOS, Mobile client >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 6.2.0 > > Attachments: IMG_0341_2.png > > > When loading the application in portrait mode and then rotating it into > landscape it leaves a whitespace on the bottom. > > !IMG_0341_2.png|width=528,height=297! > The reason is because it calculates the height including the browsers > URL/navigation bar when applying 100%. But when rotating to landscape iOS > hides the URL/navigation bar, so its actually larger than the browser width. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (OPENMEETINGS-2683) Explore what features of manifest file are useful for OpenMeetings
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner resolved OPENMEETINGS-2683. Resolution: Fixed > Explore what features of manifest file are useful for OpenMeetings > -- > > Key: OPENMEETINGS-2683 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2683 > Project: Openmeetings > Issue Type: New Feature > Components: Mobile client >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 6.2.0 > > > OpenMeetings on a Mobile device is almost unusable because the aspect ratio > on portrait mode is almost impossible to click any button. > As well as the layout of the application is more width than height. > Apparently there is a way to force the browser into landscape mode using the > manifest.json file. There might be also other features out of the manifest > file that may improve the experience. It is designed to help Progress Web > Apps to more look and feel like Native Apps on Mobile devices. > See also: > * [https://www.w3.org/TR/appmanifest/] > * [https://developer.mozilla.org/en-US/docs/Web/Manifest] > * [https://web.dev/add-manifest/] > * > [https://stackoverflow.com/questions/14360581/force-landscape-orientation-mode] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OPENMEETINGS-2679) Cant share Cam/Video on iOS/Mobile (Audio-Only works fine)
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner updated OPENMEETINGS-2679: --- Fix Version/s: (was: 7.0.0) 6.2.0 > Cant share Cam/Video on iOS/Mobile (Audio-Only works fine) > -- > > Key: OPENMEETINGS-2679 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2679 > Project: Openmeetings > Issue Type: Bug > Components: iOS, Mobile client >Affects Versions: 6.1.0, 6.2.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Critical > Fix For: 6.2.0 > > Attachments: Chrome-working.png, iOS-Safari-Fail.txt.rtf, > image-2021-10-03-11-20-27-340.png, image-2021-10-03-11-21-11-649.png, > image-2021-10-03-11-23-34-091.png, image-2021-10-08-13-34-37-328.png, > macOS-Chrome-Successful.txt.rtf, macOS-Chrome-Successful.txt.rtf > > > On iOS (no matter if using Safari or Chrome) you can share the webcam but on > the other viewers side the stream doesn't start. Just shows empty video box > This only affects Safari/Chrome on "iOS" (= Mobile). Not Safari / Chrome on > macOS (Desktop) > Screenshots of mobile devices publishing: > iOS Safari: > !image-2021-10-03-11-20-27-340.png|width=279,height=486! > iOS/Chrome: > !image-2021-10-03-11-21-11-649.png|width=451,height=249! > But on the receiving side (using Chrome on desktop) you can just see: > !image-2021-10-03-11-23-34-091.png|width=735,height=373! > > This could be related to OPENMEETINGS-2678, but I am not sure. > There is no stack trace on the receiving side or JavaScript error on the > receiving end. It seems to even think this video is playing as it asks for > permission to allow playback. But then just shows an empty video pod. > > This issue can be reproduced in the linked OpenMeetings versions 10 out 10 > times. It is 100% reproduce-able. > > Funny enough: Audio only publishing on iOS/ Safari (and also iOS/Chrome) > works :) You can publish the mic on the iOS/ Safari or iOS/Chrome side and > hear the audio on the receiving side. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OPENMEETINGS-2683) Explore what features of manifest file are useful for OpenMeetings
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner updated OPENMEETINGS-2683: --- Fix Version/s: (was: 7.0.0) 6.2.0 > Explore what features of manifest file are useful for OpenMeetings > -- > > Key: OPENMEETINGS-2683 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2683 > Project: Openmeetings > Issue Type: New Feature > Components: Mobile client >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 6.2.0 > > > OpenMeetings on a Mobile device is almost unusable because the aspect ratio > on portrait mode is almost impossible to click any button. > As well as the layout of the application is more width than height. > Apparently there is a way to force the browser into landscape mode using the > manifest.json file. There might be also other features out of the manifest > file that may improve the experience. It is designed to help Progress Web > Apps to more look and feel like Native Apps on Mobile devices. > See also: > * [https://www.w3.org/TR/appmanifest/] > * [https://developer.mozilla.org/en-US/docs/Web/Manifest] > * [https://web.dev/add-manifest/] > * > [https://stackoverflow.com/questions/14360581/force-landscape-orientation-mode] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (OPENMEETINGS-2683) Explore what features of manifest file are useful for OpenMeetings
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner reopened OPENMEETINGS-2683: > Explore what features of manifest file are useful for OpenMeetings > -- > > Key: OPENMEETINGS-2683 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2683 > Project: Openmeetings > Issue Type: New Feature > Components: Mobile client >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > OpenMeetings on a Mobile device is almost unusable because the aspect ratio > on portrait mode is almost impossible to click any button. > As well as the layout of the application is more width than height. > Apparently there is a way to force the browser into landscape mode using the > manifest.json file. There might be also other features out of the manifest > file that may improve the experience. It is designed to help Progress Web > Apps to more look and feel like Native Apps on Mobile devices. > See also: > * [https://www.w3.org/TR/appmanifest/] > * [https://developer.mozilla.org/en-US/docs/Web/Manifest] > * [https://web.dev/add-manifest/] > * > [https://stackoverflow.com/questions/14360581/force-landscape-orientation-mode] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OPENMEETINGS-2680) Openmeetings / next demo server issues
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Wagner updated OPENMEETINGS-2680:
---
Fix Version/s: (was: 7.0.0)
6.2.0
> Openmeetings / next demo server issues
> --
>
> Key: OPENMEETINGS-2680
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2680
> Project: Openmeetings
> Issue Type: Bug
> Components: iOS
>Affects Versions: 7.0.0
>Reporter: Sebastian Wagner
>Assignee: Maxim Solodovnik
>Priority: Major
> Fix For: 6.2.0
>
> Attachments: image-2021-10-06-09-18-45-862.png,
> image-2021-10-06-09-20-43-547.png
>
>
> See below errors from trying to loging into
> [https://om.alteametasoft.com:8443/next/]
> Console errors:
>
> {code:java}
> Refused to load
> https://fonts.googleapis.com/css2?family=Roboto:wght@400;500;700=swap
> because it does not appear in the style-src directive of the Content Security
> Policy.
> ReferenceError: Can't find variable: Notification
> {code}
>
> Screenshot of console errors:
> !image-2021-10-06-09-18-45-862.png|width=891,height=195!
> Screenshot of mobile phone being stuck on loading the dashboard:
> !image-2021-10-06-09-20-43-547.png|width=194,height=345!
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OPENMEETINGS-2678) OpenMeetings using non support JavaScript API in iOS - ReferenceError: Can't find variable: Notification
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner updated OPENMEETINGS-2678: --- Fix Version/s: (was: 7.0.0) 6.2.0 > OpenMeetings using non support JavaScript API in iOS - ReferenceError: Can't > find variable: Notification > > > Key: OPENMEETINGS-2678 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2678 > Project: Openmeetings > Issue Type: Bug > Components: iOS, Mobile client >Affects Versions: 6.1.0, 6.2.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Critical > Fix For: 6.2.0 > > Attachments: image-2021-10-03-11-11-05-588.png, > image-2021-10-03-11-12-31-066.png > > > Below stack trace is from iOS (Mobile) Safari. But the same behaviour is in > Chrome on iOS. > Mobile browser console stack trace: > !image-2021-10-03-11-11-05-588.png|width=845,height=121! > !image-2021-10-03-11-12-31-066.png|width=1024,height=291! > > The "Notification" API is not supported by iOS/Mobile. > See: > [https://developer.mozilla.org/en-US/docs/Web/API/Notification/requestPermission#browser_compatibility] > => Safari/iOS = Not supported. And I think Chrome/iOS is not on the table but > its also not supported. It behaves the same I think. > > The unhandled promise rejection could also additionally affect it in case its > related to playing back sound, see OPENMEETINGS-2677 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2693) Update config for manifest icons to be able to customise icon easily
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17430881#comment-17430881 ] Sebastian Wagner commented on OPENMEETINGS-2693: Website still needs to be synced once next release is done > Update config for manifest icons to be able to customise icon easily > > > Key: OPENMEETINGS-2693 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2693 > Project: Openmeetings > Issue Type: Task > Components: Mobile client >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > Update documentation to be able to easily update the icon for the manifest > file -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (OPENMEETINGS-2693) Update config for manifest icons to be able to customise icon easily
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner resolved OPENMEETINGS-2693. Resolution: Fixed > Update config for manifest icons to be able to customise icon easily > > > Key: OPENMEETINGS-2693 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2693 > Project: Openmeetings > Issue Type: Task > Components: Mobile client >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > Update documentation to be able to easily update the icon for the manifest > file -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (OPENMEETINGS-2692) Update manifest file path to use application.base.url
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Wagner reopened OPENMEETINGS-2692:
Review comments
> Update manifest file path to use application.base.url
> -
>
> Key: OPENMEETINGS-2692
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2692
> Project: Openmeetings
> Issue Type: Task
> Components: Mobile client
>Affects Versions: 7.0.0
>Reporter: Sebastian Wagner
>Assignee: Sebastian Wagner
>Priority: Major
> Fix For: 7.0.0
>
>
> Address webapp path.
>
> [~solomax]:
> {quote}this might be very inaccurate
> for ex. OpenmeetingsVariables.getApplicationName() == OpenMeetings - Next
>
> I believe it's better to use application.base.url for this
>
> And since this is calculated I would create and pass variable or create
> method for this
> {quote}
>
> See: [https://github.com/apache/openmeetings/pull/164#discussion_r730433443]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (OPENMEETINGS-2693) Update config for manifest icons to be able to customise icon easily
Sebastian Wagner created OPENMEETINGS-2693: -- Summary: Update config for manifest icons to be able to customise icon easily Key: OPENMEETINGS-2693 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2693 Project: Openmeetings Issue Type: Task Components: Mobile client Affects Versions: 7.0.0 Reporter: Sebastian Wagner Assignee: Sebastian Wagner Fix For: 7.0.0 Update documentation to be able to easily update the icon for the manifest file -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (OPENMEETINGS-2692) Update manifest file path to use application.base.url
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Wagner resolved OPENMEETINGS-2692.
Resolution: Fixed
> Update manifest file path to use application.base.url
> -
>
> Key: OPENMEETINGS-2692
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2692
> Project: Openmeetings
> Issue Type: Task
> Components: Mobile client
>Affects Versions: 7.0.0
>Reporter: Sebastian Wagner
>Assignee: Sebastian Wagner
>Priority: Major
> Fix For: 7.0.0
>
>
> Address webapp path.
>
> [~solomax]:
> {quote}this might be very inaccurate
> for ex. OpenmeetingsVariables.getApplicationName() == OpenMeetings - Next
>
> I believe it's better to use application.base.url for this
>
> And since this is calculated I would create and pass variable or create
> method for this
> {quote}
>
> See: [https://github.com/apache/openmeetings/pull/164#discussion_r730433443]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OPENMEETINGS-2692) Update manifest file path to use application.base.url
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Wagner updated OPENMEETINGS-2692:
---
Description:
Address webapp path.
[~solomax]:
{quote}this might be very inaccurate
for ex. OpenmeetingsVariables.getApplicationName() == OpenMeetings - Next
I believe it's better to use application.base.url for this
And since this is calculated I would create and pass variable or create method
for this
{quote}
See: [https://github.com/apache/openmeetings/pull/164#discussion_r730433443]
was:
this might be very inaccurate
for ex. {{OpenmeetingsVariables.getApplicationName()}} == {{OpenMeetings -
Next}}
I believe it's better to use {{application.base.url}} for this
And since this is calculated I would create and pass variable or create method
for this
See: https://github.com/apache/openmeetings/pull/164#discussion_r730433443
> Update manifest file path to use application.base.url
> -
>
> Key: OPENMEETINGS-2692
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2692
> Project: Openmeetings
> Issue Type: Task
> Components: Mobile client
>Affects Versions: 7.0.0
>Reporter: Sebastian Wagner
>Assignee: Sebastian Wagner
>Priority: Major
> Fix For: 7.0.0
>
>
> Address webapp path.
>
> [~solomax]:
> {quote}this might be very inaccurate
> for ex. OpenmeetingsVariables.getApplicationName() == OpenMeetings - Next
>
> I believe it's better to use application.base.url for this
>
> And since this is calculated I would create and pass variable or create
> method for this
> {quote}
>
> See: [https://github.com/apache/openmeetings/pull/164#discussion_r730433443]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (OPENMEETINGS-2692) Update manifest file path to use application.base.url
Sebastian Wagner created OPENMEETINGS-2692:
--
Summary: Update manifest file path to use application.base.url
Key: OPENMEETINGS-2692
URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2692
Project: Openmeetings
Issue Type: Task
Components: Mobile client
Affects Versions: 7.0.0
Reporter: Sebastian Wagner
Assignee: Sebastian Wagner
Fix For: 7.0.0
this might be very inaccurate
for ex. {{OpenmeetingsVariables.getApplicationName()}} == {{OpenMeetings -
Next}}
I believe it's better to use {{application.base.url}} for this
And since this is calculated I would create and pass variable or create method
for this
See: https://github.com/apache/openmeetings/pull/164#discussion_r730433443
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (OPENMEETINGS-2683) Explore what features of manifest file are useful for OpenMeetings
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner closed OPENMEETINGS-2683. -- Resolution: Fixed > Explore what features of manifest file are useful for OpenMeetings > -- > > Key: OPENMEETINGS-2683 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2683 > Project: Openmeetings > Issue Type: New Feature > Components: Mobile client >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > OpenMeetings on a Mobile device is almost unusable because the aspect ratio > on portrait mode is almost impossible to click any button. > As well as the layout of the application is more width than height. > Apparently there is a way to force the browser into landscape mode using the > manifest.json file. There might be also other features out of the manifest > file that may improve the experience. It is designed to help Progress Web > Apps to more look and feel like Native Apps on Mobile devices. > See also: > * [https://www.w3.org/TR/appmanifest/] > * [https://developer.mozilla.org/en-US/docs/Web/Manifest] > * [https://web.dev/add-manifest/] > * > [https://stackoverflow.com/questions/14360581/force-landscape-orientation-mode] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2683) Explore what features of manifest file are useful for OpenMeetings
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17429630#comment-17429630 ] Sebastian Wagner commented on OPENMEETINGS-2683: Done. I've added some details and screenshots in the PR and linked wiki page. It's actually quite a small PR part from adding a few icons in different resolutions. This adds so that when using the mobile browsers "Add to home screen" function: * Show a nice icon in the screens and on the mobile device * Show a nice name for the app in the mobile * Show a nice splash screen when opening OpenMeetings after saving to home screen on the mobile * Remove url and navigation bar in browser so it uses the full screen size * Fix to landscape mode (Android only, iOS does not support it) * Show a nice icon and name when rotating through currently open apps on the mobile device You _may_ call this PWA mode. However really it's just a fancy bookmark. However it makes the application look much more like a native mobile app. And it makes it easier to control the url/navigation bar of the browser. See documentation on mobile experience or iOS and Android here: [https://cwiki.apache.org/confluence/display/OPENMEETINGS/OpenMeetings+Mobile#OpenMeetingsMobile-Savetohomescreentocreatebettermobileexperience] *It has no impact on any other functionality of OpenMeetings (as well as it does not require any rewrite of any functionality).* What could be done next: * Adding a prompt in iOS to suggest landscape mode (iOS "add to home screen" functionality does not support orientation=landscape feature, needs user prompt when in portrait mode) * Potentially something that makes this "Add to home screen" easier to find for users * Documentation on how to release to the App store. Using this "Add to home screen" mode it is easier to also package it up to release OpenMeetings to an App store > Explore what features of manifest file are useful for OpenMeetings > -- > > Key: OPENMEETINGS-2683 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2683 > Project: Openmeetings > Issue Type: New Feature > Components: Mobile client >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > OpenMeetings on a Mobile device is almost unusable because the aspect ratio > on portrait mode is almost impossible to click any button. > As well as the layout of the application is more width than height. > Apparently there is a way to force the browser into landscape mode using the > manifest.json file. There might be also other features out of the manifest > file that may improve the experience. It is designed to help Progress Web > Apps to more look and feel like Native Apps on Mobile devices. > See also: > * [https://www.w3.org/TR/appmanifest/] > * [https://developer.mozilla.org/en-US/docs/Web/Manifest] > * [https://web.dev/add-manifest/] > * > [https://stackoverflow.com/questions/14360581/force-landscape-orientation-mode] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2683) Explore what features of manifest file are useful for OpenMeetings
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17426955#comment-17426955 ] Sebastian Wagner commented on OPENMEETINGS-2683: Yeah doing a PMA (progressive web application) is an option I think. In general it means nothing else then: Saving the page to your home screen. Thats it. It has some advantages and provides additional options (eg controlling full screen). This could be especially interesting for the Mobile Version of OpenMeetings. In order to compete with native Mobile Apps. It makes it more like look and feel like an actual Mobile App, since you can start OpenMeetings directly from an icon on your device. > Explore what features of manifest file are useful for OpenMeetings > -- > > Key: OPENMEETINGS-2683 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2683 > Project: Openmeetings > Issue Type: New Feature > Components: Mobile client >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > OpenMeetings on a Mobile device is almost unusable because the aspect ratio > on portrait mode is almost impossible to click any button. > As well as the layout of the application is more width than height. > Apparently there is a way to force the browser into landscape mode using the > manifest.json file. There might be also other features out of the manifest > file that may improve the experience. It is designed to help Progress Web > Apps to more look and feel like Native Apps on Mobile devices. > See also: > * [https://www.w3.org/TR/appmanifest/] > * [https://developer.mozilla.org/en-US/docs/Web/Manifest] > * [https://web.dev/add-manifest/] > * > [https://stackoverflow.com/questions/14360581/force-landscape-orientation-mode] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2680) Openmeetings / next demo server issues
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17426953#comment-17426953
]
Sebastian Wagner commented on OPENMEETINGS-2680:
If we decide to release master as 6.2.0 we can move this ticket (and any other
done) from v7.0.0 to v6.2.0
> Openmeetings / next demo server issues
> --
>
> Key: OPENMEETINGS-2680
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2680
> Project: Openmeetings
> Issue Type: Bug
> Components: iOS
>Affects Versions: 7.0.0
>Reporter: Sebastian Wagner
>Assignee: Maxim Solodovnik
>Priority: Major
> Fix For: 7.0.0
>
> Attachments: image-2021-10-06-09-18-45-862.png,
> image-2021-10-06-09-20-43-547.png
>
>
> See below errors from trying to loging into
> [https://om.alteametasoft.com:8443/next/]
> Console errors:
>
> {code:java}
> Refused to load
> https://fonts.googleapis.com/css2?family=Roboto:wght@400;500;700=swap
> because it does not appear in the style-src directive of the Content Security
> Policy.
> ReferenceError: Can't find variable: Notification
> {code}
>
> Screenshot of console errors:
> !image-2021-10-06-09-18-45-862.png|width=891,height=195!
> Screenshot of mobile phone being stuck on loading the dashboard:
> !image-2021-10-06-09-20-43-547.png|width=194,height=345!
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (OPENMEETINGS-2684) Rotating device landscape in iOS leaves whitespace and doesn't use full height
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner resolved OPENMEETINGS-2684. Resolution: Fixed > Rotating device landscape in iOS leaves whitespace and doesn't use full height > -- > > Key: OPENMEETINGS-2684 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2684 > Project: Openmeetings > Issue Type: New Feature > Components: iOS, Mobile client >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > Attachments: IMG_0341_2.png > > > When loading the application in portrait mode and then rotating it into > landscape it leaves a whitespace on the bottom. > > !IMG_0341_2.png|width=528,height=297! > The reason is because it calculates the height including the browsers > URL/navigation bar when applying 100%. But when rotating to landscape iOS > hides the URL/navigation bar, so its actually larger than the browser width. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2686) Can't click buttons to share you webcam or microphone on mobile screen in portrait mode
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17426720#comment-17426720 ] Sebastian Wagner commented on OPENMEETINGS-2686: New portrait mode: !image-2021-10-10-11-19-36-961.png|width=305,height=542! New landscape mode: !image-2021-10-10-11-20-01-343.png|width=555,height=312! > Can't click buttons to share you webcam or microphone on mobile screen in > portrait mode > --- > > Key: OPENMEETINGS-2686 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2686 > Project: Openmeetings > Issue Type: Task > Components: Mobile client >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > Attachments: image-2021-10-10-11-19-36-961.png, > image-2021-10-10-11-20-01-343.png > > > When using a Mobile phone in portrait mode - the buttons to share webcam or > microphone are really hard to click on a touch screen. > 9 out of 10 you will hit something other than the icon/button you intended. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OPENMEETINGS-2686) Can't click buttons to share you webcam or microphone on mobile screen in portrait mode
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner updated OPENMEETINGS-2686: --- Attachment: image-2021-10-10-11-20-01-343.png > Can't click buttons to share you webcam or microphone on mobile screen in > portrait mode > --- > > Key: OPENMEETINGS-2686 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2686 > Project: Openmeetings > Issue Type: Task > Components: Mobile client >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > Attachments: image-2021-10-10-11-19-36-961.png, > image-2021-10-10-11-20-01-343.png > > > When using a Mobile phone in portrait mode - the buttons to share webcam or > microphone are really hard to click on a touch screen. > 9 out of 10 you will hit something other than the icon/button you intended. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OPENMEETINGS-2686) Can't click buttons to share you webcam or microphone on mobile screen in portrait mode
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner updated OPENMEETINGS-2686: --- Attachment: image-2021-10-10-11-19-36-961.png > Can't click buttons to share you webcam or microphone on mobile screen in > portrait mode > --- > > Key: OPENMEETINGS-2686 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2686 > Project: Openmeetings > Issue Type: Task > Components: Mobile client >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > Attachments: image-2021-10-10-11-19-36-961.png > > > When using a Mobile phone in portrait mode - the buttons to share webcam or > microphone are really hard to click on a touch screen. > 9 out of 10 you will hit something other than the icon/button you intended. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OPENMEETINGS-2685) Login form on Mobile screens not mobile-friendly sizes of buttons
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner updated OPENMEETINGS-2685: --- Attachment: image-2021-10-10-11-15-24-791.png > Login form on Mobile screens not mobile-friendly sizes of buttons > - > > Key: OPENMEETINGS-2685 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2685 > Project: Openmeetings > Issue Type: New Feature > Components: iOS, Mobile client >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > Attachments: image-2021-10-10-10-39-43-085.png, > image-2021-10-10-11-15-24-791.png > > > You can hardly click into the input boxes when on a mobile device: > !image-2021-10-10-10-39-43-085.png|width=253,height=447! > It is very difficult to click anything. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2685) Login form on Mobile screens not mobile-friendly sizes of buttons
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17426719#comment-17426719 ] Sebastian Wagner commented on OPENMEETINGS-2685: After change login form uses full width available: !image-2021-10-10-11-15-24-791.png|width=220,height=391! > Login form on Mobile screens not mobile-friendly sizes of buttons > - > > Key: OPENMEETINGS-2685 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2685 > Project: Openmeetings > Issue Type: New Feature > Components: iOS, Mobile client >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > Attachments: image-2021-10-10-10-39-43-085.png, > image-2021-10-10-11-15-24-791.png > > > You can hardly click into the input boxes when on a mobile device: > !image-2021-10-10-10-39-43-085.png|width=253,height=447! > It is very difficult to click anything. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OPENMEETINGS-2685) Login form on Mobile screens not mobile-friendly sizes of buttons
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner updated OPENMEETINGS-2685: --- Summary: Login form on Mobile screens not mobile-friendly sizes of buttons (was: Login form on Mobile screens not user-friendly visibility) > Login form on Mobile screens not mobile-friendly sizes of buttons > - > > Key: OPENMEETINGS-2685 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2685 > Project: Openmeetings > Issue Type: New Feature > Components: iOS, Mobile client >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > Attachments: image-2021-10-10-10-39-43-085.png, > image-2021-10-10-11-15-24-791.png > > > You can hardly click into the input boxes when on a mobile device: > !image-2021-10-10-10-39-43-085.png|width=253,height=447! > It is very difficult to click anything. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2684) Rotating device landscape in iOS leaves whitespace and doesn't use full height
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17426718#comment-17426718 ] Sebastian Wagner commented on OPENMEETINGS-2684: Unfortunate this requires some JS for iOS to work. CSS only does not work > Rotating device landscape in iOS leaves whitespace and doesn't use full height > -- > > Key: OPENMEETINGS-2684 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2684 > Project: Openmeetings > Issue Type: New Feature > Components: iOS, Mobile client >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > Attachments: IMG_0341_2.png > > > When loading the application in portrait mode and then rotating it into > landscape it leaves a whitespace on the bottom. > > !IMG_0341_2.png|width=528,height=297! > The reason is because it calculates the height including the browsers > URL/navigation bar when applying 100%. But when rotating to landscape iOS > hides the URL/navigation bar, so its actually larger than the browser width. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (OPENMEETINGS-2685) Login form on Mobile screens not user-friendly visibility
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner resolved OPENMEETINGS-2685. Resolution: Fixed > Login form on Mobile screens not user-friendly visibility > - > > Key: OPENMEETINGS-2685 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2685 > Project: Openmeetings > Issue Type: New Feature > Components: iOS, Mobile client >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > Attachments: image-2021-10-10-10-39-43-085.png > > > You can hardly click into the input boxes when on a mobile device: > !image-2021-10-10-10-39-43-085.png|width=253,height=447! > It is very difficult to click anything. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (OPENMEETINGS-2280) Android landscape mode cannot sign up as virtual keyboard covers UI
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner resolved OPENMEETINGS-2280. Resolution: Fixed > Android landscape mode cannot sign up as virtual keyboard covers UI > --- > > Key: OPENMEETINGS-2280 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2280 > Project: Openmeetings > Issue Type: Bug > Components: UI >Affects Versions: 5.0.0-M3, 5.0.0-M4 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Fix For: 7.0.0 > > > In Android, when in landscape mode, when going to the sign up screen the > virtual keyboard covers the UI. And the UI doesn't allow scrolling, so you > can't go to the bottom of the screen to see the captch. > Needs screenshot -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (OPENMEETINGS-2686) Can't click buttons to share you webcam or microphone on mobile screen in portrait mode
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner resolved OPENMEETINGS-2686. Resolution: Fixed > Can't click buttons to share you webcam or microphone on mobile screen in > portrait mode > --- > > Key: OPENMEETINGS-2686 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2686 > Project: Openmeetings > Issue Type: Task > Components: Mobile client >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > When using a Mobile phone in portrait mode - the buttons to share webcam or > microphone are really hard to click on a touch screen. > 9 out of 10 you will hit something other than the icon/button you intended. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OPENMEETINGS-2686) Can't click buttons to share you webcam or microphone on mobile screen in portrait mode
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner updated OPENMEETINGS-2686: --- Description: When using a Mobile phone in portrait mode - the buttons to share webcam or microphone are really hard to click on a touch screen. 9 out of 10 you will hit something other than the icon/button you intended. was: When using a Mobile phone - the buttons to share webcam or microphone are really hard to click on a touch screen. 9 out of 10 you will hit something other than the icon/button you intended. On those small viewports/screens it would be great to have some more large buttons on the screen. This could be improved - but potentially forcing the mobile client into landscape mode would be more useful first. > Can't click buttons to share you webcam or microphone on mobile screen in > portrait mode > --- > > Key: OPENMEETINGS-2686 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2686 > Project: Openmeetings > Issue Type: Task > Components: Mobile client >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > When using a Mobile phone in portrait mode - the buttons to share webcam or > microphone are really hard to click on a touch screen. > 9 out of 10 you will hit something other than the icon/button you intended. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OPENMEETINGS-2686) Can't click buttons to share you webcam or microphone on mobile screen
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner updated OPENMEETINGS-2686: --- Issue Type: Task (was: New Feature) > Can't click buttons to share you webcam or microphone on mobile screen > -- > > Key: OPENMEETINGS-2686 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2686 > Project: Openmeetings > Issue Type: Task > Components: Mobile client >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > When using a Mobile phone - the buttons to share webcam or microphone are > really hard to click on a touch screen. > 9 out of 10 you will hit something other than the icon/button you intended. > > On those small viewports/screens it would be great to have some more large > buttons on the screen. > This could be improved - but potentially forcing the mobile client into > landscape mode would be more useful first. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OPENMEETINGS-2686) Can't click buttons to share you webcam or microphone on mobile screen in portrait mode
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner updated OPENMEETINGS-2686: --- Summary: Can't click buttons to share you webcam or microphone on mobile screen in portrait mode (was: Can't click buttons to share you webcam or microphone on mobile screen) > Can't click buttons to share you webcam or microphone on mobile screen in > portrait mode > --- > > Key: OPENMEETINGS-2686 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2686 > Project: Openmeetings > Issue Type: Task > Components: Mobile client >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > When using a Mobile phone - the buttons to share webcam or microphone are > really hard to click on a touch screen. > 9 out of 10 you will hit something other than the icon/button you intended. > > On those small viewports/screens it would be great to have some more large > buttons on the screen. > This could be improved - but potentially forcing the mobile client into > landscape mode would be more useful first. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OPENMEETINGS-2686) Can't click buttons to share you webcam or microphone on mobile screen
Sebastian Wagner created OPENMEETINGS-2686: -- Summary: Can't click buttons to share you webcam or microphone on mobile screen Key: OPENMEETINGS-2686 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2686 Project: Openmeetings Issue Type: New Feature Components: Mobile client Reporter: Sebastian Wagner Assignee: Sebastian Wagner Fix For: 7.0.0 When using a Mobile phone - the buttons to share webcam or microphone are really hard to click on a touch screen. 9 out of 10 you will hit something other than the icon/button you intended. On those small viewports/screens it would be great to have some more large buttons on the screen. This could be improved - but potentially forcing the mobile client into landscape mode would be more useful first. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OPENMEETINGS-2684) Rotating device landscape in iOS leaves whitespace and doesn't use full height
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner updated OPENMEETINGS-2684: --- Description: When loading the application in portrait mode and then rotating it into landscape it leaves a whitespace on the bottom. !IMG_0341_2.png|width=528,height=297! The reason is because it calculates the height including the browsers URL/navigation bar when applying 100%. But when rotating to landscape iOS hides the URL/navigation bar, so its actually larger than the browser width. was: When loading the application in portrait mode and then rotating it into landscape it leaves a whitespace on the bottom. The reason is because it calculates the height including the browsers URL/navigation bar when applying 100%. But when rotating to landscape iOS hides the URL/navigation bar, so its actually larger then the browser width. > Rotating device landscape in iOS leaves whitespace and doesn't use full height > -- > > Key: OPENMEETINGS-2684 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2684 > Project: Openmeetings > Issue Type: New Feature > Components: iOS, Mobile client >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > Attachments: IMG_0341_2.png > > > When loading the application in portrait mode and then rotating it into > landscape it leaves a whitespace on the bottom. > > !IMG_0341_2.png|width=528,height=297! > The reason is because it calculates the height including the browsers > URL/navigation bar when applying 100%. But when rotating to landscape iOS > hides the URL/navigation bar, so its actually larger than the browser width. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OPENMEETINGS-2684) Rotating device landscape in iOS leaves whitespace and doesn't use full height
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner updated OPENMEETINGS-2684: --- Attachment: (was: IMG_0341.jpeg) > Rotating device landscape in iOS leaves whitespace and doesn't use full height > -- > > Key: OPENMEETINGS-2684 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2684 > Project: Openmeetings > Issue Type: New Feature > Components: iOS, Mobile client >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > Attachments: IMG_0341_2.png > > > When loading the application in portrait mode and then rotating it into > landscape it leaves a whitespace on the bottom. > > !IMG_0341_2.png|width=528,height=297! > The reason is because it calculates the height including the browsers > URL/navigation bar when applying 100%. But when rotating to landscape iOS > hides the URL/navigation bar, so its actually larger than the browser width. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OPENMEETINGS-2684) Rotating device landscape in iOS leaves whitespace and doesn't use full height
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner updated OPENMEETINGS-2684: --- Attachment: IMG_0341_2.png > Rotating device landscape in iOS leaves whitespace and doesn't use full height > -- > > Key: OPENMEETINGS-2684 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2684 > Project: Openmeetings > Issue Type: New Feature > Components: iOS, Mobile client >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > Attachments: IMG_0341_2.png > > > When loading the application in portrait mode and then rotating it into > landscape it leaves a whitespace on the bottom. > > > The reason is because it calculates the height including the browsers > URL/navigation bar when applying 100%. But when rotating to landscape iOS > hides the URL/navigation bar, so its actually larger then the browser width. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OPENMEETINGS-2684) Rotating device landscape in iOS leaves whitespace and doesn't use full height
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner updated OPENMEETINGS-2684: --- Attachment: IMG_0341.jpeg > Rotating device landscape in iOS leaves whitespace and doesn't use full height > -- > > Key: OPENMEETINGS-2684 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2684 > Project: Openmeetings > Issue Type: New Feature > Components: iOS, Mobile client >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > Attachments: IMG_0341.jpeg > > > When loading the application in portrait mode and then rotating it into > landscape it leaves a whitespace on the bottom. > > > The reason is because it calculates the height including the browsers > URL/navigation bar when applying 100%. But when rotating to landscape iOS > hides the URL/navigation bar, so its actually larger then the browser width. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (OPENMEETINGS-2680) Openmeetings / next demo server issues
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Wagner resolved OPENMEETINGS-2680.
Resolution: Fixed
I think this is fixed.
> Openmeetings / next demo server issues
> --
>
> Key: OPENMEETINGS-2680
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2680
> Project: Openmeetings
> Issue Type: Bug
> Components: iOS
>Affects Versions: 7.0.0
>Reporter: Sebastian Wagner
>Assignee: Maxim Solodovnik
>Priority: Major
> Fix For: 7.0.0
>
> Attachments: image-2021-10-06-09-18-45-862.png,
> image-2021-10-06-09-20-43-547.png
>
>
> See below errors from trying to loging into
> [https://om.alteametasoft.com:8443/next/]
> Console errors:
>
> {code:java}
> Refused to load
> https://fonts.googleapis.com/css2?family=Roboto:wght@400;500;700=swap
> because it does not appear in the style-src directive of the Content Security
> Policy.
> ReferenceError: Can't find variable: Notification
> {code}
>
> Screenshot of console errors:
> !image-2021-10-06-09-18-45-862.png|width=891,height=195!
> Screenshot of mobile phone being stuck on loading the dashboard:
> !image-2021-10-06-09-20-43-547.png|width=194,height=345!
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (OPENMEETINGS-2685) Login form on Mobile screens not user-friendly visibility
Sebastian Wagner created OPENMEETINGS-2685: -- Summary: Login form on Mobile screens not user-friendly visibility Key: OPENMEETINGS-2685 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2685 Project: Openmeetings Issue Type: New Feature Components: iOS, Mobile client Reporter: Sebastian Wagner Assignee: Sebastian Wagner Fix For: 7.0.0 Attachments: image-2021-10-10-10-39-43-085.png You can hardly click into the input boxes when on a mobile device: !image-2021-10-10-10-39-43-085.png|width=253,height=447! It is very difficult to click anything. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OPENMEETINGS-2684) Rotating device landscape in iOS leaves whitespace and doesn't use full height
Sebastian Wagner created OPENMEETINGS-2684: -- Summary: Rotating device landscape in iOS leaves whitespace and doesn't use full height Key: OPENMEETINGS-2684 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2684 Project: Openmeetings Issue Type: New Feature Components: iOS, Mobile client Reporter: Sebastian Wagner Assignee: Sebastian Wagner Fix For: 7.0.0 When loading the application in portrait mode and then rotating it into landscape it leaves a whitespace on the bottom. The reason is because it calculates the height including the browsers URL/navigation bar when applying 100%. But when rotating to landscape iOS hides the URL/navigation bar, so its actually larger then the browser width. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OPENMEETINGS-2683) Explore what features of manifest file are useful for OpenMeetings
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner updated OPENMEETINGS-2683: --- Summary: Explore what features of manifest file are useful for OpenMeetings (was: Force landscape mode on mobile using manifest file) > Explore what features of manifest file are useful for OpenMeetings > -- > > Key: OPENMEETINGS-2683 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2683 > Project: Openmeetings > Issue Type: New Feature > Components: Mobile client >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > OpenMeetings on a Mobile device is almost unusable because the aspect ratio > on portrait mode is almost impossible to click any button. > As well as the layout of the application is more width than height. > Apparently there is a way to force the browser into landscape mode using the > manifest.json file. There might be also other features out of the manifest > file that may improve the experience. It is designed to help Progress Web > Apps to more look and feel like Native Apps on Mobile devices. > See also: > * [https://www.w3.org/TR/appmanifest/] > * [https://developer.mozilla.org/en-US/docs/Web/Manifest] > * [https://web.dev/add-manifest/] > * > [https://stackoverflow.com/questions/14360581/force-landscape-orientation-mode] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2683) Force landscape mode on mobile using manifest file
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17426496#comment-17426496 ] Sebastian Wagner commented on OPENMEETINGS-2683: Forcing landscape will only work on Android. iOS doesn't allow forcing the landscape mode. > Force landscape mode on mobile using manifest file > -- > > Key: OPENMEETINGS-2683 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2683 > Project: Openmeetings > Issue Type: New Feature > Components: Mobile client >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > OpenMeetings on a Mobile device is almost unusable because the aspect ratio > on portrait mode is almost impossible to click any button. > As well as the layout of the application is more width than height. > Apparently there is a way to force the browser into landscape mode using the > manifest.json file. There might be also other features out of the manifest > file that may improve the experience. It is designed to help Progress Web > Apps to more look and feel like Native Apps on Mobile devices. > See also: > * [https://www.w3.org/TR/appmanifest/] > * [https://developer.mozilla.org/en-US/docs/Web/Manifest] > * [https://web.dev/add-manifest/] > * > [https://stackoverflow.com/questions/14360581/force-landscape-orientation-mode] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (OPENMEETINGS-2678) OpenMeetings using non support JavaScript API in iOS - ReferenceError: Can't find variable: Notification
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Wagner resolved OPENMEETINGS-2678. Resolution: Fixed > OpenMeetings using non support JavaScript API in iOS - ReferenceError: Can't > find variable: Notification > > > Key: OPENMEETINGS-2678 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2678 > Project: Openmeetings > Issue Type: Bug > Components: iOS, Mobile client >Affects Versions: 6.1.0, 6.2.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Critical > Fix For: 7.0.0 > > Attachments: image-2021-10-03-11-11-05-588.png, > image-2021-10-03-11-12-31-066.png > > > Below stack trace is from iOS (Mobile) Safari. But the same behaviour is in > Chrome on iOS. > Mobile browser console stack trace: > !image-2021-10-03-11-11-05-588.png|width=845,height=121! > !image-2021-10-03-11-12-31-066.png|width=1024,height=291! > > The "Notification" API is not supported by iOS/Mobile. > See: > [https://developer.mozilla.org/en-US/docs/Web/API/Notification/requestPermission#browser_compatibility] > => Safari/iOS = Not supported. And I think Chrome/iOS is not on the table but > its also not supported. It behaves the same I think. > > The unhandled promise rejection could also additionally affect it in case its > related to playing back sound, see OPENMEETINGS-2677 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
