At each invocation of localc, lowriter or loimpress, the /usr/lib/libreoffice/program/soffice shell script is executed. This script will quite always guess the same environment variables. Moreover, guessing those values is time consuming. I think we could cache the below environment settings into a /var/lib/libreoffice/basis3.3/program/environment.sh file: ----- FILE_LOCKING=auto OPENGL_SUPPORT=no SAL_ENABLE_FILE_LOCKING=1 SAL_NOOPENGL=true JITC_PROCESSOR_TYPE=6 sd_cwd=/usr/lib/libreoffice/program sd_binary=/usr/lib/libreoffice/program/oosplash.bin ----- Those environment settings could be calculated again by a package manager trigger. On my old computer the cold startup of Libre Office Writer last ~24 seconds and guessing the environment variables is quite 30% of the cold startup time !
Created attachment 51286 [details] Instrumented /usr/lib/libreoffice/program/soffice I instrumented the file in order to give the duration of the configuration detection.
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
I just checked with the 3.5.0rc2 version. At each invocation of one of the below command : "libreoffice3.5 --calc" "libreoffice3.5 --writer" "libreoffice3.5 --impress" the /opt/libreoffice3.5/program/soffice shell script is executed. This script will quite always guess the same environment variables. Moreover, guessing those values is time consuming. I think we could cache environment settings into a /var/lib/libreoffice/basis3.4/program/environment.sh file. Those environment settings could be calculated again by a package manager trigger.
Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material
The bug still occurs 4.2.6.3. In addition, there are Valgrind flavors which aren't used in a production environment.
My LibreOffice is running on GNU/Linux but the /usr/lib/libreoffice/program/soffice script has the below code : --- case "`uname -s`" in NetBSD|OpenBSD|FreeBSD|DragonFly) ---
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-12-20
This bug still occurs with the 4.2.8.2 version.
This bug still occurs on 5.0.4.2 version with x64 deb package. The script which computes always the same results (since the system doesn't change) is here : /opt/libreoffice5.0/program/soffice
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170103
This bug still occur on 5.2.4.2 from Debian binary packages (GNU/Linux x86_64) that I downloaded from http://www.libreoffice.org/download/libreoffice-fresh/ . Below are the successive calls when clicking on a LibreOffice document with a file explorer or starting the application from desktop menu : --- j@VB:~$ dpkg-query -L libreoffice5.2-debian-menus | grep "writer.desktop$" /usr/share/applications/libreoffice5.2-writer.desktop j@VB:~$ grep -i exec /usr/share/applications/libreoffice5.2-writer.desktop Exec=libreoffice5.2 --writer %U Exec=libreoffice5.2 --writer j@VB:~$ which libreoffice5.2 /usr/bin/libreoffice5.2 j@VB:~$ ls -l /usr/bin/libreoffice5.2 lrwxrwxrwx 1 root root 35 déc. 19 18:49 /usr/bin/libreoffice5.2 -> /opt/libreoffice5.2/program/soffice j@VB:~$ file /opt/libreoffice5.2/program/soffice /opt/libreoffice5.2/program/soffice: POSIX shell script, ASCII text executable j@VB:~$ --- When I look at the /opt/libreoffice5.2/program/soffice script, it performs a lot of detections each time it is invoked : 1. resolve installation directory 2. parse many test purpose options and search the related tool : --record --backtrace --strace --valgrind ... 3. detect if the host system is "NetBSD|OpenBSD|DragonFly" or not ...
This bug still occurs on 5.2.7.2 version.
Dear Jérôme, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Created attachment 154564 [details] /opt/libreofficedev6.3/program/soffice in version 6.3_6.3.3.0.0 I downloaded the below daily build here : https://dev-builds.libreoffice.org/daily/libreoffice-6-3/Linux-rpm_deb-x86_64@86-TDF/2019-09-24_23.33.05/libreoffice-6-3~2019-09-24_23.33.05_LibreOfficeDev_6.3.3.0.0_Linux_x86-64_deb.tar.gz Into this file, I found the libreofficedev6.3_6.3.3.0.0-1_amd64.deb package which has the attached file with the below path : opt/libreofficedev6.3/program/soffice
Dear Jérôme, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
I downloaded the latest release : https://download.documentfoundation.org/libreoffice/stable/7.2.1/deb/x86_64/LibreOffice_7.2.1_Linux_x86-64_deb.tar.gz.torrent The libreoffice7.2_7.2.1.2-2_amd64.deb packages has the below file : /opt/libreoffice7.2/program/soffice This bug still appears into the above file.
Created attachment 175278 [details] /opt/libreoffice7.2/program/soffice shell script in version 7.2.1
I downloaded the below daily build : https://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86_64@86-TDF/current/master~2021-09-26_16.13.32_LibreOfficeDev_7.3.0.0.alpha0_Linux_x86-64_deb.tar.gz Into this file, I found the libreofficedev7.3_7.3.0.0.alpha0-1_amd64.deb package which has the file with the below path : opt/libreofficedev7.3/program/soffice This bug still occurs in version 7.3.0.0.alpha0.
Created attachment 175300 [details] /opt/libreofficedev7.3/program/soffice in version 7.3.0.0.alpha0