Description: When opening a ODT file with Writer under KDE linux (KDE neon 24.04 noble) updated today 8-18-25) it takes 80 seconds or more to get a menu. Off to the left side is a huge list of checksums. (I will load a screenshot.) After selecting the file and hitting OPEN, it takes another 40 seconds or so for it to load. This happens every time. I first ran into it with a flatpak installation of LibreOffice. I uninstalled that and loaded a version with apt (actually synaptic.) It did not help. I get the identical behavior. LibreOffice is 27.2.7.2 (X86_64). My hardware is LENOVO_MT_21A4_BU_idea_FM_ThinkBook,64 bit, AMD Ryzen 7 5700U, version: 23.104.1, memory is 32GiB of SODIMM DDR4. Steps to Reproduce: 1. Select OPEN in menu, then wait a long time (80 seconds or so) 2. Select file in menu, to the right side of a long list of checksums 3. Wait another 40 seconds or so. Actual Results: The file opens. However, and seems to "save" normally, but if I choose "save as" it again takes a long time. Expected Results: A quick opening of the file. Reproducible: Always User Profile Reset: No Additional Info: I do not see how to attach a screenshot. But the checksum, which seems to be done hundreds or times, is "checksum":"b7f7f8d9109cf94001404befbc100de80",
Tom, can you write again your LibreOffice version number? 27.2 is not yet developed, also you mentioned 7.5 which is a very, very old version.
From the help menu "About LibreOffice", the LibreOffice version is 24.2.7.2 (X86_64) / LibreOffice Community. I initially guessed at the version in the dropdown menu above, and did not see the correct version listed. Sorry!
I now believe this is not a bug in LibreOffice. The same thing also happens when I use Abiword, except that the time delay is about half as long. It still shows the same multiple checksums when trying to save with Abiword, b7f7f8d9..... I have not tried with other editors which produce .odt files. I think this bug is something in KDE Neon or some other part of the operating system. I've used linux since the early days of Debian, but only as a user, so I cannot be much help in tracking down this problem. I'm hoping that the next upgrade will take care of this. My apologies to developers who have been working on this.
Let's close per the last comment.