Description: I am unable to sort a spreadsheet when logged in to a Wayland session. Works just fine on an X11 session. Steps to Reproduce: 1.Click on the upper left corner of a spreadsheet to select all rows 2.Go to Data->Sort->Options to check box for "Range contains column labels" 3. Actual Results: Program freezes up and I have to either wait or force close (during the freeze one of my processors rapidly goes to 100%). Sometimes if I wait long enough it will un-freeze, but then if I go to Sort Criteria and attempt to choose my sort key, it freezes again. Expected Results: Program should allow me to check the "Range contains column labels" box, choose my sort key, and sort the table per my instructions. Reproducible: Always User Profile Reset: No Additional Info: On a hunch I logged out and started an X11 session, and the problem does not happen. Switched back to Wayland and it happened again exactly as described above. Version: 6.4.3.2 Build ID: 1:6.4.3-0ubuntu0.20.04.1 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded
Regarding the last two checkboxes in the bug report form, I had to log out of my X11 session and log back in to Wayland to try resetting my user profile and see if the problem persists. Didn't want to have to re-type my whole report, so I left those two boxes unchecked. Since then I got back into Wayland and tried resetting my user profile, but the problem is still there. I also tried checking if OpenGL was enabled, following the directions on the web site linked in the bug report form, but my menu items don't match the web site, and I wasn't able to find whether or not OpenGL is enabled on my setup. ** I also just tried selecting only the cells I want to sort, instead of starting by clicking the upper left corner box to select all cells, and I am able to sort normally without this problem. So I guess I found a workaround, but it still seems like a bug that should be fixed. With larger spreadsheets this could be a bit of a pain to manually select all the occupied cells, rather than clicking one button to select everything. Thank you for looking into this, and for all your work in providing a quality office suite!
Any change to provide an example file. The amount of data/type data might matter
Created attachment 161858 [details] Spreadsheet to test sorting bug Sure. It's happened on every spreadsheet I've tried to sort since I switched to Wayland (which is maybe 2 or 3). But here's one. I just tried to sort it and got the same error.
can you check your problem in LibreOffice from snap package? https://www.libreoffice.org/download/snap/
Sorting your spreadsheet worked fine for me under a Wayland session. Please also try with an appimage of a recent version https://libreoffice.soluzioniopen.com/ Arch Linux 64-bit Version: 7.1.0.0.alpha0+ Build ID: e67a755e6d4e3241360c75c3362f90a3af5999ac CPU threads: 8; OS: Linux 5.8; UI render: default; VCL: gtk3 Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 8 October 2020
Dear darkmaniels, 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
I'm sorry for sitting on this so long. I had developed a workaround of just selecting the range I needed manually and then sorting, which didn't pose the problem. I just tried it again (with the version of LibreOffice from Ubuntu's repository, rather than the snap or appimage version, and the problem is no longer there. So apparently whatever was causing it has been resolved already. Thanks for your time.