A while after starting LO Writer, I get the contents of the attached text file on my console.
I don't understand why multiple connections are made for checking for updates, but irrespective of that, there are several warnings saying:
* WARNING: failed to load NSS PEM library libnsspem.so. Using OpenSSL PEM certificates will not work.
1. It doesn't say _how_ it failed. Version mismatch? Missing file? Something else?
2. I'm assuming it's important to load this PEM library (otherwise there wouldn't be a warning). But - it doesn't even exist on my system. So why wasn't it installed with the LO packages? Or why is this not a package dependency of the LO .deb files?
Anyway, after reading this, I installed the nss-plugin-pem Debian package. Perhaps that's what LO DEBs should depend on?
Created attachment 176931 [details]
Console output of LO update process
on a windows 10 machine using console mode both LibreOffice and LibreOffice Writer were opened.
no console logs were observed.
please refer attachment for more information.
this bug is being set to NEEDINFO.
please get back if the logs are seen again and set its status to UNCONFIRMED
Version: 188.8.131.52 (x64) / LibreOffice Community
Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890
CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: en-IN (en_IN); UI: en-US
Thank you for reporting the bug. Can you please confirm if the issue still exists in the latest build?
Could you please try to reproduce it with a master build from https://dev-builds.libreoffice.org/daily/master/ ?
You can install it alongside the standard version.
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build.
Created attachment 183970 [details]
(In reply to sockseight from comment #3)
> no console logs were observed.
> please refer attachment for more information.
There is definitely console output... on Linux, anyways. And .so libraries are a Linux/Unix/Mac thing. So, narrowing the platform.
However, note that the bug is not merely about what's actually printed, but about how the code reports failure, when failures occur.