Created attachment 112027 [details]
Trying to close libreoffice during non-responsive session
When editing in the report builder after some number of changes occasionally the entire LO application becomes non-responsive requiring a force quit, restart, and recovery. Most recently this occurred when attempting to set the width of two controls that were <ctrl><shift><left-cleck> selected. Instead of increasing their size an error message box popped up, or at least began to display, and then it and the entire application ceased leaving the open windows on the desktop but non-responsive.
You could try reproducing a crash while debugging and attach the debug logs:
@James : which version of LO - distro provided or the DEBS from the official TDF download page ?
If the problem is with your distro supplied version, then you should open a report against that version of LO in their bug tracker.
Setting to NEEDINFO
I have had the same screenshot as you on Ubuntu with a much older version of the Ubuntu-provided LO packages and whilst using Base, but not in my own builds.
This occurs with LO-188.8.131.52 downloaded from the LibreOffice.org site. CentOS-6.6 is still shipping LO-4.0.4.
I only have these problems in Base. On Windows7 et al., Linux and OSX I have no problems with LO performance or crashing in Calc, Writer or Draw, and I use all of these extensively. LO on OSX has a long outstanding problem with duplex printing but it does not crash.
However, the Base component is extremely unstable in my experience. And I have experienced the same or very similar problems in Base for as long as I can remember, both in OOo and LOo. This project in fact was a reboot of an earlier essay into Base that I dropped some time ago because of the stability problems. To be of use to me I need the form and report modules to work reliably, both in design and run mode.
In case it is significant this is the JRE in use on the CentOS-6.6 host:
java version "1.7.0_71"
OpenJDK Runtime Environment (rhel-184.108.40.206.el6_6-x86_64 u71-b14)
OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode)
> @James : CentOS was known to have problems running LO, especially
> if the distro-provided package pyuno was installed. Perhaps check
> that there is no conflict on your system with regard to pyuno ?
yum provides \*pyuno\*
Loaded plugins: downloadonly, etckeeper, fastestmirror, presto, priorities,
Loading mirror speeds from cached hostfile
* Webmin: download.webmin.com
* atomic: www6.atomicorp.com
* base: mirror.csclub.uwaterloo.ca
* epel: mirror.csclub.uwaterloo.ca
* extras: less.cogeco.net
* updates: less.cogeco.net
182 packages excluded due to repository priority protections
1:libreoffice-pyuno-220.127.116.11-14.el6.x86_64 : Python support for LibreOffice
Repo : base
Other : openoffice.org-pyuno = 1:3.3.0
Other : libreoffice-pyuno(x86-64) = 1:18.104.22.168-14.el6
Filename : /usr/lib64/libreoffice/program/pyuno.so
Other : pyuno.so()(64bit)
Filename : /usr/lib64/libreoffice/share/registry/pyuno.xcd
Filename : /usr/lib64/libreoffice/program/libpyuno.so
Other : openoffice.org-pyuno(x86-64) = 1:3.3.0
Other : libpyuno.so()(64bit)
Other : libreoffice-pyuno = 1:22.214.171.124-14.el6
libobasis4.2-pyuno-126.96.36.199-1.x86_64 : Pyuno module for LibreOffice 4.2 .1.1
Repo : installed
Filename : /opt/libreoffice4.2/program/libpyuno.so
Filename : /opt/libreoffice4.2/share/registry/pyuno.xcd
Filename : /opt/libreoffice4.2/program/pyuno.so
Filename : /opt/libreoffice4.2/program/services/pyuno.rdb
libobasis4.3-pyuno-188.8.131.52-2.x86_64 : Pyuno module for LibreOffice 4.3 .5.2
Repo : installed
Filename : /opt/libreoffice4.3/program/libpyuno.so
Filename : /opt/libreoffice4.3/program/pyuno.so
Filename : /opt/libreoffice4.3/program/services/pyuno.rdb
Filename : /opt/libreoffice4.3/share/registry/pyuno.xcd
openoffice-pyuno-4.1.1-9775.x86_64 : Pyuno module for Apache OpenOffice 4.1.1
Repo : installed
Filename : /opt/openoffice4/share/registry/pyuno.xcd
Filename : /opt/openoffice4/program/pyuno.so
Filename : /opt/openoffice4/program/libpyuno.so
I do not know what pyuno is however this is what is installed on the host in question that contains that string.
@James : is this still a problem for you with the very latest production version of LibreOffice ?
I will check later today or tomorrow. I have had to abandon that project due to the difficulties I had using LOBAse and so whatever I do will be a contrived test case. But I will get to it in the very near future and report.
Reverting OS change, this was reported against CentOS.
Dear Bug Submitter,
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 INVALID
due to lack of needed information.
For more information about our NEEDINFO policy please read the
wiki located here:
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!
Dear Bug Submitter,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INVALID 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
This INVALID Message was generated on: 2016-05-09