Bug 168207 - "Search key not found" when searching by highlight color in Writer
Summary: "Search key not found" when searching by highlight color in Writer
Status: RESOLVED DUPLICATE of bug 161182
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
25.2.5.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Find-Search
  Show dependency treegraph
 
Reported: 2025-08-31 08:41 UTC by Ilya Basin
Modified: 2025-08-31 11:08 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ilya Basin 2025-08-31 08:41:17 UTC
Description:
After upgrade from 7.4.0.3 to 25.2.5.2 I noticed that Writer can't search by Highlighting color anymore. I used this feature with "Find all" and explicit white color to mark important parts of documents I needed to double check. 25.8.1.1 is also affected.

Steps to Reproduce:
highlight some text with e.g. yellow, open find and replace dialog, click "Format", switch to tab "Highlighting", click "Color", choose yellow color on the palette, "Ok", observe that "Yellow, not transparent" appeared below the "Find" input and click "Find all.

Actual Results:
the error "Search key not found" is shown below the search input

Expected Results:
all yellow-highlighted text gets a darker shade and blue border around it.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: TextDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: no
Comment 1 Dieter 2025-08-31 11:08:29 UTC
I confirm it with

Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 77b3fe6e8564ea579d8e9a5fc82c5eadf532072e
CPU threads: 12; OS: Windows 11 X86_64 (build 26100); UI render: Skia/Vulkan; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL threaded

But I think it is a duplicate of bug 1611182. Ilya, if you don't agree, please change status to NEW with a short reasoning.

*** This bug has been marked as a duplicate of bug 161182 ***