When a save dialog is opened in Writer the Calc interface is blocked, I mean, is not responding to any interaction with the user. Also, the opposite is true: when a save dialog is opened in Calc, Writer is not responding. (They are related in some way since when Calc crash, Writer also chashes.) Steps to reproduce: 1. Open a Writer and a Calc instance. 2. Open a save dialog by clicking in the "save as" button in Writer (or Calc). 3. Go to Calc (or Writer) and check if everything is working okey. What do I expect: Calc is working fine after opening a save dialog in Writer. What actually happens: Calc is not responding until I close the save dialog in Writer.
Reproduced on Linux with gtk and gtk3. With gtk3, the blocking is not as severe. I can use toolbar buttons. Launching with SAL_USE_VCLPLUGIN=gen libreoffice ..there is no problem. Ubuntu 15.10 64-bit Version: 5.0.4.2 Build ID: 1:5.0.4~rc2-0ubuntu1~wily1 Locale: en-US (en_US.UTF-8) Version: 5.2.0.0.alpha0+ Build ID: c43fdd74097cb12f69f86fd1217dd2f41ccae101 CPU Threads: 2; OS Version: Linux 4.2; UI Render: default; TinderBox: Linux-rpm_deb-x86_64@70-TDF-dbg, Branch:master, Time: 2016-01-25_23:43:01 Locale: en-US (en_US.UTF-8)
** 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.2.5 or 5.3.0 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-20170306
The bug is still present in Ubuntu 16.10 and LibreOffice 5.3.3.2 Bug behavior changed: 1. It only happens when clicking "Save As" in toolbar button, not in window menu. 2. The the blocking is less severe. 3. When I click "Open" button in the other App both programs crashed. 4. When I click "Insert Chart" button in Calc "Save As" window closes.
(In reply to rodhos92 from comment #3) > 3. When I click "Open" button in the other App both programs crashed. You click Open while having Save as dialog on the screen? Or just click Open anytime?
** 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 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
Details have changed again. Tested in Ubuntu 18.04 and LibreOffice 6.0.3.2 1. Click save as button in Calc 2. Click open button in Writer 3. Click cancel in Calc's save as prompt No result. The buttons are blocked.
" 1. Click save as button in Calc 2. Click open button in Writer 3. Click cancel in Calc's save as prompt No result. The buttons are blocked. " Each file dialog runs its own event loop. The first dialog runs it on top of the main event loop, then the second file dialog runs its event loop on top of the first file dialog loop. So the middle loop, that of the first file dialog, cannot exit until the top loop, that of the second file dialog, exits. This should be typical of nearly all the modal dialogs we have, e.g. start in calc and use format->cells, then in writer use format->title page. Now it should not be possible to close the format cells until format title is closed first. And for the same loop within a loop reason. We do have *some* asynchronous dialogs, e.g. start in writer, and format->page, then in calc, format cells. The writer format page is an async dialog, so the format cells is running its event loop on top of the main loop as normal, but the format page dialog does not have its own loop, so it can be closed while the next dialog is still running. To get these file dialog async I guess we'd have to implement XAsynchronousExecutableDialog for them, and rejig the calling code to pass in a listener to handle the dialog final response. This is a fairly big chunk of work for a fairly small gain. All that said, I don't think there is any gtk specific part to this (remaining at this point anyway) unless there's any evidence to the contrary I'm missing ?
Dear rodhos92, 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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug