Issue 128306 - Calc find crashes
Summary: Calc find crashes
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Calc
Classification: Application
Component: viewing (show other issues)
Version: 4.1.7
Hardware: PC Windows 10
: P5 (lowest) Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-25 18:14 UTC by mslenfe
Modified: 2020-03-05 19:33 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description mslenfe 2020-02-25 18:14:26 UTC 
look, someone keeps closing this issue.  Calc crashes when using find.  4.1.7 dowloaded to fix this issue on Windows 10 and the issue is still there.  It was actually fixed in 4.1.6.   IT IS AN OPENOFFICE CALC issue!  I have NO OTHER PROBLEMS with ANY OTHER SOFTWARE on this laptop.  Funny how MS office works just fine. 

Bug Bug Bug.  

Please exit denial and fix pleas.
Comment 1 Peter 2020-02-25 20:17:02 UTC 
I am sure this is an issue that has to be fixed by you on your PC.
We organize PC specific help on forum.Openoffice.Org or un a user mailing list.

I suggest you Google for Apache OpenOffice reset profile and try this.
If this does not help register on the forum and describe your issue there.

Does this help?
Comment 2 oooforum (fr) 2020-02-28 14:17:06 UTC 
Your bug report is being closed as NOT_AN_ISSUE due to a lack of information which is needed in order to accurately reproduce and confirm the problem. We need the following information:

a) Provide details of your operating system (which Windows edition used)

b) Provide a step-by-step procedure to reproduce (the simpler will be the better)

c) Provide any test case(s) which will help us confirm the problem (like a sample document)

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.