[kde] [Bug 486806] Switching keyboard layout set to Capslock puts cursor at the beginning of a row in text fields of some applications

[freeze_ball]

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

freeze_ball <freezeball at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDSINFO                   |REPORTED
         Resolution|WAITINGFORINFO              |---

--- Comment #4 from freeze_ball <freezeball at gmail.com> ---
(In reply to Nate Graham from comment #3)
> That's a good question. I'm afraid there isn't a trick to it, you just move
> aside config files until you find the one at fault. You could do it
> binary-tree style by moving aside half of them at a time per pass.

I narrowed it down and it only took an hour.
In ~/.config/kdeglobals was a line in a block

[Shortcuts]
Begin=

Looking through shortcut settings, "Begin" is assigned to "Ctrl+Home" by
default, which I had remapped as one of Spectacle's shortcuts back in Plasma 5
so it was empty since then. Removing the line and re-logging fixed that weird
behavior. What is strange is pressing Ctrl+Home didn't put cursor at the
beginning of the line in i.e. Telegram, but that is besides the point.

So exact steps to reproduce the bug are:

0. Have layout switch key as CapsLock.
1. Remove/unbind the shortcut for "System settings" -> "Input & Output" ->
"Keyboard" -> "Shortcuts" -> "Navigation" -> "Begin" so that there is a line
"Begin=" in kdeglobals config file.
2. Re-log.
3. Try to rename something in Dolphin while switching layout back and forth
every few symbols, your cursor will be put in the beginning of the text field
every time you press CapsLock.

While the original issue is resolved for me, this "Begin=" certainly looks like
an unintended behavior, and it might be worth looking into although it is very
minor.

===

Found an extra mini bug where my "Begin" was unbound (by clicking the checkbox
in System settings) then bound back again after re-logging (by clicking the
checkbox again), it turned out like this in kdeglobals:

[Shortcuts]
Begin=; Ctrl+Home

So the shortcut both had no keybind and default keybind. And the original bug
with CapsLock was triggering.

===

Thanks a lot for helping me, Nate! Big fan of your blog and your work.

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