Bug 160766 - Calc on LEAP 15.5 won't put data in cells
Summary: Calc on LEAP 15.5 won't put data in cells
Status: RESOLVED DUPLICATE of bug 160096
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2024-04-21 16:47 UTC by Ron Widell
Modified: 2024-04-22 18:48 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

multiple sheet Excel spreadsheet (417.05 KB, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet)
2024-04-21 16:57 UTC, Ron Widell

Note You need to log in before you can comment on or make changes to this bug.
Description Ron Widell 2024-04-21 16:47:48 UTC
I have a multiple sheet spreadsheet which I have been using for a number of years. I recently discovered that (at least) one of the sheets would no longer accept data input in some of the cells.

After assuming the data file was corrupt and trying it in Excel 2021 on Windows 10 with no issues, I rolled back to The issue went away.

I can submit the spreadsheet, but the instructions to recreate the issue will make little sense without it.

There are also formatting problems which were resolved by rolling back.

Steps to Reproduce:
1.Open "Apr" sheet
2.enter any data into cell C6:E6
3.tab or enter to advance to next cell
4.Notice that the cell vacated is now blank. Notice also that the floppy icon in the menu bar did not change state to reflect a change to the document.

Actual Results:
blank cells

Expected Results:
data retained in celld

Reproducible: Always

User Profile Reset: Yes

Additional Info:
acknowledge data entry & retain the data in the cells
Comment 1 Ron Widell 2024-04-21 16:57:29 UTC
Created attachment 193787 [details]
multiple sheet Excel spreadsheet

Data isn't retained in cells C6:E44, F6:H44, M6:O51, P6:R51 of (at least) the Apr sheet. the earlier shhets seem to work.

Also not that the dollar signs in rows 54-65 are aligned so far left that they are on the border of the left adjacent cell.
Comment 2 ady 2024-04-21 17:19:15 UTC
The "problem" is in Data Validity.

The reason is the (incorrect IMNSHO) patch (and users will keep rejecting it) in tdf#159595.

The patch in tdf#159595 now limits the available alternative behaviors of Data Validity (that have been present for decades).

There is a request in tdf#160096 (to at least revert it and) to use a different approach (for example, to modify the wording), instead of limiting the alternative behaviors.

This is probably another example/dupe of tdf#160096.
Comment 3 m_a_riosv 2024-04-21 23:02:02 UTC
Maybe better to mark as dup, to get it solved.
Comment 4 ady 2024-04-22 01:05:01 UTC

*** This bug has been marked as a duplicate of bug 160096 ***
Comment 5 Ron Widell 2024-04-22 16:53:12 UTC
I agree that the data entry problem described is a duplicate of tdf#160096 however, that doesn't cover the other (less critical) issue of incorrect formatting in rows 54-65.

Comment 6 ady 2024-04-22 18:48:46 UTC
(In reply to Ron Widell from comment #5)

> that doesn't cover the other (less critical) issue of incorrect
> formatting in rows 54-65.

That would be a different bug (if indeed there is a bug), and so we need a different separate independent report.

I would recommend preparing a simpler basic file, containing a cell with the same format. Additionally, a screenshot of that cell containing some numeric value that would show how it is expected to be displayed. If possible, a second screenshot of the same cell with the same content but on a version that shows the unexpected displayed result.

The reason to ask for screenshots in addition to a simple basic spreadsheet file is because with attachment 193787 [details] (which is too-complex for the newly-described behavior), I am not noticing the difference between versions. Having screenshots of what should be seen and what is actually seen would help other users to identify and replicate the problem.

With such (simple) file, please open a new report, focusing the initial description on that (other) issue.