Bug 126765 - Divide give #NAME? on Windows 8.1
Summary: Divide give #NAME? on Windows 8.1
Status: RESOLVED WONTFIX
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.3.0.3 rc
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-08 11:01 UTC by Óvári
Modified: 2020-04-17 21:59 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Test file (12.87 KB, application/vnd.oasis.opendocument.spreadsheet)
2019-08-08 11:02 UTC, Óvári
Details
Screenshot with LibreOffice 6.3.0.4 (x64) (78.63 KB, image/png)
2019-08-08 12:00 UTC, Óvári
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Óvári 2019-08-08 11:01:01 UTC
Description:
Calc can't divide on a Windows 8.1 computer if a number is divided by a non-integer.

Works correctly with LibreOffice running on Linux Mint 19.2 Cinnamon 64-bit

Steps to Reproduce:
1. Open LibreOffice Calc on a Windows 8.1 with Bing 64-bit computer
2. In cell A1 type: 48.04166667
3. In cell B1 type: =A1/1.1

Actual Results:
Cell B1 shows: #NAME?

Expected Results:
Cell B1 should shows: 43.6742424272727


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 6.3.0.3 (x64)
Build ID: c75130c129d9c5e43b76e4f26881b3db8bdb5c91
CPU threads: 2; OS: Windows 6.3; UI render: default; VCL: win; 
Locale: en-AU (en_AU); UI-Language: en-GB
Calc: threaded

Windows 8.1 with Bing
64-bit operating system, x64-based processor
Comment 1 Óvári 2019-08-08 11:02:53 UTC
Created attachment 153223 [details]
Test file

Cell B1 incorrectly shows #NAME? on Windows 8.1
Cell B1 correctly shows the value on Linux Mint 19.2

Thank you
Comment 2 Mike Kaganski 2019-08-08 11:19:46 UTC
Cannot repro with Version: 6.3.0.4 (x64)
Build ID: 057fc023c990d676a43019934386b85b21a9ee99
CPU threads: 12; OS: Windows 10.0; UI render: GL; VCL: win; 
Locale: ru-RU (ru_RU); UI-Language: en-US
Calc: CL
Comment 3 Mike Kaganski 2019-08-08 11:21:09 UTC
And also *cannot* repro with the same but Calc: threaded
Comment 4 Óvári 2019-08-08 12:00:46 UTC
Created attachment 153225 [details]
Screenshot with LibreOffice 6.3.0.4 (x64)

Maybe there is more information in the screenshot that can help?

When LO was installed, only the English (GB) was selected. English (US) etc was unselected.

Hope this helps in reproducing this bug.

Thank you
Comment 5 Óvári 2019-08-08 12:04:30 UTC
(In reply to Óvári from comment #4)
When installing:
1. `Optional Components` --> `Dictionaries` --> all unselected except `English` and `Hungarian`
2. `Additional user interface languages` were all unselected except `English (United Kingdom)`

Thank you
Comment 6 Oliver Brinzing 2019-08-09 07:35:03 UTC
no repro with:

Version: 6.3.0.4 (x64)
Build ID: 057fc023c990d676a43019934386b85b21a9ee99
CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; 
Locale: de-DE (de_DE); UI-Language: en-US
Calc: 

xml representation of attached file is:

<table:table-row table:style-name="ro1">
 <table:table-cell office:value-type="float" office:value="48.0416666666667"
  calcext:value-type="float"> text:p>48.0416666666667</text:p>
 </table:table-cell>
 <table:table-cell table:formula="of:=[.A1]/1.1" office:value-type="string"
  office:string-value="" calcext:value-type="error">
  <text:p>#NAME?</text:p>
 </table:table-cell>
</table:table-row>

maybe a problem with "Decimal separator key" ?
-> Menu Tools/Options.../Language Settings/Languages/Decimal separator key
Comment 7 Mike Kaganski 2019-08-09 07:58:36 UTC
(In reply to Oliver Brinzing from comment #6)
> maybe a problem with "Decimal separator key" ?

... which shouldn't be a problem; en-AU and en-GB use decimal dot; and - no problem with ru-RU, which uses decimal comma.

> -> Menu Tools/Options.../Language Settings/Languages/Decimal separator key

... which is a different unrelated setting, telling what to do when a specific key is pressed on keyboard, not about which separator to use (see [1]).

[1] https://help.libreoffice.org/latest/en-US/text/shared/optionen/01140000.html
Comment 8 raal 2019-08-11 09:44:02 UTC
CTRL-SHIFT+F9 helps?
Comment 9 Oliver Brinzing 2019-08-11 12:31:10 UTC
the only way i found to reproduce a file like the attached one is 
(with: Locale: de-DE (de_DE)):

1. In cell A1 type: 48,04166667
2. In cell B1 type: =A1/1.1
3. B1 shows #NAME?, cause decimal separator should be ","
4. save spreadsheet

but reloading the file will correct the error.
Comment 10 Óvári 2019-08-12 02:28:41 UTC
(In reply to raal from comment #8)
> CTRL-SHIFT+F9 helps?

No
Comment 11 Óvári 2019-08-12 02:31:49 UTC
(In reply to Oliver Brinzing from comment #9)
> the only way i found to reproduce a file like the attached one is 
> (with: Locale: de-DE (de_DE)):
> 
> 1. In cell A1 type: 48,04166667
> 2. In cell B1 type: =A1/1.1
> 3. B1 shows #NAME?, cause decimal separator should be ","
> 4. save spreadsheet
> 
> but reloading the file will correct the error.

The decimal separator is in Australia is "." not ",".

Thank you for your suggestion. Tested your suggestion of saving, closing and re-opening the spreadsheet and this corrects the error; however, shouldn't this error not be present to begin with?
Comment 12 Óvári 2019-08-27 08:37:33 UTC
(In reply to Oliver Brinzing from comment #6)
> maybe a problem with "Decimal separator key" ?
> -> Menu Tools/Options.../Language Settings/Languages/Decimal separator key
No error here, as the decimal separator key is shown correctly
Comment 13 Mike Kaganski 2019-08-27 10:43:12 UTC
I see two problems here:

1. Some situation where decimal dot is not treated as such on a system where it seemingly should. The questions: What is your Windows decimal separator setting (although that likely should not affect this)? Why "User Profile Reset: No"? ;-)

2. Having such an error made by a user on a locale with decimal comma (like ru-RU), the legitimate error shown in the document disappears after save-and-reload (so the input with dot, which rightfully isn't recognized as a valid separator, is written into the file (where only dot is expected as separator), and then everything is fine) - but I'd expect that error stays error after reload.
Comment 14 Buovjaga 2020-04-17 17:04:30 UTC
(In reply to Mike Kaganski from comment #13)
> 1. Some situation where decimal dot is not treated as such on a system where
> it seemingly should. The questions: What is your Windows decimal separator
> setting (although that likely should not affect this)? Why "User Profile
> Reset: No"? ;-)

Óvári: can you reply to this?
Comment 15 Óvári 2020-04-17 21:59:02 UTC
(In reply to Buovjaga from comment #14)
> Óvári: can you reply to this?

No longer have Windows as we have fully transitioned to GNU/Linux. Thank you