If I open libreoffice in my "user" session, the start is very very slow. [code] $ time strace -f /opt/libreoffice6.4/program/soffice.bin --calc 2>&1 | grep ftp [pid 6275] sendmsg(10, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="l\1\0\1\36\0\0\0\20\0\0\0w\0\0\0\1\1o\0\23\0\0\0/modules"..., iov_len=136}, {iov_base="\31\0\0\0ftp://ftp.libreoffice.org\0", iov_len=30}], msg_iovlen=2, msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 166 [pid 6275] sendmsg(10, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="l\1\0\1\36\0\0\0\25\0\0\0w\0\0\0\1\1o\0\23\0\0\0/modules"..., iov_len=136}, {iov_base="\31\0\0\0ftp://ftp.libreoffice.org\0", iov_len=30}], msg_iovlen=2, msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 166 real 3m51,841s user 0m21,659s sys 0m29,406s [/code] Yep, 3 minutes, 51 seconds.... But in "root": [code] # time strace -f /opt/libreoffice6.4/program/soffice.bin --calc 2>&1 | grep ftp real 0m2,906s user 0m1,291s sys 0m0,578s [/code] Only 2 seconds. I tried with "disable updates" and "disable java" but nothing. Also removing the "cache" and "config" folder (in my home) but nothing. Also I see a similar bug: https://bugzilla.opensuse.org/show_bug.cgi?id=1144361 But I think mine is different, because the time is excessively longer. < More info > [Help information] Versión: 6.4.4.2 Id. de compilación: 3d775be2011f3886db32dfd395a6a6d1ca2630ff Subprocs. CPU: 12; SO: Linux 5.6; Repres. IU: predet.; VCL: kf5; Configuración regional: es-PE (es_PE.UTF-8); Idioma de IU: es-ES Calc: threaded # cat /etc/*ease NAME="openSUSE Tumbleweed" # VERSION="20200331" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20200331" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20200331" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" LOGO="distributor-logo" # rpm -qa | grep libreoffice libobasis6.4-libreofficekit-data-6.4.4.2-2.x86_64 libreoffice6.4-base-6.4.4.2-2.x86_64 libreoffice6.4-math-6.4.4.2-2.x86_64 libreoffice6.4-calc-6.4.4.2-2.x86_64 libreoffice6.4-dict-es-6.4.4.2-2.x86_64 libreoffice6.4-es-6.4.4.2-2.x86_64 libreoffice6.4-ure-6.4.4.2-2.x86_64 libreoffice6.4-6.4.4.2-2.x86_64 libreoffice6.4-draw-6.4.4.2-2.x86_64 libreoffice6.4-freedesktop-menus-6.4.4-2.noarch libreoffice6.4-dict-en-6.4.4.2-2.x86_64 libreoffice6.4-dict-fr-6.4.4.2-2.x86_64 libreoffice6.4-impress-6.4.4.2-2.x86_64 libreoffice6.4-writer-6.4.4.2-2.x86_64 libreoffice6.4-en-US-6.4.4.2-2.x86_64
The other report was KDE-only, so you could try launching from the command line with SAL_USE_VCLPLUGIN=gen libreoffice to test, if the speed is normal.
Dear zchronos, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear zchronos, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp