Can you please explain why you believe that the root cause is a hard coded path in this extension? I unpacked the OXT and the embedded JAR file and could not find any "libreoffice" string in any of the files there. I could find all kind of other UI strings from the extension so that I tend to believe my test showing that the path is *not* hard coded.
What else makes you so sure that only the extension can be blamed for this problem? ------- Regarding your general point and closing this issue: I totally understand - and agree with - your line of arguments and also your view on what is proper with regard to file locations. Nevertheless I kindly ask you to reconsider adding my workaround (or something more appropriate to the same effect) to the LO packages on Ubuntu for the following reasons: * Users don't know or care why something fails. They just get frustrated. If we as Ubuntu have the chance to help them then we should do so. * If we can add a fix to Ubuntu that does not harm anybody but helps some people then IMHO we should do so - not as a step down from our high principles but as a step up towards just helping our users. * I estimate that we can "fix" 90% of Linux users of this extension * I have the impression that fixing it here will be much easier then getting DeutschePost to fix it, they don't really care about us. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680336 Title: libreoffice java based extension cannot find java_uno due to wrong java.library.path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1680336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
