Bug 77202 - Block position not found!
Summary: Block position not found!
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
4.2.3.3 release
Hardware: x86-64 (AMD64) Linux (All)
: medium critical
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-08 20:26 UTC by Bogumił
Modified: 2015-10-14 19:48 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
screenshot (67.43 KB, image/png)
2014-04-08 20:26 UTC, Bogumił
Details
example file (8.50 KB, application/vnd.ms-excel)
2014-04-11 16:30 UTC, Bogumił
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bogumił 2014-04-08 20:26:41 UTC
Created attachment 97095 [details]
screenshot

When I'm using:  ctrl+h and typing any word to finde, after presing find all button, calc crashes with this information: Block position not found!
Comment 1 sophie 2014-04-09 08:00:19 UTC
Hi, I do not reproduce with Version: 4.2.3.3
Build ID: 6c3586f855673fa6a1576797f575b31ac6fa0ba3 on Ubuntu 13.10. Is it with any document or a particular one? could you attach the document that crashes? Thanks - Sophie
Comment 2 Bogumił 2014-04-11 16:30:12 UTC
Created attachment 97227 [details]
example file
Comment 3 Bogumił 2014-04-11 16:44:32 UTC
Hi Sophie,

I've attache an example file.

Pleas try to use: ctrl+h and finde all words "cena" and change it to "Price"

Document crashes.

I hope you will finde solution shortly :-)



Best regard and thnaks for help
Bogumił
Comment 4 sophie 2014-04-14 12:49:11 UTC
Hi, thanks for the document, still I do not reproduce, no problem to find cena and replace it by price - What is your linux distro ? Sophie
Comment 5 Marina Latini (SUSE) 2014-07-28 12:17:17 UTC
Hi,
can't reproduce on Ubuntu 14.04 x86_64 with:

* Version: 4.2.3.3
* Build ID: 882f8a0a489bc99a9e60c7905a60226254cb6ff0

* Version: 4.2.6.2
* Build ID: 185f2ce4dcc34af9bd97dec29e6d42c39557298f

* Version: 4.3.0.3
* Build ID: 08ebe52789a201dd7d38ef653ef7a48925e7f9f7

* Version: 4.3.1.0.0+
* Build ID: 764fdb983d2fd0e24f56db987eba307ae5ae6eea
TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:libreoffice-4-3, Time: 2014-07-24_16:46:54

Can you test againg with a fresh user profile?
https://wiki.documentfoundation.org/UserProfile

Marina
Comment 6 QA Administrators 2015-09-04 02:55:31 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team

This NEEDINFO message was generated on: 2015-09-03
Comment 7 QA Administrators 2015-10-14 19:48:23 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID 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 FDO

Message generated on: 2015-10-14