[kde] [Bug 502248] New: Specific combination of keystrokes trigger function keys

Trekker4482 bugzilla_noreply at kde.org
Mon Mar 31 17:53:11 BST 2025


https://bugs.kde.org/show_bug.cgi?id=502248

            Bug ID: 502248
           Summary: Specific combination of keystrokes trigger function
                    keys
    Classification: I don't know
           Product: kde
           Version: unspecified
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: kdebugs.junction646 at simplelogin.com
  Target Milestone: ---

Created attachment 179888
  --> https://bugs.kde.org/attachment.cgi?id=179888&action=edit
Video showcasing the keystrokes and function key activation

When writing on the laptop's keyboard, specific combination of keys behave like
function keys. It also depends on writing speed.

STEPS TO REPRODUCE
1. Turn on the laptop
2. Write specific combination of character

OBSERVED RESULT
Specific character creates different function key effects:
| Keytrokes | Function key activated |
| tre       | F2                     |
| gfd       | F4                     |
| hjk       | F6                     |
| àù↵       | F5                     |
| altro␣    | F7                     |

EXPECTED RESULT
Writing the characters without activating function keys.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 41
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Kernel Version: 6.13.7-200.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics
Memory: 7.1 GiB of RAM
Graphics Processor: AMD Radeon Graphics

ADDITIONAL INFORMATION
The last one, the "altro " does not always trigger, only occasionally, it's
shown in the attached video (which is a bit slower than real time testing).
I'm using the British English system language, but with an Italian keyboard.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Unassigned-bugs mailing list