OpenOffice

[Upstream] Shouldn't detect configuration at each invocation

Bug #452073 reported by Jérôme
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
LibreOffice
Confirmed
Medium
OpenOffice
New
Low
libreoffice (Ubuntu)
Confirmed
Undecided
Unassigned
openoffice.org (Ubuntu)
Won't Fix
Wishlist
Unassigned

Bug Description

Binary package hint: openoffice.org

At each invocation of oocalc, oowriter or ooimpress, the /usr/lib/openoffice/program/soffice shell script is executed.

This script will quite always guess the same environment variables. Moreover, guessing those values is time consuming at the well known critical startup time of openoffice.

I think we could cache the below environment settings into a /var/lib/openoffice/basis3.1/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/openoffice/program
sd_binary=/usr/lib/openoffice/program/oosplash.bin
-----

Those environment settings could be calculated again by an apt trigger or a daily cron task.

ProblemType: Bug
Architecture: i386
Date: Thu Oct 15 12:46:20 2009
Dependencies:

DistroRelease: Ubuntu 9.10
Package: openoffice.org-common 1:3.1.1-4ubuntu1 [modified: var/lib/openoffice/basis3.1/share/config/javasettingsunopkginstall.xml]
PackageArchitecture: all
ProcEnviron:
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.46-generic
SourcePackage: openoffice.org
Uname: Linux 2.6.31-14-generic i686

Revision history for this message
Jérôme (jerome-bouat) wrote :
Revision history for this message
Chris Cheney (ccheney) wrote :

You are correct, of course the startup time even including this is < 2 seconds anyway, at least on my old laptop. I imagine on my desktop (once I get replacement ram so it works) would take under 0.5 second.

Changed in openoffice.org (Ubuntu):
importance: Undecided → Wishlist
status: New → Triaged
summary: - shouldn't detect configuration at each invocation
+ [ooo-build] shouldn't detect configuration at each invocation
Revision history for this message
Jérôme (jerome-bouat) wrote : Re: [ooo-build] shouldn't detect configuration at each invocation

Moreover, it wastes energy for netbooks, laptops, ect.

Revision history for this message
Chris Cheney (ccheney) wrote :

At 2 seconds for the entire OOo startup time, for my laptop the battery lasts around 21600 seconds, that is waste of much less than .009% if you consider the entire startup time of OOo as wasted energy. Which is why I marked the bug as wishlist and why I doubt upstream is ever going to take the time to fix it.

Revision history for this message
Jérôme (jerome-bouat) wrote :

If we think that the details aren't important then we can design a filesystem which leads to fragmentation like a famous shopkeeper of Redmond, just because we think that isn't important to write the new files to a place were it could have place to be extended.

I think that each detail is important. Each energy source (nuke, coal, gaz, oil, wind, water, solar cell, solar thermic facility, plants oil, ...) has a drawback (nuclear wastes/risk, carbon dioxide, cost/space, seisms, chemical wastes, used space, energy/food competition, ...). We have to lower the energy consumption when it is easy.

When I'm using Microsoft Word, it opens just in one click. When I'm using Open Office, I have the time to take a coffee before it is launched, even we the (not so) quick start.

Revision history for this message
Jérôme (jerome-bouat) wrote :

On my host the cold startup of Open Office Writer last ~24 seconds.

I think that caching the environment configuration would avoid to seek/load many datal files as well as programs helpers (sed, awk, ...) and their dependencies.

Revision history for this message
Chris Cheney (ccheney) wrote :

Wow 24 seconds? Even netbooks, which are extremely slow, don't take even a third of that time cold, what kind of system is that, an original pentium?

Revision history for this message
Jérôme (jerome-bouat) wrote :

processor: AMD Duron 800 MHz :D

However my Sony VAIO has the perfect dimensions for my work (13 inches screen with 4/3 form factor that I can't find anymore).

Moreover, I will wait until I find a cheaper laptop with a linux distro installed by default. Currently I've to pay 900 Euros for that.

Of course I can find such a laptop with Microsoft Windows installed starting at 700 Euros but I don't want to buy a Microsoft license, event if it is more expensive. Anyway I would just overwrite it with a linux distro :P

Why a laptop which includes the price of a Microsoft licence is cheaper ?

Revision history for this message
Jérôme (jerome-bouat) wrote :

I instrumented the /usr/lib/openoffice/program/soffice script in order to know how much time it is needs to guess the configuration.

It appears that guessing the environment variables requires 7 seconds during the cold start of:
-----
/bin/dash /usr/lib/openoffice/program/soffice -writer
-----

See attachement for the details.

Guessing the environment variables is quite 30% of the cold startup time !

Revision history for this message
Jérôme (jerome-bouat) wrote :

I instrumented the /usr/lib/openoffice/program/soffice script in order to know how much time it is needs to guess the configuration.

It appears that guessing the environment variables requires 7 seconds during the cold start of:
-----
/bin/dash /usr/lib/openoffice/program/soffice -writer
-----

See attachement for the details.

Guessing the environment variables is quite 30% of the cold startup time !

Revision history for this message
Jérôme (jerome-bouat) wrote :

Note that I desactivated the splash screen in /etc/openoffice/sofficerc by using the below setting:
-----
Logo=0
-----

Revision history for this message
Chris Cheney (ccheney) wrote :

I'm surprised a system that old can even hold enough ram to be able to run Ubuntu and OOo at the same time. I remember when I had a Duron 1GHz system back in mid 2000 and I don't think it could take more than ~ 512MB ram but I may be misremembering.

Revision history for this message
Jérôme (jerome-bouat) wrote :

I installed karmic from Xubuntu 9.04 (update-manager -d).

Next I installed the lxde meta-package and I replaced gdm by xdm.

Finally I removed most parts of the xfce environment as well as rsync, cups and cron (but kept anacron)

Revision history for this message
In , Jérôme (jerome-bouat) wrote :

At each invocation of oocalc, oowriter or ooimpress, the
/usr/lib/openoffice/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/openoffice/basis3.1/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/openoffice/program
sd_binary=/usr/lib/openoffice/program/oosplash.bin
-----

Those environment settings could be calculated again by a package manager
trigger or a daily cron task.

On my host the cold startup of Open Office Writer last ~24 seconds and guessing
the environment variables is quite 30% of the cold startup time !

Revision history for this message
In , Jérôme (jerome-bouat) wrote :

Created attachment 68193
I instrumented the /usr/lib/openoffice/program/soffice script in order to know how much time it is needs to guess the configuration.

Revision history for this message
Jérôme (jerome-bouat) wrote :

I filed a request for enhancement upstream:
http://qa.openoffice.org/issues/show_bug.cgi?id=109896

However, I think this enhancement has to be integrated on Ubuntu side as well.

Chris Cheney (ccheney)
tags: added: karmic
Revision history for this message
Jérôme (jerome-bouat) wrote :

This bug still occurs on lucid.

The bug appears on amd64 too.

tags: removed: karmic
Jérôme (jerome-bouat)
tags: added: lucid
Revision history for this message
In , Jérôme (jerome-bouat) wrote :

This bug still occurs on 3.2 version.

Revision history for this message
Jérôme (jerome-bouat) wrote :

On the same configuration, the new lucid version needs 6 seconds instead of 7 with karmic for guessing the configuration, thus quite the same duration.

Björn Michaelsen (bjoern-michaelsen)
Changed in openoffice.org (Ubuntu):
status: Triaged → Won't Fix
Revision history for this message
Björn Michaelsen (bjoern-michaelsen) wrote : migrating packaging from OpenOffice.org to Libreoffice

[This is an automated message.]
There are no new official OpenOffice.org releases in Ubuntu packaging anymore => Won't Fix

If the problem persists, please mark this bug as "also affects project Libreoffice" or "also affects distribution Libreoffice (Ubuntu)" if that has not happened already.

Please leave references to upstream OpenOffice.org bugs in place to allow cross pollination.

Revision history for this message
In , Jérôme (jerome-bouat) wrote :

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 !

Revision history for this message
In , Jérôme (jerome-bouat) wrote :

Created attachment 51286
Instrumented /usr/lib/libreoffice/program/soffice

I instrumented the file in order to give the duration of the configuration detection.

Revision history for this message
In , Jérôme (jerome-bouat) wrote :

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 !

Revision history for this message
In , Jérôme (jerome-bouat) wrote :

Created attachment 51286
Instrumented /usr/lib/libreoffice/program/soffice

I instrumented the file in order to give the duration of the configuration detection.

Bug Watch Updater (bug-watch-updater)
Changed in df-libreoffice:
importance: Unknown → Medium
status: Unknown → Confirmed
penalvch (penalvch)
summary: - [ooo-build] shouldn't detect configuration at each invocation
+ [Upstream] Shouldn't detect configuration at each invocation
Changed in openoffice:
importance: Undecided → Unknown
status: New → Unknown
Revision history for this message
In , Björn Michaelsen (bjoern-michaelsen) wrote :

[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

Revision history for this message
In , Björn Michaelsen (bjoern-michaelsen) wrote :

[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

Bug Watch Updater (bug-watch-updater)
Changed in df-libreoffice:
status: Confirmed → Incomplete
Revision history for this message
In , Jérôme (jerome-bouat) wrote :

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.

Revision history for this message
In , Jérôme (jerome-bouat) wrote :

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.

Bug Watch Updater (bug-watch-updater)
Changed in df-libreoffice:
status: Incomplete → Confirmed
Revision history for this message
Bryan Quigley (bryanquigley) wrote :

Is this still an issue? I just ran the script on 12.04/LibreOffice 3.5 and it took very very little time. I definitely think there is room to improve LO start speed but not convinced it's here.

Changed in libreoffice (Ubuntu):
status: New → Incomplete
Bug Watch Updater (bug-watch-updater)
Changed in openoffice:
importance: Unknown → Low
status: Unknown → New
Revision history for this message
Jérôme (jerome-bouat) wrote :

I think many improvements would make Libreoffice/Openoffice faster. We can start to work on each one without waiting for the other to be released.

Working on the script would possibly not provide a big benefit on fast machines. However, on energy efficient machines there should be a noticeable benefit as on my machine : 30% of the cold startup time.

Moreover, working on the configuration script seems easier than working on parallel startup of LibreOffice/OpenOffice processes and/or parallel reading of document files. Thus the "Return On Investment" should be interesting for this bug.

Revision history for this message
Bryan Quigley (bryanquigley) wrote :

Have you investigated which part causes the biggest slow down for you? Uncomment the last line (execute) and then
Try with, "strace -rT /usr/lib/libreoffice/program/soffice", and then attach the output here.

You could also go line by line in the script itself if you want.

Revision history for this message
In , Qa-admin-q (qa-admin-q) wrote :

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

Revision history for this message
In , Qa-admin-q (qa-admin-q) wrote :

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

Revision history for this message
In , Jérôme (jerome-bouat) wrote :

The bug still occurs 4.2.6.3.

In addition, there are Valgrind flavors which aren't used in a production environment.

Revision history for this message
In , Jérôme (jerome-bouat) wrote :

The bug still occurs 4.2.6.3.

In addition, there are Valgrind flavors which aren't used in a production environment.

Revision history for this message
In , Jérôme (jerome-bouat) wrote :

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)
---

Revision history for this message
In , Jérôme (jerome-bouat) wrote :

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)
---

Revision history for this message
In , Qa-admin-q (qa-admin-q) wrote :

** 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

Revision history for this message
In , Jérôme (jerome-bouat) wrote :

This bug still occurs with the 4.2.8.2 version.

Revision history for this message
In , Jérôme (jerome-bouat) wrote :

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

Revision history for this message
In , Qa-admin-q (qa-admin-q) wrote :

** 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

Revision history for this message
In , Jérôme (jerome-bouat) wrote :

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
...

Revision history for this message
In , Jérôme (jerome-bouat) wrote :

This bug still occurs on 5.2.7.2 version.

Marcus Tomlinson (marcustomlinson)
Changed in df-libreoffice:
importance: Medium → Unknown
status: Confirmed → Unknown
Bug Watch Updater (bug-watch-updater)
Changed in df-libreoffice:
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
In , Qa-admin-q (qa-admin-q) wrote :

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

Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

Synchronising bug status with upstream.

Changed in libreoffice (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
In , Jérôme (jerome-bouat) wrote :

Created attachment 154564
/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

Revision history for this message
In , Qa-admin-q (qa-admin-q) wrote :

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

Revision history for this message
In , Jérôme Bouat (jeromebouat) wrote :

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.

Revision history for this message
In , Jérôme Bouat (jeromebouat) wrote :

Created attachment 175278
/opt/libreoffice7.2/program/soffice shell script in version 7.2.1

Revision history for this message
In , Qa-admin-q (qa-admin-q) wrote :

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

Revision history for this message
In , Jérôme Bouat (jeromebouat) wrote :

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.

Revision history for this message
In , Jérôme Bouat (jeromebouat) wrote :

Created attachment 175300
/opt/libreofficedev7.3/program/soffice in version 7.3.0.0.alpha0

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.