https://bugs.documentfoundation.org/show_bug.cgi?id=163485
Mike Kaganski <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #3 from Mike Kaganski <[email protected]> --- The message should not show at all, together wit all the other debug output that we disable in release builds. At the point where we call it [1], we can't even know if we have Java enabled, or if we need Java. If needed, we should store the result in a variable for future reference. At the very least, if we truly *have to* emit it to the console (it would be a headless invocation), we must do that at that later stage, when we are requested to actually load Java. We could also show that message in a GUI, when we report Java loading failure, as a hint what could cause it (in interactive invocation). I believe, that this message is one most important reason for people to believe that LibreOffice is Java-based; while in reality, this is just a side effect of *some* platforms' loaders specifics, that don't allow setting some variables at a later stage. Quoting sberg from IRC: > at least for some old JREs that was/is needed on some Unixy, that's why we > have that javaldx > at least on some platforms, it's env vars we need to set that are read once by > the dynamic loader upon start, and later changes would be ignored by the > dynamic > loader ... > but maybe the original need for javaldx has gone with contemporary JREs, I > can't remember the details off the top of my head I.e., if we don't do this early enough - even before we even know if we *need* Java, we can't later load Java (but most possibly we won't have to). That's why it exists, which doesn't mean it's required for correct operation of everything that doesn't need Java. Yet, Google suggests, that people struggle hard fixing this message, which in ~100% is unrelated to their problems. [1] https://opengrok.libreoffice.org/xref/core/desktop/unx/source/start.c?r=b4295077&mo=18630&fi=663#610 -- You are receiving this mail because: You are the assignee for the bug.
