Hello, spot on! I have downladed the latest MariaDB/J connector and linked it in /etc/guacamole/lib/ instead of the one from Debian. And tadaa... Subelements now appear. Honestly, I would have placed my bets on JDK instead, since the DB could be read and written anyway. But I guess I'm lucky since it was the easiest component to replace.
Thanks for your help, regards, --- Olivier Chaudet Service informatique du LMO - UMR 8628 Bureau 2R1, bât 307 Faculté des Sciences 91405 ORSAY (33)1.69.15.31.67. De: "Nick Couchman" <[email protected]> À: "user" <[email protected]> Envoyé: Vendredi 8 Janvier 2021 20:05:25 Objet: Re: sub-elements not displayed in the web interface On Fri, Jan 8, 2021 at 5:25 AM Olivier Chaudet < [ mailto:[email protected] | [email protected] ] > wrote: Hi, here are the versions. ~$ cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 10 (buster)" NAME="Debian GNU/Linux" VERSION_ID="10" VERSION="10 (buster)" VERSION_CODENAME=buster ID=debian HOME_URL=" [ https://www.debian.org/ | https://www.debian.org/ ] " SUPPORT_URL=" [ https://www.debian.org/support | https://www.debian.org/support ] " BUG_REPORT_URL=" [ https://bugs.debian.org/ | https://bugs.debian.org/ ] " ~$ java -version openjdk version "11.0.9.1" 2020-11-04 OpenJDK Runtime Environment (build 11.0.9.1+1-post-Debian-1deb10u2) OpenJDK 64-Bit Server VM (build 11.0.9.1+1-post-Debian-1deb10u2, mixed mode, sharing) It's possible there is something in Java 11 that's causing issues, here - I'll try to see if I can get a version of OpenJDK 11 and test with that. BQ_BEGIN ~$ /usr/local/tomcat9/bin/version.sh Using CATALINA_BASE: /usr/local/tomcat9 Using CATALINA_HOME: /usr/local/tomcat9 Using CATALINA_TMPDIR: /usr/local/tomcat9/temp Using JRE_HOME: /usr/lib/jvm/java-11-openjdk-amd64/ Using CLASSPATH: /usr/local/tomcat9/bin/bootstrap.jar:/usr/local/tomcat9/bin/tomcat-juli.jar Using CATALINA_OPTS: NOTE: Picked up JDK_JAVA_OPTIONS: --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/ [ http://java.io/ | java.io ] =ALL-UNNAMED --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED Server version: Apache Tomcat/9.0.41 Server built: Dec 3 2020 11:43:00 UTC Server number: 9.0.41.0 OS Name: Linux OS Version: 4.19.0-13-amd64 Architecture: amd64 JVM Version: 11.0.9.1+1-post-Debian-1deb10u2 JVM Vendor: Debian ~$ mariadb --version mariadb Ver 15.1 Distrib 10.3.27-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2 BQ_END This is pretty close to what I'm testing with - 10.5 - so I'm guessing the mariaDB server is not to blame. BQ_BEGIN And in the manifest.mf from mariadb-java-client.jar (which comes with "apt install libmariadb-java"): Bundle-Version: 2.3.0 BQ_END Could be this, though - the MariaDB Connector/J can be downloaded directly from the MariaDB website - I'd suggest downloading the latest (2.6, I think is what I had grabbed) and drop it in GUACAMOLE_HOME/lib, restart Tomcat, and re-test. -Nick
