Description: After the last update LibreOffice to 7.26.2 (x64) / Libre Office Community My Spreadsheets are no longer working. They freeze as soon as I click something on the spreadsheet. Version: 7.2.6.2 (x64) / LibreOffice Community Build ID: b0ec3a565991f7569a5a7f5d24fed7f52653d754 CPU threads: 4; OS: Windows 10.0 Build 22000; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded After the crash I close the system and upon restarting it successfully recovers the crashed file, but upon clicking anything (even the "Close Window" button) it fades and freezes again. Steps to Reproduce: 1.Open a spreadsheet file 2.Click on anything on the screen 3.Message on top appears "LibreOffice not responding" 4.Click on "Close" (red X top right corner). 5.Get message with 2 options: 1. Close the program. / 2. Wait for the program to respond. 6. Clicking on "Wait for the program to respond" does not work, program stays frozen. 7. Click "Close" again 8. Select "Close the program". Upon opening the program again OpenOffice asks to recover the crashed file, which it does successfully, but upon clicking anything we start back from 1. above. Actual Results: All described in steps to reproduce. Expected Results: All described in steps to reproduce. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.2.6.2 (x64) / LibreOffice Community Build ID: b0ec3a565991f7569a5a7f5d24fed7f52653d754 CPU threads: 4; OS: Windows 10.0 Build 22000; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded My system: Intel(R) Core(TM) i3-8130U CPU @ 2.20GHz 2.21 GHz. 20.0 GB RAM. 64-bit operating system, x64-based processor. No pen or touch input.
Could you give a try at https://wiki.documentfoundation.org/QA/FirstSteps ? If still stuck, you can give a try to LO 7.3.1
Ronny: please do not send private email but respond on the bugtracker by using this link: https://bugs.documentfoundation.org/show_bug.cgi?id=148296# Just to quote the email: " Good Day, Thank you for your reply and advice. I found out what causes the problem. If I start the PDF editing program Nitro Pro before I start LibreOffice (Spreadsheet, or Writer, or any one of them), LibreOffice freezes. But if I start LibreOffice first, everything works normal. So the solution is simple .... Start LibreOffice first 🙂. Thank you once again." V Stuart: what next move should we apply here? I mean, we're not going to buy Nitro Pro to give it a try, should we put WFM or do you have another idea?
(In reply to Julien Nabet from comment #2) from OP > I found out what causes the problem. If I start the PDF editing program > Nitro Pro before I start LibreOffice (Spreadsheet, or Writer, or any one of > them), LibreOffice freezes. But if I start LibreOffice first, everything > works normal. So the solution is simple .... Start LibreOffice first 🙂. > > Thank you once again." > > > V Stuart: what next move should we apply here? I mean, we're not going to > buy Nitro Pro to give it a try, should we put WFM or do you have another > idea? I would suspect Nitro Pro to have a print-to-PDF component that registers as an active printer when run. LibreOffice would attempt to read the "printer" details, even "querying" the printer for its page settings. Since it is hanging, not crashing, for anything definitive we would need a WinDbg back trace with symbols [1] of the attached soffice.bin process when it hangs with Nitro Pro running. Ronny, or someone with Nitro Pro installed, would need to configure for that and then provide. Either forcing a dunp (of the hung process), or interactively from the WinDbg console with a "~* kp" command [2]. =-ref-= [1] https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg [2] The Mozilla folks provide some help for poking at FireFox. The same process, just attach to soffice.bin. As here: https://firefox-source-docs.mozilla.org/contributing/debugging/stacktrace_windbg.html
Hi good day Julien and Stuart, I think you are correct that the "Print to PDF" component might be causing the problem. As you mentioned it, I remember that I also have a similar problem when I use the Bank Mode feature of my Avast Secure Web Browser. As soon as I want to print a document to a PDF file the Secure Web Browser starts to freeze. It does not matter if I use the Nitro Pro or the Microsoft Print to PDF printing options, they both cause the browser to freeze, and the only way to get out is to close the app via the Task Manager, nothing else will work. So the common denominator here appears to be the "Print to PDF" feature. I hope this was useful. Kind regards, Ronny. =======
[Automated Action] NeedInfo-To-Unconfirmed