Created attachment 61588 [details] RAR of the test files I used. Problem description: XLSX Window Freezing Bug. A Frozen row cannot be saved. When opened, it opens as Split with GUI problems. Removing the Split is the only way to correct the GUI. Steps to test: 1) I created new documents in the ODS, XLSX, and XLS formats. This was done by selecting File->Spreadsheet. Sample data was entered and the top row was frozen by selecting Window->Freeze. I saved copies of each file type with the top row frozen. 2) The ODS file opens correctly with the top row frozen. It can be closed, open, and still remains frozen. I then editted the file content, saved it, closed it, and opened again. The top row remains frozen and the last view state was saved (selected cell and rows in the view). 3) The XLS file opens correctly with the top row frozen. It can be closed, open, and still remains frozen. I then editted the file content, saved it, closed it, and opened again. The top row remains frozen and the last view state was saved (selected cell and rows in the view). 4) The XLSX file does NOT open correctly. The top row and header (containing letters) GUI is intermixed. Vertical scroll doesn't help in correcting it. The Frozen check box no longer exists in the Window menu, rather, the Split check box is selected. When unchecked, the GUI returned to a normal state after the vertical scroll make it to the top. 5) Resaving the XLSX file with the top row frozen again does not correct the problem. It repeats the problem. Steps to test: 1) Perform step 1 above (for XLSX) and then steps 4 and 5. Current behavior: XLSX files cannot retain a frozen row. XLS and ODS files can retain a frozen row. Expected behavior: Frozen rows to be saved and existent upon next open without any bugs. Platform (if different from the browser): Windows 7 Home Premium, 64-bit, Service Pack 1 LibreOffice Specs: LibreOffice 3.5.3.2 Build ID: 235ab8a-3802056-4a8fed3-2d66ea8-e241b80 This problem exited with my previous 3.5.2 version as well.
*** This bug has been marked as a duplicate of bug 40070 ***
Goodness. I am glad you found this original bug listing. However, it's boggles my mind that this bug has been known for over a year! Ouch!