I'm running: Version: 7.2.0.0.alpha0+ / LibreOffice Community Build ID: c1659be6ff0e0c91e0c7d1e6acb6ab18821e2bf7 CPU threads: 4; OS: Linux 5.9; UI render: default; VCL: gtk3 Locale: en-US (en_IL); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-03-02_06:18:34 and as I start LO writer, I get: warn:ucb.ucp.webdav:8143:8212:ucb/source/ucp/webdav-neon/NeonSession.cxx:1839: Neon returned NE_ERROR, http response status code was: 0 'Server certificate verification failed: issuer is not trusted' repeatedly. First, if the certificate is wrong - Writer should not hammer the server again and again. Second: I never specified any webdav server to connect to. I don't see why Writer is connecting to a webdav server at all. Why is that? Third: Suppose for some reason Writer needs to connect to such a default server, local or otherwise. Then - it's a bug that the certificate doesn't get verified. Is the default misconfigured? Fourth: Why doesn't the console message say which server this was?
Thank you for reporting the bug. To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile (https://wiki.documentfoundation.org/UserProfile) and re-test? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present.
(In reply to Dieter from comment #1) > Thank you for reporting the bug. To be certain the reported issue is not > related to corruption in the user profile, could you please reset your > Libreoffice profile (https://wiki.documentfoundation.org/UserProfile) and > re-test? I suppose that I could, but the bug would stand regardless of any theoretical profile corruption: Hammering the server repeatedly just shouldn't happen. Also, isn't it far-fetched to assume that a profile which otherwise works fine for me, and in which I never specified a WebDAV server, suddenly gets a WebDAV server?
(In reply to Eyal Rozenberg from comment #2) > Also, isn't it far-fetched to assume that a profile which otherwise works > fine for me, and in which I never specified a WebDAV server, suddenly gets a > WebDAV server? I don't know, but it's sometimes the easiest way to solve a problem.
(In reply to Dieter from comment #3) > I don't know, but it's sometimes the easiest way to solve a problem. So, when you start a nightly, you don't get these messages?
(In reply to Eyal Rozenberg from comment #4) > So, when you start a nightly, you don't get these messages? I checked the following build: master~2021-05-10_17.24.21_LibreOfficeDev_7.2.0.0.alpha0_Linux_x86-64_deb.tar.gz Didn't see any warnings related to WebDAV on the console. Profile was empty.
[Automated Action] NeedInfo-To-Unconfirmed
Could you please try to reproduce it with a master build from http://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
(In reply to Xisco Faulí from comment #7) > Could you please try to reproduce it with a master build from > http://dev-builds.libreoffice.org/daily/master/ ? Cannot reproduce with: Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: 250e4886d85a7e131da76f181b3fa7be02d1a76d CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: en-IL (en_IL); UI: en-US Did something actually get changed, or is it arbitrarily not firing whatever WebDav-related code is in there? I wonder.
(In reply to Eyal Rozenberg from comment #8) > (In reply to Xisco Faulí from comment #7) > > Could you please try to reproduce it with a master build from > > http://dev-builds.libreoffice.org/daily/master/ ? > > Cannot reproduce with: > > Version: 7.4.0.0.alpha0+ / LibreOffice Community > Build ID: 250e4886d85a7e131da76f181b3fa7be02d1a76d > CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: gtk3 > Locale: en-IL (en_IL); UI: en-US > > Did something actually get changed, or is it arbitrarily not firing whatever > WebDav-related code is in there? I wonder. webdav code was refactored recently. that might be the reason. Closing