[kde] [Bug 491486] New: KCalc behaves as if NumLock is off when launched from "Launch" button

[Neil Schelly]

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

            Bug ID: 491486
           Summary: KCalc behaves as if NumLock is off when launched from
                    "Launch" button
    Classification: I don't know
           Product: kde
           Version: unspecified
          Platform: Debian stable
                OS: Linux
            Status: REPORTED
          Severity: minor
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: neil at schelly.net
  Target Milestone: ---

***
If you're not sure this is actually a bug, instead post about it at
https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
I have a Microsoft Natural Ergonomic Keyboard 4000. It has buttons along the
top for shortcuts to various applications and functions. I use one of them as a
launcher for kcalc. When I assign a shortcut key to it, it is labelled "Launch
(1)" and it has a picture of a calculator on it.

When launching kcalc from one of the shortcut buttons, it will behave as if
NumLock is off until I either toggle it off then on or click out of the
application and back in. When launching kcalc from another shortcut, like
Ctrl-Alt-K for example, the number pad will work correctly right away.

If I launch kcalc from this button and press keys on the number pad, they will
behave as if NumLock is off. PgUp/PgDn in the number pad will highlight the
buttons in kcalc for C and AC in the application as if I were hitting the
normal PgUp/PgDn keys. The operand keys (/ * - +) all also highlight the
intended key in the application. Numbers will not type.

STEPS TO REPRODUCE
1. Assign a shortcut to launcing kcalc for the "Launch (1)" button on my
keyboard or any other shortcut button along the top of the keyboard.
2. Open kcalc with that shortcut key.

OBSERVED RESULT

1. Press numbers and operands in the number pad. Operands will press the
operand buttons in the kcalc window. Most numbers will be ignored. 9 will act
like PgUp and press the C button in the application (as if NumLock was off). 3
will act like PgDn and press the AC button in the application (as if NumLock
was off).
4. I can toggle NumLock off and on by pressing it twice, and then the number
pad will work as expected.
4 (alternate) I can also just click to another window and then back to kcalc,
and the number will work as expected.

EXPECTED RESULT

I expect kcalc to recognize the number pad presses as soon as it opens.

SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux 12
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.0-23-amd64 (64-bit)
Graphics Platform: offscreen
Processors: 16 × Intel® Core™ i9-9880H CPU @ 2.30GHz
Memory: 31.0 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 630

ADDITIONAL INFORMATION
* This behavior was new when I upgraded from Debian 11 Bullseye to Debian 12
Bookworm.
* I tried installing the Debian oldstable/11/Bullseye version of kcalc, and it
didn't make a difference. Both versions of kcalc exhibited the above behavior.
* I created shortcuts to kcalc with other built-in shortcut buttons, and I
still get the weird NumLock behavior.
* I created shortcuts to kcalc with "normal" keyboard keys, like Ctrl-Alt-K,
and it behaves as expected.
* I created shortcuts to other applications with the built-in shortcut buttons,
and the number pad works as expected right away in those programs.

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