Bug 439898 - Unable to configure layout switch to Cpas Lock and disable Caps Lock mode on Shift+Caps Lock
Summary: Unable to configure layout switch to Cpas Lock and disable Caps Lock mode on ...
Status: RESOLVED UPSTREAM
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_keyboard (other bugs)
Version First Reported In: 5.22.3
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-07-15 18:21 UTC by kostyarin
Modified: 2021-07-27 19:16 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kostyarin 2021-07-15 18:21:40 UTC
SUMMARY

Topic. No way. Urgent. Lots of pain with it.


STEPS TO REPRODUCE
1. If you are using only one keyboard language, add one anotehr

   OPTION ONE
    1. Configure keyboard layout switch to Caps Lock
    2. Shift + Caps Lock switches Caps Lock mode (but no one asked to do this)

   OPTION TWO
   1. (the smae)
   2. Also configure keyboard layout switch to Shift + Caps Lock
   3. Shift+Caps Lock switches keyboard, Caps Lcok works as regular Caps Lock

   OPTION THREE
   1. Disable Caps-Lock in configurations
   2. Try the OPTION ONE and OPTION TWO
   3. Still got Caps Lock mode


OBSERVED RESULT
- Caps-Lock/Shift + Caps Lock can't be disabled.

EXPECTED RESULT
1. Shift + Caps Lock doesn't work if it's not enabled explicitly.
2. Disable Caps-Lock disables Caps-Lock.
3. Ability to disable Shift+Caps Lock.
4. Etc, etc, etc.


SOFTWARE/OS VERSIONS
   Linux/KDE Plasma: 
   Operating System: Arch Linux
   KDE Plasma Version: 5.22.3
   KDE Frameworks Version: 5.84.0
   Qt Version: 5.15.2
   Kernel Version: 5.12.15-arch1-1 (64-bit)
   Graphics Platform: Wayland
   Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz
   Memory: 15.5 ГиБ of RAM
   Graphics Processor: Mesa Intel® HD Graphics 520

ADDITIONAL INFORMATION
   I'm switching keyboard layout very often. And use Shift for upper case. And got CAPS LOCK MODE instead of ПЕРЕКЛЮЧЕНИЕ НЕ ДРУГУЮ РАСКЛАДКУ. So, to switch keyboard sometimes I'm forced (by KDE) to switch + to type + to backspace + to "shift+caps lock" + caps lock. If in the first switch the "shift" is pressed. Pain. Pain. Useless system configurations, that doesn't do what they mean. Wired implicit configurations.
Comment 1 Andrey 2021-07-15 22:48:22 UTC
I think it's not Plasma specific, it's just default XKB configuration files presented in distro. See Advanced tab in KCM Keyboard Settings for more options.
Did you see other behavior in other DEs?

You can make your own Caps Lock option displayed in the KCM, by editing XKB files.
But that is out of scope here.
Comment 2 kostyarin 2021-07-16 02:34:03 UTC
> I think it's not Plasma specific,
> it's just default XKB configuration
> files presented in distro. See
> Advanced tab in KCM Keyboard Settings
> for more options.

> Did you see other behavior in other DEs?

> You can make your own Caps Lock option
> displayed in the KCM, by editing XKB files.

> But that is out of scope here.

It's completely Plasma bug. It doesn't called "Standard XKB configurations with funny pins". It's called keyboard configurations. Check it out https://imgur.com/xWIndhu


Being a user, I expect this selection to work as it's expected.

If it's called "Standard XKB configurations with funny pins" then no problems -- since no one know what it is and how it works. And a misbehavior is expected.

But when I switch pins this way (see image), there is only one way how it should work. And it can't be seen in other DE.

Jut to make it clear:

- Have you ever hear about UX/UI?
- What should got a user with such settings?
- Is misleading one of KDE/Plasma goals?

I think "It's standard XKB" is not the solution.


---

P.S.: Also, looks like, all other DE misbehavior can be a reason to KDE misbehavior. "I just don't want to even delve into it" will be more fair.
Comment 3 Andrey 2021-07-27 12:53:41 UTC
I'm sorry but Plasma has nothing to do with distro supplied XKB configuration, which is responsible for the behavior you described.
What I can suggest is to report this problem to upstream project:
https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues
and add the link here.
I'll help you there edit the configs to disable unneeded functionality for you.
Comment 4 kostyarin 2021-07-27 19:16:36 UTC
> I'm sorry but Plasma has nothing to do with distro supplied XKB configuration, > which is responsible for the behavior you described.
> What I can suggest is to report this problem to upstream project:
> https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues
> and add the link here.
> I'll help you there edit the configs to disable unneeded functionality for you.

Ok. I found similar bug https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues/73 And I will watch it. There is "disable caps lock" option that can help (and doesn't work too).

Thank you, sir.