Description: No access to database engines which use JDBC drivers Steps to Reproduce: 1. Load an ODB file that uses any JDBC driver to connect to its corresponding backend DB 2. Watch it fail miserably - e.g. with an error message similar to that below : Impossible d'établir une connexion à la source de données externe. Aucun pilote SDBC n'a été trouvé pour l'URL 'jdbc:postgresql://127.0.0.1:5435/lotest'. 3. No access to JDBC driven database data Actual Results: See above Expected Results: As with the x86_64 version, database access should continue to be supported unfettered. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.2.0.4 / LibreOffice Community Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b CPU threads: 8; OS: Mac OS X 11.5.2; UI render: default; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Calc: threaded
This and tdf#144129 seem duplicates of tdf#144128 - why file separate bugs for non-working components that depend on Java, when it's known that Java doesn't work? :)
(In reply to Mike Kaganski from comment #1) > This and tdf#144129 seem duplicates of tdf#144128 - why file separate bugs > for non-working components that depend on Java, when it's known that Java > doesn't work? :) Because a tweet about the 7204 Arm build asked for testers and reporting of bugs. I tested and reported. Collabora seems disinclined to invest in fixing anything related to Java and LO on Mac and I can foresee those bugs being closed as WONTFIX. I am concerned that the LO project is keen to release for an arch where a significant proportion of functionality is missing just to keep pace with the corresponding commercial provider's offer.
(In reply to Alex Thurgood from comment #2) > I am concerned that the LO project is keen to release for an arch where a > significant proportion of functionality is missing just to keep pace with > the corresponding commercial provider's offer. Do you see "macOS (Arm)" as an option in the "Choose your operating system" drop-down? I guess no - juss as myself. Do you know why? Just because this is not yet "fully supported" - as it was explicitly told when we discussed it with cloph on IRC. The release is not "just to keep pace", but to respond to the demand and *to have testing*, without which you can't have a good quality release at some future stage.
*** Bug 144129 has been marked as a duplicate of this bug. ***
How can you blame a java-using component for not supporting an architecture, when there is no Java runtime from Oracle (or anyone else) for those machines? Ports from openJDK, mostly driven by Microsoft were still in early stages at the point of the 7.2 release phase... In any case not having feature parity is one of the reasons why the apple silicon port is not flagged as officially supported, so it is not really a bug, but a known limitation. There is now a GA release available https://github.com/microsoft/openjdk-aarch64 - but it is openJDK 16 based, and not our baseline of JDK 11 (though stated to be coming soon). I guess with that it is worth giving it a shot again, but it's certainly not seen as a high priority/necessity for providing the apple silicon build for the regular end user... As such confirming, but setting it to enhancement. The builds just are done without Java support for the moment.
FWIW, Oracle JDK 17 is now available : https://download.oracle.com/java/17/latest/jdk-17_macos-aarch64_bin.dmg
FWIW, I requested a backport to 7.2 for Stephan's fix in https://bugs.documentfoundation.org/show_bug.cgi?id=144128#c4
This is now resolved as WFM in Version: 7.3.4.2 / LibreOffice Community Build ID: 728fec16bd5f605073805c3c9e7c4212a0120dc5 CPU threads: 8; OS: Mac OS X 12.4; UI render: default; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Calc: threaded with Oracle JDK 17