Bug 2215739 - Decimal separator on keypad doesn't respect regional formatting under Wayland
Summary: Decimal separator on keypad doesn't respect regional formatting under Wayland
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-desktop
Version: 39
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: KDE SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: RejectedBlocker
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-18 07:28 UTC by Mattia Verga
Modified: 2024-11-27 21:13 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-11-27 21:13:33 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 449706 0 NOR UNCONFIRMED Keypad decimal separator should respect regional formatting 2023-06-18 07:28:35 UTC

Description Mattia Verga 2023-06-18 07:28:04 UTC
When entering decimal numbers using keyboard keypad, the decimal separator key is always entered as '.' (dot) even when regional settings are set to use decimal separator to ',' (comma).

This happens on several languages like Italian, German, etc.

This only happens when using a Wayland desktop session. Using the same settings (plasma regional settings, keyboard map) running in a X11 desktop session works as expected.

I've tested the bad behavior on different packages like Libreoffice Calc (GTK), Calligra (QT) and even in the test input field under plasma system settings -> input devices -> keyboard.

I suppose the bug has been present since the switch from X11 to Wayland as I originally reported upstream more than one year ago: https://bugs.kde.org/show_bug.cgi?id=449706
Not sure I chose the right component, though.

See also LibreOffice discussion on bug report https://bugs.documentfoundation.org/show_bug.cgi?id=143540

Reproducible: Always

Steps to Reproduce:
1. Set regional settings o a language like Italian or German (using ',' as decimal separator)
2. Logout/login to apply regional settings. Use a Wayland desktop session.
3. open a spreadsheet app like LO Calc or Calligra and try to enter a decimal number using keypad
Actual Results:  
The number is entered as '12.34' which is recognized as text because of the '.'

Expected Results:  
The number is entered as '12,34' which is recognized as number because uses the right decimal separator

Comment 1 Fedora Blocker Bugs Application 2023-06-18 07:32:17 UTC
Proposed as a Blocker for 39-final by Fedora user mattia using the blocker tracking app because:

 Breaks expected functionality in several packages by entering numbers in the wrong format (spreadsheets recognize numbers as text instead of decimal numbers)

Comment 2 Fedora Release Engineering 2023-08-16 08:11:09 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.

Comment 3 Geraldo Simião 2023-08-27 03:37:59 UTC
Cannot reproduce this bug on Fedora-KDE-Live-x86_64-39-20230822.n.0.iso decimal separator working as expected.
System Locale: LANG=pt_BR.UTF-8
    VC Keymap: br
   X11 Layout: br

Comment 4 Mattia Verga 2023-08-27 07:44:46 UTC
These are the steps to reproduce the issue, tested with Fedora-KDE-Live-x86_64-39-20230826.n.0.iso

- start KDE Live system as normal
- in KDE "system settings | regional" set the system to use Italian
- logout
- on login screen set the keyboard layout to Italian and login using a Wayland session
- start Calc and type any float number in a cell (using the decimal separator from the keypad). Expected "12,34" (recognized as number), get "12.34" (recognized as text)
- logout
- on login screen set the keyboard layout to Italian and login using a X11 session
- start Calc and type any float number in a cell. Get "12,34" (recognized as number)

For "decimal separator on the keypad" I mean https://mattia.fedorapeople.org/keypad.jpg (I don't know if it's the right name).

Comment 5 Geoffrey Marr 2023-08-28 20:15:17 UTC
Discussed during the 2023-08-28 blocker review meeting: [0]

The decision to classify this bug as a "RejectedBlocker (Final)" was made as, while we agree this is an annoying bug that should be fixed, it doesn't really violate any release criterion, can be worked around by using the other key, and has already been the case for a while.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2023-08-28/f39-blocker-review.2023-08-28-16.07.txt

Comment 6 Aoife Moloney 2024-11-08 10:53:59 UTC
This message is a reminder that Fedora Linux 39 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '39'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 39 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 7 Aoife Moloney 2024-11-27 21:13:33 UTC
Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26.

Fedora Linux 39 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.