[kde] [Bug 475655] New: KDE Connect SMS hotkey mapped itself after updating

bugzilla_noreply at kde.org bugzilla_noreply at kde.org
Sun Oct 15 11:00:42 BST 2023


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

            Bug ID: 475655
           Summary: KDE Connect SMS hotkey mapped itself after updating
    Classification: I don't know
           Product: kde
           Version: unspecified
          Platform: Debian stable
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: reg at loggedfixes.com
  Target Milestone: ---

Sorry, it took me some time to report this, so not a "fresh bug."

SUMMARY (not sure if useful)

Updated several times after a fresh install of Debian 12. Installed ~2 months
ago and updated several times in the first few weeks.
Aftert the updates my Num 6 stopped working. Either with NumLock ON or OFF.
Regardless of keyboard. With some help online, I discovered that a hotkey for
launching KDE Connect SMS was mapped on Num Right.
Removing the hotkey resolved the issue.
Resetting all hotkeys to Defaults, doesn't map the hotkey back to Num Right.

STEPS TO REPRODUCE

(After updating the hotkey appeared by itself.)

1. System Settings -> Shortcuts -> KDE Connect SMS
2. `Launch KDE Connect SMS` hotkey: `Num+Right` (which is the numpad's right
arrow, when NumLock is OFF)

OBSERVED RESULT

Numpad 6 (with NumLock ON) stops working.
Using the hotkey does nothing. Journalctl registers nothing (don't know where
else to look). `libinput` captures the key, though.

EXPECTED RESULT

1) This shouldn't be a hotkey for launching the SMS app?
2) Num Right shouldn't map to Num 6 as well. (Right?)
3) Using the hotkey should be doing something / an application should launch.

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

ADDITIONAL INFORMATION

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


More information about the Unassigned-bugs mailing list