Description: I was using LibreOffice v24.x without issues. I installed v25.2.0.3 with the Help pack this morning. If I start any spreadsheet and try EDITTING it by using copy/paste into another cell, Calc hangs. The same issue occurs with CUT command. I used: a) Safe-mode and disabled all user extensions and hardware extensions → same issue (as far as I am aware I had none installed but I tried this anyways) b) Safe-mode to Reset to Factory Settings (settings + user profile) → same issue (as far as I am aware I was using all factory default settings but I tried this anyways) I redownloaded the binaries and did an Install-Repair → same issue I retried (a) + (b) after the Install-Repair → same issue I booted Win11 Pro 64Bit into SafeMode with/without networking -> same issue Clipboard history was disabled long ago so having it enabled is not the cause. I added SAL_ACCESSIBILITY_ENABLED=0 as an ENV variable but that did not fix it. I ran Win11 Sandbox and installed LibreOffice and Cut-n-Paste worked so something in my Win11 env is the issue. I produced a minidump file for review. Steps to Reproduce: 1.Open any spreadsheet or start a new spreadsheet from scratch 2.select any cell with data 3.CTRL-C or CTRL-X Actual Results: Calc hangs immediately after the CTRL-C or CTRL-X Expected Results: Calc should either Cut or Copy the selected data in the selected Cell without hanging so that user can continue editing the file. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 25.2.0.3 (X86_64) / LibreOffice Community Build ID: e1cf4a87eb02d755bce1a01209907ea5ddc8f069 CPU threads: 12; OS: Windows 11 X86_64 (10.0 build 22631); UI render: Skia/Raster; VCL: win Locale: en-CA (en_CA); UI: en-US Calc: threaded
Created attachment 199077 [details] Procdump analysis file produced from Calc Hanging
I looked at the analysis file and noted it listed Python3.dll in the file. I do have Python v3.11.3 and v3.13.1 installed on my machine.
Michael: it looks as if the problem here is a loop over all cells in a11y. I believe that we had a similar issue somewhere, but can't find it immediately.
Created attachment 199079 [details] minidump file from the crash
(In reply to Mike Kaganski from comment #3) > Michael: it looks as if the problem here is a loop over all cells in a11y. I > believe that we had a similar issue somewhere, but can't find it immediately. There's tdf#153131 that is reported to happen with Windows Speech Recognition. (In reply to cyrussanii23 from comment #0) > I added SAL_ACCESSIBILITY_ENABLED=0 as an ENV variable but that did not fix > it. Interesting, I would have expected that to disable the Windows accessibility bridge and thus avoid the problem. Are you sure the environment variable was applied (might e.g. require a logout/login or restart)? > I ran Win11 Sandbox and installed LibreOffice and Cut-n-Paste worked so > something in my Win11 env is the issue. Do you also have Windows Speech Recognition active (like in tdf#153131) or any other way to further narrow down what tool/other software on your system might be causing this?
My mistake....I hadn't logged out/rebooted after setting the ENV variable. I have now re-added the variable and done a full reboot. I can now start Calc from the menu and Cut-N-Paste with no issues. I have always had Windows Speech Recognition OFF as well as Voice Access. So, as you suspected, the accessibility variable is the solution for me. Thanks for all the help and quick action on this!
(In reply to cyrussanii23 from comment #6) > My mistake....I hadn't logged out/rebooted after setting the ENV variable. > I have now re-added the variable and done a full reboot. > I can now start Calc from the menu and Cut-N-Paste with no issues. > > I have always had Windows Speech Recognition OFF as well as Voice Access. > > So, as you suspected, the accessibility variable is the solution for me. Thanks for the feedback. Closing as duplicate of tdf#165155, which is likely a duplicate of tdf#153131 itself. (But let's wait there for feedback of whether the fix for tdf#153131 actually fixes the problem for those affected by the issue.) *** This bug has been marked as a duplicate of bug 165155 ***
*** This bug has been marked as a duplicate of bug 153131 ***