Bug 93570

Summary: EDITING: Search Replace all crashes Writer immediately
Product: LibreOffice Reporter: Sebastian <semox78>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INSUFFICIENTDATA    
Severity: normal CC: semox78, serval2412
Priority: medium    
Version: 4.4.5.2 release   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
Crash report or crash signature: Regression By:

Description Sebastian 2015-08-21 08:54:59 UTC
In LO Writer Version: 4.4.5.2 Build-ID: 40m0(Build:2), as well as in new LO 5.x from LO's main Website I experience crashes when using "Search & Replace"-->"Replace all" function from Edit menu.

When searching for a String and replacing it one after another by clickinginginging, the function works and I receive no faults. If I click on replace'em all, then a Alert Notification pops up and shows a number, i.e. 17 replacements made. After this without any further user interaction, LO terminates and I have no chance to do anything.
Comment 1 Julien Nabet 2015-08-21 09:24:22 UTC
Do you reproduce this with a brand new file?
Eg: create one and type "test, test, test"
use "search and replace" to replace "test" by "test1"

Also for the test, could you rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile#GNU.2FLinux) and give a new try?
Comment 2 Xisco Faulí 2016-09-11 13:18:28 UTC Comment hidden (obsolete)
Comment 3 Xisco Faulí 2016-10-10 10:29:14 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-20161010