Description: I tried to search for any character that was a particular font in bold. When I pressed Replace All, a prompt appeared saying "to continue Undo must be disabled". I accepted, then progress wheel appeared for an indefinite time (I waited 15 minutes before aborting). Steps to Reproduce: 1. Open document 2. Open Find & Replace dialogue 3. Place cursor in Find field 4. Select a font in Format dialogue which appears many times in document 5. Place cursor in Replace field 6. In Format dialogue select same font previously selected from Font tab in step 4 and select a background color (yellow) from Highlight tab 7. Click Replace All Actual Results: 1. After 60,000 character replacements, prompt appears "To proceed with this action, you must first turn off the "undo" function. Do you want to turn off the "undo" function?" 2. Clicking No or Cancel resumes normal control of the application. Clicking Yes results in indefinite hanging. Expected Results: 1. Clicking Yes should allow the operation to complete. Reproducible: Always User Profile Reset: No Additional Info: In my document, after 60000 characters replacements, only 286 were remaining. I was able to do a second search/replace with no issue on jus the remaining selection. Clicking "Yes" to turning off the Undo feature seems to go down a code pathway that causes the hanging. Version: 6.4.1.2 (x64) Build ID: 4d224e95b98b138af42a64d84056446d09082932 CPU threads: 12; OS: Windows 10.0 Build 18362; UI render: GL; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: threaded
Created attachment 158827 [details] screenshot Sample input in search/replace dialogue
Interesting to note that if I do search and replace in chunks, i.e. without accepting to disbable the Undo feature, then I can still do a single click (ctrl+z) undo of a mass replacement. Is it then possible for the algorithm to do large search/replace operations in 60,000 character (or whatever defines the limit) chunks? This would allow the user to undo mass changes, which is desired, rather than leave them without Undo feature for such large changes.
I confirm it with Version: 7.0.0.0.alpha0+ (x64) Build ID: 5dcbd1bb557450a2d658a710c163b310c0cee157 CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win; Locale: de-DE (de_DE); UI-Language: en-GB Calc: CL
Dear kaanchan, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Created attachment 179141 [details] sample file Still present in Version: 7.3.2.2 (x64) / LibreOffice Community Build ID: 49f2b1bff42cfccbd8f788c8dc32c1c309559be0 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL Tested with attached file
*** Bug 155450 has been marked as a duplicate of this bug. ***
Reproducible in: Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded As well as a recent master build: Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: f4c24da1e7f11664e0d2f688d2531f068e4a3bc0 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Hangs with 100% use of a core. Same freeze in OOo 3.3, so issue is inherited. Changing severity to "major" as it's a complete freeze that requires force-quitting and might result in data loss.
Still present in Version: 25.2.4.3 (X86_64) / LibreOffice Community Build ID: 33e196637044ead23f5c3226cde09b47731f7e27 CPU threads: 12; OS: Windows 11 X86_64 (10.0 build 26100); UI render: Skia/Vulkan; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL threaded
*** Bug 165447 has been marked as a duplicate of this bug. ***
*** Bug 166278 has been marked as a duplicate of this bug. ***
Mateusz Wlazłowski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/17c9b49f3d215b58604a3d301b18ada322e3986f tdf#131431 Move next node if pCurrentCursor hasn't moved in replaceAll It will be available in 26.8.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Created attachment 205457 [details] .odt file created to test bug fix .odt file created to test bug fix
Tested bug fix and confirm that when using Find and Replace to find underlined characters and apply yellow highlighting I no longer get a message "To proceed with this action, you must first turn off the "undo" function. Do you want to turn off the "undo" function?". Instead, the underlined characters are highlighted in yellow, as desired. Steps to reproduce 1. Open test file "2026-02-10 Test file animals.odt" 2. Edit > Find and Replace 3. Click on "Find:" field > Attributes > Other options > Underline > OK 4. Click on "Replace:" field > Format > Highlighting > Color > Yellow > OK 5. Replace All When using Find and Replace to find bold or italicized characters and apply yellow highlighting I no longer get a message "To proceed with this action, you must first turn off the "undo" function. Do you want to turn off the "undo" function?". Instead, the yellow highlighting is applied. But the characters are no longer bold or italicized; instead they are regular. Steps to reproduce 1. Open test file "2026-02-10 Test file animals.odt" 2. Edit > Find and Replace 3. Click on "Find:" field > No Format (if necessary) 3. Click on "Find:" field > Format > Font > look under "Western" > Style > either Bold or Italic > OK 4. Click on "Replace:" field > Format > Highlighting > Color > Yellow > OK 5. Replace All The expected result is that bold and italicized fonts would retain their respective font styles after highlighting.
(In reply to christopherlum334 from comment #14) > When using Find and Replace to find bold or italicized characters and apply > yellow highlighting I no longer get a message "To proceed with this action, > you must first turn off the "undo" function. Do you want to turn off the > "undo" function?". > Instead, the yellow highlighting is applied. > But the characters are no longer bold or italicized; instead they are > regular. > > The expected result is that bold and italicized fonts would retain their > respective font styles after highlighting. Thanks for testing I checked 26.2.0.3 and it had the same issue you're describing -- not related to the patch Version: 26.2.0.3 (X86_64) Build ID: afbbd0df0edb6d40b450b0337ac646b0913a760c CPU threads: 8; OS: Linux 6.17; UI render: default; VCL: gtk3 Locale: en-GB (en_US.UTF-8); UI: en-US Flatpak Calc: threaded Could you make a new bug report and CC me? (unless this was already reported) Thanks
I have submitted Bug 170738 and cc: mateusz.csi@gmail.com