| Summary: | EDITING: Calc crashes when using VLOOKUP function | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Alan Whiteley <alan> |
| Component: | Calc | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED NOTABUG | ||
| Severity: | normal | CC: | iplaw67, jmadero.dev, raal |
| Priority: | medium | ||
| Version: | 4.3.5.2 release | ||
| Hardware: | Other | ||
| OS: | macOS (All) | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Attachments: |
EXAMPLE: CSV File 1
EXAMPLE: CSV File 2 |
||
|
Description
Alan Whiteley
2014-12-30 15:20:37 UTC
Please provide a test document and clear reproducible steps. Marking as NEEDINFO. Once you provide clear reproducible steps (simple) and a simple test document, set to UNCONFIRMED. Thanks. Created attachment 111573 [details]
EXAMPLE: CSV File 1
Created attachment 111574 [details]
EXAMPLE: CSV File 2
Steps to reproduce error: 1) Open PP-OUT.csv 2) Open Postcode.csv 3) Switch to PP-OUT.csv 4) In cell E2 of PP-OUT.csv, type =VLOOKUP(D2, 5) Switch to Postcode.csv to select lookup array, and Calc crashes Have replicate the exact same error three times immediately before posting this update. This has worked with previous versions of Calc, as it does with MS-Excel, so would expect the above to work in recent versions of Calc. Sorry: PP-OUT.csv is EXAMPLE: CSV File 1 Postcode.csv is EXAMPLE: CSV File 2 In LO 4142 osx 10.10.1, I just get error 501 when I select an array from the other sheet, but no crash. Can not reproduce on Version: 4.5.0.0.alpha0+ Build ID: 5f2cfd1beed6466715b7a1ed6a22b93cc250c79b Locale: fr_ OSX 10.10.1 I can select a range of cells in second csv without a crash occurring. I can not confirm with Version: 4.4.0.0.beta2+ Build ID: e1de94244c1b0419c1c3415c02381e8b7a87abe0 TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:libreoffice-4-4, Time: 2014-12-14_11:45:23 I can not confirm with Version: 4.3.6.0.0+ Build ID: 1b9bcc2e7f31e880e71c8d2a2aaf1b2839d4d32a TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:libreoffice-4-3, Time: 2014-12-14_15:56:02 I get no crash on
Version: 4.3.5.2
Build ID: 3a87456aaa6a95c63eea1c1b3201acedf0751bd5
either, so either I'm not doing something to trigger the bug or else your instructions for reproducing are incomplete or your profile is corrupt.
Thanks for trying. The instructions to reproduce are complete. Not sure what the previous commenter means by "profile". I have tried reinstalling v4.3.5.2 and get the same error. I have tried some other scenarios, e.g.: 1. In cell E2 type =LOWER( and press left arrow to move to (and select) cell D2 2. Calc crashes So, the error is not specific to function VLOOKUP. Other non-function related scenarios work, e.g.: 1. In cell E2 type ABCa nd press left arrow to move to cell D2 2. Calc okay Could it be the en-GB language pack I also have installed? As functions are key to my use of Calc, I may have to look for alternatives now. Reverted to v4.2.8.2. All problems resolved. (In reply to Alan Whiteley from comment #10) > Thanks for trying. The instructions to reproduce are complete. Not sure > what the previous commenter means by "profile". > For the test, could you rename your LibreOffice directory profile (see https://wiki.documentfoundation.org/UserProfile) and give it a new try? Reinstalled v4.3.5.2 over v4.2.8.2 and problem now appears resolved. Did not need to rename LibreOffice directory profile. Closing bug. I take issue in saying that this was not a bug - that is to imply that I have been lying. The bug was real. Resolution by going back to an earlier release and then reinstalling the current release over it found a way round the bug, but did not *fix* the bug. The bug persists, you just don't want to expend effort to fix it. WONTFIX is a more accurate status for the bug. (In reply to Alan Whiteley from comment #15) > I take issue in saying that this was not a bug - that is to imply that I > have been lying. The bug was real. Resolution by going back to an earlier > release and then reinstalling the current release over it found a way round > the bug, but did not *fix* the bug. The bug persists, you just don't want > to expend effort to fix it. WONTFIX is a more accurate status for the bug. Feel free to change the status of the bug, bugtracker is open. But because the bug is gone I can not imagine how should someone solve it. regards P.S. I believe you are not liar |