Bug 127528 - Installing new version 6.3.1.2 stripped all headers from all spreadsheets.
Summary: Installing new version 6.3.1.2 stripped all headers from all spreadsheets.
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.3.1.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-12 19:57 UTC by n4ark
Modified: 2021-04-20 03:55 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Update screwed up all spreadsheets (219.02 KB, image/png)
2019-09-12 20:10 UTC, n4ark
Details
example of how your update trashed a complex spreadsheet (16.69 MB, application/vnd.ms-excel.sheet.macroEnabled.12)
2019-09-13 02:00 UTC, n4ark
Details
"freeze\unfreeze button" in menu. (299.54 KB, image/jpeg)
2020-09-19 21:26 UTC, Nowitsky Nikolay
Details

Note You need to log in before you can comment on or make changes to this bug.
Description n4ark 2019-09-12 19:57:19 UTC
Description:
See above.

Steps to Reproduce:
1.Open any spreadsheet
2.
3.

Actual Results:
Install the latest damn release.

Expected Results:
Headers SHOULD NOT BE REMOVED FROM SPREADSHEETS.


Reproducible: Always


User Profile Reset: No



Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: SpreadsheetDocument
[Information guessed from browser]
OS: Windows 10 PRO
OS is 64bit: YES
Comment 1 n4ark 2019-09-12 20:10:24 UTC
Created attachment 154143 [details]
Update screwed up all spreadsheets
Comment 2 m_a_riosv 2019-09-13 00:20:55 UTC
You don't need to shout (capitals).

Does it happen with all files?

Please test Menu/Help/Restart in Safe Mode.
Comment 3 n4ark 2019-09-13 01:57:09 UTC
What part of "screwed up all spreadsheets" leads you to believe there was only one affected

tried safe mode but no help

hope using all lower case text without punctuation makes it easier to read

look for another attachment
Comment 4 n4ark 2019-09-13 02:00:52 UTC
Created attachment 154145 [details]
example of how your update trashed a complex spreadsheet

play with the attachment watch it morf into nothing thanks so much
Comment 5 QA Administrators 2019-09-13 02:51:38 UTC Comment hidden (obsolete)
Comment 6 Buovjaga 2020-04-19 15:58:17 UTC
Do you mean this:
1. Open the example spreadsheet (which has 4 frozen rows and a frozen column)
2. Scroll downwards

Result: you jump to row 769 and are unable to get the first view back. Moving with arrow keys or page up moves in the cells, but the view is not updated.

Just trying to figure out what is the main issue and how to describe it more clearly.
Comment 7 Nowitsky Nikolay 2020-09-19 21:26:51 UTC
Created attachment 165693 [details]
"freeze\unfreeze button" in menu.
Comment 8 Nowitsky Nikolay 2020-09-19 21:27:26 UTC
Checked it on 6.4, all headers here, if you unfreeze rows and columns. See attached image, with headers clearly visible.
Comment 9 Buovjaga 2020-09-20 09:13:08 UTC
n4ark: please respond, we need your feedback
Comment 10 QA Administrators 2021-03-20 04:42:05 UTC Comment hidden (obsolete)
Comment 11 QA Administrators 2021-04-20 03:55:07 UTC
Dear n4ark,

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-FollowUp