I discovered this after an update to LibreOffice 25.2.0.3 was installed from Flatpak. I am not sure if the problem goes beyond the display of the active cell, i.e. calculation and functionality. I have verified that it is not formatting, and that there are no special setting on cells on the range of cells. The problem does not exist on earlier versions of LibreOffice Calc, and I encounter it only on version 25.2.0.3.
No issue with Version: 25.2.0.3 (X86_64) / LibreOffice Community Build ID: e1cf4a87eb02d755bce1a01209907ea5ddc8f069 CPU threads: 16; OS: Windows 11 X86_64 (10.0 build 26100); UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Please test in safe mode, Menu/Help/Restart in Safe Mode Please attach a sample file, reduce the size as much as possible without private information, and paste the information in Menu/Help/About LibreOffice, there is a copy icon.
I restarted in Safe Mode, and the result is the same. It is still a bug. I have tried numerous approaches to isolate the cause of the problem. 1) This problem does not exist, when I use an exact copy of the Calc file on a different computer, but with a different version of LibreOffice calc. I encountered this problem when my recent FLATPAK update ran this week. 2) The bug still occurs when I copy test data in a spreadsheet, with no forumlae, no references etc....just a speadsheet with simple data. I suspect that it is a memory overflow issue. This problem appears when the spreadsheet contents go beyond ~15,000 rows by 14 columns (colA-colN). You can test it for yourself, by doing the following. Copy the number "1", in 40,000 rows across 14 columns (A-N). Notice what happens to the blue border line around the cells are you pass rows ~20,000. The border of the active cell disappears. This problem exists in all file formats....XlXS, XLS, ODS,SYLK, etc.
Created attachment 199011 [details] screenshot of active-cell-border starts to disappear at row 18,578
Created attachment 199022 [details] Screenshot Version: 24.8.4.2 (X86_64) / LibreOffice Community Build ID: bb3cfa12c7b1bf994ecc5649a80400d06cd71002 CPU threads: 16; OS: Windows 11 X86_64 (10.0 build 26100); UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded
Created attachment 199023 [details] Screenshot 25.2 Please paste here the information on Menu/Help/About LibreOffice (There is an icon to copy)
*** Bug 165133 has been marked as a duplicate of this bug. ***
Reprduced Version: 25.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1acd37a671b9d3633a7d31a0b60478815fbc685f CPU threads: 4; OS: Linux 6.8; UI render: default; VCL: gtk3 Locale: ja-JP (ja_JP.UTF-8); UI: en-US Calc: threaded bisected with linux-64-25.2 commit 1acd37a671b9d3633a7d31a0b60478815fbc685f step 1.Calc open 2.End key + down arrow key.(A1048576) 3.Cell focus is displayed or not.
> step > 1.Calc open > 2.End key + down arrow key.(A1048576) > 3.Cell focus is displayed or not. I made a mistake with the key. Here are the correct steps. Step1. Open Calc. Step2. Ctrl + Down arrow key. (Step3.) Is Cell focus displayed? Hasn't it?
Created attachment 199092 [details] Screnshot 25.2.1 Version: 25.2.1.1 (X86_64) / LibreOffice Community Build ID: e538fb6403facdfd3db0250c3b3278236c675c2a CPU threads: 16; OS: Windows 11 X86_64 (10.0 build 26100); UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded
Created attachment 199098 [details] screen shots 25.2.1(Linux) reproduce
Created attachment 199099 [details] screen shots 25.8.a(Linux) not repro source eec87ad741c361315433f548faf3e676d1b52a8d fixed?
*** Bug 165246 has been marked as a duplicate of this bug. ***
Issue fixed by commit eec87ad741c361315433f548faf3e676d1b52a8d [log] author Armin Le Grand (Collabora) <Armin.Le.Grand@me.com> Tue Jan 28 21:02:25 2025 +0100 committer Armin Le Grand <Armin.Le.Grand@me.com> Wed Jan 29 11:35:15 2025 +0100 tree 285950bdf6bee27f15802e3a4ded4076ae4213d3 parent ec9dbbe288ccb759ed95533fb849dac8a65c4a6b [diff] tdf#164403 CairoSDPR: adapt hairline width Closing as duplicated of bug 164403 *** This bug has been marked as a duplicate of bug 164403 ***