Bug 160879 - Find and replace only work in safe mode
Summary: Find and replace only work in safe mode
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.2.3.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: User-Profile-Upgrade
  Show dependency treegraph
 
Reported: 2024-05-01 02:10 UTC by Ray Shain
Modified: 2024-05-01 03:17 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Windows config from about (47.30 KB, image/jpeg)
2024-05-01 02:10 UTC, Ray Shain
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ray Shain 2024-05-01 02:10:59 UTC
Created attachment 193913 [details]
Windows config from about

This problem occurs in version 7.6.6.3, and in the prior version I was using, 7.2.3.2.  When in normal mode, neither clicking the find and replace menu item under edit nor the keyboard CTRL-H will bring up the find and replace dialog window.  When I reopen Writer in safe mode, all works as intended.  My machine info is attached as windows spec.jpg.  I have no user installed extensions in writer.  

I've restarted in safe mode, resetting my entire user profile to factory settings and archiving my old profile.  After testing find and replace successfully, I've restarted in normal mode, saving as appropriate, and the function again fails to appear when selected.

I first noticed this issue when I went from version 6 to version 7.  I was trying to wait for a fix in later versions, but the same thing happens after each update.
Comment 1 Ray Shain 2024-05-01 02:31:34 UTC
The bug originally appeared after an update.  I just completely deleted Libre Office from my machine, including Appdata entries but without editing the registry.  I then did a clean install, and find and replace works in normal mode.  This seems to indicate some issue with the automating scripts in the upgrade process of the install program.
Comment 2 Stéphane Guillou (stragu) 2024-05-01 02:55:13 UTC
Thanks for the report, Ray.

Let's mark as "works for me" as your issue is resolved after a full reinstall, and it will be difficult to investigate further without profiles to compare + knowledge of which LO version you were using before going from 6 to 7.

For good measure I tested:
1. create a new user profile with LO 6.4.8+ (linux-64-6.4 bibisect repo's master)
2. copy across that profile to an installation of LO 7.2.8+ (linux-64-7.2 bibisect repo's master)
3. Test Ctrl + H with Writer 7.2: it works.