telman@telman:~$ uname -a
Linux telman 3.0.0-16-generic #29-Ubuntu SMP Tue Feb 14 12:49:42 UTC 2012 i686 i686 i386 GNU/Linux
telman@telman:~$ libreoffice --version
LibreOffice 3.4 340m1(Build:402)
Steps to reproduce:
1. Open a large CALC document in LibreOffice.
2. Make some minor changes.
3. Close LibreOffice.
4. You will be asked to save an unsaved document.
5. Accept save choise.
As the above mentioned Calc file is too large, the OS (Ubuntu) will advise to user a "Force Quit Popup" choise with the following content:
"The window "RAPOR_2011_12_31.XLS - LibreOffice Calc" is not responding.
Forcing this application to quit will cause you to lose any unsaved changes."
[Cancel,ForceQuit] choices are presented here
It was the user choice to save the unsaved too large document
and he made the decision to wait "the save operation" to be finished.
There is no wrong behavior to present the force quit popup.
it is superfluously wrong decision of OS or LibreOffice. I am not sure wich one do it. anyway, I gues the apps and os make the common decision on this.
If we guess that the current behavior is true then the same "force quit popup" should be presented in case of user save decision w/o previously close action.
conclusion: the Force quit Popup should not be presented to user in case of saving too large document with the precided close action.
Platform (if different from the browser):
Browser: Mozilla/5.0 (X11; Linux i686) AppleWebKit/535.11 (KHTML, like Gecko) Ubuntu/11.10 Chromium/17.0.963.79 Chrome/17.0.963.79 Safari/535.11
Thanks for bugreport
When LO saves big document, it takes all CPU time given to LO. It has no time to respond on UI interaction. Desktop notices it and proposes to kill application.
Developers know about this problem. This problem is among GSoC tasks for summer 2012. After solving, saving of document will be placed in separate process. And LO's UI will work properly while saving document.
Telman: Could you attach a sample document, that causes this problem for you? Otherwise it's somewhat hard to reproduce.
Please also check is this bug is still valid if you use any of the current LO releases: http://www.libreoffice.org/download/pre-releases/
Dear Bug Submitter,
Please read the entire message before proceeding.
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 FDO