When having opened multiple documents, one document having a popup open (like document properties), the following problem occurs. Pressing Ctrl+Q in another window that has no popup open seems to be completely ignored (there is no message of any kind). In the File menu the "Quite" is grayed out. It's somewhat tricky for a beginner to find out what's wrong: You'll have to close the popups(s) first...
I confirm the behaviour with Version: 7.2.2.2 (x64) / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL It's not clear to users, why they can't exit. Perhaps an information could pop up, if you press Strg+Q cc: Design-Team for further input and decision Additional observation In file Menu, entry is "Exit", if it is greyed out and "Exit LibreOffice", if entry is active. Can't see a reason, why this is different and I would expect also "Exit LibreOffice", if it is greyed out.
It's a multi-window application flaw and the alternative to close the current window only wouldn't be an improvement. My take: WF.
Is it solely a usability issue, or does it also have an impact when Windows is shut down in such a state? I mean: If one of the documents is not saved, Ctrl+Q won't trigger any question regarding saving that document. My guess is if you shut down Windows, there also won't be such a question, and LO will be terminated the hard way.
(In reply to Ulrich Windl from comment #3) > does it also have an impact when Windows is shut down in such a state? Operating systems tell you when the shut down process is delayed by running programs. (In reply to Ulrich Windl from comment #3) > Ctrl+Q won't trigger any question regarding saving that document. The confirmation dialog to save changes wasn't open when you exit the application. But consider a modal dialog, for example the options, where you make a lot of adjustments and all is lost when you accidentally press ctrl+Q in another module.
Another possibility would be to bring the dialog window to the front, I think I have seen other applications do that in similar circumstances.
(In reply to Michael Warner from comment #5) > Another possibility would be to bring the dialog window to the front, I > think I have seen other applications do that in similar circumstances. You may have opened a paragraph style dialog in Writer, the options dialog in Impress, and a Calc sheet that just has not been saved. Now you terminate the application from Draw. Writer "keeps this in memory" until the user closes the modal dialog (and probably tells somehow per message box). But you change your mind in Calc and cancel at save... Surely this example can be resolved with elaborated procedures. But it sounds quite dangerous to me and the benefit does not outweigh the effort.
I'm unsure what mechanism would be triggered when shutting down Windows, but I'd strongly prefer to see some dialog asking for save rather than the application be killed after some timeout. (I only know that some programs pop up a message when windows is shutting down, while others do not (and seem to be killed after a timeout (maybe when they don't react on the termination message)).
(In reply to Ulrich Windl from comment #7) > I'm unsure what mechanism would be triggered when shutting down Windows, but > I'd strongly prefer to see some dialog asking for save rather than the > application be killed after some timeout. This has also been requested for Linux in bug 142176.
Topic was on the agenda of the design meeting but didnt receive more attention. And while I suspect side-effects from changing the exit procedure I understand the issue and maybe a smart solution is behind the door.
Repro Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e9374f74385d7dfe77d1902d3d82af20143bc775 CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: fr-FR (fr_FR); UI: fr-FR Calc: threaded
Repro Version: 5.4.0.0.alpha1+ Build ID: 9feb7f7039a3b59974cbf266922177e961a52dd1 CPU threads: 8; OS: Windows 6.19; UI render: GL; Locale: fr-FR (fr_FR); Calc: group Version: 6.4.0.0.alpha1+ (x64) Build ID: 9bc848cf0d301aa57eabcffa101a1cf87bad6470 CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: GL; VCL: win; Locale: fr-FR (fr_FR); UI-Language: en-US Calc: threaded Version: 7.0.0.0.alpha1+ (x64) Build ID: 574c57090642347980d2395e1e183cc7b5c171ad CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: fr-FR (fr_FR); UI: en-US Calc: threaded Version: 7.1.8.0.0+ (x64) / LibreOffice Community Build ID: a94b58277c7aeaa83ce14347cd0b8f7137969d03 CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: fr-FR (fr_FR); UI: en-US Calc: threaded This bug seems to be old.
Dear Ulrich Windl, 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