Description: Main Issue: Unable to switch sheet or close application after applying data validation using cell range Note: * In data validity dialog, Choosing cell range and when trying to select source, it actually selects the cells instead of choosing those cells as sources for validation. Manual Entry for sources works. * Able to edit cell in current sheet after data validation setting and save document. But can not switch sheet or close document. Application could be closed only from external commands like pkill soffice.bin Steps to Reproduce: 1.Apply data validation using cell range 2. 3. Actual Results: 1. Can not switch active sheet 2. Can not close application by clicking close button 3. When type = and clicking next cell for setting formula, it change cell selection instead of adding cell reference in formula * No total UI freeze: can edit current sheet. Can Save document. Expected Results: 1. Ability to switch active sheet 2. Ability to close application by clicking close button 3. When typing = and clicking next cell for setting formula, it shall add cell reference in formula Reproducible: Always User Profile Reset: No Additional Info: I use PCLinuxOS on KDE Plasma 6. Libreoffice is clean installed using officially (PCLinuxOS) provided libreoffice manager Before Data validation settings, No issues. Work around: Since document save is working, I apply data validation using manual entry. Save document. Kill application using pkill soffice.bin. When I open document again, I observe no issue (as long as I do not change validation settings). Using the validation does not create issue.
I believe this is a duplicate of Bug 166527.
Can be a duplicate of tdf#137113?
Regarding Actual Results 3: When "Error Alert" > "Show error message when invalid values are entered" is turned off, this occurs in cells with the Validation. After it occurs, we cannot input anything into any cells within the same document. If this investigation result is correct and matches what was intended in Comment 0, it might be a duplicate of or related to Bug 168261. Regarding the other parts: Bug 166527 has the same issues as this one. Also, in the following nightly build that fixed Bug 166527 (26.2.0.0.alpha0+), everything could not be reproduced except Actual Results 3. Tested with: Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 9ee57c6ac279cf3ea25f1598de6deab6e2d6735a CPU threads: 8; OS: Windows 11 X86_64 (build 26100); UI render: Skia/Raster; VCL: win Locale: ja-JP (ja_JP); UI: ja-JP Calc: CL threaded Jumbo Version: 25.8.3.0.0+ (X86_64) / LibreOffice Community Build ID: 8b83439dc0cc270a1eb517d3efb652293f1fbce8 CPU threads: 8; OS: Windows 11 X86_64 (build 26100); UI render: Skia/Raster; VCL: win Locale: ja-JP (ja_JP); UI: ja-JP Calc: CL threaded Jumbo
I have the same issue in Version: 25.8.0.2 (X86_64) Build ID: 80a8bc2ef75d415a197e282da0ebf917315d5e24 CPU threads: 4; OS: Linux 6.8; UI render: default; VCL: kf5 (cairo+xcb) Locale: zh-TW (zh_TW.UTF-8); UI: zh-TW Calc: threaded After this issue, Calc couldn't be closed. Bibisect result: f7d807a21a9564dc2f99a29fdcb3e0c1cdd72964 is the first bad commit commit f7d807a21a9564dc2f99a29fdcb3e0c1cdd72964 Author: Jenkins Build User <tdf@maggie.tdf> Date: Wed Jan 29 10:32:26 2025 +0100 source 63b26e8e20f6a4eeb3117925b7a727f565e3a2dc source 63b26e8e20f6a4eeb3117925b7a727f565e3a2dc instdir/program/libsclo.so | Bin 26809816 -> 26820224 bytes instdir/program/setuprc | 2 +- instdir/program/versionrc | 2 +- 3 files changed, 2 insertions(+), 2 deletions(-) Source commit: commit 63b26e8e20f6a4eeb3117925b7a727f565e3a2dc Author: Pranam Lashkari <lpranam@collabora.com> Date: Fri Jan 24 18:06:18 2025 +0530 sc: convert data validity dialog async Change-Id: Ifef985c15a58c1c081f9a011e174e3b2547f3ea2 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/179402 Reviewed-by: Caolán McNamara <caolan.mcnamara@collabora.com> Tested-by: Caolán McNamara <caolan.mcnamara@collabora.com> Tested-by: Jenkins CollaboraOffice <jenkinscollaboraoffice@gmail.com> Reviewed-on: https://gerrit.libreoffice.org/c/core/+/180704 Tested-by: Jenkins But I saw another commit saying it fixes tdf#156263, which is "regression caused by 63b26e8e20f6a4eeb3117925b7a727f565e3a2dc" commit ef7151c271d14f623759f87d30e452f2e6d66664 Author: Pranam Lashkari <lpranam@collabora.com> Date: Wed Sep 17 21:26:17 2025 +0200 tdf#156263: fixes freeze after opening data validity dialog after making dialog async ScValidationRegisteredDlg was destroyed while dialog is still running causing undefined behaviour regression caused by 63b26e8e20f6a4eeb3117925b7a727f565e3a2dc Change-Id: Idef30f12b88c46cb30a01ffb12588bb11e279750 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/191105 Tested-by: Jenkins CollaboraOffice <jenkinscollaboraoffice@gmail.com> Reviewed-by: Caolán McNamara <caolan.mcnamara@collabora.com> Reviewed-on: https://gerrit.libreoffice.org/c/core/+/191116 Tested-by: Jenkins BTW, it's the same bibisect result in tdf#168261
Created attachment 202990 [details] Test file You can test with this attached file. 1. Open the file with Calc 2. Select the whole column C 3. Select "Data" - " Validity" - Allow: "Cell range" 4. Click the button after the Source: field 5. Try selecting Sheet 2 (but you can not select it now) 6. At this point, Calc couldn't be closed either. I had to kill its process instead.
Franklin, can you explain why you set New instead of duplicate? Did you test with master after the mentioned fixing commit?
(In reply to Timur from comment #6) > Franklin, can you explain why you set New instead of duplicate? > Did you test with master after the mentioned fixing commit? Um, sorry, I just saw it "UNCONFIRMED" and thought I could confirm this bug exists. I'm not sure if it is a duplicate of tdf#128261, though I know they should be related. Sorry if I shouldn't change it. I tested with the latest master of bibisect linux-64-25.8 repository. Didn't test with the latest master in libreoffice core repo though (as it would take hours to compile in my laptop).
(In reply to Franklin Weng from comment #7) > (In reply to Timur from comment #6) > > Franklin, can you explain why you set New instead of duplicate? > > Did you test with master after the mentioned fixing commit? > > Um, sorry, I just saw it "UNCONFIRMED" and thought I could confirm this bug > exists. I'm not sure if it is a duplicate of tdf#128261, though I know they > should be related. Sorry if I shouldn't change it. should be tdf#168261 > > I tested with the latest master of bibisect linux-64-25.8 repository. > Didn't test with the latest master in libreoffice core repo though (as it > would take hours to compile in my laptop).
It looks like a duplicated of bug 156263 *** This bug has been marked as a duplicate of bug 156263 ***
*** This bug has been marked as a duplicate of bug 166527 ***