Date: prev next · Thread: first prev next last
2019 Archives by date, by thread · List index


Hello,

Taking a look at https://bugs.documentfoundation.org/show_bug.cgi?id=126728 
"LibreOffice slow start due to FTP access failure (kde5 only)", I noticed
these lines:
109              case KProtocolManager::EnvVarProxy: // Proxy values set
through environment variables
110                  // In such cases, the proxy address is not stored in
KDE, but determined dynamically.
111                  // The proxy address may depend on the requested
address, on the time of the day, on the speed of the wind...
112                  // The best we can do here is to ask the current value
for a given address.
113                  aFTPProxy = KProtocolManager::proxyForUrl(
114                      QUrl(QStringLiteral("ftp://ftp.libreoffice.org";)));
115                  break;
116              default: // No proxy is used
117                  break;
118          }
...
and almost the same block around line 140

See
https://opengrok.libreoffice.org/xref/core/shell/source/backends/kf5be/kf5access.cxx?r=d3c6ac6d#114

The problem is "ftp://ftp.libreoffice.org"; doesn't exist, so :
1) url proxy for FTP won't be retrieved
2) it slows down (depending on timeout value) the LO startup (at least for
those who use KDE5/Plasma)

Any thoughts? (What ftp address to put?)

Julien



--
Sent from: http://document-foundation-mail-archive.969070.n3.nabble.com/Dev-f1639786.html

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.