Summary: | kioslaverc entries cause very slow startup of LibreOffice main window | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Buggy <hkuest-g38> |
Component: | LibreOffice | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | hkuest-g38 |
Priority: | medium | ||
Version: | 6.4.5.2 release | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: |
Description
Buggy
2021-02-28 17:38:22 UTC
The problem appeared on OpenSuSE 15.1 and OpenSuSE 15.2. Do you require a comment from my side? Hello Buggy, Thank you for reporting the bug. it seems you're using an old version of LibreOffice. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version. I created a new VM (2 CPU's, 2048 MB RAM, 30 GB disk space), installed OpenSuSE 15.2 (German - Deutsch with German keyboard) in a NATed network using the installation option "Desktop with KDE-Plasma", initially I used a wicked network configuration, but later a Network Manager configuration showed the same behavior for the package 6.4.5.2 (start loffice) shipped with OpenSuSE as the latest build 7.1.1.2 (starting libreoffice7.1 after deinstallation of the libreoffice shipped with the release and installing all RPM's as root using "rpm -i LibreOffice_7.1.1.2_Linux_x86-64_rpm/RPMS/*.rpm"): Create ~myuser/.config/kioslaverc ProxyUrlDisplayFlags=0 [Proxy Settings] Proxy Config Script= ProxyType=3 ReversedException=false socksProxy= Modify /etc/xdg/kioslaverc to #[Proxy Settings] #NoProxyFor=NO_PROXY #ftpProxy=FTP_PROXY #httpProxy=HTTP_PROXY #httpsProxy=HTTPS_PROXY Then the initial startup of LibreOffice is start, only a warning of the "Network Proxy Configuration" is shown: "No usable proxy-configuration script could be found". A second startup about 10 minutes later is delayed significantly, the above configuration warning is not displayed again. |