Description: Crash of the document recovery window Steps to Reproduce: 1. download full getting started guide 4.2 and 5.0 from https://wiki.documentfoundation.org/images/0/0f/GS42-GettingStartedLO.odt and https://wiki.documentfoundation.org/images/f/f3/GS50-GettingStartedLO.odt 2. open GS Guide 5.0 in LO 3. select menu Edit - Track Changes - Compare Document 4. select GS Guide 4.2 and wait 5. Press Undo 6. File recovery dialog appears 7. Press OK -> error popups.. window still present.. not happens anyore Actual Results: File recovery stuck Expected Results: Shouldn't be so Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.0.0.alpha0+ (x64) Build ID: 52820b52b3bca45e2db527d1cc5f4488b2e0b9d0 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL
Also in 5.3
Pressing OK working fine with 5.2
Confirmed on windows 10 x64 with Version: 6.4.6.1 (x64) Build ID: 985dd72ca280d5c6da2e9f90f7ff9286cafe7ff8 CPU threads: 12; OS: Windows 10.0 Build 19041; UI render: default; VCL: win
(In reply to Telesto from comment #0) > 7. Press OK -> error popups.. window still present.. not happens anyore Not happens what? Please refrain from vague phrases that don't allow to understand what you mean. Better be overly verbose than unclear. Use full sentences, with exact nouns instead of "it"s and such, even if that means you will repeat the same word tens of times. This is not a novel, this is STR, which must be unambiguous. https://www.chiark.greenend.org.uk/~sgtatham/bugs.html#clarity
Specifically, I didn't write about mistyped "anymore" (which is not a problem). (In reply to Telesto from comment #0) > Steps to Reproduce: > ... > 2. open GS Guide 5.0 in LO > 3. select menu Edit - Track Changes - Compare Document Given the size of the document, you omitted one detail relevant here: should one wait for layout to finish (so it stops jumping back when you scroll, and "Page 1 of N" in status bar stops changing, and N becomes 533), or should one start comparison immediately, or does this not matter. (But you might not notice this, OK...) > 4. select GS Guide 4.2 and wait Wait for what? I *guess* that you meant "... until "Manage Changes" dialog appears", but that's just my guess. Maybe you meant that something else appears for you; and that could happen e.g. that you see a different thing at this point than what I see. A good report would not let it unsaid, and a person who reports hundreds of bugs is expected to follow best practices. > 5. Press Undo How? without closing the dialog? or closing it? That is a very important detail, and "I didn't write to close it, so it naturally means it should stay open" is not an argument. It's good to read "Press "Undo" button on toolbar, without previously closing "Manage Changes" dialog", or something like that. Also, how many times should one press the "Undo"? > 6. File recovery dialog appears Not that big, just another illustration of ignoring the importance of details: the dialog is not "File recovery", it's "LibreOfficeDev 7.1 Document Recovery". > 7. Press OK -> error popups.. window still present.. not happens anyore There's no "OK" in the "Document Recovery" dialog. Which error (its text) exactly? which "window" is meant - the "Document Recovery" dialog's? or any other window that you see, but didn't mention? and finally, what "not happens anymore" and when? do you mean that you don't see the same problem when try to repeat the steps? or what?
(In reply to Mike Kaganski from comment #5) > > 7. Press OK -> error popups.. window still present.. not happens anyore > There's no "OK" in the "Document Recovery" dialog. Or did you mean "Due to an error, LibreOffice crashed. All the files you were working on will now be saved" dialog, which is different from the "Document Recovery" dialog appearing the next time you launch the program ("LibreOffice will attempt to recover ...")? (The two dialogs/different modes of the same dialog (?) should really be named differently for disambiguation.) This likely the exact thing that happened here that you see something different from what I see (me using a debug build), so extra level of details is again very important, also mentioning the "Documents are being saved" window appearing (is *this* a window you were talking about in #7?).
1. download full getting started guide 4.2 and 5.0 from https://wiki.documentfoundation.org/images/0/0f/GS42-GettingStartedLO.odt and https://wiki.documentfoundation.org/images/f/f3/GS50-GettingStartedLO.odt 2. open GS Guide 5.0 in LO 3. select menu Edit - Track Changes - Compare Document 4. select GS Guide 4.2 and with until the comparing process finishes 5. Close the track changes dialog 6. Press Undo (to delete the comparison, number of steps is different between versions; but all steps) 7. The LibreOffice document recovery opens ("Due to an error") 8. Press OK -> A Windows dialog opens error; closing LibreOffice 7/8 don't happen for me today; everything simple hangs/freezes
Next attempt (based on bug 136124) 1. Open attachment 162927 [details] 2. Tools -> Options -> Save/ load set autosave to 1 minute 3. CTRL+A 4. CTRL+X 5. Edit -> Track changes -> Manage 6. Minimize - 7. Wait -> LibreOffice starts blinking in the task bar 8. Click it -> Crash Dialog & press OK -> Crash again (something in the same area: bug 131681)
Created attachment 165112 [details] Screencast Another case 1. Open attachment 165096 [details] bug 122792 2. CTRL+A 3. CTRL+X 4. CTRL+V -> Crash -> Document recovery appears 5. Press OK; saving starts... nearly finished.. error appears (see screencast)
(In reply to Telesto from comment #9) > Created attachment 165112 [details] > Screencast > > Another case > 1. Open attachment 165096 [details] bug 122792 > 2. CTRL+A > 3. CTRL+X > 4. CTRL+V -> Crash -> Document recovery appears > 5. Press OK; saving starts... nearly finished.. error appears (see > screencast) Still working fine with 6.3 (so maybe throwing bugs together, based on comment 0)
Dear Telesto, 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
1. download full getting started guide 4.2 and 5.0 from https://wiki.documentfoundation.org/images/0/0f/GS42-GettingStartedLO.odt and https://wiki.documentfoundation.org/images/f/f3/GS50-GettingStartedLO.odt 2. open GS Guide 5.0 in LO 3. select menu Edit - Track Changes - Compare Document 4. select GS Guide 4.2 and with until the comparing process finishes 5. Close the track changes dialog 6. Press Undo -> Crash (a problem, but not the point of the bug) 7. The LibreOffice Document Recovery dialog opens (The following files will be recovered..) 8. Press OK 9. Documents are being saved dialog opens; LibreOffice stopped working. Close the program dialog appears Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: dc92a4d973086ce8a6a5f75ba0f4d4c9ca05537a CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL threaded
(In reply to Telesto from comment #12) > 9. Documents are being saved dialog opens; LibreOffice stopped working. > Close the program dialog appears No repro using Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: d752cb42473547872741c74a70809f28f9fe789c CPU threads: 12; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL threaded
With comment 12 steps: No repro on Linux: BigPtrArray crash at step 6, but at step 9, but LO closes, and Ubuntu Apport catches the crash. Reopening LO goes directly to reporting the step 6 crash, and then the document recovery works. Version: 7.6.6.3 (X86_64) / LibreOffice Community Build ID: d97b2716a9a4a2ce1391dee1765565ea469b0ae7 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded On Windows 11, I get the crash at step 6, and then "Document are being saved" is stuck on step 9 with progress bar not moving. If I close that dialog and restart LO, I get the crash report dialog, with signature "BigPtrArray::Index2Block(long)": - https://crashreport.libreoffice.org/stats/crash_details/fa9252b3-d5df-4605-9d10-6edc7f42a120 - https://crashreport.libreoffice.org/stats/crash_details/99030566-c721-4ae7-b885-26253eab36a4 ... but that's the step 6 (bug 135072) crash that's reported after, correct? After the crash report dialog, the document recovery works as expected. Version: 7.6.6.3 (X86_64) / LibreOffice Community Build ID: d97b2716a9a4a2ce1391dee1765565ea469b0ae7 CPU threads: 4; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 CPU threads: 4; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded So, is the issue that the "Documents are being saved" freezes?
(In reply to Stéphane Guillou (stragu) from comment #14) > So, is the issue that the "Documents are being saved" freezes? Telesto: looks like we need more info on this at the moment.
Dear Telesto, 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 INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO 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! Warm Regards, QA Team MassPing-NeedInfo-Ping