That was it! Interesting, I would have expected it in previous rhel versions.
--Steve From: Corentin SORIANO <coren...@soriano.app.INVALID> Date: Thursday, October 24, 2024 at 6:53 AM To: user@guacamole.apache.org <user@guacamole.apache.org> Subject: Re: Please join us in testing "staging/1.6.0" Do you have SELinux enabled? I have encountered exactly the same error in the past with active SELinux on RHEL 9 (not present in previous RHEL releases). I use this workarround to build the client without disabling SELinux: setsebool -P selinuxuser_execmod Do you have SELinux enabled? I have encountered exactly the same error in the past with active SELinux on RHEL 9 (not present in previous RHEL releases). I use this workarround to build the client without disabling SELinux: setsebool -P selinuxuser_execmod on mvn package setsebool -P selinuxuser_execmod off I hope this can help you. -- Cordialement, Corentin SORIANO -- On 2024-10-23 23:35, Barnhart, Steven wrote: Has anyone had trouble building the staging/1.6.0 docker branch? I am getting this error: 80.60 [INFO] <s> [webpack.Progress] 92% chunk asset optimization closure-compiler-plugin 83.11 [INFO] undefined:1 83.11 [INFO] 83.11 [INFO] 83.11 [INFO] SyntaxError: Unexpected end of JSON input 83.11 [INFO] at JSON.parse (<anonymous>) 83.11 [INFO] at ChildProcess.<anonymous> (/tmp/guacamole-docker-BUILD/guacamole/src/main/frontend/node_modules/closure-webpack-plugin/src/closure-compiler-plugin.js:1007:34) 83.11 [INFO] at ChildProcess.emit (node:events:517:28) 83.11 [INFO] at maybeClose (node:internal/child_process:1098:16) 83.11 [INFO] at ChildProcess._handle.onexit (node:internal/child_process:303:5) --Steve From: Michael Jumper <mjum...@apache.org> Date: Thursday, October 3, 2024 at 1:28 PM To: user@guacamole.apache.org <user@guacamole.apache.org> Subject: Please join us in testing "staging/1.6.0" Hello fellow Guacamole enthusiasts, We recently merged a massive rewrite of the way guacamole-server handles rendering that *should* improve responsiveness, framerate, and bandwidth usage in several cases. The change specifically affects the VNC and RDP protocol support. If anyone is interested in testing, please do. The branch containing these changes is "staging/1.6.0": https://urldefense.com/v3/__https://github.com/apache/guacamole-server/tree/staging/1.6.0__;!!KGKeukY!yR_aRsd5Xovxdxbuz_8o0VztyfYcidCbZq5VIwekRnooAmCztcGmE2_Fu_iDrC8j4Nqsl5Uedhg7xoMcy23hfw$<https://urldefense.com/v3/__https:/github.com/apache/guacamole-server/tree/staging/1.6.0__;!!KGKeukY!yR_aRsd5Xovxdxbuz_8o0VztyfYcidCbZq5VIwekRnooAmCztcGmE2_Fu_iDrC8j4Nqsl5Uedhg7xoMcy23hfw$> These changes do not depend on anything in guacamole-client, but please by all means test the "staging/1.6.0" branch of that, too, if you feel up to the task. Beware that part of these changes adds support for the RDP "Graphics Pipeline Extension" (GUACAMOLE-377). This is generally a good thing, but testing has shown that XRDP's implementation of this uses lossy compression more often than the Windows RDP implementation, resulting in the new scroll detection not recognizing things as well as otherwise. If using XRDP, I would recommend using the "staging/1.6.0" version of guacamole-client, as well, and selecting the "Disable Graphics Pipeline Extension" option in the connection settings. It's otherwise enabled by default. - Mike --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@guacamole.apache.org For additional commands, e-mail: user-h...@guacamole.apache.org
