Bug 87231 - Sheet indication is dropped when referencing a cell on an other sheet
Summary: Sheet indication is dropped when referencing a cell on an other sheet
Status: RESOLVED DUPLICATE of bug 79441
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.2.7.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium critical
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-11 10:27 UTC by Yanis Zavakos
Modified: 2014-12-11 10:31 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

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

Note You need to log in before you can comment on or make changes to this bug.
Description Yanis Zavakos 2014-12-11 10:27:10 UTC 
It happened twice, both in a spreadsheet (personal finance) created 1 year ago ("file1") and in a spreadsheet created using release 4.2.7.2 ("file2). 

In the case of file1, all cell references to cells in the previous sheet have been dropped but the values have (temporarily?) remained unchanged (e.g. on the sheet "December", cell reference "=November.H32" has changed to "=H32), the value however has remained unchanged. Fearing losing all file info, I re-referenced other sheet cells 2 days ago without any further drop of spreadsheet indication.  

In the case of file2, spreadsheet indication vanished but the values changed to the values of the referenced cells on the same sheet.

Since I am extremely busy, I downloaded and installed release 4.2.5.2 which I used without problems before updating to 4.2.7.2

Dear friends, thank you very much for your attention. I hope that this info will be helpful.


Hardware: HP ProBook 4530s, 8 GB RAM
Operating System: Windows 7 Home Premium 64-bit SP1
Comment 1 raal 2014-12-11 10:31:03 UTC 
Probably duplicate of bug 79441. See also bug 87010, bug 86916, bug 86125.

Please try https://bugs.freedesktop.org/show_bug.cgi?id=87010#c2  (or 4.3.5 rc)

Feel free to reopen if it does not solve the problem for you.

*** This bug has been marked as a duplicate of bug 79441 ***